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

## Overview\[#UUID-ab3cd9e0-4b29-67f6-88c3-923964ddbe5d_id_1500010840122_id_h_01FDGFK6476BJ1HWMC2SWBGJ2X]

Ada Glass for Intercom helps you create a seamless handoff from your
chatbot to a live agent in Intercom, all from within Ada. To use Ada
Glass for Intercom, you must have an Intercom account.

> **Note**
>
> The number of handoff platforms your organization can use varies
> depending on your subscription package. For more information, see Ada's
> [Pricing](https://www.ada.cx/pricing) page, or contact your Ada team.

## Configure your Intercom instance\[#UUID-ab3cd9e0-4b29-67f6-88c3-923964ddbe5d_id_1500010840122_id_h_01FDGFKEWRH56D511AGX0CDTGM]

Prepare Intercom for the Ada Glass integration by completing the
following steps in Intercom:

### Create a private app in Intercom\[#UUID-ab3cd9e0-4b29-67f6-88c3-923964ddbe5d_id_1500010840122_id_h_01FDGG7CZRTQ0HQPTRS6Q35BK0]

1. To set up a private app in Intercom, you need to have access to the
   Intercom developer hub. To grant access to the developer hub,
   navigate to **Settings** > **General** > **Teammates (Select the
   user here)** > **Permissions and Roles** > **Apps and
   Integrations**. Then turn on the following permissions for the
   desired user:

   * Can access developer hub

   * Can install, configure and delete apps

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

2. Ada Glass for Intercom supports private apps in Intercom that are
   v2.4 or below. To confirm your version, go to **Developer Hub >
   Configure > API Version in Intercom**.

3. Navigate to **Settings** > **Developers** > **Developer Hub**.
   This will open up the **Developer Hub** page.

4. Click **New App**.

5. Create a new private app, and call it “Ada Integration.”

### Grant permissions\[#UUID-ab3cd9e0-4b29-67f6-88c3-923964ddbe5d_id_1500010840122_id_h_01FDGG7TGWGZHY1E3TJV11DSJX]

1. Navigate to **Settings** > **Developers** > **Developer Hub**.
   This will open up the **Developer Hub** page.

2. Under **People and conversation data** and **Workspace data**, grant
   the appropriate **Permissions**—select the following (reference the
   screenshot below).

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

### Add webhooks\[#UUID-ab3cd9e0-4b29-67f6-88c3-923964ddbe5d_id_1500010840122_id_h_01FDGG853TAA1F6W1190S0XRBZ]

> **Info**
>
> Configure only one app with the Ada webhook URL. Having multiple apps
> configured results in duplicated agent messages and Intercom events,
> even if the additional apps aren't used.

1. Navigate to **Settings** > **Developers** > **Developer Hub**.
   This will open up the **Developer Hub** page.

2. Go to **Configure** > **Webhooks** to view your Intercom Webhooks.

3. Click **Edit** and enter these details:

   * Your Request Endpoint URL (Ada Webhook URL):
     [https://sparta.svc.ada.support/webhook](https://sparta.svc.ada.support/webhook)

   * Webhook topics:

     * conversation.admin.closed

     * conversation.admin.replied

     * conversation.admin.assigned

     * conversation.admin.snoozed

     * conversation.admin.unsnoozed

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

### Add an Ada conversation attribute\[#UUID-ab3cd9e0-4b29-67f6-88c3-923964ddbe5d_id_1500010840122_id_h_01FDGG8E8HGTG2H5ZC350JR4D6]

For an Intercom handoff, Ada uses custom attributes as identifiers for
the various elements of a conversation. Examples of these elements
include the conversation ID, the chatter ID, and the client handle. But
don't worry! You only need to add a single universal attribute
(ada_custom_attributes) that encompasses all these elements
automatically.

1. In Intercom, go to **IntercomAgent Workspace** > **Settings** >
   **Instance Name** > **Data** > **Conversation data**.

2. Click the **Create Attribute** button to add a new attribute.

3. In the **Name** field, enter **ada_custom_attributes**.

4. Click the **Format** drop-down menu, then select **Text**.

5. Click **Save**.

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

### Create tags in Intercom\[#UUID-ab3cd9e0-4b29-67f6-88c3-923964ddbe5d_id_1500010840122_id_h_01FDGG8YRQMTTR250P2TF6VYCW]

1. Navigate to the **Settings** page.

2. Under the **\*Your Workspace Name\*** data tab, click on the
   **Tags** item.

3. Create your first tag by clicking the **New tag** button.

   > **Note**
   >
   > If you have pre-existing tags created, you may find the **New tag**
   > button on the top right corner of the Tags screen.

4. After you name your new tag, click the checkmark beside the input
   field or press **Enter** to save it.

The tag is now ready to use in Intercom and the Intercom block in Ada.

### Configure conversation assignments\[#UUID-ab3cd9e0-4b29-67f6-88c3-923964ddbe5d_section-idm456417593929763392896292805]

Ada's Intercom integration only supports single-agent assignment. If a
conversation is assigned to a team rather than a single agent, the
chatter and the agent can't reliably send each other messages.

To ensure agents and chatters can speak to each other without
interruptions, configure your Intercom integration to assign a single
agent to every incoming conversation from Ada. For more information, see
[Assign conversations to teammates and teams](https://www.intercom.com/help/en/articles/6561699-assign-conversations-to-teammates-and-teams?q=assign+chat+to+team)
at Intercom's documentation.

## Configure Ada Glass for Intercom\[#UUID-ab3cd9e0-4b29-67f6-88c3-923964ddbe5d_id_1500010840122_id_h_01F5X7NYNJY8P5VPG5AQEBVATC]

To configure the Ada Glass for Intercom integration in Ada:

1. Navigate to the **Settings** page.

2. Click **Integrations**, then scroll down to **Handoff
   Integrations**.

3. Next to **Intercom**, click **Configure**.

4. In the Connect Ada to Intercom window, click **Connect**.

5. If a prompt to log into your Intercom account appears, log in. A
   window that says "Ada Chat wants to access \[your Intercom account
   name]" appears.

6. Verify that the Intercom account listed is the correct one to
   connect to Ada, and click **Authorize access**.

### Use the Ada Glass for Intercom Live Agent block\[#UUID-ab3cd9e0-4b29-67f6-88c3-923964ddbe5d_id_1500010840122_id_h_01F5X7PF4Z72SDE6XSQVYQFVM5]

1. Create a new Answer to handle handoffs to Intercom live agents.

2. Click and drag the Intercom block from the block bar into the
   Answer.

3. Add any applicable tags, such as "Ada." (These tags will be mapped
   to the conversation in Intercom.)

4. Select the appropriate department from the Department dropdown.

5. Click the **Save** button at the bottom of the screen.

6. Train the Answer so that it is surfaced when chatters require a live
   agent.

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

#### Configure tags in the Intercom block\[#UUID-ab3cd9e0-4b29-67f6-88c3-923964ddbe5d_id_1500010840122_id_h_01FDGGA1YTZEPCJADTM2EPCRAY]

The Intercom block supports the ability to add tags that will be
attributed to Contacts (represented by the “People” column in Intercom’s
tags interface) and Conversations. These are separated by two fields:
Contact Tags and Conversation Tags.

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

In the above image, the Contact Tags field has been filled with three
tags that will be attributed to the contact: contact1, contact2, and
contact3. Adding a tag in this field will reference an existing tag
created in Intercom with the same name. If a tag with the same name does
not exist in Intercom, a new tag will be created in Intercom and
automatically attributed to the contact.

To add a new tag, type in the name of the tag, then add a comma (`,`).

The Conversation Tags field functions identically to the Contact Tags
field, the only difference being that the tags will be attributed to the
conversation created during the handoff. A tag can be used in both
Contact Tags and Conversation Tags, and will attribute both the contact
and conversation with the same tag. As a rule of thumb, while
conversations will be transferred from Ada to Intercom immediately, tags
will be delayed 30-60 seconds.

### Configure off hours\[#UUID-ab3cd9e0-4b29-67f6-88c3-923964ddbe5d_id_1500010840122_id_h_01F5XF0KHSAP26TR98FGWAC775]

The Intercom API does not support automatic off-hours routing, so we
recommend using the [Scheduled block](/scripted/docs/build-and-maintain-your-bot/work-with-blocks-and-apps/serve-time-specific-content-using-the-scheduled-block)
to ensure that chatters are routed effectively. If chatters try to
connect to agents before or after business hours, the Scheduled block
will redirect them to a process that will handle an off-hours requests.
Talk to your Ada team for more info.

## Chatter experience\[#UUID-ab3cd9e0-4b29-67f6-88c3-923964ddbe5d_id_1500010840122_id_h_01F5X7QH74B6RBTNH4Z6CF29PP]

Once the chatter has confirmed they would like to speak with an agent,
they will receive a message informing them to wait while they are
connected a support agent.

When the chat is assigned to an agent, the agent's name is provided to
the chatter to identify who they are chatting with. The chatter will
continue the conversation with the live agent in the same chat window
that they were corresponding with the bot in, resulting in a seamless
experience for the chatter.

## Intercom live agent experience\[#UUID-ab3cd9e0-4b29-67f6-88c3-923964ddbe5d_id_1500010840122_id_h_01F5X8G7H1JMTS8588RQ4DDBAT]

If you would like to have your chatter identified in Intercom, you can
collect chatter's personal information and save them as variables. Below
are the variables that are supported:

* **first_name/firstname**

* **last_name/lastname**

* **email**

* **phone_number/phonenumber/phone**

If the bot has captured the specific information from the chatter, such
as the info listed above, it will be mapped to the chat, along with
tags. Agents will also see the conversation the chatter had with the bot
leading up to the handoff.

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

You can find the contact tags displayed in the bot transcript forwarded
to the chat interface, as well as on the lead tags section in the right
panel.

## Transcripts\[#UUID-ab3cd9e0-4b29-67f6-88c3-923964ddbe5d_id_1500010840122_id_h_01F5X8GDWJTYH5ZBAZX1K8EFK2]

The full transcript of the chat is visible in the Intercom transcripts,
so an agent can have the entire context of the conversation to help
solve customer issues.

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

> **Note**
>
> File transfers can only be done between the agent and the chatter at
> this time.

---

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