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.
- 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.
- A Slack or Microsoft Teams connection, if ticket conversations are to happen there. See AI Connections.
- 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.
designate_board_worker, and check with list_agent_tasks that its can_work_board is true. See 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.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.
6. File a ticket
- Portal
- CLI
- MCP
- On Ankra AI → Work, press New ticket.
- 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.
- Set the properties: Priority (Medium unless you change it), Kind (Request unless you change it), and Environment for the cluster it is about.
- 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.
- Press Create ticket.
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. 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. Tick I reviewed this specific production change., then press Approve this change or Reject change.
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 the portal does not set
Next steps
- AI Board - statuses, resolutions, conditions and choices
- Follow, steer and stop an agent run
- Work the AI board with your own agent