# Help desk ticketing in Slack and Teams, for people who hate logging tickets

Employees ask in Slack, Microsoft Teams or email, the way they'd ask a coworker. Risotto turns the message into a ticket with its priority already set. Your team works it from a keyboard-first inbox, or answers right in Slack or Teams.

[Book a demo](/demo)

The agent inbox in the Risotto dashboard. Example data.

## An inbox built for agents

Each agent starts the day with the tickets that need them, sorted into "Needs action" and "Waiting on others".

- **Keyboard first.** Move with j and k, resolve with d, and press ⌘K to jump to any ticket, view or action.
- **Shared saved views,** so the whole team works from the same queue.
- **Mobile-ready**, so you can work the queue from your phone.

> "We've completely replaced JIRA Assist with Risotto." — Peter Hadjisavas, Head of IT, Hazel Health

## The whole request on one page

Open a ticket and read it top to bottom: the employee's message from Slack or Teams, the steps Risotto worked through, and every reply since. Your team talks in internal notes the requester never sees, and the reply box answers in the employee's own thread. Status, priority, assignee and your department's own fields sit beside the conversation.

The page updates while it's open, so you see what Risotto or a teammate just did without reloading. Prefer chat? Agents can answer in Slack or Teams, and the ticket stays in step. Admins and supervisors can open the ticket's Assistant tab to investigate it and plan the fix. [See AI Assist](/product/ai-assist)

IT-2318 from the inbox above, on its own page: what Risotto looked up, Priya's internal note, and her reply about to go to Slack. Example data.

## Every ticket, in one table

Risotto keeps every ticket from IT, HR and Finance in one table. Filter by status, priority, category, department, assignee, requester, date or any custom field, choose your columns, and save "HR, waiting on employee" as a view the whole team shares. Resolve or reassign a stack of tickets at once, and export the view to CSV for the quarterly review. Tickets Risotto solved without a person are marked, so its work is easy to spot.

Every ticket across IT, HR and Finance, with example data. Try the filters, or select a few tickets and resolve them.

## Fields, priority and departments

Risotto turns the conversation into a structured ticket, so nobody copies context into a form. It sets the priority from what the employee wrote, so "VPN is down for the whole sales team" goes ahead of a monitor request. Agents can change it. Categories, tags and custom fields (text, single select and multi-select) hold the data your team reports on.

IT, HR, Finance, Legal and other teams each get a department with a private queue and their own permissions. Large teams can split theirs into sub-departments without changing where employees ask.

An HR ticket in the Benefits sub-department, with HR's own fields. Example data.

## How does Risotto route tickets?

Risotto sends each escalated ticket to its department, then picks a person by one of three rules. The ticket arrives with the conversation and what Risotto already tried.

| Routing mode | How it assigns |
|---|---|
| Round robin | Takes turns across the team |
| Round robin, online in Slack | Takes turns across the people who are online in Slack right now |
| Fewest open tickets | Gives the ticket to the person with the fewest open tickets |

## Reporting on every request

Risotto counts a ticket as solved automatically only when it finished the request with no person stepping in. Posting a link and hoping doesn't count.

The analytics dashboard puts AI and human time to resolve side by side, and works out the time saved from your own numbers. Filter by department, assignee and date range, and select any percentage to see the tickets behind it.

[See Analytics and Insights](/product/insights)

The analytics dashboard. Example data.

## Already on Jira, ServiceNow or Freshservice?

Keep it. Risotto adds AI on top with two-way sync, and each department chooses: keep Jira for IT and give HR or Legal Risotto's ticketing. [AI for your ITSM](/product/ai-for-itsm)

## Frequently asked questions

### Does Risotto have its own ticketing system?

Yes. Risotto's ticketing has an agent inbox, a table of every ticket with filters and saved views, custom fields, AI-set priority, routing rules, departments and sub-departments, bulk actions, CSV export and reporting. Employees ask in Slack, Teams or email.

### Can Risotto replace Jira Service Management?

Yes. Risotto's ticketing can run your whole service desk, with an agent inbox, custom fields, routing rules and reporting. Prefer to keep Jira Service Management? Run Risotto on top with two-way sync. [Risotto vs Jira Service Management](/compare/jira-service-management)

### How does Risotto route tickets?

Risotto routes each ticket to the right department, then to a person by round robin, round robin among people online in Slack, or fewest open tickets. The ticket arrives with the full conversation and what Risotto already tried.

### Can agents work tickets in Slack?

Yes. Agents can answer in Slack or Teams, or work from the dashboard inbox. The conversation and the ticket stay in step either way.

## Run your queue where your employees already are

[Book a demo](/demo)

Source: https://www.tryrisotto.com/product/ticketing
