HELP-123. The whole conversation lives on the ticket and stays in sync with the Slack thread, Teams thread or email it started from, so your team and the requester never have to switch tools.
How tickets work
1
2
An AI agent can answer first
If the channel has an AI agent, it replies first, using your knowledge and tools. While the agent handles the conversation, the ticket stays unpublished: it has no number, it’s hidden from views, and notifications, SLAs and automations are paused. When the agent can’t resolve the request, it escalates and publishes the ticket to your team.
3
4
Your team works it
The assignee owns the ticket and followers stay informed. Reply to the requester, or leave a private note for your team. Break the work down with tasks, approvals and subtickets, while SLAs track response and resolution times.
5
It's resolved and closed
The ticket’s status moves from Open through In Progress and Waiting to Done and Closed. Archive tickets you no longer need in your lists.
The ticket page
Open a ticket in the web app to read and work everything about it on one page.Header
Banners
Incidents also show an incident header with their linked tickets.
Title and description
Click the title or description to edit it. Chips above the description show:- Source: where the ticket came from (Slack, Microsoft Teams, Email, Form, Ravenna, or an integration such as Jira or Linear). For Slack tickets, the chip opens the request thread.
- Subticket of: the parent ticket, when this ticket is a subticket.
- Ticket ID: click to copy it.
Tabs and sidebar
The tabs hold Subtickets, Tasks and Links by default, each with a count. The sidebar holds the sections below. Sections with no data stay hidden.Arrange sections
Drag sections between the sidebar and the tab row to put them where you work. For example, move Attributes into a tab, or Tasks into the sidebar. Ravenna saves the layout to your account and uses it on every ticket you open.Conversation
The conversation lists public replies, private notes and ticket activity (status changes, assignments, SLA events and more) in order. Each message shows where it was sent from, for example via Slack. Email replies show their Subject, To and Cc.Action dock
The dock at the bottom of the ticket holds:- Composer: press R for a public reply or P for a private note. Attach files with the paperclip and send with ⌘ + Enter. On incidents, check Send to all linked tickets to post to every linked ticket.
- Status and Assignee pickers (S and A).
- Archive, and Previous and Next to move through the view.
Actions menu
Open … in the header. The same actions are in the command launcher (⌘ + K).Format the description
In the web app
Select text in the description to open the formatting menu (Bold, Italic, Underline, Strikethrough, Code, Hyperlink), or type Markdown. HTML typed into the description stays as plain text.Through the API
When you create or update a ticket through the API, Ravenna storesdescription exactly as you send it and applies formatting when the web app displays the ticket. GET responses and webhooks return the same raw string you sent.
Markdown is the most reliable format. Basic HTML also works.
A recommended description:
description.md
jq --rawfile, so you don’t have to escape JSON by hand. queueId is the ID of the channel the ticket goes to:
Learn more about how tickets fit with workspaces, agents and workflows in Core concepts