Ticket Priority
How Risotto sets a ticket's priority from your urgency criteria and VIPs, and how you change it
Every ticket in Risotto can have a priority: Urgent, High, Medium, or Low. The priority sorts and filters your tickets, and it decides the ticket's SLA targets.
Risotto sets the priority once, from the request that opens the ticket:
- VIPs: if the requestor is a VIP of the ticket's department, or the request comes from one of the department's urgent Slack channels, the ticket is Urgent. Risotto does not evaluate the request.
- AI-suggested priority: otherwise, Risotto evaluates the request against the department's urgency criteria and suggests a priority. A runbook can also change this value with the Update Ticket tool.
- Manual: a person can set or change the priority of any ticket at any time. A priority that a person sets always wins over the suggested priority. The Update Ticket tool does not change it.
You configure urgency criteria and VIPs for each department on Settings > <department> > Priority. An Org Admin, a Manager, or a Supervisor of the department can change these settings. See Permissions.
AI-suggested priority
When a ticket is created, Risotto reads the request and suggests a priority from the department's urgency criteria. If Risotto cannot decide, the ticket has no priority until someone sets one.
The dashboard marks a suggested priority with a sparkles icon. Hover over the icon to see "AI-suggested priority". When a person sets the priority, the icon goes away.
If you move a ticket to another department, Risotto does not evaluate its priority again. It does so only if the ticket had no priority yet.
Urgency criteria
What counts as urgent for Security is not what counts as urgent for Workplace. Each department can define, in plain language, what each priority level means for it.
On the Priority page, the Urgency criteria section has one text box for each level: Urgent, High, Medium, and Low. Each box takes up to 500 characters. An empty box uses Risotto's default criteria for that level:
| Level | Default criteria |
|---|---|
| Urgent | Work-stopping issues affecting many people or a critical business function, such as an outage of a business-critical system, a suspected security incident, or a time-sensitive issue blocking an executive or customer-facing event. |
| High | An individual is fully blocked from doing their job with no workaround (e.g. locked out of a critical account, primary device failure), or an issue is degrading work for an entire team. |
| Medium | Work is degraded but a workaround exists, or the request has a deadline that is not immediate (e.g. new software access, hardware for an upcoming start date). |
| Low | General questions, guidance, and convenience requests with no time pressure. |
VIP users
VIP users are requestors whose tickets should always be urgent: executives, on-call leads, or anyone whose requests your team never wants to wait. When a VIP submits a request, Risotto sets the ticket to Urgent and skips the AI evaluation for that ticket.
You configure VIPs for each department in the VIPs box of the Priority page, below the Urgent criteria. There are three ways to match:
- Employees: click Add employee and pick people by name.
- Urgent Slack channels: click Select channel... and pick a Slack channel. Requests from those channels are urgent no matter who sends them, which suits an incident or exec-support channel. This applies to Slack requests only.
- IdP profile rules: click Add rule to make tickets urgent when the requestor's identity provider profile meets the rule's requirements. The rule matches profile fields, not group membership.
Set up priority for a department
Open the Priority page
Go to Settings > <department> > Priority. Priority is in the Tickets section of the department's settings.
Write urgency criteria
Under Urgency criteria, optionally write a definition for each priority level. Leave a box empty to use the default criteria.
Designate VIPs
In the VIPs box, add Employees, Urgent Slack channels, or IdP profile rules.
Save
Click Save at the top of the Ticket Priority card. The message "Urgency criteria updated" appears.
Your changes apply to new tickets. Risotto does not evaluate the priority of existing tickets again.
Change the priority of a ticket
Open the ticket
Open the ticket from the Inbox or Tickets > All.
Pick a priority
In the Properties section of the ticket details, click Priority and pick a level. If the ticket has no priority, click Add priority.
Where priority shows up
- Tickets > All: a Priority column and a Priority filter.
- Inbox: each row shows the priority, and you can set Sort by to Priority to see the most urgent tickets first.
- Ticket details: the Priority row in the Properties section, which you can change.
- Slack agent channel: the ticket card shows the priority when the ticket has one, and the priority links to the ticket list filtered by that priority. The ticket details that you open from the card always show a Priority field, so you can set or change the priority from Slack.
- SLAs: the ticket's priority decides its response and resolution targets. See Ticket SLAs.
- Synced ticketing systems: priority maps to your connected ITSM's priority field where the integration supports it. See your ticketing integration's page for its mapping. For Jira, turn on Sync priority to Jira. For Freshservice, turn on Sync priority to Freshservice. Both are off by default.
Troubleshooting
A VIP's ticket didn't come in as urgent
Confirm the person is a VIP of the department the ticket was in when it was created. VIP status is per department, so someone who's a VIP for IT isn't automatically a VIP for People. Risotto checks VIPs only when the ticket is created, so adding a VIP does not change existing tickets. If the person matches through an IdP profile rule, confirm their identity provider profile has the field value that the rule requires.
AI suggestions don't match how we triage
Add or refine the urgency criteria for each level. The defaults are generic; a couple of sentences per level in your team's own terms improves the suggestions.
Priority isn't syncing to our ticketing system
Priority mapping depends on the integration. Check your ticketing integration's page for its mapping table and any limitations.
Something wrong or missing? Report an issue · View as Markdown