> 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/dynamic-experiences/dynamic-experience-image/create-dynamic-tickets-and-send-it-to-user-via-whatsapp-bot.md).

# Create Dynamic Tickets And Send It To User Via WhatsApp Bot

The video demonstrates how to generate dynamic tickets and send them to users via a WhatsApp bot.

The process involves:

* Creating a new experience in Dynamic Image.
* Adding personalization variables.
* Designing the ticket layout with QR codes, text blocks, and images.

In the Tickets app:

* Create a new object and link it to the bot flow.
* Set up an automation app for authentication with the Tickets app and enter the event ID.
* Map variables to populate the ticket with user information and ticket details.
* Add a message block to the bot flow to send the dynamic ticket as an image message via WhatsApp.

Finally, save, enable, and test the workflow by triggering it with a keyboard input.

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


---

# 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/dynamic-experiences/dynamic-experience-image/create-dynamic-tickets-and-send-it-to-user-via-whatsapp-bot.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.