> For the complete documentation index, see [llms.txt](https://helpdocumentation.gitbook.io/user-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdocumentation.gitbook.io/user-documentation/crm-v2/boards/create-and-manage-cards.md).

# Create and Manage Cards

A **Card** represents a single lead, task, or deal inside your CRM board. It moves across different stages like **New → Scheduled Visit → Visit Done → Won**.

#### Step 1: Create a Card Layout

1. After creating stages, click **Go to Card**.
2. Remove the sample text.
3. Add required **Super Fields** (lead details), such as:
   * First Name
   * Last Name
   * WhatsApp Number
   * Budget
   * Property Type
4. Use the **+ icon → Text** to add fields.
5. Use **+ icon → Buttons** to add actions like:
   * **Open Chat**
   * **Move Chat**

You can customize button size, color, and card design.

#### Step 2: Add Filters (Optional)

* Go to **Filters**
* Add conditions for qualified leads (if required)
* Click **Create Board**

#### Step 3: Add Contact to Board

1. Go to **CRM → Contacts**
2. Open a contact and update the required super fields
3. Save changes
4. Open the board to view the contact as a card

### Step 4: Update Lead Details

* Click on the variable (Super Field) inside the card
* Enter values (e.g., Budget: 50 Lakh)
* Save and refresh to see updated data

#### Step 5: Move Leads Between Stages

You can:

* **Drag & drop** the card to the next stage
* Or use the **Move Chat** button to select the desired column

You can also click **Open Chat** to directly start conversation with the lead.

That’s how you create, customize, and manage cards inside a CRM board to track leads efficiently.

{% embed url="<https://www.youtube.com/watch?v=nD-CQBumhtA>" %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://helpdocumentation.gitbook.io/user-documentation/crm-v2/boards/create-and-manage-cards.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.