Docs

Help desk / 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

Each ticket has its own page in the dashboard, at /tickets/<ticket ID>, for example /tickets/IT-142. To open it, click a ticket's title in Tickets > All, or open a ticket from the Inbox. You can open the tickets of the departments where you are an Agent or a Supervisor, and of their sub-departments. See Ticket Inbox.

The page has the ticket's title and timeline on the left, with the reply box at the end, and the ticket aside on the right.

To watch ticketing in the dashboard first, see the two-and-a-half-minute video.

  • Header: Tickets > <ticket ID>, then two buttons: copy the ticket ID, and ⋯, the ticket menu. On the right, Slack or Teams opens the ticket's thread in a new tab. For a ticket synced to a ticketing system, a link with the system's logo and the external ticket key, for example ITSD-1042, opens the synced ticket. See External ticket links. At the end of the bar, Team chat opens the ticket's team chat in the docked panel. When you opened the ticket from a list, the header also has the ticket's place in that list, for example 5 / 7, and the Previous ticket and Next ticket buttons. Press k or j to do the same.
  • Title: click the title to rename the ticket, then press Enter or click away. The title can't be empty.
  • Aside width: drag the aside's left edge to resize it, from 360px up to 700px. Your browser keeps the width. In a narrow window, the aside shows under the timeline.

Live updates

The ticket page updates on its own while it is open. You do not need to reload it to see a change made by Risotto, a teammate, or a connected ticketing system. This covers the status, assignee, title, priority, department, and agent state, plus new comments and internal notes, tool calls, workflow actions, tags, and CC participants. The page checks for changes again each time it reconnects, so a gap while your computer was asleep is filled in.

Ticket aside

The ticket aside is the column beside the timeline. In the Inbox, the same aside opens beside the timeline, with an Assistant tab next to Ticket History. On the ticket page, the Assistant opens in the docked panel as Team chat instead.

The aside has two sections. Every field keeps its controls, so you change the status, priority, assignee, category, or department from its row.

SectionWhat it holds
PropertiesThe ticket's own fields, one per row. See the list below.
Additional fieldsThe department's additional fields, with the number of fields in the header. The section shows only when the department has fields.

Properties has these rows, in this order until you move them:

  • Status, Priority, Assignee, Category, Department
  • Requested by (or External sender)
  • Tags
  • CC recipients, on email tickets and tickets with CC participants
  • Request source: the Slack channel, the email address the request was sent to, the Jira project, or Public API
  • Feedback, once the requester rates the ticket
  • Created, and Resolved with the time to resolve
  • Response SLA and Resolution SLA, when the department has ticket SLAs on
  • Runbook (or Runbooks): the runbooks the agent followed, and Also matched for the other runbooks matched to the ticket. When the agent followed none, the row is Matched runbooks. Point at a runbook to see its version, when and why the agent followed it, and the approvals its steps asked for.

On an email ticket, click Add participant under CC recipients to copy another email address on the ticket's replies. Click a CC recipient to copy their ID or remove them.

Change a field

You can change a ticket's fields when you are an Agent or a Supervisor of its department.

  1. Open the field's menu

    In the Properties section, click the value of Status, Priority, Assignee, or Category. A menu opens with a search box.

  2. Choose the new value

    Click the new value. The change saves right away.

  • Status lists every status except Awaiting approval, which only the approval flow sets. While a ticket waits for an approval, you can only move it to Resolved or Closed.
  • Priority and Category end with a sparkles icon when the AI set the value and nobody changed it. In the Category menu, the AI's choice is marked AI-suggested.
  • Assignee shows Add an assignee when nobody owns the ticket.
  • Department moves the ticket. See Moving a ticket to another department.
  • On a resolved ticket, Tags has an Auto-Solved button that adds the Auto-Solved tag, and the tag has an x that removes it, each after a confirmation. Add the tag when Risotto solved the ticket with no human help. Remove it when Risotto did not.

Collapse a section

Click a section header to collapse the section. Click it again to expand it.

Move a row

Each row of Properties has a grip at its left edge, labeled Move and the row's name. The grip shows when you point at the row or move keyboard focus to it. On a touch screen it always shows. The SLA rows move together.

  • Drag: press the grip and move the row up or down. A line shows where it will drop.
  • Menu: click the grip to open its menu, then choose Move to top, Move up, Move down, or Move to bottom. The menu lists only the moves the row can make. With the keyboard, move focus to the grip and press Enter to open the menu.

After a move, the row flashes in its new place and a screen reader announces its new position. Properties always stays first.

Reset the layout

Click any grip and choose Reset layout. The rows return to their default order, and every section expands.

Timeline

