# Creating Tickets from Slack

How requests in Slack become Risotto tickets: request channels, the ticket reaction, direct messages, the Create a ticket shortcut, and the App Home.

> **Info:** Using Microsoft Teams? See [Creating Tickets from Microsoft
> Teams](https://www.tryrisotto.com/docs/operating/creating-tickets-teams) for how Teams channels and
> direct messages create tickets. Emoji commands such as 🎫 are not yet
> supported in Teams.

Risotto tracks every request as a ticket, from the first message until the request is resolved. In Slack, a ticket starts in one of these ways:

- An employee posts a request in a [request channel](#post-in-a-request-channel).
- Someone reacts to a message with 🎫 (`:ticket:`), for example in a channel in [Silent mode](#pick-requests-with-silent-mode-and-the-ticket-reaction).
- An employee [sends Risotto a direct message](#send-risotto-a-direct-message).
- You turn a direct message you received into a ticket with the [Create a ticket shortcut](#turn-a-direct-message-into-a-ticket).
- An employee starts a request from the [Risotto App Home](#start-a-request-from-the-app-home).

A ticket's ID starts with its department's prefix, for example `IT-142`. Every ticket appears under **Tickets > All** in the dashboard.

> **Tip:** To sync tickets to an external ticketing system, see [Ticketing
> integrations](https://www.tryrisotto.com/docs/dashboard/settings/integrations#ticketing).

## Post in a request channel

A request channel is a Slack channel that Risotto is in, with **Silent mode** off. To set one up, see [Initial Slack channel setup](https://www.tryrisotto.com/docs/guides/initial/slack-helpdesk).

### What the requester sees

The employee posts their request in the channel. Risotto reads each new message and decides whether it is a request. If it is, Risotto creates a ticket and replies in the message's thread. While it works, its steps show in the thread, starting with the ticket's creation, for example "Creating ticket IT-142: Laptop not charging". When it answers, the steps stay above the reply, collapsed under "Created ticket IT-142". See [Thinking steps](https://www.tryrisotto.com/docs/concepts/ticket-lifecycle#thinking-steps).

*Product example: A Slack thread in #risotto-requests-test, in outline: Priya asks for help with a laptop that won't charge, and Risotto replies after creating ticket IT-142.*

The requester continues the conversation by replying in the thread.

Some messages never start a ticket, such as a message that begins by mentioning a colleague, or one shorter than three characters. See [Messages that do not start a ticket](https://www.tryrisotto.com/docs/dashboard/settings/request-sources#messages-that-do-not-start-a-ticket).

### What your team sees

Risotto posts each new ticket in the agent channel of the ticket's department. The post starts with the ticket ID, which links to the ticket in the dashboard, and the title, which links to the original message, followed by the channel the request came from. Slack shows the requester, the department, and the request with it. The conversation with the requester follows in the post's thread.

*Product example: Risotto's post for ticket IT-142 in #risotto-agents-test, in outline: the ticket ID and title, the requestor and department, the request, and a thread of 3 replies.*

If the ticket's department has no agent channel, Risotto posts in the agent channel of your default department. To set a department's agent channel, see [Connect the agent channel to a department](https://www.tryrisotto.com/docs/guides/initial/slack-helpdesk#connect-the-agent-channel-to-a-department).

### Settings that change when a channel creates tickets

Each request channel has its own settings. In the dashboard, go to **Settings > Request Sources**, click **Manage in Slack**, and open the channel's row on the **Requests** tab. These settings change when and where tickets start:

- **Silent mode**: Risotto does not reply, and opens a ticket only for a message that mentions it or has the ticket reaction. See [Pick requests with Silent mode and the ticket reaction](#pick-requests-with-silent-mode-and-the-ticket-reaction).
- **Ticket everything**: Every message becomes a ticket, without the request check.
- **Continue over DM**: Risotto moves each conversation to a direct message with the requester.
- **Lock to department**: Every ticket from the channel goes to one department.

For every channel setting, see [Channel settings](https://www.tryrisotto.com/docs/dashboard/settings/request-sources#channel-settings).

## Pick requests with Silent mode and the ticket reaction

In a channel with **Silent mode** on, Risotto does not reply to messages or open tickets on its own. It opens a ticket only when a message mentions **@Risotto**, or when someone reacts to a message with 🎫. Use Silent mode in a channel your team already answers, so that Risotto handles only the requests you pick. A channel you add to Risotto starts with Silent mode on.

1. **Turn on Silent mode**

   In the dashboard, go to **Settings > Request Sources** and click **Manage
   in Slack**. On the **Requests** tab, under **Slack channels**, click the
   channel's row to open it, and turn on **Silent mode**. The message "Channel
   setting updated" confirms the change. While Silent mode is on, the row
   hides **Continue over DM**, **Prompt for escalation**, and **Ticket
   everything**.

   *Product example: Slack's Requests tab in the Risotto dashboard with #risotto-requests-test open and the Silent mode switch on.*

2. **React with 🎫 to the request**

   In Slack, add a 🎫 (`:ticket:`) reaction to the message that starts the
   request. Risotto creates a ticket and replies in the thread. The author of
   the thread's first message is the requester. A **Thinking...** line shows
   under the thread first, then Risotto's steps, starting with "Creating
   ticket IT-143: …".

   *Product example: A Slack thread in #risotto-requests-test, in outline: Marcus's question has a ticket reaction, and Risotto replies after creating ticket IT-143.*

- Anyone can add the reaction. Risotto ignores it in an agent channel and on a thread that already has a ticket.
- The reaction works in any channel Risotto is in, not only in Silent mode. Use it to ticket a message that Risotto skipped, such as a message from another app.
- To ticket a whole thread instead, mention **@Risotto** in a reply in the thread. The thread's first message is the request, and its author is the requester.

> **Warning:** If another app in your workspace also acts on 🎫, change Risotto's ticket
> emoji, for example to 🎟️ (`admission_tickets`). See [Change an
> emoji](https://www.tryrisotto.com/docs/operating/slack-emojis#change-an-emoji).

For the other reactions Risotto understands, see the [Slack reactions](https://www.tryrisotto.com/docs/operating/slack-emojis).

## Send Risotto a direct message

Employees can send the Risotto app a direct message in Slack. Risotto opens a ticket for each new direct message and answers in the message's thread.

*Product example: Marcus's direct message to Risotto in Slack, in outline: his VPN keeps disconnecting, and Risotto replies in the thread after creating ticket IT-141.*

When an employee who already has an open request sends a new direct message, Risotto checks whether the message is about that request. If it might be, Risotto asks in the new message's thread "It looks like you have an open request: … Is this a new request or related to that one?", with the buttons **New request** and **It's related to the open request**. The question names the open request and links to its thread.

*Product example: A new direct message from Marcus to Risotto, in outline, and Risotto's question in its thread: It looks like you have an open request, with the New request and It's related to the open request buttons.*

To skip the question and always open a new ticket, turn on **Disable DM disambiguation** on the **Direct Messages** row. See [Direct messages](https://www.tryrisotto.com/docs/dashboard/settings/request-sources#direct-messages).

## Turn a direct message into a ticket

When someone sends you a request in a Slack direct message, you can turn their message into a Risotto ticket with Risotto's **Create a ticket** shortcut. Risotto then continues the conversation with them in their own direct message with Risotto.

> **Warning:** If you use a custom Slack app, update it first. See [Update the Slack
> app](https://www.tryrisotto.com/docs/guides/update-slack-app).

1. **Open the message's actions**

   In the direct message, hover over the request and click **More actions**
   (the three dots at the end of the toolbar).

2. **Choose Create a ticket**

   Choose Risotto's **Create a ticket** shortcut. Slack shows the app's name
   under it.

   *Product example: A Slack direct message from Priya Shah, in outline, with the message's More actions menu open and Risotto's Create a ticket shortcut highlighted.*

   The **Create ticket** dialog opens. It says "@Risotto will create a ticket
   from this message and continue the conversation with \[name] via DM:" and
   quotes the message.

3. **Add a note (optional)**

   In **Additional information**, type a note for the requester. Risotto sends it
   to them privately, in the thread of their direct message, under your name. If
   you leave it empty, Risotto sends "I created this ticket for your request.
   Please reply to this DM here in the thread. Thanks!"

   *Product example: Risotto's Create ticket dialog in Slack, in outline: the quoted message from Priya, a note in Additional information, and the Skip auto-response option.*

4. **Skip Risotto's answer (optional)**

   Under **Options**, check **Skip auto-response** to create the ticket without
   Risotto answering the requester, so your team can answer instead. The ticket
   then waits for your support team.

5. **Click Create**

   Click **Create**. Risotto confirms with "Ticket IT-144 created
   successfully!", with the ticket ID linked to the ticket in the dashboard.
   Only you see the confirmation.

   *Product example: The direct message with Priya after Create, in outline: Risotto's message, only visible to you, says Ticket IT-144 created successfully!.*

### What the requester sees

In the requester's direct message with Risotto, Risotto posts "Hi \[name]! @\[you] created a ticket for your request:", quotes the request, and asks them to reply in the thread. Your note follows in the thread, under your name and photo, then Risotto's first answer, unless you checked **Skip auto-response**.

*Product example: Priya's direct message with Risotto, in outline: Risotto says Dana Reyes created a ticket for her request, then Dana's note and Risotto's first answer for IT-144.*

Like any other ticket, the ticket gets a post in the agent channel, and your note is added to the ticket and to the post's thread.

### Where the shortcut works

- The shortcut works in direct messages and group DMs. In a public channel, Risotto shows "This feature is currently only available for direct messages and group direct messages." Use the 🎫 reaction there instead.
- The shortcut works on a top-level message only. On a thread reply, Risotto shows "This feature is not currently available for thread replies."
- The requester is the person who wrote the message, not you.
- If your Slack workspace has more than one Risotto app, for example one for IT and one for Security, the menu shows one **Create a ticket** shortcut for each app. Each shortcut files the ticket in its own Risotto organization. Slack shows the app name under each shortcut, so give each app a different name to tell them apart (see [Create a new organization](https://www.tryrisotto.com/docs/guides/create-new-org)).
- The ticket needs an agent channel, either for its department or for your default department. Without one, Risotto does not create the ticket and shows "Unable to create ticket. Please configure an organization agent channel or one for the IT department."
- Risotto must be able to message the requester. If the message's author is a bot, a deactivated user, or a member of another Slack workspace, Risotto does not create the ticket and shows "Unable to create ticket: a direct message with the message sender could not be opened."
- Risotto cannot download files from a direct message it is not part of. If it could not copy every attachment, it asks the requester to send the files again in the thread.

## Start a request from the App Home

Employees can start a request from the **Home** tab of the Risotto app in Slack, and pick the department it goes to.

> **Warning:** If you use a custom Slack app, update it first. See [Update the Slack
> app](https://www.tryrisotto.com/docs/guides/update-slack-app).

### Choose the departments

1. **Open the App Home card**

   In the dashboard, go to **Settings > Request Sources** and click **Manage
   in Slack**. On the **Requests** tab, find the **App Home** card.

   *Product example: Slack's Requests tab in the Risotto dashboard: the App Home card listing IT, with the Add Department button highlighted.*

2. **Add a department**

   Click **Add Department**. In the **Add Department** dialog, pick a
   department under **Department** and click **Add**. The department shows as
   a row on the card. Repeat for each department employees can pick.

   *Product example: The Add Department dialog over the App Home card, with People picked and the Add button highlighted.*

Only top-level departments can be added. To remove a department, see [App Home](https://www.tryrisotto.com/docs/dashboard/settings/request-sources#app-home).

### What employees see

The **Home** tab shows a **Start a new request** button, then **Active requests**: the employee's open tickets, newest first, with their IDs and assignees.

*Product example: The Home tab of the Risotto app in Slack, in outline: the Start a new request button and two active requests with their IDs and assignees.*

The button opens the **Start a new request** form:

- **Associated department**: The departments on the **App Home** card, each with its description.
- **Service**: Shown when the department has items in the [Service Catalog](https://www.tryrisotto.com/docs/dashboard/settings/service-catalog#from-the-slack-app-home). Optional. Picking a service replaces the description with the service's own questions.
- **Description**: The request, in the employee's words.
- **Attachments**: Optional. Up to 10 files.

*Product example: The Start a new request form in Slack, in outline: IT as the associated department, a description, an empty Attachments field, and the Create button.*

The employee clicks **Create** to send the request, or **Cancel** to close the form.

If no department is on the **App Home** card, the **Home** tab shows only a short introduction to Risotto.

Source: https://www.tryrisotto.com/docs/operating/creating-tickets
