Docs

Integrations / Ticketing

Email

Configure Risotto to create tickets automatically from support emails

Turn your support email into a powerful ticketing system by forwarding emails to Risotto. When customers email your support address, Risotto creates tickets and tracks resolution progress.

Prerequisites

Before setting up email ticketing, ensure you have:

  • Google Workspace Admin access - You'll need admin privileges to configure email routing
  • Risotto workspace configured - Your Risotto instance should be set up with team members and basic workflows
  • Risotto Org Admin or Manager role - Only Org Admins and Managers see Settings > Request Sources and the Email page that it opens, where the inbox and its Forwarding Address are
  • Support email address - The email address customers will use to contact support (e.g., support@yourcompany.com)

Risotto Configuration

To set up email ticketing in Risotto, you'll configure your email inbox directly in the dashboard:

  1. Access Request Sources

    1. Navigate to the Request Sources page in Settings 2. On the Email card, click Manage in Email 3. Look for the Email inboxes section
  2. Configure Email Inbox

    Click Add Email Address in the Email inboxes section. The Add Email Source dialog opens.

    1. Enter the Support Email Address (for example, support@yourcompany.com).
    2. Select the Department that receives tickets from this inbox.
    3. Turn on Allow External Senders if people outside your organization write to this address (see Inbox settings).
    4. Click Create Email Source.
  3. Get Forwarding Address

    After configuration, Risotto will provide you with a unique parsing email address that you'll use in your email provider setup below.

    Each configured inbox appears as an expandable row in the Email inboxes section, labeled with the support address and showing the department it routes to. Expand it to see these settings, among others:

    • Support Address — the customer-facing email address (for example, alexsupport@yourcompany.com).
    • Forwarding Address — the unique Risotto parsing address, shown as a long generated ID with a Copy button next to it. This is the address you'll forward customer emails to.
    • Lock to department: the department that tickets from this inbox are routed to (for example, People).

Inbox settings

Expand an inbox under Settings > Request Sources > Manage in Email > Email inboxes to change how it behaves. Each switch takes effect as soon as you flip it.

SettingWhat it does
Create ticketsOpen a ticket for each new email. When off, Risotto ignores emails that are not part of an existing thread.
Lock to departmentRoute every ticket from this inbox to the department you pick.
Allow external sendersAccept email from people outside your organization. Off by default. When off, Risotto drops an email from a sender who is not a known member of your Slack workspace: no ticket opens and the sender gets no bounce.
Allow forwarded sender as requestorWhen a known Risotto user forwards an email to the inbox, open the ticket for the original sender of the forwarded message. The forwarder stays on the ticket as a CC recipient. Applies only when the email passes SPF, the subject starts with Fwd: or Fw:, and the forwarder is a known member of your Slack workspace.
Continue over DMSend a Slack direct message to the requestor when the inbox opens a ticket, if the requestor has a linked Slack account.
Include quoted historyQuote the earlier comments below each reply Risotto sends by email, including comments from before the current recipients joined.
Track CC recipientsRecord the To and CC recipients of the email that opened the ticket as CC recipients on the ticket, and copy them on every reply. Off by default.
Open a new ticket when a new sender repliesOff by default. When on, a reply from a person who is not on the thread's ticket opens a new ticket for that person. The requestor, a current participant, and the assignee are on the ticket. A member of any department never gets a new ticket. The new ticket uses the reply's subject as its title and does not copy the reply's To and CC recipients. When Create tickets is off, the reply is added as a comment instead.
Send from support addressSend replies from your support address instead of notifications@tryrisotto.com. The switch is read-only. To turn it on, contact Risotto support. Risotto gives you two DNS records to add for your domain: a DKIM TXT record and a Return-Path CNAME record. When both records verify, Risotto turns the switch on. The setting applies to one inbox, so ask for each inbox that needs it.

Replies by email

When a ticket comes in by email, Risotto sends each public reply on that ticket, such as a reply that you post in the dashboard, to the requester by email. Internal notes are never sent by email.

When an email ticket escalates, Risotto does not email the requester. If the inbox has Continue over DM on, Risotto tells the requester in that DM. Otherwise the requester hears from your team when someone posts a public reply.

Risotto sends the reply through an email inbox of the ticket's current department. It uses the inbox that received the ticket when that inbox belongs to the department, and otherwise another inbox of the same department.

When a reply is not sent, admins get the warning Email reply not sent: no support email address on the Alerts page, and in your notifications channel if one is set up. Risotto sends this warning once for each department, until an admin dismisses it. Later replies that are not sent do not show a new warning.

To make sure that the requester gets your replies, do one of these before you reply:

  • Add an email inbox to the department that the ticket is in.
  • Move the ticket back to a department that has an email inbox.

Replies to a resolved ticket