The timeline lists everything that happened on the ticket, oldest first:

  • Comments: the requester's messages and every reply. The header says where each one was posted: "commented in Slack" (point at Slack to see the channel), "commented in Jira" or another ticketing system, "sent via" an email address with the sender and any To and CC addresses, "commented via API", or "commented in Risotto" for a reply written in the dashboard.
  • Internal notes: notes your team wrote, and notes Risotto added for your team, in a light-yellow card. The requester never sees them.
  • Risotto's steps, tool calls, and action cards: see Stream of consciousness, Tool calls and approvals, and Action card.
  • Attachments: files sent with a comment show under it. Click an image to open it in a viewer, or a file to download it. While Risotto scans a file for malware, it shows Scanning and you can't open it. A clean file shows a shield icon. A file shows Malware found when the scan found a threat, and Not scanned when it could not be scanned, for example because it is password-protected. You can't open a file with malware.

Reply or add an internal note

The reply box is at the end of the timeline. You can reply or add a note when you are an Agent or a Supervisor of the ticket's department.

  1. Write your message

    Click the reply box and type. The toolbar formats the text as Markdown, and Preview shows how it will look. To attach files, click the paperclip. You can attach up to 10 files, and up to 25 MB in total.

  2. Choose who sees it

    Click the arrow next to Send and choose Send reply or Send internal note. On an email ticket, the choices are Send to all (when the ticket has CC recipients), Send to requestor, and Send internal note.

  3. Send it

    Click Send, or press ⌘Enter on a Mac. For an internal note the box turns yellow, says Only visible to your team, and the button is Send note. On an email ticket, the button is Send to all or Send to requestor.

A reply goes to the requester where they asked:

  • In the ticket's Slack or Microsoft Teams thread, with your name and picture.
  • By email from the department's support address, for an email ticket. See Email.
  • To the synced ticketing system, such as Jira, as a comment.

A reply also posts in the ticket's thread in the agent channel. The timeline does not show where a reply was delivered. After a reply, the ticket moves to Awaiting response, unless it is resolved, closed, a duplicate, paused, or waiting for an approval. An internal note stays with your team: it shows on the ticket and, with a lock icon, in the ticket's thread in the agent channel.

To have Risotto answer, click Mention Risotto (the @ button in the toolbar) in a reply. If Risotto had stopped working on the ticket, for example after an escalation, the mention turns it back on.

Remove a comment

An Org Admin can remove a comment or an internal note from the timeline, for example when someone posted a password. Hover the comment and click the trash button (Remove comment or Remove note) beside its time. The dialog Remove this comment? reads "Risotto removes its text and attachments from this ticket. You can't restore it. Copies in Slack, Teams, email, or a ticketing system such as Jira are not deleted. Delete them there separately." Click Remove comment to confirm.

  • The comment keeps its author and time. Its text and attachments are replaced by "An admin removed this comment on" and the date.
  • Risotto does not send a removed comment by email, quote it in later email replies, or sync it to a ticketing system.
  • Copies that were already sent stay where they are. Delete the Slack or Teams message, the email, or the Jira comment yourself.
  • Managers, Members, and department roles cannot remove comments.

Stream of consciousness

Risotto records the steps it took in the background before each reply. This shows how it reached its answer.

The steps fold into a line at the top of the Risotto reply they led to, for example Worked through 5 steps. Click the line to expand it: one row per step, each with an icon. For a knowledge question the steps look like:

  • Searching for sources with query: "MacBook models available to order"
  • Examining Laptop ordering guide...
  • Examining Hardware refresh policy...
  • Refining answer...
  • Verifying sources...

When Risotto took steps but posted no reply, for example because it escalated the ticket, the line stands on its own in the timeline. Progress indicators such as "Taking a look now..." are not steps and are not listed. The line is not an internal note and has no yellow tint.

Tool calls and approvals

Each tool that Risotto runs shows as a card with Tool, the tool's name, and ok or failed. Click Parameters to see what Risotto sent, and Output to see what came back. When someone approved the call, an Approval row shows who approved it and when.

When a tool needs approval before it runs, the timeline shows an Action entry with a Tool approval card. The card has an Awaiting Approval badge, the Tool, its Parameters, and Expires at, 7 days after the request. Agents and Supervisors of the ticket's department can decide from the dashboard, whatever channel the ticket came from.

  1. Check the parameters

    Read the Parameters to see exactly what the tool will do.

  2. Approve or deny

    Click Approve to run the tool, or Deny to decline it.

The card then says, for example, "dana.whitfield@northwind.com approved this". Risotto runs the tool, or not, and goes on with the ticket. If the request did not go through, the Approve and Deny buttons come back so you can try again.

While a ticket waits for an approval, Reprocess ticket and Escalate ticket are not available.

