> This page is for version Scripted.
> For other versions, use one of these documentation indexes:
> - Generative (default): https://developers.ada.cx/generative/llms.txt
> - Scripted: https://developers.ada.cx/scripted/llms.txt

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://developers.ada.cx/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://developers.ada.cx/_mcp/server.

# Create basic email tickets using the Zendesk Handoff block

## Overview\[#UUID-768a2001-ee26-449d-1e61-ebd37b13b218_id_360025885994_id_h_01F4D8TTRZ7MSW242X95SS35WW]

Our Zendesk Ticketing integration allows the bot to create email tickets
for your support team directly in your Zendesk instance. Customize the
subject line and tags in your email tickets to align with triggers and
routing rules in Zendesk.

## Set Up\[#UUID-768a2001-ee26-449d-1e61-ebd37b13b218_id_360025885994_id_set-up]

### In Zendesk\[#UUID-768a2001-ee26-449d-1e61-ebd37b13b218_id_360025885994_id_in-zendesk]

Before you can set up Zendesk email ticketing handoffs in Ada, you'll
need the following information from Zendesk:

* Your company's [Zendesk subdomain](https://support.zendesk.com/hc/en-us/articles/4409381383578-Where-can-I-find-my-Zendesk-subdomain-)

* Your Zendesk login email

* A [Zendesk API token](https://support.zendesk.com/hc/en-us/articles/4408889192858)

Once you have this information, you're ready for set up in Ada.

### In Ada\[#UUID-768a2001-ee26-449d-1e61-ebd37b13b218_id_360025885994_id_in-ada]

1. In the Ada dashboard, click **Settings** > **Integrations**.

2. Switch the **Zendesk Support** toggle to on. The configuration
   window appears.

3. In the configuration window, enter your **Zendesk Subdomain**.

4. Enter your team's **Zendesk Login Email**. This must be an admin
   level account.

   > **Info**
   >
   > Use a general admin account that's not associated with a specific
   > person. If, for any reason, you downgrade or remove this person's
   > Zendesk account, then the integration will break and support tickets
   > are no longer sent. On the other hand, a general admin account is
   > not very likely to have its admin privileges revoked.

5. Enter your Zendesk API Token (use the same admin account to [create one in Zendesk](https://support.zendesk.com/hc/en-us/articles/4408889192858)).

6. Click **Add Integration**.

![](/_fern-files/_img/caf4b0cf198d099a4f4623f7ff951cdd514810ef7b50e1bcfe0cd4f48b31126b.webp)

## Usage\[#UUID-768a2001-ee26-449d-1e61-ebd37b13b218_id_360025885994_id_usage]

Now that you've completed set up, the final step is using a Zendesk
Handoff block in your Answers.

1. In the Answer's View, select or create your *Handoff Answer*.

2. If you previously had an Email Handoff block in the answer, delete
   it.

3. Add a 'Zendesk Handoff' block to the end of your answer.

4. Input a subject line in the 'Ticket Subject' field. This will be the
   subject line of the tickets that are created in Zendesk from these
   handoffs. Click the 'Make unique' checkbox to add the chatter's
   email to the subject line of each Zendesk ticket. Please note that
   Zendesk triggers require an exact match to the content of the
   'Ticket Subject' field.

5. Add your Zendesk Tags in the 'Tags' field (you can add multiple by
   separating each tag with a comma and no spaces).

6. Place a checkmark next to 'Inline Transcript' and 'Inline Chatter
   Info' if you want the transcript of the chatter's conversation with
   the bot, and the metadata collected on the chatter, to be included
   directly in your ticket. If these options remain unchecked, the
   transcript and metadata will be attached to the ticket as a separate
   file.

7. Provide a 'Confirmation Message' that chatter's will receive
   indicating that their submission was sent.

8. Save your answer.

![](/_fern-files/_img/19b929e8ddcf8b93dc1d1d2d94ad1defa35c07c9dc93617643039169e5033a71.webp)

## Ticket\[#UUID-768a2001-ee26-449d-1e61-ebd37b13b218_id_360025885994_id_h_01F4D8VB457TH5AE8SMVRGVDGB]

Email tickets will include a transcript of the conversation that
preceded the ticket creation. Tickets will also include chatter
information that was collected by the browser, as well as any variables
captured in the answer that houses the Zendesk ticket handoff block (see
this page on
[variables](/scripted/docs/build-and-maintain-your-bot/personalize-conversations/get-started-with-variables)).

Here's an example of what that would look like (note that for this
scenario the "Inline Chatter Info" option was selected).

<table>
  <thead>
    <tr>
      <th>
        Dashboard View
      </th>

      <th>
        Conversation View
      </th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td>
        **Block**

        ![](/_fern-files/_img/8926059c8740a630bea5c345b23c85265fbb973f01fbacdda5012f07ab95fa09.webp)
      </td>

      <td rowspan="2">
        ![](/_fern-files/_img/a76f321f1962afe82c379f9c1ba0e8423589ebb8310cfd35a1021e98f1b1e05f.webp)
      </td>
    </tr>

    <tr>
      <td>
        **Ticket Information**

        ![](/_fern-files/_img/968d497712b345685683fd8c2529359b493d88e09f097d3157ffa79eee12ba50.webp)
      </td>
    </tr>
  </tbody>
</table>

The input "please?" has been saved as the variable "notes".

> **Note**
>
> * If a global `name` variable is captured anytime during a conversation,
>   the ticket will be associated with that name.
>
> * If a global `email` variable is captured anytime during a
>   conversation, the bot will not ask a user to input their email address
>   again.
>
> * If errors occur with a ticket being created, those with bot
>   credentials will be notified.
>
> * If you try to create a ticket using an email address that is
>   associated with a seat in your Zendesk environment, it will appear as
>   though the ticket has been successfully submitted, it will generate an
>   error and the ticket will not actually be submitted.
>
> * **The Zendesk Handoff block will not be available for you in your
>   block drawer until the configuration has been successfully
>   completed.**

---

Have any questions? Contact your Ada team, or email us at [](<mailto:help@ada.support%20%E2%80%9CHelp Docs inquiry%E2%80%9D>).