> 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.

# Configure and use Ada Glass for Zendesk Messaging

## Overview\[#UUID-98fb0e96-9b92-a864-b73a-d631766a608b_id_4417150051859_id_h_01FV0J4GJZGHCBYERH8VNZ6R2F]

Zendesk Messaging Glass is Ada's integration with the Zendesk Messaging
asynchronous chat product. Zendesk Messaging Glass gives you access to
Ada's full feature set within your Zendesk environment, letting your
brand leverage the Ada Chat experience.

> **Info**
>
> <table class="no-borders">
>   <tbody>
>     <tr>
>       <td>
>         ![](/_fern-files/_img/f5435222735a5b23e5bb763ca4ccb5daee14dc843086db11d19d699791904fce.webp)
>       </td>
>
>       <td>
>         This topic is about Zendesk Messaging. If you're looking for
>         information about Zendesk Chat, please see [Configure Ada Glass for Zendesk Chat](/docs/scripted/integrate-ada-with-other-tools/use-ada-with-zendesk/configure-ada-glass-for-zendesk-chat).
>       </td>
>     </tr>
>   </tbody>
> </table>

### About asynchronous chat\[#UUID-98fb0e96-9b92-a864-b73a-d631766a608b_id_4417150051859_id_h_01FVAT8YD3E3JW3XYCY56T12EA]

Asynchronous chat means that conversations between chatters and your
live support agents can extend indefinitely, until either the chatter or
agent ends the chat manually. It is not limited by automatic timeouts or
disconnects, as is the case with session-based chat platforms like
Zendesk Chat, and it supports .jpg, .jpeg, .pdf, and .png attachments,
up to a limit of 50MB.

### Requirements\[#UUID-98fb0e96-9b92-a864-b73a-d631766a608b_id_4417150051859_id_h_01FVAT98A0DZEBT5Y8SCCM7X5C]

Ada Glass for Zendesk Messaging requires that your Zendesk and Ada
accounts have the following products enabled and configured:

#### Zendesk\[#UUID-98fb0e96-9b92-a864-b73a-d631766a608b_id_4417150051859_id_h_01FVAT9FPZ7DSNSFXXPTTVYQCW]

