Use case

Employees ask in chat. IT gets a real ticket.

Risotto is chat-based ticketing for IT teams that work in Slack or Microsoft Teams. Employees ask in a channel, a DM or by email. Risotto’s AI agent answers or takes the action in the thread, and every request becomes a ticket, in Risotto or synced both ways with Jira Service Management, ServiceNow or Freshservice.

Book a demo

Why help requests get lost in chat

Before Risotto, most IT teams have the same help channel: busy, useful and hard to track.

  • Requests get buried in the thread, and nobody owns them.
  • Employees bump their own message to get an answer.
  • Someone copies each message into the ITSM so the work counts.
  • The same questions come back every week.

A portal fixes the tracking, but employees go back to chat. And a chatbot that only answers the first message hands everything after it back to IT.

“Slack is really easy. It’s one of the easiest communication tools we’ve ever had in a corporate world, and that ease of use makes it the best place for ticket intake.”

From message to resolved ticket

Risotto handles a request from chat end to end, and records every step.

  1. An employee asks. In a Slack or Teams channel, a DM or by email, in plain words. Screenshots and error messages are fine.
  2. Risotto opens the ticket the moment the request arrives, with the full conversation attached. Posts from the bots and alerting tools you allow can open tickets too.
  3. The AI agent works the request in the thread. It answers from Confluence, Notion, Google Drive, SharePoint, OneNote, Guru or Coda. It resets passwords and MFA in Okta and Microsoft Entra ID, and grants access after the right approval. In Slack, it shows each step as it works.
  4. It asks for details when it needs them, in a native Slack form or a Teams card.
  5. A person takes over when needed. Risotto routes the ticket to the right department and person, with the conversation and what it already tried. The employee sees who picked it up, and the agent never starts over.

Keep your ITSM, or use ours

Risotto puts each ticket where your team already works.

  • Jira Service Management Two-way sync, including custom fields
  • ServiceNow Two-way sync, and Risotto fills in your custom fields. ServiceNow incidents also become Risotto tickets.
  • Freshservice Two-way sync
  • Zendesk or Linear Two-way sync of comments and status. Agents’ replies reach the employee’s thread.
  • Risotto Its own ticketing, with custom fields, AI-set priority, routing rules, departments and sub-departments

Your ITSM keeps its workflows, reporting and history. AI for your ITSM · Ticketing in Risotto

Work the queue from chat or the dashboard

Risotto lets IT pick up each ticket where it is easiest.

  • In Slack. Every ticket gets a thread in your team’s agent channel. React with an emoji to resolve, pause, escalate or assign it to yourself, or open the ticket card to change its assignee, status, priority or department.
  • In the Risotto inbox. A keyboard-first inbox with ⌘K, shared saved views and live ticket pages. It works on your phone too.
  • In your ITSM. Agents keep working in Jira Service Management, ServiceNow or Freshservice, and the ticket stays in step with the chat.
  • With routing. The AI sets the priority. Routing rules assign each ticket by round robin, fewest open tickets, or who is online in Slack.

When a ticket needs a person, the Assistant goes first

Risotto’s AI Assist can pick up each escalated ticket before your team opens it. It reads the Okta logs, device and HR data, past tickets and your docs, then writes a plan with the reason for each change. Your agent approves it, asks for a different plan, or takes over. AI Assist

IT controls what happens in chat

Risotto resolves only what you put in scope. Most teams start with password resets and knowledge questions, then add more once they like the results.

  • Channels by department. Route each channel to a department, so HR or Finance requests reach a private queue with its own permissions.
  • Approvals. Approval policies apply to access rules, tools and any runbook step. Approvers decide in Slack, Teams or email.
  • An audit log. Who asked, who approved, what ran and when, on every ticket.

Find what to automate next

Risotto Insights reads every ticket that went to a person and finds what would have closed it: an access rule, a runbook template, or a question your knowledge base can’t answer yet. Approve the fix the Assistant drafts, and Risotto handles that request next time. Insights

What IT teams say

Risotto customers moved IT support into chat and kept the tickets.

“We want AI to seamlessly fit into our team’s daily operations, meeting our users where they already work… Risotto’s minimal operational overhead and integration into Slack has enabled us to achieve exactly that.”

“We doubled our resolution rate on day one, and it hasn’t dropped since.”

  • 27% of IT requests auto-resolved end to end each month at Docker. Read the story
  • 56% of support tickets at Vidyard automatically resolved or given initial triage. Read the story
  • 6.5 hours average AI resolution time at ThoughtSpot, against 31 hours for human agents. Read the story

Frequently asked questions

What is chat-based ticketing?

Chat-based ticketing is a help desk where employees ask for help in a chat tool, such as Slack or Microsoft Teams, and each request becomes a tracked ticket. Risotto adds an AI agent that resolves requests in the thread and hands the rest to IT with full context.

What is AI ticket automation?

AI ticket automation handles a ticket from the first message to closed: it opens the ticket, picks the department, sets the priority, resolves what it can and routes the rest. Risotto does this in Slack and Microsoft Teams, and it takes the action, such as a password reset or an access grant after approval, instead of only replying. The AI agent

Which tickets can Risotto resolve on its own?

Password and MFA resets in Okta and Microsoft Entra ID, access requests with approvals, device actions in Jamf, Iru and Intune, knowledge questions and HR self-service. You choose what’s in scope. The AI agent

How do I turn Slack or Teams messages into tickets?

Add Risotto to your help channels, or let employees send it a DM. Risotto turns each request into a ticket the moment it arrives, in its own ticketing or in Jira Service Management, ServiceNow or Freshservice. Slack and Risotto · Microsoft Teams and Risotto

Can I keep Jira Service Management, ServiceNow or Freshservice?

Yes. Risotto syncs tickets both ways with Jira Service Management, ServiceNow and Freshservice, so your workflows and reporting stay in your ITSM. You can also use Risotto’s own ticketing. Add AI to your ITSM

Does chat-based ticketing work in Microsoft Teams?

Yes. Risotto works in Teams channels and DMs, with the same tickets, approvals and audit log as in Slack. Approvals and forms are Teams cards, and each channel can route to a department. Microsoft Teams and Risotto

Keep the chat. Get the ticket.

Book a demo