# Cards

The area of **Sales** Hablla's Sales area is where you manage your commercial, support, or project processes in a visual and intuitive way. Management is done through **Boards** in the Kanban style, where each **Card** represents a deal, a sales opportunity, a support ticket or an activity in progress.

This tool allows clear tracking of your pipeline, centralizing financial information, contacts, products and related activities in a single place.

***

### Creating a New Board (Pipeline)

It all starts with creating a **Board**, which represents a complete process. You can have separate boards for different teams or objectives.

When creating a new board, you define:

* **Board name:** The title that identifies the process (e.g.: "Direct Sales Pipeline").
* **Board type:** The purpose of your pipeline.
* **Reasons for Loss/Win:** Enable it so your team can record why a deal was won or lost, generating valuable data for analysis.
* **Additional Settings:** Define the responsible department, default custom fields and other permissions.

{% hint style="info" %}
The choice of **board type** (Opportunity, Ticket or Activity) is important, as it defines the default fields and behaviors of your pipeline, such as the inclusion of financial values.
{% endhint %}

***

### Viewing your Deals

Hablla offers three main ways to view and analyze the cards on your board, allowing you to choose the one that best fits your workflow.

#### Board View (Kanban)

This is the main and most used view. It displays your **Stages (columns)** and the **Cards** within each, providing a clear view of your process flow. You can easily drag and drop cards from one column to another to update their status.

#### List View

For a more straightforward, tabular analysis, the list view displays all cards in rows, with columns for **Status, Name, Labels, Owner,** and dates. It is useful for sorting, ordering and getting an overview of a large volume of deals.

#### Board Dashboard

For analysis and insights, the Dashboard compiles your board's data into charts and indicators. Track important metrics such as:

* **Quantity and Values:** See the total number of cards and the financial value in each status (New, In progress, Won, Lost).
* **Conversion Charts:** Analyze the count of cards by campaign, source and status.
* **Reports:** Access summaries by users and reasons for win/loss.

***

### Adding and Managing Cards

#### Adding a New Card (Deal)

To create a new opportunity, click on **"+ Add"**. A form will appear for you to fill in the initial information:

* **Card title:** The name of the deal. **(Required)**
* **Forecast date:** The estimated date for closing.
* **Owner:** The person responsible for the opportunity.
* **Board and List:** Where the card will be created.
* **Custom fields and Description.**

#### Fields of a Deal (Card)

A card stores all the information about a negotiation. The fields include **Main Information** (title, owner, people and organizations linked), **Financial Values** (total value, recurring, discounts), **Important Dates** (forecast, closing), **Status** (in service, won, lost), **Marketing** (campaign, source), **Products** and **Checklist**.

***

### Filtering, Importing and Exporting

#### Filtering your Deals

Use the **Custom Filters** to segment your view and find exactly what you need. Available filters include Name, Source, Status, Campaign, Organization, Person, Product, Labels and Department.

#### Importing and Exporting Data

You can add multiple cards at once via spreadsheet import or export your board's data for external analysis in CSV, JSON or XLSX formats.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.hablla.com/hablla-docs-en/data/cards.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.