> 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/message-blocks/contact-message-block.md).

# Contact Message Block

The **Contact Message Block** inside **Send Message** allows you to share contact details directly in the chat. This helps users save your contact information quickly with a single tap.

#### How to Use the Contact Message Block

1. Open your **Chat Flow** in the bot builder.
2. Add a **Trigger** or keyword.
3. Click **Add Node**.
4. Select **Send Message → Contact Message**.

#### Add Contact Details

5. Enter the **First Name**, **Middle Name**, and **Last Name**.
6. Add the **Formatted Name** (the name under which the contact will be saved).

#### Optional Details

You can also add additional information such as:

* **Prefix or Suffix**
* **Birthday**
* **Business Name**
* **Company and Department**
* **Phone Number** and contact type
* **Address**
* **Website URL**
* **Email Address**

7. Click **Save Message**.

Once the flow is triggered, the contact card will be sent to the user, allowing them to easily save the contact in their phone.

{% embed url="<https://youtu.be/u-GFVkC6A4E>" %}


---

# 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/message-blocks/contact-message-block.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.