> ## 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 conversation flow

> How a tagged Crisp conversation becomes an OpenCX session, how the AI replies, hands off and resolves, and what is synced onto the session.

After setup, the segments on a Crisp conversation decide who answers it. The AI answers conversations that carry the AI segment (`opencx` by default). It never answers the others; OpenCX only checks their segments and status to see when the segment is added.

## How a conversation reaches the AI

**1. The conversation gets the AI segment**

You tag the conversation in the Crisp inbox, or a Crisp routing rule or workflow adds the segment for you.

**2. OpenCX opens a session**

The tagged conversation becomes a session in OpenCX, linked to that Crisp conversation. Earlier messages in the conversation are brought in, so the AI has the context.

**3. The AI answers**

If the customer is waiting when you tag the conversation, the AI answers right away. After that, it answers each new customer message.

## How the AI replies

* The AI replies inside the Crisp conversation, on the channel the customer used there: website chat, WhatsApp or email.
* Customers see the AI under the name and avatar you choose, with Crisp's **Bot** badge. The name defaults to your organization's name.
* Files the AI sends appear in Crisp as links to the file.
* With **Reasoning link** turned on, each AI reply is followed by a private note linking to that reply in OpenCX, where your team can see why the AI answered. Customers do not see it.

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

## When the AI hands off

**1. The segments are swapped**

The AI removes the AI segment and adds the handed-off segment (`opencx_handed_off` by default).

**2. A private note lands in Crisp**

The AI leaves a private note in the Crisp conversation with a summary and a link to the session in OpenCX. Your customer does not see it.

**3. The conversation is assigned (optional)**

If you chose **Also assign an operator**, the conversation is assigned to the operator you picked.

## When an operator takes over

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.

Private notes from operators do not stop the AI. They are saved on the session as internal comments.

## Give a conversation back to the AI

Remove the handed-off segment and add the AI segment again. If a teammate has taken the session in OpenCX, it stays with them: give it back to the AI from the OpenCX inbox.

## Resolving

* **When the AI resolves a session**, the Crisp conversation is marked resolved with a summary note, linking to the session in OpenCX, when there is a summary, as long as it still carries the AI segment.
* **When a teammate resolves a session in OpenCX**, the Crisp conversation is marked resolved. Reopening the session reopens the conversation.
* **When you resolve a conversation in Crisp**, its session in OpenCX closes.
* **When the customer writes again**, the same session reopens.

## What is synced onto the session

| From Crisp | On the OpenCX session |
| - | - |
| Customer's name, email and phone | The session's contact. OpenCX matches an existing contact by email, then by phone. Existing contact details are never overwritten. |
| The conversation's data | Custom data. Each key is prefixed `crisp_`. Text, number and true/false values are synced. |
| Other segments | Tags. |
| Customer and operator messages and files | Messages and files on the session. |
| Operators' private notes | Internal comments. |

## Replies from the OpenCX inbox

Replies your teammates write from the OpenCX inbox on a linked session are delivered to the Crisp conversation under their name. Bold, italics, lists and links keep their formatting.

To open the conversation in Crisp, use **Open in Crisp** on the session's **Crisp conversation** card in the OpenCX inbox.

## Pausing the AI

Turn off **Enabled** on the Crisp card to stop the AI in Crisp. Your settings stay in place.

While it is off, nothing is sent to Crisp: replies from the OpenCX inbox on linked sessions are refused with a message saying the integration is paused.

***

## Related Documentation

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

> [card] [Connect Crisp](https://docs.open.cx/integrations/crisp/connect.md)
>
> Credentials, web hook events and settings.

> [card] [Overview](https://docs.open.cx/integrations/crisp/overview.md)
>
> What the Crisp integration does and how it fits with your team.

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