Ticket Statuses & Lifecycle
What each ticket status means, which events move a ticket between statuses, how escalation and reopening work, and which status changes the API accepts
Every request Risotto handles becomes a ticket. The ticket's status tells you who has the ball: the requester, your team, an approver, or nobody, because the ticket is finished. This page explains what each status means and which events move a ticket from one status to the next.
To find, filter, and change tickets in the dashboard, see Tickets and Ticket details.
Status reference
| Status | API value | What it means | Set by | Final? |
|---|---|---|---|---|
| Open | open | A new request that nobody has answered yet | Risotto, when the request arrives | No |
| In progress | in_progress | Someone is working on it. Optional, for teams that use it | A person, or a connected ticketing system | No |
| Awaiting response | waiting_for_response | Risotto or your team replied last. The ball is with the requester | Risotto or your team replying | No |
| Awaiting support | waiting_for_support | The ball is with your team. Every escalation lands here | The requester replying, an escalation, or a reopen | No |
| Awaiting approval | waiting_for_approval | An access request is waiting for an approver's decision | Risotto's approval flow, or a status synced in from Jira | No |
| Paused | paused | An explicit hold while your team does work that takes hours or days | The pause reaction, or a person | No |
| Resolved | resolved | The request is complete | Risotto, a person, or auto-resolve | Yes |
| Closed | closed | The request was canceled or closed without a resolution | The requester canceling, or a person | Yes |
| Duplicate | duplicate | The ticket duplicates another ticket | A person in the dashboard, or a status synced in from Jira | Yes |
- The dashboard shows a Resolved ticket that Risotto solved without your team's help as Auto-solved.
- The ticket card in Slack, the ticket list in the agent channel, and the Jira, ServiceNow, and Airtable status mappings use older names for three statuses: Waiting for Response, Waiting for Support, and Waiting for Approval.
- Final statuses are not locked. A finished ticket can reopen.
- Syncing tickets to Jira? Jira Status Sync explains how each status maps to your Jira workflow.
The ticket lifecycle
The diagram shows each status, who has the ball, and the events that move a ticket on. Only a person or a connected ticketing system sets In progress. From there, the ticket moves like an Open ticket.
What moves a ticket
Replies
- Risotto or your team replies to the requester. The ticket moves to Awaiting response. A reply from the dashboard, from the agent channel, or in the ticket's thread counts. A reply does not change a ticket that is paused, finished, or waiting for an approval.
- The requester replies in the thread. The ticket moves to Awaiting support. If Risotto is active on the ticket, it answers, and the ticket moves back to Awaiting response. A reply does not change a paused or finished ticket.
- Someone else replies in the thread. In Slack, a reply from a person who is neither the requester nor an Agent or Supervisor of the ticket's department does not change the status, unless it tags @Risotto. One agent channel can serve several departments, so the same rule applies to replies in the agent channel.
When Risotto steps back
Risotto stops replying on its own when a person on your team answers the requester:
- In Slack, a reply in the agent channel, or a reply in the ticket's thread from an Agent or Supervisor of the ticket's department or of its parent department.
- In Jira, Freshservice, or Linear, a public comment on the synced ticket from a Risotto dashboard user who has signed in at least once.
A comment from an Agent or Supervisor of the ticket's department or of its parent department also assigns the ticket to that person. This applies to a comment from Slack, the dashboard, the API, or a connected ticketing system such as Jira, and only when all of these are true:
- The ticket has no assignee, or it is assigned to Risotto. Risotto never takes a ticket from a person who holds it.
- The person who comments is not the requester.
- The ticket is not resolved or closed.
An internal note also assigns the ticket. When the ticket is synced to a ticketing system, Risotto sets the assignee there too. To turn this off for a department, use the Assign the ticket to the agent who comments switch on the department's General page. See Departments. A reply from someone outside the ticket's department does not assign the ticket. The Send as my response button in the agent channel assigns the ticket only when the ticket has no assignee.
Assigning a ticket, adding an internal note (even one that assigns the ticket), or a reply from the requester does not make Risotto step back.
To bring Risotto back, tag @Risotto in the thread.
Escalation
Escalation hands the ticket to your team. Whatever triggers it, the result is the same:
- The ticket moves to Awaiting support and gets the
Escalatedtag. - Risotto stands by and does not reply until someone tags @Risotto.
- Risotto tells your team, through the department's escalation contact and escalation routing.
The waiting-on-customer timer is the department's Escalate tickets waiting on customer setting, in wall-clock hours since the last reply. It is off unless you set it. See Auto Resolve. To escalate from the dashboard, see Reprocess or escalate.
Access approvals
When an access request needs an approver's decision, the ticket moves to Awaiting approval. When the approvers decide, Risotto tells the requester and, if no other request on the ticket is still open, resolves the ticket. If the request expires before anyone decides, Risotto escalates the ticket.
Only Risotto's approval flow, or a status synced in from Jira, sets Awaiting approval. You cannot pick it in the dashboard, in bulk updates, on the ticket card in Slack, or through the API or MCP. While a ticket is awaiting approval, you can move it only to Resolved or Closed. The dashboard refuses any other change with "This ticket is waiting for an approval; it can only be resolved or closed until the approval completes." Replies in the thread and the pause reaction do not change the status.
A pending approval ends early in these cases:
- Resolved, closed, marked as a duplicate, or canceled. Risotto cancels every access request on the ticket that no approver has decided yet, and approvers get no more reminders. A decision made earlier stays as it is. Reopening the ticket does not bring the request back: the requester asks again. Requests handed to Opal or Okta Identity Governance stay open when the ticket is resolved, closed, or marked as a duplicate, so Risotto can still apply that system's answer. A cancel by the requester cancels them too.
- Canceled in the thread. The requester can ask Risotto in the ticket thread to cancel a request that still waits on approval. Risotto asks them to confirm, then cancels the request and its approval, and grants no access. In Slack, Risotto removes the buttons from each approver's message that has no answer and adds "This request was cancelled." Microsoft Teams cannot edit the message, so a later click there gets the closed notice. If an approver decided first, the decision stays. A request to remove access does not cancel a request that is still waiting: Risotto asks the requester whether to cancel it. A request handed to Opal or Okta Identity Governance cannot be canceled this way: the requester withdraws it in that system.
- Escalated. Risotto cancels the pending approval of the most recent access request on the ticket. To try again, tag @Risotto in the thread and ask for the access again.
An approver can still click Approve or Deny on an old approval message. The click changes nothing. In Slack, Risotto removes the buttons and says why, for example "This request was cancelled. Your response was not recorded." The other reasons are "This request was already approved.", "This request was already denied.", and "This request expired before anyone decided."
Inactivity auto-resolve
Risotto resolves a ticket in Open, In progress, or Awaiting response that has had no reply for the department's Auto-resolve delay, in business days. It can remind the requester first (see Auto-resolve Delay). When it resolves the ticket, it posts "It's been a bit since I've heard from you so I'll mark this resolved. If you need anything else, please open a new request!"
Tickets in Awaiting support, Awaiting approval, and Paused are never auto-resolved: a person or an approver owes the next step. A ticket waiting for someone to create an account by hand is not auto-resolved either. To skip tickets assigned to a person, turn on Skip auto-resolve for agent-assigned tickets. See Auto Resolve.
Pausing a ticket
Pause a ticket when your team does work that takes hours or days and the ticket must stay open until it is done.
In Slack, add the ⏸️ :double_vertical_bar: reaction to the first message of the ticket's thread. The requester or your team can add it. You can also set Paused in the dashboard. While a ticket is paused:
- Risotto does not reply to new messages in the thread, even if someone tags @Risotto.
- Replies do not change the status.
- Auto-resolve and the waiting-on-customer timer skip the ticket.
To unpause the ticket, remove the reaction. The ticket moves to Awaiting support. You can change the pause emoji in the Slack Reactions card. The reaction does not change a ticket that is awaiting approval.
Cancellation
The ticket is Closed when the requester cancels the request: they tell Risotto they no longer need help, decline its offer to escalate, or delete the original message.
Reopening a finished ticket
Tag @Risotto in the thread of a Resolved, Closed, or Duplicate ticket to reopen it. The ticket moves to Awaiting support and Risotto picks it up again. Anyone in the thread can tag Risotto. A tag does not reopen a ticket while Risotto waits for an approval or for the requester's identity verification.
- Slack. A reply that does not tag @Risotto does not reopen the ticket. Risotto adds the reply to the ticket as a comment and tells the sender, in a message only they can see: "This ticket has been resolved, so I won't respond to new messages here. If you need more help, you can tag me in a reply to reactivate this ticket, or start a new thread for a new request."
- Microsoft Teams. In a channel thread, a reply must mention Risotto to reopen the ticket. In a direct message, a new message within 1 hour after the ticket is resolved reopens it when Risotto reads it as a continuation. Otherwise the message opens a new ticket. A Closed ticket does not reopen from a direct message.
- Email. A reply from the requester to a Resolved ticket reopens it, without a tag. A reply from anyone else, or to a Closed or Duplicate ticket, is added as a comment and the status does not change. A reopen by email does not turn Risotto back on for an escalated ticket. See Email.
- Dashboard. A reply in the dashboard never reopens a finished ticket, even one that tags @Risotto. Neither does a comment posted through the API or synced from Jira or ServiceNow. Change the status instead, or ask the Assistant in the ticket's Team chat to reopen a Resolved ticket.
If the ticket syncs to Jira, ServiceNow, or Airtable, a reopen also moves the external ticket back to an open status. Tickets in Freshservice, Zendesk, Linear, Asana, and GitHub Issues stay resolved there. A reopen does not message the assignee. The ticket shows in the assignee's Inbox under Needs action.
What Risotto reads when it reactivates
Risotto stores each message as a comment on the ticket when it arrives. When you tag @Risotto to bring it back, it rebuilds its context from the ticket's comments, including replies your team posted in the thread.
- To steer it, tag @Risotto with an explicit instruction, for example "ignore the reply above and handle the original request from scratch". The newest message carries the most weight.
- For a clean start, ask the requester to post the request again in a new thread. That opens a new ticket with no history.
- To leave a note Risotto never reads, start your reply in the agent channel with
:lock:. See Slack emojis.
What Risotto is doing on a ticket
The status tells you who has the ball. The Slack thread tells you what Risotto itself is doing.
Thinking steps
In a Slack ticket thread, Risotto shows its work with Slack's thinking steps:
- When a message arrives, a Thinking... line appears under the thread.
- As Risotto works, a collapsible plan replaces the line. Each step is a row, and the plan's title names the latest step. The first plan in a thread starts with the ticket's creation, for example "Creating ticket IT-142: Laptop won't connect to VPN", and, for a synced ticket, its sync to your ticketing system. These rows link the ticket in the dashboard and in your ticketing system.
- While Risotto waits on someone else, the plan stays open with the title Waiting for approval, Waiting for identity verification, Waiting for account creation, or Waiting for account removal.
- When Risotto's turn ends, the plan stops and stays in the thread above the answer. The first plan is titled with the ticket, for example "Responded and created ticket IT-142". Later plans are titled "Done". If you turn off Keep thinking steps for the channel in Request Sources, Risotto removes the plan instead, so the answer stands alone.
The same steps go to the ticket's stream of consciousness in the dashboard. A thread with thinking steps has no status banner and no Chat with the team button: to reach your team, the requester asks for a person, and Risotto escalates.
Microsoft Teams, Assistant threads, tickets opened by a bot, and older tickets that started with a banner keep the 👀 reaction and the status banner below.
Status banners
| Banner | What it means |
|---|---|
| Waiting for response from … | Risotto or your team replied last. The ball is with the requester |
| Waiting for support team | The ticket is with your team |
| Standing by, tag @Risotto to reactivate | Risotto stepped back after an escalation or a reply from your team. Tag @Risotto to bring it back |
| Awaiting admin approval | An action Risotto wants to take waits for an admin to approve it. Risotto does not answer until then |
| Awaiting user identity verification | Risotto asked the requester to verify their identity before a sensitive action |
| Waiting for approval | An access request waits for an approver |
| Awaiting manual account creation | A person must create the account by hand |
| Awaiting manual account deprovision | A person must remove the account by hand |
| Paused | The ticket is paused |
| Getting someone to assist | The ticket was escalated and then closed. Your team handles the conversation directly |
| Resolved | The request is complete. Tag @Risotto to reopen it |
| Closed | The ticket was canceled or closed without a resolution. Tag @Risotto to reopen it |
Changing status via the API and MCP
The Risotto API and the MCP server check each status change against this table and reject any other change with a validation error. In the dashboard you can pick any status except Awaiting approval, and a ticket that is awaiting approval can move only to Resolved or Closed.
| Current status | Allowed next statuses |
|---|---|
open | in_progress, paused, resolved, closed |
in_progress | waiting_for_response, waiting_for_support, paused, resolved, closed |
waiting_for_response | open, in_progress, resolved, closed |
waiting_for_support | in_progress, resolved, closed |
waiting_for_approval | resolved, closed |
paused | open, in_progress, resolved, closed |
resolved | open, closed |
closed | none |
- Setting the status a ticket already has is always accepted.
- No status can move to
waiting_for_approval, andduplicatecan't be set or left through the API. Mark duplicates in the dashboard. resolvedandclosedcancel pending approvals and Risotto's open access requests, except requests handed to Opal or Okta Identity Governance. Onlyresolvedalso resolves the linked ticket in your ticketing system.- The API has no move out of
closed. To reopen a closed ticket, tag @Risotto in its thread. If your integration needs to reopen tickets later, finish them asresolved. - A change to
openthrough the API changes only the status in Risotto, not the linked ticket in your ticketing system. - A ticket created through the API with
escalate: truestarts in Awaiting support with theEscalatedtag and Risotto switched off. Changing its status through the API does not turn Risotto back on, and comments posted through the API don't either.
Related pages
Something wrong or missing? Report an issue · View as Markdown