> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ankra.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Set up the ticket desk and work tickets with the Ankra agent

> Check that the Ankra agent can take tickets, choose plan review and where ticket conversations happen, then file a ticket and approve the agent's plan.

The ticket desk decides how Ankra AI works tickets with your team: whether the Ankra agent can take them, whether its plans need an independent review, which health-check findings become tickets, and where each ticket's conversation happens. In about fifteen minutes you have the desk set up, a ticket you filed worked by the Ankra agent, and its plan approved by you.

How tickets move and what each status means is in [AI Board](https://docs.ankra.ai/platform/ai-board.md).

## Before you start

* **Tickets turned on for your organisation.** **Ankra AI → Work** is in the menu. If the Overview reads **Tickets are not turned on**, [contact support](https://docs.ankra.ai/platform/support.md).
* **An organisation administrator** to change the ticket desk. Everyone else can read it: the desk says **Organisation administrators can change the ticket desk. You can inspect its current settings.**
* **AI execution access** to file a ticket. Without it, **New ticket** reads **Your role can read tickets. AI execution access is required to create one.** See [Roles and access](https://docs.ankra.ai/guides/roles-and-access.md).
* **A Slack or Microsoft Teams connection**, if ticket conversations are to happen there. See [AI Connections](https://docs.ankra.ai/platform/ai-connections.md).
* **The Ankra CLI 0.77.0 or later**, for the steps the portal does not offer.

## 1. Open the ticket desk

Open **Ankra AI → Settings** and press **Configure work routing**, or press **Ticket desk** on **Ankra AI → Work** (`/next/ai/tickets/desk`).

**You should see** **Ticket desk**, with the tabs **Ankra agent** and **Communication**.

## 2. Check that the Ankra agent can take tickets

On the **Ankra agent** tab, under **One Ankra agent**, read the status beside **Ankra agent**:

* **Available for automatic staffing** - at least one agent may work tickets. Go on to step 3.
* **No eligible agent reported** - no agent can take tickets, so every automatic ticket goes to a person. **Ask Ankra to check ticket staffing** asks Ankra AI what to change.

The portal cannot change which agents work tickets, or the identity they act as. When no agent is eligible, give the board an identity and make an agent a board worker:

```bash theme={null}
ankra ai board-identity status
ankra ai board-identity provision --role operator
ankra ai tasks list
```

Then, from an MCP client connected to Ankra, ask it to make one of the agents in that list a board worker with `designate_board_worker`, and check with `list_agent_tasks` that its `can_work_board` is true. See [Agents that work tickets](https://docs.ankra.ai/platform/ai-agents.md#agents-that-work-tickets).

**You should see** **Available for automatic staffing** when you reload the ticket desk.

## 3. Choose whether plans need an independent review

With **Require an independent plan review** ticked and a working reviewer agent (`ankra ai tasks templates hire reviewer`), every plan is reviewed before a person is asked to approve it. With no reviewer set, the tick does nothing. The review pass is separate from the work pass, and an agent cannot approve its own work. Production changes still need explicit execution approval, whichever you choose.

## 4. Choose which findings become tickets

Under **Automatic insight tickets**, tick the severities to file under **File insights at these severities**: **Critical**, **Warning** and **Info**. Insights come from the health check Ankra AI runs on its own, which is switched on with **Check cluster health on its own** under [Finding problems on its own](https://docs.ankra.ai/platform/ai-autonomy.md#finding-problems-on-its-own).

## 5. Choose where ticket conversations happen

**1. Pick a destination**

Open the **Communication** tab. Choose a **Slack destination**, and under **Microsoft Teams** a **Microsoft Teams destination**, or both. **Enter a destination ID** takes a channel or conversation ID when the list cannot be read.

**2. Choose which tickets reach it**

Under **Which tickets reach these destinations?**, choose **Every automatic ticket**, **Tickets matching these filters** or **Channel mirroring off**. With filters, set the **Minimum priority**, tick the **Ticket sources**, and list **Environment types** (leave it empty for every type).

**3. Choose what is posted in the thread**

Under **Updates in the ticket thread**, choose **All events, including comments**, **Decisions, status, ownership and escalation** or **Opening message only**.

**4. Preview it**

**Conversation preview** shows where a ticket would go, **Using your unsaved changes**. **Try another ticket** lets you change the preview's staffing, environment type, priority and source. The preview sends no message.

**5. Save**

Press **Save changes**.

**You should see** **Ticket desk settings saved.**

These rules apply to both destinations. Manual tickets are never mirrored. Threads that already exist keep their destination; new threads use the saved settings. Your own notifications are set separately, under **Your account → Notifications**.

When your organisation has [projects](https://docs.ankra.ai/concepts/projects.md), **Project channels** on the same tab gives a project its own Slack or Teams channel. **Add a project channel**, choose the **Project**, and pick its **Slack channel** or **Microsoft Teams channel**.

## 6. File a ticket

> [tab] Portal
>
> 1. On **Ankra AI → Work**, press **New ticket**.
> 2. Enter a title where the form reads **Ticket title**, and a **Description**: what is happening, what should happen, and how you will know it is done.
> 3. Set the properties: **Priority** (**Medium** unless you change it), **Kind** (**Request** unless you change it), and **Environment** for the cluster it is about.
> 4. Leave **Work mode** on **Ankra agent**. The form reads **Ankra picks this up when an agent is free. Production changes still need approval.** Choose **My team** instead for work a person does: it stays with your team, with no automatic staffing, mirroring or escalation.
> 5. Press **Create ticket**.

> [tab] CLI
>
> ```bash theme={null}
> ankra tickets create --title "Ingress certificate expires Friday" --kind incident --cluster my-cluster
> ```
>
> `--staffing manual` keeps it with your team.

> [tab] MCP
>
> Ask your MCP client to file it with `file_ticket`. See [Work the AI board with your own agent](https://docs.ankra.ai/guides/board-own-agent.md).

**You should see** the ticket open on its **Overview**, with the **Next step** **Ankra will staff this ticket when an eligible agent is available.**

## 7. Let the agent take it

Ankra assigns the ticket to the agent on its own. You do not need to do anything.

**You should see** the ticket's **Owner** under **Properties** change to **Ankra agent**, and its status move on from **Triage** to **Investigating** and then **Planning**. The **Next step** says what the agent does next. Its **Work** tab lists the **Agent runs**; see [Follow, steer and stop an agent run](https://docs.ankra.ai/guides/agent-runs.md).

To steer it, write under **Add context** on the **Timeline** tab: a person's comment wakes the agent.

## 8. Approve what it wants to change

**1. Review the plan**

When the ticket reaches **Awaiting Approval**, open its **Plan** tab and read the **Proposed plan**. Press **Review and decide**.

**2. Decide**

Under **Decision**, choose **Approve** or **Request changes**, add a **Review note**, and press **Approve and release work** or **Request changes**. Requesting changes sends the plan back to the agent with your note.

From the CLI: `ankra tickets plan review T-42 --verdict approve`, or `--verdict request_changes --rationale "<why>"`.

**3. Approve each production change**

A production change the plan needs still asks on its own, under **Proposed production changes** on the ticket's **Overview** and in [Needs you](https://docs.ankra.ai/platform/activity-inbox.md). Tick **I reviewed this specific production change.**, then press **Approve this change** or **Reject change**.

**You should see** the ticket move to **Executing**, then **Verifying**. Each change the agent makes is listed under **Recorded changes**.

## Verify

Open the ticket once it reaches **Verifying**. **Review verification evidence** opens its **Evidence** tab, where **Evidence and verification** shows how the agent checked the result. When you agree, press **Close ticket**, choose the **Resolution** **Fixed**, and add a **Verification observation** if you have one: without it, the close is recorded as your own word, not as a fix the platform verified.

**You should see** the ticket's **Overview** show its **Outcome**, and the ticket leave the board's open lanes. **Filters → Show → Closed tickets** on **Ankra AI → Work** finds it again.

## What can go wrong

| What you see | What it means |
| - | - |
| **No eligible agent reported** | No board worker can take tickets. Provision the board identity and designate a board worker, as in step 2 |
| **Ankra will staff this ticket when an eligible agent is available.** stays | The ticket is waiting for an agent. Check the ticket desk's status |
| **Choose a Slack or Teams destination, or turn channel mirroring off.** | Mirroring is on with no destination chosen |
| **Select at least one ticket source for filtered mirroring.** | **Tickets matching these filters** is chosen with no **Ticket sources** ticked |
| **Ticket desk settings changed while this draft was open.** | Someone else saved the desk. Read **Current saved settings**, then press **I reviewed the current settings; keep my draft** to save yours |
| **Slack's directory is unavailable or the workspace is not connected.** | The Slack workspace is not connected to Ankra. See [AI Connections](https://docs.ankra.ai/platform/ai-connections.md) |

## What the portal does not set

| Setting | Where it is set |
| - | - |
| Which agents work tickets | `designate_board_worker` over MCP |
| The identity those agents act as | `ankra ai board-identity provision`, `status` and `revoke` |
| Mirroring tickets into Jira, Linear or a webhook | `ankra tickets sync connections create`. See [Sync tickets to Jira, Linear or a webhook](https://docs.ankra.ai/guides/ticket-sync.md) |
| Project channels, from a script | `ankra tickets settings projects set` |

## Next steps

* [AI Board](https://docs.ankra.ai/platform/ai-board.md) - statuses, resolutions, conditions and choices
* [Follow, steer and stop an agent run](https://docs.ankra.ai/guides/agent-runs.md)
* [Work the AI board with your own agent](https://docs.ankra.ai/guides/board-own-agent.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.