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

# Audio Message Block

The **Audio Message Block** inside **Send Message** allows you to send voice notes or audio files directly to users during a chatbot conversation. Audio messages help create a more personal interaction and can build trust with users.

#### How to Use the Audio Message Block

1. Open your **Chat Flow** in the bot builder.
2. Click **Add Node**.
3. Select **Send Message → Audio Message**.

#### Add Audio

You can add audio in two ways:

* **Upload a pre-recorded audio file** from your system, or
* Paste the **audio URL**.

After selecting the file, click **Start Upload**.

4. Click **Save Message**.

Once the flow is triggered, the audio message will be automatically sent to the user in the chat. This block is useful for sending **voice instructions, greetings, or personalized voice responses**.

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


---

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