Actions64
- Website Actions
- Conversation Actions
- People Actions
- Operator Actions
- Settings Actions
- Analytics Actions
- Availability Actions
- Campaign Actions
- Helpdesk Actions
- Visitors Actions
- Batch Actions
- Verify Actions
Conversation → Handle AI Review Action
AI-generatedOverview
This node operation handles actions from an AI review picker in a conversation on the Crisp platform. It processes different user-selected actions such as approving and sending the AI-generated response, copying the response to the input field, editing the response before sending, rejecting the AI suggestion, or requesting a regeneration of the AI response. This is useful in scenarios where an operator reviews AI-generated messages before sending them to a customer, allowing for manual intervention and control over automated responses.
Use Case Examples
- An operator receives an AI-generated message suggestion and chooses to approve and send it directly to the customer.
- An operator decides to edit the AI-generated message before sending it to ensure it fits the conversation context better.
- An operator rejects the AI suggestion and sends a private note indicating the rejection.
- An operator requests the AI to regenerate a new message suggestion if the original is not satisfactory.
Properties
| Name | Meaning |
|---|---|
| Website ID | The website ID from your Crisp dashboard, used to identify the website for the conversation. |
| Session ID | The session ID of the conversation to which the AI review action applies. |
| Action Type | The specific action selected from the AI review picker, such as approve and send, copy to input, edit then send, reject, or regenerate. |
| Original AI Response | The original AI-generated response from the picker that is subject to the selected action. |
| Edited Message | The edited message content to send, applicable only if the action type is 'edit then send'. |
| Additional Fields | Optional additional metadata fields related to the conversation, such as email, first name, last name, phone, company, state, blocked status, assigned user ID, role, domain, and verification string. |
Output
JSON
type- Type of message sent (e.g., text, note)from- Sender of the message, typically 'operator'origin- Origin of the message, typically 'chat'content- Content of the message, which varies based on the action type and may be the AI response, edited message, or a note indicating rejection or regeneration request
Dependencies
- Crisp API with Basic Authentication using website ID and API credentials
Troubleshooting
- Ensure the session ID and website ID are correctly provided and valid to avoid API errors.
- If the edited message is required (for 'edit then send' action), ensure it is not empty to prevent errors.
- Handle API errors gracefully, especially for invalid or expired credentials.
- Check that the action type is one of the supported options to avoid unexpected behavior.