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

# Deploy your bot on mobile using Zendesk Messaging SDKs

You can use Zendesk Messaging SDKs to allow chatters to interact with
your bot on their web or mobile devices. There are several other ways to
do this, including using [Ada's SDKs](/scripted/docs/use-ada-with-your-website/deploy-ada-on-your-website-or-app/embed-ada-on-your-website-or-app#UUID-94cb704f-b01b-0ea1-33f7-fd1d285dfa30_section-idm4628099243435233884218806686),
but this method is convenient if you already have an integration with
Zendesk configured.

## Understand chatter experience with Zendesk Messaging SDKs\[#UUID-de9fedc7-5d76-443c-3c5e-4d58de5c9c20_section-idm43398108553550]

The chatter experience through Zendesk Messaging SDKs is very similar to
Ada's default web experience in a lot of ways, with some exceptions.
Here are some basics:

* Chatters can use the same conversation window to exchange messages
  with both your bot and with human agents, with seamless handoffs to
  Zendesk Messaging in between.

* Chatters and agents can send files to each other. For information on
  how Zendesk validates files, see [Working with attachments](https://support.zendesk.com/hc/en-us/articles/4408821905434#topic_i32_zhh_3nb)
  at Zendesk's documentation.

* After the chatter has been handed off to an agent, the chat window is
  reserved for their conversation with the agent. Only the agent can
  disengage the conversation by marking the ticket as "solved." After
  this, depending on your organization's [trigger settings](/scripted/docs/integrate-ada-with-other-tools/use-ada-with-zendesk/deploy-your-bot-on-mobile-using-zendesk-messaging-sdks#UUID-de9fedc7-5d76-443c-3c5e-4d58de5c9c20_section-idm4489127723513633987902441891),
  Zendesk automatically marks the ticket as "closed."

  Until the ticket is marked as "closed," any messages the chatter sends
  go to the agent, not the bot. The chatter has to wait until the ticket
  is closed to be able to send messages to your bot again.

* You can use Zendesk's multi-bot routing feature. For more information,
  see [Connect Zendesk social channels to multiple bots using Sunshine Conversations](/scripted/docs/integrate-ada-with-other-tools/use-ada-with-zendesk/connect-zendesk-social-channels-to-multiple-bots-using-sunshine-conversations).

### Understand how Ada features work with Zendesk Messaging SDKs\[#UUID-de9fedc7-5d76-443c-3c5e-4d58de5c9c20_section-idm4563995364032033981091711353]

* The language the bot sends messages in depends on the chatter's
  browser settings. You can override the default language by setting the
  locale manually. For more information, see the [Set locale](https://developer.zendesk.com/api-reference/widget-messaging/web/core/#set-locale)
  section of Zendesk's Core messaging Web Widget API documentation.

* The reports that provide an
  [overview](/scripted/docs/measure-success/analyze-chat-data/get-an-overview-on-your-bot-s-performance)
  on your bot's performance should perform as expected. However, some
  [detailed reports](/scripted/docs/measure-success/analyze-chat-data/view-detailed-reports-on-your-bot-s-performance)
  may not contain information about conversations that took place on
  Zendesk channels, depending on the data they require.

* You can manage whether your bot remembers chatters between
  conversations in Agent Workspace. You can choose to retain
  conversation history, or to treat all chatters as anonymous, with no
  saved previous conversation history. For more information, see the
  instructions in Zendesk's
  [troubleshooting](https://support.zendesk.com/hc/en-us/articles/4531075858458)
  documentation.

  This setting only applies to Zendesk's Web Widget, and not mobile; on
  mobile, Zendesk saves chatter history by default.

* You can control which website domains chatters can see your Zendesk
  Web Widget on. For more information, see [Creating an allowlist for the Web Widget](https://support.zendesk.com/hc/en-us/articles/4500748175258-Installing-the-Web-Widget#topic_edv_xd5_2tb)
  at Zendesk's documentation.

## Set up Zendesk Messaging SDKs with your bot\[#UUID-de9fedc7-5d76-443c-3c5e-4d58de5c9c20_section-idm4499707571385633986534063849]

Setting up your bot to work with Zendesk Messaging SDKs requires some
work in your bot, in Sunshine Conversations, in Zendesk, and finally in
your own website. If you have any trouble with any portion of these
procedures, don't hesitate to contact your Ada team for assistance.

### Before you begin\[#UUID-de9fedc7-5d76-443c-3c5e-4d58de5c9c20_section-idm4513257290800033986539440405]

Before proceeding, do a quick check to see that you have the following:

* Access to Zendesk Messaging (on Agent Workspace)

* A subscription to Zendesk Suite Professional, Enterprise, Enterprise
  Plus, **or** a standalone Sunshine Conversations license add-on

* Access to the Zendesk Conversations API through Zendesk Admin Center,
  so you can create API keys

* A completed Sunshine Conversations integration in your Ada bot. For
  more information, see [Connect Sunshine Conversations with Ada](/scripted/docs/integrate-ada-with-other-tools/use-ada-with-other-chat-handoff-tools/configure-and-use-sunshine-conversations#UUID-7eb532ef-c172-286f-d881-27ac1d51b70a_id_360057424874_id_h_01FAE9RKNBKD57R8Z988FE7NPS)

* Your bot's name configured in your Ada dashboard, so the bot's name
  appears on messages in your widget and in Zendesk tickets. For more
  information, see [Access branding customization options](/scripted/docs/build-and-maintain-your-bot/change-your-bot-s-look-and-feel/customize-your-bot-s-branding#UUID-628bb378-6983-64c2-4c42-41036002ddfe_id_1500012348861_id_h_01F6MR79G9P48JP7XZ9XAG0JNE)

Additionally, contact your Ada team to make sure your bot is ready for
the next steps. There are some features you may need Ada staff to enable
on your behalf that you can't proceed without.

### Configure your Zendesk widget\[#UUID-de9fedc7-5d76-443c-3c5e-4d58de5c9c20_section-idm4622825778553633986549244736]

You can customize your web or mobile widgets in Zendesk Admin Center:

* For information on how to customize how your widget looks, see
  [Configuring the widget launcher](https://support.zendesk.com/hc/en-us/articles/4500747797914-Configuring-the-appearance-of-the-Web-Widget#id_jnl_xtm_gnb)
  at Zendesk's documentation.

* For more detailed information on additional settings you can change,
  see [Zendesk Web Widget and SDKs](https://developer.zendesk.com/api-reference/widget-messaging/introduction/)
  at Zendesk Developers' documentation.

### Install your Zendesk widget on your website\[#UUID-de9fedc7-5d76-443c-3c5e-4d58de5c9c20_section-idm4597454210996833987672184123]

After configuring your Zendesk widget, you can install it on your
website so chatters can interact with it.

* To install your widget on your website, find the installation script
  in your Admin Center and add it to your website's code.

* Optionally, you can choose to enable your widget on your Zendesk Help
  Center.

For installation instructions, see [Installing the Web Widget](https://support.zendesk.com/hc/en-us/articles/4500748175258-Installing-the-Web-Widget)
at Zendesk's documentation.

### Configure settings in Zendesk Admin Center\[#UUID-de9fedc7-5d76-443c-3c5e-4d58de5c9c20_section-idm4489127723513633987902441891]

In Zendesk Admin Center, you can configure two settings for your bot's
behavior:

* You can set up triggers to automatically close tickets a certain
  amount of time after the agent marks them as "solved." For more
  information, see [Understanding and managing handback events](https://support.zendesk.com/hc/en-us/articles/4408824482586#topic_ux4_cqq_5pb)
  at Zendesk's documentation.

* To collect customer satisfaction data, you can set up Zendesk's CSAT
  survey. For more information, see [About CSAT ratings in messaging](https://support.zendesk.com/hc/en-us/articles/4408832620570-About-CSAT-ratings-in-messaging)
  at Zendesk's documentation.

Lastly, to allow your bot to start interacting with chatters, you have
to connect your bot with Zendesk. For more information, see [Connect your bot with Zendesk Admin Center](/scripted/docs/integrate-ada-with-other-tools/use-ada-with-zendesk/configure-and-use-ada-glass-for-zendesk-messaging#UUID-98fb0e96-9b92-a864-b73a-d631766a608b_section-idm43400010489800).

### Set up handoffs using HTTP Request blocks\[#UUID-de9fedc7-5d76-443c-3c5e-4d58de5c9c20_section-idm4574482559744033988075850145]

Instead of using Ada's usual handoff blocks, Zendesk Messaging SDKs use
API requests to hand chatters off to human agents.

> **Tip**
>
> When configuring handoffs using the HTTP Request block, make sure you
> toggle on the **Count as Handoff** setting on the block to collect data
> for your reports.

For complete documentation on Sunshine Conversations' API, see [Metadata sent to Zendesk](https://docs.smooch.io/guide/switchboard/#metadata-sent-to-zendesk)
at Sunshine Conversations' developer documentation. To get started,
however, you can use these values using the variables in your Ada bot.

<table>
  <thead>
    <tr>
      <th>
        Name
      </th>

      <th>
        Value
      </th>

      <th>
        Notes
      </th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td>
        URL
      </td>

      <td>
        `https://api.smooch.io/v2/apps/{appId}/
        conversations/{conversationId}/passControl`
      </td>

      <td />
    </tr>

    <tr>
      <td>
        appId
      </td>

      <td>
        `<sunco-app-id>`
      </td>

      <td>
        * Sent in URL
        * Found in **Zendesk Admin Center** >
          **APIs** > **Conversations API**
      </td>
    </tr>

    <tr>
      <td>
        conversationId
      </td>

      <td>
        `@sunshine_conversation_id`
      </td>

      <td>
        Sent in URL
      </td>
    </tr>

    <tr>
      <td>
        Authorization
      </td>

      <td>
        `Basic @sunshine_basic_token`
      </td>

      <td>
        Sent in header
      </td>
    </tr>

    <tr>
      <td>
        switchboardIntegration
      </td>

      <td>
        `“next”`
      </td>

      <td>
        Sent in body
      </td>
    </tr>

    <tr>
      <td>
        metadata:first_message_id
      </td>

      <td>
        `@sunshine_first_message_id`
      </td>

      <td>
        * Sent in body
        * Sends first message of the most recent interaction, overriding
          default behavior of sending just the last 10 messages in the
          conversation
      </td>
    </tr>
  </tbody>
</table>

Here's an example of a completed handoff using an HTTP Request block:

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

In the above example, the request block also passes tags into Zendesk.
This is how they look in the human agent's conversation with the
chatter:

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

---

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