To trigger human takeover, use the following Custom Payload response:
{ "human-takeover": true }
To trigger human takeover, use the following Custom Payload response:
{ "human-takeover": true }
Use the “chips” rich message with the ID sb-human-takeover to provide options like “Human support” to users, allowing them to initiate manual takeover.
To manually initiate human takeover, create a new Intent and add a Custom Payload response with the syntax: { "human-takeover": true }.
Future user messages within ten days of human takeover, without an answer from the chatbot, will trigger agent notifications.
Conversations that the chatbot has successfully answered are marked as read and moved to the bottom of the Inbox list.
If enabled, requests are sent only when a user message is longer than three characters and contains at least two words. This prevents mistaken requests and ensures meaningful interactions.
When a human agent in Chat.RPAiX replies to a user, the human takeover is automatically activated, ensuring a seamless transition between automated and human-assisted interactions.
If you’re using Slack, no messages will be sent by the chatbot if it knows the answer to the user’s question. All conversation messages are forwarded to Slack once human takeover is active.
The chatbot is fully reactivated when the conversation is either archived or deleted.
Yes, you can force a Dialogflow message to be sent by adding the custom Payload value "force-message": true to the Intent.
No, default fallback messages are not sent within ten days of human takeover if the chatbot is unable to answer the user’s question in the same conversation.
Once the human agent goes offline, the chatbot is reactivated and resumes handling conversations.
The (chatbot) Chat.RPAiX remains disabled as long as the human agent is online and actively engaged in the conversation.
When human takeover is activated, the Chat.RPAiX is automatically disabled while the human agent is online and available to handle the conversation.