The AI doesn't reply to a conversation
The AI doesn't reply to a conversation
Check, in order:
- The conversation carries the AI segment. It is
opencxunless you changed AI tag. The AI never answers conversations without it. - Enabled is on in the Crisp card.
- The AI is turned on in OpenCX for the conversation’s channel: web chat, WhatsApp or email.
- Assist mode is off for that channel. With assist mode on, the AI’s reply stays in OpenCX as a draft and is not sent to Crisp.
- The web hook in Crisp uses the URL from the Crisp card and has all eight events turned on. See Connect Crisp.
- No human operator has replied. A reply from an operator stops the AI on that conversation.
- The customer is not blocked in OpenCX, by contact or by email domain. A blocked customer’s messages are not saved on the session and the AI does not answer them.
The AI stopped answering a conversation
The AI stopped answering a conversation
The AI handed off, or a human operator replied in Crisp. In both cases the AI segment was removed and the handed-off segment was added.To give the conversation back to the AI, remove the handed-off segment and add the AI segment again.
Customers get two answers
Customers get two answers
Crisp’s own AI agent or an automated workflow is answering the same conversation. Make sure they do not answer the conversations you tag for OpenCX.
Saving the credentials fails
Saving the credentials fails
OpenCX checks the credentials with Crisp before saving. Check that:
- The workspace ID is the Website ID from Settings → Workspace → Setup & Integrations in Crisp.
- The token identifier and the token key come from the same token.
- The token is not restricted to IP addresses that leave OpenCX out. If it is, allow OpenCX’s addresses first. Until then, saving fails with a message from Crisp. Ask [email protected] for the current list.
I can't see the token key anymore
I can't see the token key anymore
Crisp shows the token key only once, and OpenCX never shows it again after you save. Create a new token in Crisp, then enter the new token identifier and token key in the Crisp card.
A private note didn't stop the AI
A private note didn't stop the AI
That’s expected. Only a reply from a human operator stops the AI. Private notes from operators are saved on the session as internal comments.
The AI's reply is not in Crisp
The AI's reply is not in Crisp
Assist mode is on for that channel. The AI’s reply stays in OpenCX as a draft and is not sent to Crisp.
Crisp did not accept a reply
Crisp did not accept a reply
Crisp turned the reply down or could not be reached, for example when the workspace token hit its daily request limit.
- A reply you send from the OpenCX inbox shows an error. Send it again.
- If Crisp took the text of a reply but not one of its files, the reply counts as sent. An internal comment on the session names the files the customer did not get.
- An AI reply is not counted as sent. The AI answers the customer again when the next event arrives from Crisp for that conversation.
Old sessions lost their Crisp conversation
Old sessions lost their Crisp conversation
That’s expected after you connect a different Crisp workspace, or disconnect Crisp. Sessions from the earlier workspace stay in OpenCX, but replies to them no longer go to Crisp.
A customer's file shows as “File not received”
A customer's file shows as “File not received”
OpenCX could not copy the file: its link pointed to a private or internal address, or the download failed. The AI did not read it. Open the conversation in Crisp to see the file.
A file from the AI shows as a link
A file from the AI shows as a link
That’s expected. Files the AI sends appear in Crisp as links to the file.
A contact's details didn't change
A contact's details didn't change
OpenCX matches the customer to an existing contact by email, then by phone. Existing contact details are never overwritten.
Some conversation data is missing from the session
Some conversation data is missing from the session
Text, number and true/false values from the conversation’s data are synced as custom data. Each key is prefixed
crisp_, so look for crisp_ followed by the key’s name.Limits
Related Documentation
Connect Crisp
Credentials, web hook events and settings.
Conversation flow
How tagging, replies, handoff and resolving work.
Overview
What the Crisp integration does and how it fits with your team.
Human handoff
Global handoff rules and office hours.