How Risotto works
Follow one employee request from the first message to a resolved ticket: intake, routing, the agent's decision, tools and approvals, replies, and escalation to your team
When an employee asks for help, Risotto turns the message into a ticket, sends the ticket to a department, and runs an AI support agent on it. The agent answers, takes an action, or hands the ticket to your team. This page follows one request through each stage. Each stage links to the page that covers it in depth.
To watch four requests go through these stages, from an access request to an escalation, see the three-minute video.
A message arrives
Risotto takes requests from your request sources: Slack and Microsoft Teams channels, direct messages, support email addresses, and Jira, ServiceNow, and Freshservice tickets. Every source leads to the same kind of ticket and the same agent.
In a Slack channel, Risotto first checks whether a new message is a request at all. A message that isn't, such as an announcement, gets no ticket, unless the channel has Ticket everything on or the message mentions Risotto. A channel in Silent mode ignores new messages unless they mention Risotto. A direct message always becomes a ticket. If the requester already has an open ticket in direct messages and the new message looks like the same request, Risotto asks whether it is new or related.
Risotto opens a ticket and routes it
When it creates the ticket, Risotto works out:
- A title: a short summary of the request.
- The department: if the source is locked to a department, that department. Otherwise Risotto compares the request with the name and description of each top-level department, and falls back to the default department when none fits. See Enterprise routing.
- The priority: from the department's urgency criteria. A source or requester that the department marks as always urgent makes the ticket Urgent. See Ticket priority.
With the department known, Risotto matches runbooks: the department's Department request runbook, if it has one, and the Request match runbooks whose description fits the request, up to five in all. It searches the organization-wide runbooks and the department's own. After the requester's second message, it matches once more against the whole conversation and adds any new matches. It also sorts the ticket into one of the department's categories.
The ticket starts as Open.
The agent decides how to help
Each new message from the requester starts a turn of the support agent. The agent reads the conversation, the instructions of the matched runbooks, your organization's additional instructions, and who the requester is. Then it picks a path:
- A matched runbook applies. The agent follows the runbook's instructions, with the tools the runbook references. A runbook's instructions win over the agent's defaults. When two runbooks match and conflict, it follows the more specific one.
- Access to an app. The agent finds the app among your applications and grants the access the requester is eligible for, under its access rule.
- Something to be provided, such as hardware or a service. If you publish a service catalog, the agent finds the item, collects its form, files the request in Jira Service Management or Freshservice, and gives the requester the reference. If Risotto could not import an item's form, the agent gives the requester a link to the item's page in the source portal and files nothing. See Items requested in the source portal.
- A question or a problem. The agent searches your knowledge and answers only from what it finds, with a numbered link to each source. If nothing relevant turns up, it escalates instead of guessing.
- Too vague to act on. The agent asks one follow-up question.
The agent also answers questions about the requester's own profile, such as their manager, from your identity provider. Support agent context controls which fields it sees.
Tools run, with approval where required
Tools are the actions the agent takes in your systems. The core tools are always available. Other tools are available on a ticket when a matched runbook references them.
Before some tools run, a person has to agree:
- Approval. A tool that requires approval, or whose approval policy requires it for this requester, pauses the turn. Risotto sends an approval request, and the agent continues once an approver decides.
- User verification. A tool with user verification first asks the requester to confirm who they are.
- Access requests follow their access rule's approvers. Meanwhile the ticket shows Awaiting approval.
If Risotto can't open an approval or a verification, for example because the requester has no Okta Verify push enrolled, it escalates the ticket.
Risotto replies or resolves
Each turn ends with one outcome:
- Reply. Risotto posts an answer, a result, or a question in the conversation the request came from. The ticket moves to Awaiting response.
- Resolve. When the work is done and the requester confirms it, for example with a "thanks", or when they ask to close the ticket. Risotto never resolves while an approval or other work is still pending. The dashboard shows a ticket that Risotto solved without your team as Auto-solved.
- Escalate. See the next section.
- Cancel. When the requester asks to cancel. The ticket moves to Closed.
If the department turns on answer review, Risotto holds knowledge or runbook answers in the agent channel until someone on your team approves them. A ticket that sits idle is resolved after the department's auto-resolve delay, after one reminder.
Escalation to your team
Risotto escalates when the requester asks for a person, when the knowledge search finds nothing, when a tool fails in a way the agent can't fix, when a runbook says to, or when the agent itself runs into an error. If the source has Prompt for escalation on, Risotto first asks the requester to confirm.
When it escalates:
- The department's escalation routing picks who gets the ticket. A rule can assign a person or hand the ticket to a sub-department, whose own rules then apply. Without a matching rule, Risotto tags the department's escalation contact.
- Your team gets a summary of what the requester needs and why the agent escalated.
- The requester gets the department's custom escalation message, or "We're on it! Someone from the team will get back to you as soon as possible."
- The ticket moves to Awaiting support and gets the
Escalatedtag. Risotto stands by until someone tags @Risotto. - If the department syncs only escalated tickets, Risotto creates the ticket in your ticketing system now.
From there, your team works the ticket like any other, through to Resolved. Ticket statuses and lifecycle covers every status and what moves a ticket between them.
What you configure at each stage
| Stage | What shapes it |
|---|---|
| A message arrives | Request sources: which channels, inboxes, and projects create tickets, and their department locks |
| Routing | Departments and their descriptions, categories, and priority criteria |
| The agent's decision | Runbooks, knowledge indexes and articles, additional instructions, access rules, and the service catalog |
| Tools and approvals | Tools and approval policies |
| Replies and escalation | The department's answer review, escalation settings, and auto resolve |
Where to watch it work
- Ticket details: the timeline shows the steps the agent took before each reply, and each tool call with its parameters, output, and approval. The ticket's Properties list shows the runbook that the agent followed as Runbook, or Runbooks when it followed several, and the other matches as Also matched. When the agent followed none, one Matched runbooks row lists them. Point at a runbook to see its version, when and why the agent followed it, and the approvals its steps asked for.
- Analytics: how many tickets were solved, how many Risotto solved on its own or with knowledge, and response and resolution times.
Something wrong or missing? Report an issue · View as Markdown