> 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/bot-builder/whatsapp-chatbot/create-whatsapp-bot-to-collect-user-data-in-crm.md).

# Create WhatsApp Bot to Collect User Data in CRM

You can build a WhatsApp bot to collect user details and store them in the CRM.

#### Steps to Create Bot

1. Go to **CRM → Super Fields** and create fields like **City, Customer Category, Product Category, GST Number**.
2. Go to **Chatbot → Create Bot Flow** and give a name.
3. Add a **Trigger (Keyword on WhatsApp)** and select channel.

#### Collect User Data

4. Send a **welcome message** with user name.
5. Ask for **City** and save it to the **City field**.
6. Ask **Customer Type (Retailer / Wholesaler)** using buttons.

#### Conditional Flow

7. If **Retailer** → Ask for **Product Category** and save it.
8. If **Wholesaler** → Ask for **GST Number** and save it.

#### Assign to Team

9. Use **Assign to Agent** to route chats to specific team members.

#### Final Step

10. **Save and Enable** the bot flow.

Now, all user responses will be **automatically stored in CRM fields** and assigned to the right team.

{% embed url="<https://youtu.be/pRkVvWfx5Fs>" %}


---

# 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/bot-builder/whatsapp-chatbot/create-whatsapp-bot-to-collect-user-data-in-crm.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.