When the requestor replies by email to a Resolved ticket, the ticket reopens and moves to Awaiting support. Replies to Closed tickets are added as comments and do not change the status. Replies from other senders are also added as comments, unless the inbox has Open a new ticket when a new sender replies on and the sender is not on the ticket. Then the reply opens a new ticket. See Reopening a finished ticket.

Email Provider Setup

Google Workspace Configuration

Overview

Google Workspace uses Email Forwarding with Recipient Address Mapping to route incoming emails to Risotto's parsing system. This method ensures emails are processed while maintaining copies in your original inbox.

  1. Access Google Admin Console

    1. Go to admin.google.com
    2. Sign in with your admin account
    3. Navigate to Apps → Google Workspace → Gmail
  2. Configure Email Routing

    1. In the Gmail settings, expand the Routing section (described as "Configure routing features"). Do not select Default routing, which appears just above it and is described as "Create domain-wide routing rules, such as for split delivery or a catchall address."
    2. Scroll down to Email forwarding using recipient address map
    3. Click Configure next to this option
  3. Set Up Address Mapping

    Basic Configuration:

    1. Check Apply forwarding to all incoming messages (recommended)
    2. Enable Also route to original destination to keep copies in your inbox
    3. Optionally enable Add X-Gm-Original-To header for tracking

    Add Your Mapping:

    The Edit setting dialog for Email forwarding using recipient address map opens with a name field at the top (for example, "Forward inbound HR requests to Risotto") followed by four numbered sections.

    1. Under 1. To forward emails, map original recipient to new recipient, click Add to create a row in the Address / Map to address table
    2. Address: Enter your support email (e.g., hr@yourcompany.com)
    3. Map to address: Enter the Risotto forwarding address (for example, abc123+456@post.tryrisotto.com, copied from the Risotto inbox settings above)
    4. Under 2. Messages to affect, choose All incoming messages or Only external incoming messages
    5. Under 3. Routing options, check Also route to original destination
    6. Under 4. Options, optionally check Add X-Gm-Original-To header
    7. Click Save
  4. Review and Activate

    1. Review your configuration settings
    2. Click Save to apply the routing rule

Understanding Recipient Address Mapping

How it works:

  • Incoming emails to your support address are automatically copied to Risotto
  • Original emails remain in your team's inbox (If "Also route to original destination" is enabled)
  • Risotto processes the forwarded emails and creates tickets
  • No disruption to your existing email workflow

Key benefits:

  • Seamless integration - Works with your existing email setup
  • No email loss - All emails are preserved in both systems
  • Bulk configuration - Map multiple email addresses at once
  • Flexible routing - Control which emails get forwarded

Advanced Configuration

Multiple Email Addresses: Use the Bulk Add feature to configure multiple support addresses:

support@yourcompany.com, abc123+456@post.tryrisotto.com
billing@yourcompany.com, abc123+456@post.tryrisotto.com
feedback@yourcompany.com, abc123+456@post.tryrisotto.com

Selective Forwarding:

  • Choose Apply forwarding to external incoming messages only to forward only customer emails
  • Use Apply forwarding to all incoming messages to include internal emails in ticket tracking
Microsoft 365 Configuration

Configuration overview:

  • Use Transport Rules in Exchange Admin Center
  • Set up mail flow rules for external forwarding
  • Configure recipient address mapping similar to Google Workspace

Testing Your Setup

  1. Send Test Email

    Send a test email to your support address from your own work account to check that the forwarding works. Use an outside account only if Allow external senders is on for the inbox; otherwise Risotto drops the email without a ticket.

  2. Verify Ticket Creation

    Check your Risotto dashboard to confirm that a ticket was automatically created from the test email.

  3. Test Email Preservation

    Confirm that the original email also appears in your support team's inbox as expected.

Troubleshooting

Common Issues and Solutions

Emails not forwarding:

  • Verify admin console configuration is saved
  • Wait up to 24 hours for Google Workspace changes to propagate
  • Check that email addresses are entered correctly

Tickets not created in Risotto:

  • Confirm Risotto email parsing endpoint is configured
  • Verify the forwarding email address matches Risotto settings
  • Check Risotto logs for parsing errors

Duplicate emails:

  • Ensure "Also route to original destination" setting matches your preferences
  • Review if multiple forwarding rules are conflicting

No ticket for an email from outside your organization:

  • Turn on Allow external senders for the inbox. When it is off, Risotto drops mail from anyone who is not a known member of your Slack workspace, with no bounce.

A person added to the email thread later does not get Risotto's replies:

  • Risotto copies only the recipients of the email that opened the ticket, and only when Track CC recipients is on.
  • Open the ticket in the dashboard and add the person under CC Recipients with Add participant.

The requester does not get a reply that you posted:

  • Check that the reply is public. Internal notes are not sent by email.
  • Check that the ticket's department has an email inbox. A ticket moved to a department with no inbox gets no email replies. See Replies by email.

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