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

# Email

> Route email conversations from Intercom through OpenCX AI with handoff to your Intercom inbox.

Email conversations that arrive in Intercom are handled the same way as Messenger chats — OpenCX picks them up via webhook, generates an AI reply, and posts it back as the AI admin. The key difference is a longer initial processing delay and email-specific formatting.

## Pre-requisites

<Warning>
  **Connect your Intercom workspace first.** The AI has nothing to respond to until the webhook is active — start with [Connect Intercom](/integrations/intercom/connect) and come back here.
</Warning>

* **Intercom connected and webhook active** — see [Connect Intercom](/integrations/intercom/connect).
* **Email channel configured in Intercom** — your Intercom workspace must be receiving emails (via forwarding or a connected inbox).

## How conversations land in Intercom

```mermaid theme={"dark"}
flowchart LR
  A[Customer emails your support address] --> B[Email arrives in Intercom]
  B --> C[AI replies via Intercom email]
  C --> D{AI can resolve?}
  D -- Yes --> E[Conversation resolved]
  D -- No --> F[Handoff note + unassign]
  F --> G[Rep picks up in Intercom inbox]
  G --> H[Rep replies — lands in customer's inbox]
```

## Setting up

<Steps>
  <Step title="Confirm email is routing to Intercom">
    Send a test email to the address Intercom is configured to receive. The conversation should appear in your Intercom inbox.
  </Step>

  <Step title="Confirm the AI processes the email">
    The AI should reply within approximately 30 seconds (email conversations have a longer initial delay). Check that the reply appears as a message from the AI admin.
  </Step>

  <Step title="Trigger a test handoff">
    Reply to the email thread with something like *"I want to talk to a human."* The AI should hand off — you'll see an internal handoff note and the conversation moved to your team's queue.
  </Step>

  <Step title="Verify the rep reply loop">
    Pick up the handed-off conversation in your Intercom inbox. Reply as an agent — the message should land in the customer's email inbox.
  </Step>
</Steps>

<Tip>
  If the AI doesn't reply to emails, confirm that the conversation is being assigned to the AI admin. Some Intercom routing rules may assign email conversations to a human team by default.
</Tip>

## What the rep sees

* The conversation appears in their **Intercom inbox** as an email thread.
* The full AI-to-customer transcript is already in the thread.
* An **internal handoff note** with summary, sentiment, and language.
* `opencx_handed_off` tag on the conversation for filtering views and reports.
* Replies sent from the Intercom inbox land in the customer's email inbox.

## Channel-specific details

<AccordionGroup>
  <Accordion title="Longer initial processing delay" icon="clock">
    OpenCX waits approximately **30 seconds** after the first email message before processing — significantly longer than the 4-second wait for Messenger. This gives Intercom time to finalize the conversation, apply routing rules, and assign the conversation to the AI admin. Email delivery is asynchronous, so this delay does not affect the customer's experience.
  </Accordion>

  <Accordion title="Outbound email automations are ignored" icon="filter">
    Emails initiated by Intercom outbound campaigns, automated sequences, or templates (where the source is not `customer_initiated`) are skipped. This prevents the AI from responding to your own email marketing.
  </Accordion>

  <Accordion title="Attachment handling" icon="paperclip">
    Email attachments follow the same rules as Messenger: supported image types are downloaded and uploaded to OpenCX storage. PDFs, videos, and audio files are forwarded as placeholder text when **Forward unsupported attachments** is enabled in [settings](/integrations/intercom/connect#settings-reference). Otherwise they are acknowledged but not processed.
  </Accordion>

  <Accordion title="Email thread formatting" icon="list">
    Intercom handles email threading natively. When the AI replies, the response appears as a new message in the email thread. Quoted previous messages and signatures are managed by Intercom's email formatting — OpenCX processes the latest message content only.
  </Accordion>
</AccordionGroup>

***

## Related Documentation

<CardGroup cols={2}>
  <Card title="Web (Messenger)" icon="comments" href="/integrations/intercom/channels/web">
    Messenger conversation specifics on top of the shared setup.
  </Card>

  <Card title="Connect Intercom" icon="plug" href="/integrations/intercom/connect">
    Credentials, webhook, and admin selection.
  </Card>

  <Card title="Intercom overview" icon="intercom" href="/integrations/intercom/overview">
    What else the Intercom integration covers.
  </Card>

  <Card title="Troubleshooting" icon="wrench" href="/integrations/intercom/troubleshooting">
    AI not replying to emails, webhook errors, handoff not firing.
  </Card>
</CardGroup>