> For the complete documentation index, see [llms.txt](https://documentation.taskmaverick.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.taskmaverick.com/missions/what-are-missions/ticket.md).

# Ticket

A Ticket is an automatic alert that appears when something needs management attention. Tickets are not created manually — they're *triggered by conditions in other Missions*.

**Examples:** "COVID-19 Alert", "Maintenance Alert", "Physical Injury Alert", "Low Inventory Alert"

## What triggers a Ticket?

<table data-view="cards" data-full-width="false"><thead><tr><th>Trigger</th><th>What happens</th></tr></thead><tbody><tr><td><strong>Specific answer</strong></td><td>Employee selects a flagged response in a Survey, Checklist, Test, or Audit</td></tr><tr><td><strong>Mission overdue</strong></td><td>A Mission stays open or unclaimed too long</td></tr><tr><td><strong>Low rating</strong></td><td>A completed Mission receives a poor quality rating</td></tr><tr><td><strong>Low test score</strong></td><td>A Test or Audit score falls below a threshold</td></tr></tbody></table>

## How Tickets work

1. An admin attaches a Ticket to a condition (e.g. "if employee answers 'Yes' to 'Were you injured?'")
2. When the condition is met, the Ticket appears on the [**Ticket Board**](/mobile-app/your-mobile-boards.md#ticket-board)
3. A manager claims the Ticket, investigates, and closes it

**Example:** An employee completes an inventory Checklist and reports only 4 bottles of wine left. A Ticket is triggered to the manager's board: "Low Wine Stock — order more wine."

## How to set up a Ticket

Go to **Missions → As Tickets→ Create Ticket**

{% stepper %}
{% step %}

#### Step 1 - Mission Attributes

| Field             | Required |
| ----------------- | -------- |
| Title             | Yes      |
| Categories / Tags | Yes      |
| Alert             | No       |
| {% endstep %}     |          |

{% step %}

#### Step 2 — Content Builder (optional)

You can optionally add a [**Survey** ](/missions/what-are-missions/survey.md)to a Ticket. When the manager closes the Ticket, they answer Survey questions first — useful for documenting how the issue was resolved.
{% endstep %}

{% step %}

#### Step 3 - Mission Settings

See [Mission Settings](/missions/how-to-guides/configure-mission-settings.md#ticket-specific) for all options.
{% endstep %}
{% endstepper %}

{% embed url="<https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLLw6mmkCzf1jpC9LdKjS%2Fuploads%2FPEFR3CODCDXa9tq1PKRa%2FCreate%20a%20ticket%20edited%20Composition.gif?alt=media&token=f84a351e-5f90-4bf4-ba0f-c67135a1993c>" %}

## Good to know

* Tickets **cannot** be created on mobile or scheduled - they only appear when conditions are met
* A Ticket **can trigger another Ticket** (but never itself)
* Tickets with Surveys can generate further Tickets from Survey responses - be careful not to create circular flows
* Every Ticket needs a [**Destination Board**](/missions/how-to-guides/configure-mission-settings.md#ticket-specific) specified in its settings. Without one, it won't appear anywhere


---

# 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://documentation.taskmaverick.com/missions/what-are-missions/ticket.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.