> For the complete documentation index, see [llms.txt](https://docs.zero.inc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zero.inc/settings/integrations/intercom.md).

# Intercom

Support conversations say things about an account that no property captures. Connecting Intercom syncs its conversations into Zero as issues, linked to the right companies and contacts, so they sit alongside the rest of the record.

## How to connect Intercom to Zero

Only workspace admins can connect or disconnect issue tracker integrations.

{% stepper %}
{% step %}
Create an internal app in the [Intercom Developer Hub](https://app.intercom.com/a/apps/_/developer-hub) and copy its **Access Token**.

The token needs read access to conversations and contacts.
{% endstep %}

{% step %}
In Zero, go to **Settings → Connections → Integrations**. Scroll to **Issue Tracker integrations** and click **Connect Issue Tracker**.
{% endstep %}

{% step %}
Select **Intercom**, paste the Access Token into the **Issue Tracker API Key** field, and click **Connect Integration**.

<figure><img src="https://storage.googleapis.com/zero-production-api-docs/images/intercom_connect_issue_tracker_zero.png" alt="Connect Issue Tracker dialog with Intercom selected, an empty API key field and a link to the provider&#x27;s developer hub"><figcaption></figcaption></figure>
{% endstep %}
{% endstepper %}

The first sync starts immediately after connecting and pulls conversations from the **last 90 days**. After that, the integration updates **hourly**; the connected card shows the sync status and the last update time. You can also trigger a sync manually from the card's **⋯ menu → Sync data**.

## What gets synced

Each Intercom conversation becomes an issue in Zero:

* **Name** — the conversation title or subject; falls back to "Conversation with \<author>".
* **Status** — closed conversations sync as **Closed**, snoozed conversations stay snoozed, and everything else syncs as **Todo**.
* **Priority** — conversations marked as priority in Intercom are flagged as priority issues.
* **Labels** — Intercom conversation tags. Tag changes are picked up on later syncs, even without new activity on the conversation.
* **Messages** — the full conversation transcript as plain text: the initial message plus replies and notes.
* **Response and resolution time** — from Intercom's time-to-first-admin-reply and time-to-first-close statistics.
* **Link** — a deep link that opens the conversation in the Intercom inbox.

## How issues are matched to companies and contacts

Zero uses the conversation's primary contact to link each issue:

* The contact's **email** is matched (case-insensitively) against contact emails in your workspace.
* The **email domain** is matched against company domains. For free-mail senders, the matched contact's company is used instead.
* The source email is stored on the issue, so conversations are linked retroactively when a matching contact is created later. Associations are re-checked on every sync.

## Where the data appears in Zero

In any company list, add the properties related to **Issues** — for example **Issues**, **Open issues**, **Closed issues**, and **Issues by month**. These fields are shared with the other issue trackers (Linear, Pylon, Plain, Front). Click an issue to preview the conversation and open it in Intercom. You can also use **Issues** as an entity in [**Reports**](/features/reports.md) to chart the data and pin it to dashboards.

## Disconnecting

Open the connected card's **⋯ menu → Disconnect**. Disconnecting stops the sync and removes the synced issue data from Zero.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.zero.inc/settings/integrations/intercom.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.