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

# Connect Crisp

> Create a Crisp API token, save it in OpenCX, add the web hook in Crisp and tag a conversation so the AI answers it. Read this when you set up Crisp.

You connect Crisp with a workspace API token. Then you add a web hook in Crisp so OpenCX hears about your tagged conversations.

> [!NOTE]
>
> You need the Crisp workspace owner for the token, and the Integrations settings permission in OpenCX.

## Before you start

> [accordion] The workspace owner in Crisp
>
> Only the workspace owner can create the API token in Crisp.

> [accordion] The Integrations settings permission in OpenCX
>
> Connecting or changing the integration needs the Integrations settings permission in OpenCX.

> [accordion] The AI turned on for your channels
>
> A session takes the channel of its Crisp conversation: web chat, WhatsApp or email. Turn the AI on for each of those channels under [**Settings → Autopilot**](https://platform.open.cx/settings/autopilot). With assist mode on, the AI's reply stays in OpenCX as a draft and is not sent to Crisp.

## Setup

**1. Create an API token in Crisp**

In Crisp, go to **Settings → Workspace → Advanced configuration → REST API** and select **Create Token**.

Copy the token identifier and the token key.

> [!WARNING]
>
> Crisp shows the token key only once. Copy it before you close the dialog.

**2. Copy your Website ID**

In Crisp, go to **Settings → Workspace → Setup & Integrations** and copy the **Website ID**. This is your workspace ID.

**3. Save your credentials in OpenCX**

In OpenCX, go to [**Settings → Integrations**](https://platform.open.cx/settings/integrations) or [**Settings → Ticketing**](https://platform.open.cx/settings/ticketing) and open **Crisp**.

Paste the workspace ID, the token identifier and the token key, then save.

OpenCX checks the credentials with Crisp before saving. The token key is stored encrypted and is never shown again.

**4. Add the web hook in Crisp**

Copy the web hook URL shown on the Crisp card in OpenCX.

In Crisp, go to **Settings → Workspace → Advanced configuration → Web Hooks** and select **Add a Web Hook**. Paste the URL and turn on these events:

* `message:send`
* `message:received`
* `session:set_segments`
* `session:set_state`
* `session:set_email`
* `session:set_phone`
* `session:set_nickname`
* `session:set_data`

> [!WARNING]
>
> Treat the web hook URL as a secret. Crisp does not sign these web hooks, so anyone who has the URL can post events for your workspace.

**5. Tag a conversation to try it**

In the Crisp inbox, tag a conversation with `opencx`. The AI answers in that conversation, and a session for it appears in your [OpenCX Inbox](https://platform.open.cx/inbox).

To send conversations to the AI automatically, add the segment from a Crisp routing rule or workflow.

If the AI does not answer, see [Troubleshooting](https://docs.open.cx/integrations/crisp/troubleshooting.md).

## Settings

Change these on the Crisp card under [**Settings → Integrations**](https://platform.open.cx/settings/integrations).

| Setting | Default | What it does |
| - | - | - |
| **AI tag** | `opencx` | The Crisp segment that marks the conversations the AI answers. |
| **Handed-off tag** | `opencx_handed_off` | The Crisp segment added when the AI hands off or an operator takes over. |
| **When the AI hands off** | Only swap the tags | **Only swap the tags** removes the AI tag and adds the handed-off tag. **Also assign an operator** does the same, then assigns the conversation to the operator you pick. |
| **Operator** | None | The Crisp operator who gets handed-off conversations. Pick one when you choose **Also assign an operator**. |
| **Display name** | Your organization's name | The name customers see on AI replies in Crisp. |
| **Avatar** | None | The image customers see on AI replies in Crisp. Upload one from the card. |
| **Enabled** | On | Turn it off to stop the AI in Crisp without removing your settings. |
| **Reasoning link** | Off | After each AI reply, leave a private note in Crisp linking to that reply in OpenCX. |

## Replace the token key

The token key is never shown again after you save it. To replace it, enter a new one on the Crisp card and save.

## Good to know

> [accordion] Crisp's own AI agent and workflows
>
> If you use Crisp's own AI agent or automated workflows, make sure they do not answer the conversations you tag for OpenCX. Otherwise customers get two answers.

> [accordion] Tokens restricted to IP addresses
>
> If you restrict the Crisp token to specific IP addresses, allow OpenCX's addresses first. Otherwise saving fails with a message from Crisp. Ask [support@open.cx](mailto:support@open.cx) for the current list.

> [accordion] Crisp's daily request limit
>
> Crisp allows a limited number of API requests per day for a workspace token. Every AI reply uses a few. See Crisp's documentation for the current number.

***

## Related Documentation

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