> For the complete documentation index, see [llms.txt](https://docs.bizmagnets.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bizmagnets.ai/bot-flows/ticketing/tickets.md).

# Tickets

It allows businesses to manage customer issues, service requests, or inquiries efficiently by using a structured messaging format that integrates with ticketing systems.

<figure><img src="/files/3rFVjWVb5UVjnqvBR6h5" alt=""><figcaption></figcaption></figure>

## Steps to Prepare a Ticket&#x20;

1. In the bot flow builder, select the Ticket Media from the available actions.

<figure><img src="/files/WwLxo9mSp5YibODexJZW" alt=""><figcaption></figcaption></figure>

2. Enter the body the message.

<figure><img src="/files/H8ywdVIz2c12l4hpMlOD" alt=""><figcaption></figcaption></figure>

3. Enter the button name which proceeds with ticket creation.

<figure><img src="/files/7ZuwVrPxabpnsA0eHINw" alt=""><figcaption></figcaption></figure>

4. Enter the Screen name which is a internal name for this specific card or screen within your flow.&#x20;

<figure><img src="/files/3rYdtwuU8tnnZxo4Li3S" alt=""><figcaption></figcaption></figure>

5. Enable Ticket Types switch to the ON position if you want to use this feature.
6. For the validation settings, you can set the attempt limit to 1. The Validation Error Message is optional. Specify the Action on Invalid Response, and enable the Additional Validation Settings.

<figure><img src="/files/cjT0gczQ2xWPctqsouNd" alt=""><figcaption></figcaption></figure>

7. Click the **Save** to create the ticket card.

By following these steps you can prepare the Ticket Flow Card, enabling your bot to initiate the ticket creation process for users interacting with it. Remember to test your flow thoroughly to ensure it functions as expected.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.bizmagnets.ai/bot-flows/ticketing/tickets.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.