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

# Text Message Block

The **Text Message Block** is the most commonly used block inside **Send Message**. It allows you to automatically send plain text replies to users when a trigger is activated.

This block is commonly used for greetings, confirmations, follow-ups, or instructions and forms the foundation of most chatbot conversations.

#### How to Use the Text Message Block

1. Open your **Chat Flow** in the bot builder.
2. Set a **Trigger or Keyword**.
3. Add a **Send Message** block.
4. Select **Text Message**.
5. Enter the message you want to send.
6. You can personalize the message using **variables** such as **Name, Phone Number, or Custom Fields**.
7. Click **Save**.

Once the trigger keyword is activated, the text message will be automatically sent to the user, and you can continue building the rest of your chatbot flow.

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


---

# 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/text-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.