The page header opens the ticket in each linked system. The chat link shows Slack or Teams, and the ticketing link shows the external ticket key with the system's logo, for example ITSD-1042, for Jira, Linear, Zendesk, or another ticketing system. Hover a link to see where it goes, for example Open in Slack or Open in Jira. Each one opens in a new tab. The ticket menu lists the same links.

Action card

When Risotto handles an access request, the timeline shows an Action entry with a card for the request.

The card's title is the kind of request: Access grant, Access revocation, or General request. An access grant or revocation links to its access grant page. Next to the title is the request's status, for example Solved, Awaiting Approval, or Denied, and on the right is the person who gets the access. Below them, the card shows the details that apply:

  • Escalated to: the person the request was escalated to
  • Matched rule: the access rule that matched, linked to its settings
  • Matched application: the application, linked to its settings
  • Reason: the reason the requester gave
  • Duration: how long the requester asked for the access
  • Reminds at, Expires at, Last reminded: for time-limited access
  • Revoked at: when the access was removed

When an Opal or Okta Identity Governance rule handles the request, the card has a via Opal or via Okta OIG badge, with Access type, Resource, and a link to the request in that system.

Once per ticket, Risotto looks for the requester's other recent activity: up to 2 open tickets in the same department, and up to 2 pending campaign tasks, from the last 7 days. If it finds any, it adds an internal note to the ticket, for example "I noticed that Owen also recently opened 1 other ticket:", followed by each ticket's ID and title (for example [IT-144]: Monitor for my 4th-floor desk) and each campaign by name. Risotto posts the same message in the ticket's thread in the agent channel.

Risotto also adds an internal note to each of those earlier tickets that links to the new one, for example "Owen also opened: [IT-153] Figma access for the brand refresh".

Ticket actions

The ⋯ button after the ticket ID in the page header opens the ticket menu. It lists every ticket command, the same list as a right-click on a ticket row: open the ticket in Slack, Teams, or your ticketing system, copy its ID or link, and change it. See Ticket commands. The commands that you see depend on your role. On the ticket page, the menu does not show Open ticket, because you are already on the ticket. In the Inbox, the same menu is in the detail pane's header.

Reprocess or escalate

Open the ticket menu and choose:

  • Reprocess ticket (r): asks Reprocess ticket? Click Confirm, and Risotto evaluates the ticket again with your current setup. Use it to retry a ticket that got stuck, or after you change an access rule or runbook. Risotto posts a response in the thread, which can take up to a minute. See Reprocessing a ticket.
  • Escalate ticket (e): asks Escalate ticket? Risotto tags the department's escalation user or group, marks the ticket escalated, and moves it to Awaiting support. Reason (optional) starts with "Escalated from the Risotto dashboard." Click Confirm.

Both need you to be an Agent or a Supervisor of the ticket's department. The ticket's other commands, such as Resolve ticket (d) and Assign to me (i), are in the same menu and in the command menu.

Moving a ticket to another department

Pick a new department for the ticket in the dashboard, or choose Move to another department on the ticket card in Slack. In the dashboard, you can also use the Move to department… command. See Ticket commands.

  1. Choose the department

    In the aside's Properties section, click Department and choose the new department.

  2. Confirm the move

    The dashboard shows Move ticket to <department>? with what changes, then click Move ticket.

The confirmation can list these changes:

  • The ticket's thread in the agent channel moves to the new department's channel. Replies in the old thread are ignored.
  • The sync with your ticketing system stops, starts, or changes. A synced ticket is closed in the old system and stays there for reference, and a new one is created in the new system.
  • The category is cleared, and Risotto picks one from the new department's categories.
  • Who can access the ticket changes. The dialog lists up to 10 people who lose access and 10 who gain it.

When nothing important changes, it says "No significant changes detected. The department will be updated." After the move, the ticket can get a new ID from the new department, and the page opens it under that ID.

In Slack, the dialog is Confirm Department Change and the button is Confirm Changes.

Both places have the checkbox Activate Risotto to respond with new department. It is off by default.

  • Off: Risotto moves the ticket and does not reply.
    • If the new department is a top-level department, nothing else changes. An escalated ticket stays escalated.
    • If the new department is a sub-department, Risotto escalates the ticket there with the sub-department's own escalation rules. A person who already owns the ticket stays the assignee, unless an escalation rule of the sub-department assigns someone else.
  • On: Risotto hands the ticket back to the agent. It clears the escalation (including the Escalated tag), and Risotto responds on the ticket in its new department. After that reply, the ticket waits for the requestor, so the department's nudge and auto-resolve apply if nobody answers.

Something wrong or missing? Report an issue · View as Markdown