Email Handoffs allow your AI Agent to escalate email conversations to your human support team on your preferred agent platform. The handoff block you choose determines how tickets are created, how email threads are handled, and whether human agents can reply using the same email address as the AI Agent.
Email Handoffs support a variety of escalation scenarios depending on your platform and end-user experience requirements.
Seamless thread continuation: End users receive human agent replies in the same email thread, from the same support address as the AI Agent. Ideal for maintaining conversation continuity and a consistent brand experience. Supported by Zendesk Support and Zendesk Ticketing (with SMTP Connector).
Attachment handling during escalation: End user attachments—such as screenshots, receipts, or documents—are passed to human agents automatically. Supported by all handoff methods.
Customizable ticket routing and categorization: Control how tickets are created in your agent platform, including subject lines, tags, priority, and custom fields. Supported by Zendesk Support, Zendesk Ticketing, and Salesforce.
Platform-agnostic escalation: Route email escalations to any third-party platform using the Email block or HTTP Request block, even without a direct integration.
Several handoff methods are compatible with the Email channel. The following table compares key functionality across supported platforms.
The following Handoff blocks are compatible with the Email channel.
Set up email Handoffs in a few steps. For detailed instructions for each handoff method, see Implementation & usage.
In your handoff flow, set an availability rule to apply only when the channel is Email.
Configure your preferred Handoff block to enable email escalations to human agents.
Creates a new ticket in Zendesk. Human agent replies are delivered to the end user in the same thread—and from the same address—as the Email AI Agent.
Follow the linked steps to integrate and configure Zendesk Support with your AI Agent.
Ensure your handoff has an availability rule set to apply only when the channel is Email.
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:
Creates a new Zendesk ticket via API. With the SMTP Connector configured, human agent replies can continue in the same email thread as the original end-user conversation, using the same BYOD address as the AI Agent. Without the SMTP Connector, human agents must use a different email address, and replies are sent in a new email thread.
If you haven’t already, configure Zendesk Ticketing in your AI Agent.
Ensure your handoff has an availability rule set to apply only when the channel is Email.
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. This block allows you to save the entire chat transcript as a variable, which you can then pass along to the live agent for additional context during the handoff.
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.
In the block drawer, under Action Apps, click and drag the Zendesk Ticketing block into your handoff, below the Fetch Chat Metadata block.
email_latest_cc_list variable to pass CC’d recipients from multiple participant conversations directly into the Zendesk ticket. All CC’d participants will automatically receive replies from human agents after handoff.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.
taxes@example.com and legal@example.com). Addresses on different domains (for example, help@foo.com and help@bar.com) are not supported for same-thread behavior. If the addresses are on different domains, configure the Zendesk SMTP Connector separately for each inbox’s domain.Creates a new case in Salesforce if the Create Case option is selected, or updates an existing case if the Update Case option is selected. Human agent replies to the case are sent to the end user in a new email thread from a different email address.
If you haven’t already, configure Salesforce actions in your AI Agent.
Ensure your handoff has an availability rule set to apply only when the channel is Email.
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. This block allows you to save the entire chat transcript as a variable, which you can then pass along to the live agent for additional context during the handoff.
In the block drawer, under Action Apps, click and drag the Salesforce block into your handoff, below the Fetch Chat Metadata block.
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.
Sends a formatted email to the recipient address specified in the block’s “Recipient Email” field. Ada also sets the Reply-To and CC headers using system variables (e.g., @email_from_address, @email_latest_CC_list).
Ensure your handoff has an availability rule set to apply only when the channel is Email.
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. This block allows you to save the entire chat transcript as a variable, which you can then pass along to the live agent for additional context during the handoff.
In the block drawer, under Action Apps, click and drag the Email block into your handoff, below the Fetch Chat Metadata block.
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.
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:
text/plain.text/html.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.
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.