> ## Documentation Index
> Fetch the complete documentation index at: https://chatbase.co/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Escalate AI agent conversations to Intercom

> Connect Intercom so your AI agent can escalate a conversation by opening a ticket for your support team

The Chatbase Intercom integration lets your AI agent open an Intercom Ticket when a customer needs a person, with an AI-written summary of the conversation and a link back to the full chat in Chatbase. It's for teams that handle support in Intercom and want the AI agent to resolve routine questions first. It works with US-hosted Intercom workspaces, from any channel where the [Escalations](https://chatbase.co/docs/user-guides/chatbot/actions/escalate-to-human.md) Action runs, such as the Chat Bubble, Help Page, WhatsApp, Messenger, Instagram, and email.

> [card] What you can do:
>
> Let the AI resolve routine questions on its own, and hand off to Intercom the moment a case needs a person, with the full context already attached.

## Before you start

* A Chatbase account on the **Basic** plan or higher.
* A Chatbase AI agent. The connection is per AI agent, and each AI agent can connect one Intercom workspace.
* An Intercom workspace hosted in the **US** region that you can authorize access for, with Intercom Tickets available. Workspaces hosted in the EU or Australia aren't supported.

## How to connect Intercom

**1. Open your Chatbase AI agent**

Log in to your [Chatbase dashboard](https://www.chatbase.co/dashboard/) and select the AI agent you want to connect.

**2. Connect Intercom**

Choose **Integrations**, then connect your Intercom account to authorize access.

![Connecting Intercom from the Chatbase Integrations page](https://mintcdn.com/chatbase/EB093lU6eg6qI3KF/user-guides/integrations/images/intercom/intercom.png?fit=max\&auto=format\&n=EB093lU6eg6qI3KF\&q=85\&s=0f6f784acd1d083e0fbc77b5dc1279d7)

While connecting, Chatbase adds a customer ticket type named **Chatbase Support** to your Intercom workspace, or reuses it if it already exists. Every ticket the AI agent creates uses this type.

**3. Create the Escalations Action**

Go to **Build > Actions > Create Action**, select **Create ticket** under **Escalations**, and choose **Intercom** as the **Ticket Platform**. Intercom has no extra options on the Action. Follow the [Escalations Action guide](https://chatbase.co/docs/user-guides/chatbot/actions/escalate-to-human.md) for the rest of the setup.

> [!TIP]
>
> Test the integration by asking your AI agent to speak to a human, and confirm a ticket appears in Intercom with the conversation summary attached.

## What the ticket contains

Chatbase creates an Intercom **Ticket**, not a Conversation. Each ticket has:

* **Ticket type:** **Chatbase Support**.
* **Title:** written by the AI agent from the customer's issue. The customer is never asked for it.
* **Description:** an AI-written summary of the conversation, in the customer's language.
* **Contact:** the customer's email. The AI agent asks for a name too, but only the email is sent to Intercom.
* **Note:** an internal note with a link to the full conversation in Chatbase, added right after the ticket is created.

Chatbase sets no tags or custom attributes, and doesn't attach files the customer sent in the chat.

### Example

The following exchange is illustrative. A customer on the Chat Bubble writes "I can't log in after resetting my password, can a person help?" The AI agent asks for an email and name, the customer replies "Jane Doe, [jane@example.com](mailto:jane@example.com)", and Intercom receives a **Chatbase Support** ticket with:

* **Title:** Unable to log in after password reset
* **Description:** The customer reset their password but still can't log in and asks for help from the support team.
* **Contact:** [jane@example.com](mailto:jane@example.com)
* An internal note with the link to the conversation in Chatbase

## What the customer sees

The AI agent asks for the customer's email and name if it doesn't already have them, creates the ticket, and tells the customer the ticket number. On the Chat Bubble, Help Page, and Center Stage, a **Ticket Created** card also shows the ticket number. If creation fails, the card reads **Failed to create ticket**.

Your team works the ticket in Intercom. Nothing syncs back to the Chatbase conversation, and the AI agent keeps answering in the chat. Creating a ticket uses no extra message credits beyond the AI agent's normal reply.

## Intercom compared with Chatbase Helpdesk

An Intercom escalation is one way: Chatbase opens the ticket, and your team continues in Intercom. With [Chatbase Helpdesk](https://chatbase.co/docs/user-guides/chatbot/help-desk/help-desk-overview.md) as the ticket platform, the Escalations Action also offers:

* **Live handover in the same conversation.** The AI agent stops replying and your team's replies show up in the chat, including on WhatsApp, Messenger, and Instagram. See [Handover with Chatbase Helpdesk](https://chatbase.co/docs/user-guides/chatbot/actions/escalate-to-human.md#handover-with-chatbase-helpdesk).
* **Details collection** with your own fields, as a form in the Chat Bubble and Help Page or by asking in the conversation.
* **Ticket tags** set by the AI agent. See [Tags](https://chatbase.co/docs/user-guides/chatbot/actions/escalate-to-human.md#tags).

## Troubleshooting

> [accordion] Connecting fails with "Failed to create ticket type in Intercom"
>
> Chatbase couldn't create or find the **Chatbase Support** ticket type. The full message is "Failed to create ticket type in Intercom. Please ensure your Intercom app has permission to manage ticket types." Check that Tickets are available in your Intercom workspace, then connect again.

> [accordion] Connecting fails with another Intercom error
>
> Errors appear as a message starting with **Intercom integration failed**, for example "Failed to connect to Intercom". Check that you're connecting a US-hosted workspace, since EU and Australia workspaces aren't supported, and try again.

> [accordion] Tickets stopped being created, but the card still says Connected
>
> The card shows **Connected** as long as a saved connection exists, even if Intercom no longer accepts it (for example, after access was revoked in Intercom). Tickets then fail, the customer sees **Failed to create ticket**, and nobody is notified. Open the conversation in [Activity](https://chatbase.co/docs/user-guides/chatbot/activity.md#conversations) and check the **Create ticket** Action's **Result** for the error, then disconnect and connect again.

> [accordion] The ticket shows no customer name
>
> That's expected. Chatbase sends only the customer's email to Intercom.

## Frequently asked questions

> [accordion] Does Chatbase create an Intercom Ticket or a Conversation?
>
> A Ticket, of the **Chatbase Support** type that Chatbase adds to your workspace when you connect.

> [accordion] Does the Intercom integration work with EU or Australia workspaces?
>
> No. Only Intercom workspaces hosted in the US region are supported.

> [accordion] Do replies from Intercom show up in the Chatbase chat?
>
> No. Nothing syncs back to Chatbase. The only thing the chat shows is the ticket number when the ticket is created.

> [accordion] What happens to my Actions if I disconnect Intercom?
>
> Chatbase lists the Intercom **Create ticket** Actions and deletes them when you confirm. Tickets already in Intercom aren't affected.

> [accordion] Does creating an Intercom ticket use message credits?
>
> No extra credits. The AI agent's reply that creates the ticket costs the same as any other reply.

## Next steps

> [card] [Escalations Action](https://chatbase.co/docs/user-guides/chatbot/actions/escalate-to-human.md)
>
> Configure when your AI agent escalates, which details it collects first, and which channels it can escalate from.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.