Email handoffs
Enable your AI Agent to escalate email conversations to your human support team on your preferred agent platform. This guide outlines the handoff methods compatible with the Email channel, and provides step-by-step instructions for configuring each.
Handoff methods
Your AI Agent can create an email handoff using any of the following methods
- Zendesk Support: Facilitates a seamless transition of email conversations to human agents within Zendesk, maintaining the same email thread and sender address.
- Zendesk Ticketing: Creates customizable email tickets in Zendesk, allowing for detailed information capture and routing. Human Agents will need to use a different email address than the AI Agent for responding to end user escalations.
- Salesforce Case: Generates cases in Salesforce, transferring conversation details to your Salesforce environment. Human Agents will need to use a different email address than the AI Agent for responding to end user escalations.
- Email Systems: Forwards emails directly to a specified email address, without integration into a ticketing system.
Key Features
Configuration
To create a new handoff flow that applies only to Email conversations, set an availability rule on your handoff to apply when the channel is Email.

Zendesk Support

- Follow the linked steps to integrate and configure Zendesk Support with your AI Agent.
- In your handoff flow, drag the Zendesk Support block into your handoff.
- In the Zendesk Support block, configure the fields that are required to complete your handoff:
- Standby Message: An automated response that informs users when to expect a reply.
- If you do not set one, a default standby message will be sent: “An agent will be with you as soon as they can. You’ll be notified here when the agent responds”
- Group: A collection of agents organized by role or expertise to optimize ticket routing and management.
- Subject: The subject assigned to the ticket upon creation.
- If you do not set one, a default ticket subject will apply: “Conversation with chatter_ID”
- Zendesk Fields: Ticket fields that streamline workflow and routing, including subject, description, tags, priority, groups, and custom fields.
- Tags: Keywords applied to tickets based on detected topics or intent, helping with categorization, routing, and automation. You can use both variables and plain text for tags.
- Error Fallback: An automated response triggered if an error occurs while attempting to trigger the handoff, acknowledging the issue and guiding users on next steps.
- Standby Message: An automated response that informs users when to expect a reply.
Zendesk Ticketing

-
If you haven’t already, configure Zendesk Ticketing in your AI Agent.
-
In your handoff flow, in the block drawer on the right side of your screen, under Action Apps, click and drag the Fetch Chat Metadata block into your handoff. With the Fetch Chat Metadata block, you can save the chat transcript as a variable, so you can pass it along to the live agent.
- Under Select Variables for Inputs, beside Chatter Token, click inside the field and add the red chatter_token metavariable.
- Under Save Response as Variables, click the Select Optional Variables drop-down menu, then select any optional variables you’d like to capture:
-
Transcript and Summary: Select this option to save the conversation transcript and summary to a variable.
-
Transcript Only: Select this option to save just the conversation transcript to a variable.
-
Summary Only: Select this option to save just the conversation summary to a variable.
-
Chatter Info: Select this option to save the customer’s metadata to a variable. This is the same information available about the customer’s meta variables when you’re viewing a chat transcript.
- For each optional variable you selected, click the Choose a Variable drop-down menu, then select an existing variable, or create a new one, to capture the information.
- Under Fallback Answer, you can click to edit the AI Agent’s response if an error occurs.
-
In the block drawer, under Action Apps, click and drag the Zendesk Ticketing block into your handoff, below the Fetch Chat Metadata block.
- Follow the instructions in Use the Zendesk Ticketing app block, ensuring that you add any fields and variables you want to include in your tickets.
- Add the File Data Token field, and in that field, add the email_attachments variable to ensure that your AI Agent can pass any attachments to Zendesk.
- Turn on the Count as Handoff toggle to ensure your reporting is accurate.
-
Add any other custom messaging you want customers to receive during your handoff, and click Save. At the top of your screen, ensure your handoff toggle is set to Active so your AI Agent can start handing customers off as needed.
Salesforce Case

