Defining Fallback, Handoff, and Stop AI Scenarios

Learn more about how the AI will stop and notify you when it has hand off the communications to a human.

Fallback

Fallbacks are what happens whenever the AI runs into a situation that it doesn't know how to handle. This could be something like the contact giving a gibberish answer, sending photos that the AI can't understand, or something unexpected happening in the conversation. When this happens, the AI will, by default, stop responding to the contact, add a tag called "fallback_reached", and the assigned user will be notified.

Fallbacks do not stop the AI from working. The AI bot is also instructed to answer back with a general answer like I am not the right person to answer that question or something like that.

Handoff

We utilize a handoff prompt to place a tag on the contact that has met the following requirements:

The contact has established a day for the appointment or consultation; The contact has established a time for the appointment or consultation; The contact has provided their phone number; The contact has agreed to or requested to schedule an appointment or consultation.

Once this is met, the conversation is marked as unread, and the assigned user is sent a mobile app notification to take over the conversation.

Stop AI

We have developed the STOP AI tag to give you the ability to toggle on and off the AI for specific conversations. This tag is also automatically applied once someone has had over 20 responses with your AI chat. This helps prevent abuse and increased Open AI API costs. This can be adjusted by support request.

Did this answer your question?
😞
😐
😁