# Help desk

Work tickets, teach the agent, automate, and handle access requests: the dashboard in the order you use it.

## The dashboard

- [Dashboard overview](https://www.tryrisotto.com/docs/dashboard/overview): Where each part of the Risotto dashboard lives in the sidebar, and who can see it.
- [Account settings](https://www.tryrisotto.com/docs/dashboard/account-settings): Change your name, photo, email addresses and sign-in methods, set the dashboard's theme, see the devices you're signed in on, and sign out
- [Keyboard shortcuts](https://www.tryrisotto.com/docs/dashboard/keyboard-shortcuts): Every keyboard shortcut in the dashboard, the shortcuts panel that lists the keys for the page you're on, and the command palette for going to pages and running commands

## Tickets

- [Inbox](https://www.tryrisotto.com/docs/dashboard/tickets/inbox): Work your own queue of open tickets: see what needs action, preview and resolve tickets without leaving the list, and pick up unassigned work
- [Ticket inbox](https://www.tryrisotto.com/docs/dashboard/tickets/all): Find, filter, and sort the tickets you can access, save views, and update tickets in bulk
- [Needs attention](https://www.tryrisotto.com/docs/dashboard/tickets/needs-attention): The tickets with the status Awaiting support: the ones waiting for a person on your team
- [Views](https://www.tryrisotto.com/docs/dashboard/tickets/views): Save a filtered ticket list as a named view, share it with your organization, and manage every view you can open
- [Ticket details](https://www.tryrisotto.com/docs/dashboard/tickets/ticket-details): Read a ticket's conversation and what Risotto did on it, reply or add internal notes, approve tool calls, and change the ticket's status, assignee, priority, category, and department
- [Ticket statuses and lifecycle](https://www.tryrisotto.com/docs/concepts/ticket-lifecycle): What each ticket status means, which events move a ticket between statuses, how escalation and reopening work, and which status changes the API accepts

## Where tickets come from

- [Creating tickets from Slack](https://www.tryrisotto.com/docs/operating/creating-tickets): How requests in Slack become Risotto tickets: request channels, the ticket reaction, direct messages, the Create a ticket shortcut, and the App Home.
- [Creating tickets from Microsoft Teams](https://www.tryrisotto.com/docs/operating/creating-tickets-teams): How Risotto turns Microsoft Teams channel posts and direct messages into tickets, and how it keeps several requests apart in one chat
- [Creating tickets from email](https://www.tryrisotto.com/docs/operating/creating-tickets-email): Give a department a support email address, so each email sent to it becomes a ticket that your team answers from the agent channel or the dashboard
- [Setting up Jira as a request source](https://www.tryrisotto.com/docs/operating/creating-tickets-jira): Turn each new issue in a Jira project into a Risotto ticket for a department, and choose which issue types and request types count
- [Slack reactions](https://www.tryrisotto.com/docs/operating/slack-emojis): The emoji reactions that resolve, pause, forget, assign, ticket, or escalate a Slack thread or turn it into an article, the reactions Risotto adds, agent channel shortcuts, and how to change the emojis
- [Reprocessing a ticket](https://www.tryrisotto.com/docs/operating/reprocessing-tickets): Run Risotto on a ticket again so it picks up your current access rules, runbooks, and knowledge, or retry a ticket that got stuck

## Teach the agent

- [Runbooks](https://www.tryrisotto.com/docs/dashboard/runbooks): Tell the agent how to handle a kind of request: when the runbook applies, the steps to follow and the tools to use
- [Runbook forms](https://www.tryrisotto.com/docs/dashboard/runbooks/forms): Collect several typed answers from a requester in one runbook step: build a reusable form, attach it to a runbook, and Risotto posts it as a Slack form or Teams card, or asks for the fields in conversation
- [Using additional instructions](https://www.tryrisotto.com/docs/operating/additional-instructions): Teach Risotto your organization's terms, systems, and places with one set of instructions that the support agent and automations follow
- [Support agent context](https://www.tryrisotto.com/docs/dashboard/settings/support-agent/context): Choose which details about people and devices the support agent can see while it works a ticket, and test what it sees about you
- [Service catalog (Experimental)](https://www.tryrisotto.com/docs/dashboard/settings/service-catalog): Import request types from Jira Service Management or service items from Freshservice, so employees can request them in chat and Risotto files the request for them

### Knowledge

- [Articles](https://www.tryrisotto.com/docs/dashboard/knowledge/articles): Write and manage articles, Risotto's built-in knowledge base, and turn resolved Slack threads into articles with the ✍️ emoji
- [Indexes](https://www.tryrisotto.com/docs/dashboard/knowledge/indexes): Index knowledge sources such as Confluence, Notion and Google Drive so Risotto's agents can answer from them, and manage who gets answers from each index
- [Slack AI search](https://www.tryrisotto.com/docs/dashboard/knowledge/connect): Connect Slack AI search so Risotto's agents can search public Slack channels live, without an index
- [Playground](https://www.tryrisotto.com/docs/dashboard/knowledge/playground): Ask a question and see which articles and indexes Risotto's agent finds and how it answers, optionally as a specific user or department
- [Indexing best practices](https://www.tryrisotto.com/docs/concepts/indexing): How Risotto indexes and searches your knowledge sources, and how to choose and maintain indexes that give good answers

## Automate

- [Tools](https://www.tryrisotto.com/docs/dashboard/tools): Turn on the actions the agent can take, set who approves them, test them, and manage them in bulk
- [Credential vault](https://www.tryrisotto.com/docs/dashboard/settings/credential-vault): Store a secret once and reference it from tools, custom API sources, MCP servers, knowledge indexes, and connectors
- [Automations](https://www.tryrisotto.com/docs/dashboard/automations): Run the agent on a schedule, on a ticket event, on an HR or identity event, or when another system calls a webhook, with its own instructions, tools and approval rules
- [Campaigns](https://www.tryrisotto.com/docs/dashboard/campaigns): Send a message, a form, or an access review to many people at once in Slack, and track who has responded
- [Assistant](https://www.tryrisotto.com/docs/dashboard/assistant): Chat with the Assistant on its own page, in a panel docked beside any dashboard page, or on a ticket: it investigates escalated tickets, runs your organization's tools with your approval, and builds setup for you.
- [Set up the Assistant for a department](https://www.tryrisotto.com/docs/guides/setup-tier-2-assistant): Turn on auto start for a department, add instructions for each phase, check which data sources and tools the Assistant can use, and find its output on escalated tickets
- [Artifacts](https://www.tryrisotto.com/docs/dashboard/artifacts): Open, use, change, and delete the live pages that the Assistant builds for you: custom dashboards and small internal tools that run your organization's tools.

## Access requests

- [Applications](https://www.tryrisotto.com/docs/dashboard/applications): List the applications Risotto grants access to, create them or import them from Okta, Okta OIG, or Opal, and export their access rules
- [Access rules](https://www.tryrisotto.com/docs/dashboard/applications/access-rules): Create access rules that decide how Risotto grants one level of access to an application, who approves the request, and for how long.
- [Access grants](https://www.tryrisotto.com/docs/dashboard/applications/access-grants): See every access request and revocation Risotto has handled: who got which access, on which ticket, and when it expires. Expire a grant early or make it permanent.
- [Approval policies](https://www.tryrisotto.com/docs/dashboard/settings/approval-policies): Define a named, org-wide set of rules for who has to approve a request, and attach it to access rules, tools, and runbooks
- [License servers](https://www.tryrisotto.com/docs/dashboard/applications/license-servers): Connect Zoom, JetBrains, or Tableau so that an access rule grants access by assigning a license, and removes it when access ends.
- [Sign-in verification](https://www.tryrisotto.com/docs/dashboard/settings/identity/sign-in-verification): Have requesters prove who they are by signing in to your own Okta or Microsoft Entra ID app before Risotto runs a tool that requires user verification

## Measure

- [Analytics](https://www.tryrisotto.com/docs/dashboard/analytics): Track ticket volume, resolution and response times, automation rates, categories, tools, sources, and requester feedback
- [Insights (Experimental)](https://www.tryrisotto.com/docs/dashboard/insights): See which escalated requests Risotto could automate next, act on them with the Assistant, and find where your knowledge has gaps

Source: https://www.tryrisotto.com/docs/help-desk
