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

# Crisp overview

> Keep your team in Crisp while the OpenCX AI answers the conversations you tag, hands them off with a summary and keeps status in sync.

Your team keeps working in Crisp. The AI answers only the Crisp conversations that carry a segment you choose. The segment is `opencx` by default. Segments are Crisp's tags. The AI never answers conversations without the segment; OpenCX only checks their segments and status to see when the segment is added.

> [!TIP]
>
> Setup starts at [**Settings → Integrations**](https://platform.open.cx/settings/integrations) or [**Settings → Ticketing**](https://platform.open.cx/settings/ticketing) in your OpenCX dashboard. Open **Crisp**.

## What you get

> [accordion] You choose which conversations the AI answers
>
> Tag a conversation with the AI segment and the AI takes it. Earlier messages in the conversation are brought in, so the AI has the context. If the customer is waiting when you tag it, the AI answers right away.
>
> To send conversations to the AI automatically, add the segment from a Crisp routing rule or workflow.

> [accordion] AI replies inside Crisp
>
> The AI replies in the Crisp conversation, on the channel the customer used there: website chat, WhatsApp or email. Customers see the AI under a name and avatar you choose, with Crisp's **Bot** badge. The name defaults to your organization's name.

> [accordion] Handoff with a summary
>
> When the AI hands off, it removes the AI segment and adds a handed-off segment (`opencx_handed_off` by default). It leaves a private note in Crisp with a summary. It can also assign the conversation to an operator you pick.

> [accordion] Your team takes over by replying
>
> Any reply from a human operator in Crisp stops the AI on that conversation. The segments are swapped the same way as on a handoff. To give the conversation back to the AI, remove the handed-off segment and add the AI segment again.

> [accordion] Status stays in sync both ways
>
> When the AI resolves a session, the Crisp conversation is marked resolved with a summary note. When a teammate resolves or reopens a session in OpenCX, the Crisp conversation follows. Resolving a conversation in Crisp closes its session in OpenCX. If the customer writes again, the same session reopens.

## In your OpenCX inbox

> [accordion] Each tagged conversation is a session
>
> Each tagged conversation becomes a session in OpenCX, linked to that Crisp conversation. The session holds the customer's and your operators' messages and files.

> [accordion] Customer details, data and tags come with it
>
> The session gets the customer's name, email and phone, the conversation's data from Crisp as custom data, and Crisp's other segments as tags. See [what is synced](https://docs.open.cx/integrations/crisp/conversations.md#what-is-synced-onto-the-session).

> [accordion] Reply from OpenCX too
>
> Replies your teammates write from the OpenCX inbox on a linked session are delivered to the Crisp conversation under their name.

> [accordion] Your per-channel AI settings apply
>
> A session takes the channel of its Crisp conversation: web chat, WhatsApp or email. The AI must be turned on for that channel in OpenCX. With assist mode on, the AI's reply stays in OpenCX as a draft and is not sent to Crisp.

## Not included yet

* Moving a handed-off conversation to a Crisp sub-inbox.
* Importing your past Crisp conversations.
* Satisfaction surveys (CSAT) in Crisp conversations.

***

## Related Documentation

> [card] [Connect Crisp](https://docs.open.cx/integrations/crisp/connect.md)
>
> Create a token in Crisp, save it in OpenCX and add the web hook.

> [card] [Conversation flow](https://docs.open.cx/integrations/crisp/conversations.md)
>
> How tagging, replies, handoff and resolving work.

> [card] [Troubleshooting](https://docs.open.cx/integrations/crisp/troubleshooting.md)
>
> AI not replying, two answers, saving fails.

> [card] [Human handoff](https://docs.open.cx/handoff/introduction.md)
>
> Global handoff rules and office hours.


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