-
If you haven’t already, configure Salesforce actions in your AI Agent.
-
In your handoff flow, in the block drawer on the right side of your screen, under Action Apps, click and drag the Fetch Chat Metadata block into your handoff. With the Fetch Chat Metadata block, you can save the chat transcript as a variable, so you can pass it along to the live agent.
- Under Select Variables for Inputs, beside Chatter Token, click inside the field and add the red chatter_token metavariable.
- Under Save Response as Variables, click the Select Optional Variables drop-down menu, then select any optional variables you’d like to capture:
- Transcript and Summary: Select this option to save the conversation transcript and summary to a variable.
- Transcript Only: Select this option to save just the conversation transcript to a variable.
- Summary Only: Select this option to save just the conversation summary to a variable.
- Chatter Info: Select this option to save the customer’s metadata to a variable. This is the same information available about the customer’s meta variables when you’re viewing a chat transcript.
- For each optional variable you selected, click the Choose a Variable drop-down menu, then select an existing variable, or create a new one, to capture the information.
- Under Fallback Answer, you can click to edit the AI Agent’s response if an error occurs.
-
In the block drawer, under Action Apps, click and drag the Salesforce block into your handoff, below the Fetch Chat Metadata block.
- In the Select Action list, click Create Case.
- Beside Case Reason, add your transcript variable.
- Beside Name and Email Address, add the variables that contain that information.
- Add the File Data Token field, and in that field, add the email_attachments variable to ensure that your AI Agent can pass any attachments to Salesforce.
- Add any additional fields and variables you want to include in your cases.
- Turn on the Count as Handoff toggle to ensure your reporting is accurate.
-
Add any other custom messaging you want customers to receive during your handoff, and click Save. At the top of your screen, ensure your handoff toggle is set to Active so your AI Agent can start handing customers off as needed.
Email System

-
In your handoff flow, in the block drawer on the right side of your screen, under Action Apps, click and drag the Fetch Chat Metadata block into your handoff. With the Fetch Chat Metadata block, you can save the chat transcript as a variable, so you can pass it along to the live agent.
- Under Select Variables for Inputs, beside Chatter Token, click inside the field and add the red chatter_token metavariable.
- Under Save Response as Variables, click the Select Optional Variables drop-down menu, then select any optional variables you’d like to capture:
- Transcript and Summary: Select this option to save the conversation transcript and summary to a variable.
- Transcript Only: Select this option to save just the conversation transcript to a variable.
- Summary Only: Select this option to save just the conversation summary to a variable.
- Chatter Info: Select this option to save the customer’s metadata to a variable. This is the same information available about the customer’s meta variables when you’re viewing a chat transcript.
- For each optional variable you selected, click the Choose a Variable drop-down menu, then select an existing variable, or create a new one, to capture the information.
- Under Fallback Answer, you can click to edit the AI Agent’s response if an error occurs.
-
In the block drawer, under Action Apps, click and drag the Email block into your handoff, below the Fetch Chat Metadata block.
- In the Select Variables for Inputs section, complete the mandatory variable fields:
-
Recipient Email(s): Add the primary recipient email address. You can add the email variable, or manually enter the recipient’s email address. Separate multiple email addresses with a comma.
-
Reply-To Email: Enter the Reply-to email address you wish to assign to receive replies to your email.
-
Email Subject: Enter the email subject.
-
Email Content: Enter the body text of the email, including the email_transcript variable.
- Click the Select Optional Inputs drop-down menu, then select any optional variable fields you’d like to add:
-
File Data Token: Add the email_attachments variable to pass it on to the agent.
-
BCC Email(s): Add blind carbon copy recipient email addresses. BCC addresses are not visible to other recipients.
-
CC Email(s): Add secondary recipient email addresses. These addresses are visible to other recipients.
-
Content Type: Enter the MIME type you want to use in your email:
- If you just want to enter plain text, or if you’re not sure what to use, enter
text/plain
. - If you want to use HTML tags, enter
text/html
.
- If you just want to enter plain text, or if you’re not sure what to use, enter
-
Reply-To Name: Enter the name of the Reply-to recipient.
-
Sender Name: Enter the name of the email sender. This appears in the From field.
- Under Fallback Answer, you can click to edit the AI Agent’s response if an error occurs.
- Turn on the Count as Handoff toggle to ensure your reporting is accurate.
-
Add any other custom messaging you want customers to receive during your handoff, and click Save. At the top of your screen, ensure your handoff toggle is set to Active so your AI Agent can start handing customers off as needed.