# From one message in Slack or Teams to a resolved request

Risotto works each request in the Slack or Microsoft Teams thread where it started, from the first reply to the closed ticket.

[Book a demo](/demo)

## How a request flows through Risotto

### Ask in Slack or Teams

A message to Risotto gets an answer or an action, with a follow-up question first only when it needs one.

[See the AI agent](/product/ai-agent)

### It acts, with approval where your policy says

Someone who asks Risotto for Lucidchart gets it right away, because your policy lets anyone have it. Amplitude waits for the approval your policy names, with an end date if the policy sets one.

[See how access works](/product/access-requests)

### Every request becomes a ticket

The ticket Risotto opens carries the conversation and every action it took, and it closes when the work is done.

[Ticketing](/product/ticketing) · [AI for your ITSM](/product/ai-for-itsm)

### Harder requests come with a plan

When a request needs your team, Risotto's AI Assist has already investigated it and written a plan that waits for your approval.

[See AI Assist](/product/ai-assist)

### Never answer the same question twice

Answer a question once in Slack, add the writing-hand reaction, and Risotto closes the ticket and turns the thread into a knowledge article. The next person who asks gets your answer without waiting for you.

### Automate what keeps coming back

Tell Risotto's Assistant how your team handles a request, and it builds the runbook the agent follows, with a script tool for steps that must run the same way every time. Insights shows which requests to automate next.

[Runbooks](/product/runbooks) · [Automations](/product/automations) · [Script tools](/product/script-tools) · [Insights](/product/insights)

## How is Risotto different from a portal or a first-generation bot?

A portal or a first-generation bot hands the work back to the employee, and Risotto does it.

| | Portals and first-generation bots | Risotto |
|---|---|---|
| Where employees ask | A portal, a form or a separate bot | Slack or Microsoft Teams channels and DMs, or email |
| What they get | A link to an article, or a ticket in a queue | The access granted or the password reset, in the thread |
| Who builds new workflows | Specialists in a workflow tool | IT, by describing them to the Assistant |

## Employees don't need to know which team owns it

With Risotto, each request lands in the private queue of the team that owns it, under that team's own permissions. At Thinkific, 6 departments onboarded in less than two months.

[See solutions by team](/solutions) · [Read the Thinkific story](/customers/thinkific-automates-46-percent-support-tickets-with-risotto)

> "Risotto started autosolving tickets immediately. Within the first few weeks, we saw departments that had never tracked ticket requests before, like our Cloud team, asking to get on the platform and streamline their support function." — Erik Van Dijk, Senior IT Manager, Jobber

[Read the Jobber story](/customers/jobber-builds-enterprise-wide-ai-support-funnel-with-risotto)

## IT sets the limits

Every change Risotto makes stays inside the approval policies and department permissions you set.

[Security and trust](/security)

## What IT teams say

> "We doubled our resolution rate on day one, and it hasn't dropped since." — Jose Izquierdo, Head of AIT Operations, Gusto

> "We accomplished nearly the same configuration with Risotto in an hour that took us months with another company." — Phillip Rickett, Head of IT, Fundrise

## Frequently asked questions

### What is AI-native ITSM?

AI-native ITSM is IT service management where an AI agent takes the request and does the work, with a ticket and an audit log for each. Risotto is the AI-native ITSM for Slack and Microsoft Teams.

### How long does it take to roll out Risotto?

Days to weeks, because Risotto connects to systems you already run. ThoughtSpot was up and running in less than a week, and Gusto was fully deployed across IT in two weeks. Start your security review early: it often takes longer than setup. [Read the ThoughtSpot story](/customers/thoughtspot-automates-multi-department-support-with-ai) · [Read the Gusto story](/customers/how-gusto-auto-resolves-55-of-tickets-with-risotto)

### Does Risotto replace our ticketing system?

It can, but it doesn't have to. Risotto syncs both ways with Jira Service Management, ServiceNow and Freshservice, or runs as your service desk with its own ticketing. [AI for your ITSM](/product/ai-for-itsm) · [Ticketing](/product/ticketing)

## Walk one of your own requests through Risotto

[Book a demo](/demo)

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