# Request Sources

See every Slack channel, Teams channel, email inbox, Jira project, Freshservice agent group, and ServiceNow assignment group that creates Risotto tickets, and change each one's settings

Risotto creates tickets from the sources on **Settings > Request Sources**. The page has one card for each connected integration that creates tickets: Slack, Microsoft Teams, Email, Jira, Freshservice, and ServiceNow. The Email card is always shown. The other cards show once their integration is connected.

Each card lists its sources. A row shows the source's name, the settings that differ from the defaults, such as **Silent mode** or **Continue over DM**, and the department its tickets go to when the source is locked to one. A source that does not create tickets shows **Paused** (an email inbox with **Create tickets** off) or **Off** (Slack App Home with no departments). The card's header counts the sources and the departments they are locked to.

> **Note:** Only Org Admins and Managers see the **Request Sources** page. A user whose
> org role is Member cannot open it, so they cannot see an inbox's **Forwarding
> Address**. Ask an Org Admin to copy the address for you, or to change your
> role. See [Permissions](https://www.tryrisotto.com/docs/operating/permissions).

## Change a source

The cards are read-only. You add, remove, and change sources on each integration's page.

1. **Open Request Sources**

   In the dashboard, go to **Settings > Request Sources**.

2. **Open the integration**

   On the source's card, click **Manage in \<integration>**, for example **Manage in Slack**. The integration's page opens on its **Requests** tab, where the settings below are.

   *Product example: Settings, Request Sources: the Slack, Microsoft Teams, Email and Jira cards, with Manage in Slack.*

## Slack channels

The Slack card lists **App Home**, **Direct Messages**, and every channel Risotto is in. Public channels show a `#` and private channels show a lock. On Slack's **Requests** tab, the **Slack channels** card lists the same channels, and each row opens to show its settings. The tab also has the **App Home** card and the **Slack Reactions** card. See [Slack reactions](https://www.tryrisotto.com/docs/operating/slack-emojis) for the reactions.

### Add a Slack channel

1. **Open Slack's Requests tab**

   On **Settings > Request Sources**, click **Manage in Slack**.

2. **Click Add Channel**

   On the **Slack channels** card, click **Add Channel**.

3. **Pick the channel**

   In **Channel**, search for a public channel and pick it. You can also paste a channel ID.

4. **Join the channel**

   Click **Join Channel**. Risotto joins the channel and the toast "Successfully joined channel" shows.

   *Product example: The Add Channel dialog on Slack's Requests tab, with #onboarding-forms picked and Join Channel.*

**Add Channel** joins public channels only. To add Risotto to a private channel, invite the Risotto app to the channel in Slack. The channel then shows on the **Slack channels** card.

A new channel starts with **Silent mode** on, so Risotto does not answer in it until you turn **Silent mode** off. See [Initial Slack channel setup](https://www.tryrisotto.com/docs/guides/initial/slack-helpdesk) for the full flow.

To stop Risotto from monitoring a channel, open the channel's row and click **Remove from channel**, then **Continue**. Risotto leaves the channel. You can invite it back later.

### Channel settings

Open a channel's row on the **Slack channels** card to see its settings. Each switch saves when you click it, and the toast "Channel setting updated" shows.

*Product example: Slack's Requests tab with the #it-help channel open: its switches and Lock to department set to IT.*

Some settings turn others off or hide them, so a row shows only the settings that apply:

- **Continue over DM**: Redirect all requests to private message. Requires an agent channel to be set on the department. Hidden while **Silent mode** is on. While it is on, **Silent mode**, **Prompt for escalation**, and **Ticket everything** are hidden.
- **Prompt for escalation**: Risotto asks the requestor for confirmation before it escalates to a human, with the buttons **Yes, escalate** and **No, cancel**. This setting does not change when Risotto creates a ticket, or which tickets sync to your ticketing system. Risotto does not ask when it escalates because a runbook step cannot be done as written, or because an action it took was a mistake.
- **Silent mode**: Stop Risotto from replying to questions. Risotto ignores new messages in the channel unless the message mentions Risotto or someone reacts with the ticket emoji. On for a new channel. While it is on, **Continue over DM**, **Prompt for escalation**, and **Ticket everything** are hidden.
- **Ticket everything**: Create tickets from every message in this channel, bypassing the usual request detection. Short greetings such as "Hi team" are ticketed too. Messages posted by bots on the channel's **Bot allowlist** are ticketed as well.
- **Bot allowlist**: Shown when **Ticket everything** is on. The Slack apps and bots whose messages create tickets in this channel. See [Ticketing bot messages](#ticketing-bot-messages).
- **Do not remember resolved threads**: Off by default. When on, Risotto does not save the channel's resolved threads as knowledge it can search for later answers.
- **Keep thinking steps**: On by default. When Risotto finishes a turn, its [thinking steps](https://www.tryrisotto.com/docs/concepts/ticket-lifecycle#thinking-steps) stay in the thread, collapsed above the answer. The first plan shows the ticket number. Turn it off to remove the steps when Risotto answers. The **Direct Messages** row has this setting too, and a plain direct message uses it. A conversation that **Continue over DM** moved to a direct message uses the setting of the channel where it started.
- **Lock to department**: All requests in this channel will be classified under this department. Pick a department in **Select a department...**. To unlock the channel, click the **x** next to the department.

You set these switches for each channel, so you can turn on **Continue over DM** for as many channels as you like. A channel that you add starts with **Silent mode** on. While **Silent mode** is on, the **Continue over DM**, **Prompt for escalation**, and **Ticket everything** switches are hidden. Turn off **Silent mode** to show them. **Silent mode** and **Continue over DM** cannot be on at the same time: while **Continue over DM** is on, **Silent mode** is hidden. In a silent channel, a :ticket: reaction still creates a ticket, and Risotto answers in the channel thread.

With **Continue over DM** on, Risotto opens a direct message with the requestor and continues the conversation there. The DM starts with "I'm here to assist with your request", where "your request" links to the original message, so Slack shows the original post as a forwarded message. Below it, a threaded reply tags the requestor and asks them to reply in that thread. When Risotto cannot build the link, or when the DM goes to a person tagged in someone else's message, the DM quotes the request text instead.

Risotto also replies in the channel thread to say that it will continue in a DM. Your team's replies in the agent channel go to the DM.

- The setting applies when Risotto creates a ticket. If you turn it off, tickets that already moved to a DM stay in the DM.
- After a ticket moves to a DM, Risotto ignores new replies in the original channel thread. It does not add them to the ticket. Ask the requestor to reply in the DM.

### Direct messages

The **Direct Messages** row covers messages that people send to Risotto directly. It has no **Silent mode**, **Continue over DM**, **Ticket everything**, or **Remove from channel**. It has one setting of its own:

- **Disable DM disambiguation**: Off by default. When someone who already has an open request sends Risotto a new direct message, Risotto checks whether the message is about that request. Turn this on to skip the check: each new direct message creates a new request.

### Ticketing bot messages

By default, Risotto does not process a message that another Slack app or bot posts. This stops two bots from replying to each other without end. To create a ticket from one bot message, react to it with the ticket emoji (`:ticket:` by default), or mention Risotto in a reply in its thread. See the [Slack reactions](https://www.tryrisotto.com/docs/operating/slack-emojis).

To ticket every message a bot posts, such as a form or workflow that posts requests into a channel, turn on **Ticket everything** for the channel and add the bot to the channel's **Bot allowlist**:

1. **Open the channel**

   On **Settings > Request Sources**, click **Manage in Slack**. On the **Requests** tab, open the channel's row.

2. **Turn on Ticket everything**

   Turn on **Ticket everything**. The **Bot allowlist** row appears below it, with "Bot messages will be ignored."

3. **Click Add bot**

   Click **Add bot**. The list shows **Bots in this channel**: the apps and bots that are members of the channel.

4. **Pick the bot**

   Click a bot to add it. The toast "Bot allowlist updated" shows, and the bot shows below **Add bot**.

   *Product example: A channel with Ticket everything on, and the Bot allowlist's Add bot list open on the channel's bots.*

To add a bot that is not in the channel yet, paste its ID into the same search box and click **Add \<ID>**. Risotto accepts a member ID (starts with `U` or `W`), a bot ID (starts with `B`), or an app ID (starts with `A`). You can copy a member ID from the bot's Slack profile with **Copy link** or **Copy member ID**.

Only bots on the allowlist are ticketed. Every other bot's messages in the channel are ignored, and an empty allowlist ignores all bot messages. Remove a bot by clicking the **x** on its entry.

When an allowlisted bot posts a new message in the channel:

- Risotto creates a ticket with the bot as the requestor. The bot's name appears on the ticket and on the first comment. A bot has no email address, so anything that needs the requestor's email, such as looking the requestor up in your identity provider, is skipped.
- Only top-level messages create tickets. A bot's replies inside a thread, edits, file uploads, and channel events such as topic changes are not ticketed.
- The channel's requestor domain filter does not apply to bot messages.
- In a channel with **Continue over DM** on, Risotto looks for a user mentioned in the bot's message and continues over DM with that person as the requestor. If the message mentions no one, Risotto cannot open a DM with a bot, so it escalates the ticket to your team right away.

> **Note:** Slack Workflow Builder posts all of its messages from one shared workflow bot.
> Allowlisting that bot admits every workflow that posts in the channel.

### Requests that link to a Slack message

If a new request links to another Slack message, Risotto reads that message and adds a quote of it to the request. The quote starts with "Linked Slack message in #channel:" and shows the message, the first message of its thread, and the replies near it. The agent, the ticket's first comment, and the synced ticket all see the quote, so a short request such as "can someone help with this?" plus a link has the full ask.

Risotto reads a linked message only if all of these are true:

- The message is in the same conversation as the request, or in a public channel. Risotto never reads a private channel, a DM, or a group DM.
- For a message in another channel, the requestor is a full member of your Slack organization (not a guest or a Slack Connect user), and Risotto is already a member of that channel. Risotto does not join a channel to read a message.

Risotto reads at most 3 links in one request, and at most 6 messages and 2,500 characters for each link. Mentions in the quote are plain text, so nobody is notified. If Risotto cannot read a link, it creates the ticket with the request as written. Risotto quotes links only in the message that starts a ticket, not in later replies.

### Messages that do not start a ticket

In a request channel, Risotto reads each new message and decides whether it is a request. Some messages are skipped before that decision:

- **A message addressed to a person or a user group.** A message that begins with an `@mention` of someone other than Risotto reads as chat between colleagues, so it does not open a ticket. This lets a team chat and file requests in one channel.
- **A message shorter than three characters.** "ok" and "+1" are ignored. Anything longer reaches the normal request check.
- **A message posted by another app or bot**, unless the channel has **Ticket everything** on and the bot is on its [Bot allowlist](#ticketing-bot-messages).
- **Any message in a channel with Silent mode on**, unless the message mentions Risotto.

To ticket a message Risotto skipped, react to it with the ticket emoji (`:ticket:` by default). This works for every case above, one message at a time.

To ticket every message instead, turn on **Ticket everything** for the channel. Risotto then tickets each message of three characters or more, including a message addressed to a colleague and any message from a bot on the channel's allowlist.

> **Tip:** Mentioning Risotto in the message also works. A message that mentions Risotto
> opens a ticket without the request check.

To ticket a thread that Risotto skipped, tag **@Risotto** in a reply in the thread. Risotto opens one ticket for the thread: the first message of the thread is the request, and its author is the requestor. Risotto answers in the thread, and later tags in the same thread use the same ticket.

### App Home

Employees can also create a request from Risotto's **Home** tab in Slack, where they pick the department the request goes to. The **App Home** card on Slack's **Requests** tab lists the departments that employees can pick. With no departments, the card shows "Not configured", and the Request Sources page shows App Home as **Off**.

- To add a department, click **Add Department**, pick a department, and click **Add**. Only top-level departments are listed. The button is unavailable when every top-level department is already on the card.
- To remove a department, open its row and click **Remove**.

## Microsoft Teams channels

Risotto handles requests from the Teams channels on its list and from direct messages. Before you add a channel, add the Risotto bot to the channel's team in Microsoft Teams. See the [Teams channel setup guide](https://www.tryrisotto.com/docs/guides/teams/teams-helpdesk) for the full flow.

1. **Open the Teams Requests tab**

   On **Settings > Request Sources**, click **Manage in Microsoft Teams**.

2. **Click Add Channel**

   On the **Microsoft Teams channels** card, click **Add Channel**.

3. **Pick the team and channel**

   Pick a **Team**, then a **Channel**, and click **Add Channel**. The channel is added with **Silent channel** on.

4. **Set up the channel**

   Open the channel's row and change its settings.

   *Product example: Microsoft Teams' Requests tab with the Ask IT channel open, with its Silent channel switch.*

Each channel has these settings:

- **Silent channel**: On for a new channel. Risotto stays silent and only engages when someone @mentions it in the channel. Turn it off to let Risotto respond to requests automatically.
- **Lock to department**: All requests in this channel will be classified under this department. Click the **x** next to the department to unlock the channel.

**Personal Chat** appears alongside your Teams channels and covers direct messages sent to Risotto. Direct messages work with no setup, so Personal Chat has no **Silent channel** switch. Set a department on Personal Chat to route all of them to one team. See [Creating Tickets from Microsoft Teams](https://www.tryrisotto.com/docs/operating/creating-tickets-teams).

## Jira projects

Risotto can create a ticket from each new issue in a Jira project. A Jira project is a request source for a department that already syncs tickets to that project. Set up ticket sync on the department first. See [Jira](https://www.tryrisotto.com/docs/integrations/ticketing/jira).

1. **Open Jira's Requests tab**

   On **Settings > Request Sources**, click **Manage in Jira**.

2. **Click Add Project**

   On the **Jira projects** card, click **Add Project**. The button is unavailable, with the tip "No departments with Jira ticket sync available", when no department can add one.

3. **Pick the department**

   In **Add Jira Request Source**, pick a **Department**. Each department is listed with the Jira project its ticket sync uses. A department that already has a Jira request source is not listed.

4. **Create the source**

   Click **Create**.

Several departments can use the same Jira project, each with its own issue type or request type filters. Open a project's row to change its settings:

- **Allowed Issue Types**: The Jira issue types that create tickets. Default is "All types allowed". Click the edit button to pick types. When the department's ticket sync sets an issue type, the row shows "(from dept settings)" and a lock, and you change it in the department's ticket sync settings.
- **Allowed Request Types**: Shown for a Jira Service Management project. The customer request types that create tickets. Default is "All types allowed".
- **Continue over DM**: Send a Slack DM to the requestor when a ticket is created from this Jira project.

To stop listening for new issues from a project, click **Disconnect**, then **Disconnect** in the dialog. This cannot be undone.

## Email inboxes

Risotto creates a ticket from each email that is forwarded to an inbox's forwarding address.

1. **Open the Email Requests tab**

   On **Settings > Request Sources**, click **Manage in Email**.

2. **Click Add Email Address**

   On the **Email inboxes** card, click **Add Email Address**.

3. **Fill in the inbox**

   In **Add Email Source**, enter the **Support Email Address** that people send requests to, and pick the **Department** its tickets go to. Turn on **Allow External Senders** to accept email from outside your organization.

4. **Create the inbox**

   Click **Create Email Source**. Risotto creates the inbox and its forwarding address.

5. **Copy the forwarding address**

   Open the inbox's row and click **Copy** next to **Forwarding Address**. Set up your email provider to forward the support address's email to it.

   *Product example: Email's Requests tab with the it\@northwind.com inbox open, with Copy next to its forwarding address.*

For the forwarding setup in your email provider and the details of each setting, see [Email](https://www.tryrisotto.com/docs/integrations/ticketing/email). Each inbox has these settings:

- **Create tickets**: On by default. Open a ticket for each new email. When off, emails that are not part of an existing thread are ignored, and the Request Sources page shows the inbox as **Paused**.
- **Support Address**: The customer-facing email address that people send requests to.
- **Forwarding Address**: Forward customer emails to this address to create tickets. Risotto generates it. Click **Copy** to copy it.
- **Lock to department**: All requests received via this address will be classified under this department.
- **Allow external senders**: Accept emails from senders outside the organization. Off by default. When off, Risotto drops an email from a sender who is not a known member of your Slack workspace, with no ticket and no bounce.
- **Allow forwarded sender as requestor**: Open the ticket for the original sender of a forwarded email when a known Risotto user forwards it and the email passes SPF.
- **Open a new ticket when a new sender replies**: Off by default. When someone who is not the requestor or a current participant replies to an email thread, Risotto creates a new ticket instead of adding the reply to the existing ticket.
- **Continue over DM**: Send a Slack direct message to the requestor when a ticket is created from this inbox.
- **Include quoted history**: Quote the earlier comments below each email reply, including messages from before the current recipients were added.
- **Track CC recipients**: Record the To and CC recipients of the first email as CC recipients on the ticket and copy them on replies.
- **Send from support address**: Send replies from the support address instead of `notifications@tryrisotto.com`. Read-only; contact Risotto support to turn it on.

## Freshservice and ServiceNow

When Freshservice or ServiceNow is connected, its card lists the agent groups or assignment groups that create Risotto tickets. On the integration's **Requests** tab:

- **Freshservice agent groups**: Click **Add Agent Group**, pick a **Workspace**, an **Agent Group**, and a **Department**. See [Freshservice](https://www.tryrisotto.com/docs/integrations/ticketing/freshservice#request-sources).
- **ServiceNow assignment groups**: Click **Add Assignment Group**, pick a **Department**, and enter the **Assignment Group** name as ServiceNow shows it. Leave **Assignment Group** blank to listen to all assignment groups. See [ServiceNow](https://www.tryrisotto.com/docs/integrations/ticketing/servicenow).

Each group has these settings:

- **Silent mode**: Tickets or incidents created from this group are not imported into Risotto. In ServiceNow, an incident that is assigned to Risotto's ServiceNow service account is still imported.
- **Continue over DM**: Send a Slack DM to the requestor when a ticket is created from this source.
- **Department**: All requests received via this source will be classified under this department. Only departments with Freshservice or ServiceNow ticketing on are listed.
- **Disconnect**: Remove the source. Risotto stops listening for new tickets or incidents from the group. This cannot be undone.

Source: https://www.tryrisotto.com/docs/dashboard/settings/request-sources