* [Sunshine Conversations](https://developer.zendesk.com/documentation/custom-data/conversations/what-is-sunshine-conversations-/)

  * Channel: [Web Messenger](https://docs.smooch.io/guide/web-messenger/)

* [Zendesk Agent Workspace](https://support.zendesk.com/hc/en-us/articles/4408821259930-About-the-Zendesk-Agent-Workspace)

#### Ada

* Ada Glass for Zendesk Messaging

* [Sunshine Conversations channel integration](/scripted/docs/integrate-ada-with-other-tools/use-ada-with-other-chat-handoff-tools/configure-and-use-sunshine-conversations)

## Configure Zendesk Messaging Glass\[#UUID-98fb0e96-9b92-a864-b73a-d631766a608b_id_4417150051859_id_h_01FVATD3R357PKHB6503AENPGK]

You should have your Sunshine Conversations app open while configuring
Zendesk Messaging Glass. You'll need it to retrieve the required
authentication information needed to complete the set up.

Here's how to configure Zendesk Messaging Glass:

1. On the Ada dashboard, go to **Settings** > **Integrations** >
   **Handoff Integrations**.

2. On the **Zendesk Messaging** card, click **Configure**, then in the
   Connect Ada to Zendesk Messaging dialog box, click **Next**.

3. On the **Configure Zendesk Messaging** dialog box, complete the
   following fields using your Zendesk credentials, found under
   Settings in your Sunshine Conversations app.

   * **Zendesk Subdomain**

   * **Zendesk Login Email**

   * **Zendesk API Token**

     > **Tip**
     >
     > Refer to the Zendesk user guide [Generating a new API token](https://support.zendesk.com/hc/en-us/articles/4408889192858-Generating-a-new-API-token)
     > for guidance on creating an API token for your Zendesk Messaging
     > integration.

4. Click **Finish**, then close the success dialog box.

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

### Create an end conversation trigger\[#UUID-98fb0e96-9b92-a864-b73a-d631766a608b_id_4417150051859_id_h_01G3VJRSN5G5AST9F72GNT3MG4]

> **Tip**
>
> Zendesk may change their functionality without notice. For more details
> and the most up to date information about creating triggers, refer to
> Zendesk's guide [Creating triggers for automatic ticket updates and notifications](https://support.zendesk.com/hc/en-us/articles/4408886797466-Creating-triggers-for-automatic-ticket-updates-and-notifications).

Create a trigger in Zendesk to automatically end the agent conversation
once the ticket status is set to *solved*. This trigger releases the
chatter from the Zendesk agent conversation and allows them to resume
chatting with your Ada chatbot.

1. In the Zendesk Admin Center, go to **Objects and rules** >
   **Triggers**, then click **Add trigger**.

2. On the Add new trigger page, add a **trigger name**,
   **description**, and **category**.

3. Under Meet ALL of the following conditions, click **Add Condition**,
   then use the drop-down menus to set the condition to *Status Is
   Solved*.

4. Under Actions, click **Add action**, then use the drop-down menus to
   set the action to *Status Closed*.

5. Click **Create**.

With the trigger in place, your chatters are now automatically released
back to your Ada chatbot when the agent selects *Submit as Solved* at
the end of a live support conversation.

> **Note**
>
> Chatters on web or mobile can release themselves from an agent
> conversation by clicking the **X** at the top of the chat window.

### Connect your bot with Zendesk Admin Center\[#UUID-98fb0e96-9b92-a864-b73a-d631766a608b_section-idm43400010489800]

In Zendesk, add your bot so it can be the first means of interacting
with your chatters. For more information, see [Managing third-party bots in Admin Center](https://support.zendesk.com/hc/en-us/articles/5064149334426) at
Zendesk's documentation.

Here's a summary of what the actions do:

* **Connect** - Makes a switchboard setup where Ada is the first
  responder, Zendesk Agent Workspace is the second, and Zendesk's Answer
  Bot is not connected to any other switchboard integrations.

* **Disconnect** - Sets Answer Bot back as the first responder, but
  keeps Ada in the switchboard in case you want to reconnect it in the
  future. This can be handy while you're testing your bot.

* **Uninstall** - Removes Ada from your switchboard, and uninstalls it
  from your Sunshine Conversations app. We don't recommend doing this;
  if you do, you'll have to reinstall Ada in your Zendesk account again.

If you can't see the above actions, you can perform the same actions in
the Sunshine Conversations API. For instructions on how to do that, see
[Configuring the switchboard with Zendesk and a bot partner](https://docs.smooch.io/guide/switchboard/#configuring-the-switchboard-with-zendesk-and-a-bot-partner)
at Sunshine Conversations' documentation. If you continue to have
difficulty, feel free to contact your Ada team for assistance.

> **Note**
>
> Sunshine Conversations Web Messenger won't appear in your list of
> channels in Zendesk Admin Center. However, it's accessible in the
> Sunshine Conversations API if you need to see or update it.

## Use the Zendesk Messaging block\[#UUID-98fb0e96-9b92-a864-b73a-d631766a608b_id_4417150051859_id_h_01FVATDB89F81SK0G6K6E38P9F]

This quick guide will help you get your Zendesk Messaging Answer up and
running.

Here are the steps:

1. On the Ada Dashboard, go to **Build** > **Answer**, then create a
   new handoff Answer, or select an existing one.

2. \[Optional] In the Answer editor, add **Capture** blocks configured
   to capture the chatter's name, email address, and phone number.

   > **Note**
   >
   > In order for the chatter's information to map to the correct fields
   > on the Zendesk ticket, the variables you use to capture their name
   > and email address must be named exactly as they appear below:
   >
   > * **name**
   >
   > * **email**

3. Drag and drop the **Zendesk Messaging** block into the Answer
   editor, then configure the block using the following table as a
   guide:

   <table>
     <thead>
       <tr>
         <th>
           Field
         </th>

         <th>
           Description
         </th>
       </tr>
     </thead>

     <tbody>
       <tr>
         <td>
           **Standby Message**
         </td>

         <td>
           Support requests can occur both during business hours, or during
           off hours. Use this message to acknowledge the chatter's request and
           present information about response times.

           > **Tip**
           >
           > Craft a message for chatters with helpful information, such as
           > average wait times, or if agents are offline. Use the [Scheduled block](/docs/scripted/build-and-maintain-your-bot/work-with-blocks-and-apps/serve-time-specific-content-using-the-scheduled-block) to help make this an even smoother experience.
         </td>
       </tr>

       <tr>
         <td>
           **Department**
         </td>

         <td>
           This drop-down menu lists all the available support departments.
           Select the appropriate department for this handoff.
         </td>
       </tr>

       <tr>
         <td>
           **Zendesk Fields**
         </td>

         <td>
           Map your Zendesk fields to the block. Use these fields to enhance
           your support process:

           * Present your agents with key chatter details.
           * Use [Support triggers](https://support.zendesk.com/hc/en-us/articles/4408819011354-Recipe-Routing-messaging-tickets-using-Support-triggers) to route incoming tickets to the right team.

           Zendesk Field types **Text**, **Number**, **Boolean**, and **Dropdown** field types are
           all accepted.

           * If you're using the Dropdown field type, make sure you send the **Tag** value associated with the dropdown to Zendesk, to
             ensure that the value gets saved properly in your ticket.
         </td>
       </tr>

       <tr>
         <td>
           **Tags**
         </td>

         <td>
           Use tags to identify the purpose of this handoff. Tags attach to
           the Zendesk ticket automatically.

           > **Note**
           >
           > Separate each tag with a comma.
         </td>
       </tr>

       <tr>
         <td>
           **Error Answer**
         </td>

         <td>
           Click the drop-down menu and select the Answer to surface to a
           chatter should a communication error occur.
         </td>
       </tr>
     </tbody>
   </table>

4. Click **Save**.

Your Zendesk handoff Answer is ready to go. Add training to this Answer
so that your bot recognizes a request for agent support. Connect this
Answer, or other specialized handoff Answers, to Answer flows that may
require an agent's intervention.

## Agent Experience\[#UUID-98fb0e96-9b92-a864-b73a-d631766a608b_id_4417150051859_id_h_01FVATDH4A4DNVWN45BR1N5EHC]

When a handoff occurs through your Ada chatbot, the primary agent
experience remains largely unchanged.

* Agents still handle all Live Agent conversations from their Zendesk
  Agent Workspace dashboard.

* Agents can also respond to chatters asynchronously, and over an
  extended timeframe.

In all tickets except those created between June and August 2023,
transcripts show bot messages with the channel set to "messaging":

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

Between June and August 2023, tickets originating from your bot had the
channel set to "Sunshine Conversations API":

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

These settings update once a chatter starts a new chat session. For bots
that have long [persistence settings](/scripted/docs/build-and-maintain-your-bot/personalize-conversations/manage-when-your-bot-forgets-customers),
you or your agents may wish to tell chatters to clear their caches to
display the updated channel source in the ticket.

## Chatter Experience\[#UUID-98fb0e96-9b92-a864-b73a-d631766a608b_id_4417150051859_id_h_01FVATDPS5B5PKQM26X89YFTRA]

The chatter's experience is seamless. Once they are handed over to the
live support agent, the only thing that changes about their experience
is who they are chatting with. Bot and agent conversations remain in the
same chat window.

Chatters can also minimize or close the chat window, regardless if its
Ada's or another brand's chat environment, and expect their conversation
history to persist; however, if they click the **End Chat** button, the
conversation history does clear.

---

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