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

# Image Message Block

The **Image Message Block** inside **Send Message** allows you to send an image to users along with an optional caption. Using images in chatbot messages helps increase engagement and makes your communication more visually appealing.

#### How to Use the Image Message Block

1. Open your **Chat Flow** in the bot builder.
2. Add a **Send Message** block.
3. Select **Image Message**.

#### Add the Image

You can send images in two ways:

**Static Image**

* Upload the image directly from your system, or
* Paste the **image URL**.

**Dynamic Image**

* Select a previously created **Image Experience**.
* Map the required variables if applicable.

#### Add Caption (Optional)

You can include a caption along with the image to provide additional information or context.

Example:\
*“New collection has dropped. Check it out!”*

4. Click **Save Message**.

Once the trigger is activated in the flow, the image message will automatically be sent to the user.

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


---

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