When the AI hands a chat to your team

Learn when Opskeet's AI agent hands a chat to a person, what your team sees, and how to take over or hand a chat back.

Updated
On this page

The AI hands a chat to your team when it shouldn't or can't carry on. Visitors are never stuck with a bot.

Why it hands over

Your team sees one of these reasons in the note:

  • Asked for a person: the visitor asked, or clicked Talk to a person.
  • Not in the knowledge: it couldn't find the answer, offered a person, and the visitor said yes.
  • Needs something the AI can't do, like a refund or an account change.
  • A guardrail says so.
  • Frustrated.
  • Reached the AI's reply limit: Hands over after (10 replies by default) or the daily limit.
  • The AI couldn't answer: something went wrong.
  • Still unresolved when they went quiet.

If it isn't sure enough of an answer, it tells the visitor so and offers a person instead of guessing.

What happens

  1. The visitor sees "I'm bringing in someone from the team. They'll reply here."
  2. Your team gets an internal note with the reason.
  3. The chat moves out of AI is answering and notifies the assignee, or everyone.
  4. If you use auto-assign, it's assigned.

Take over a chat

Any visible reply from a teammate takes the chat over. You can also click Take over in the bar that says "The AI is answering." Internal notes don't take over.

Hand a chat back

Click Hand back to the AI in the conversation's actions, or press I. If the visitor wrote last, the AI answers right away.

You can't hand back tickets or closed chats.

See handover reasons over time

Reports → AI → Why it handed over shows the reasons for the period. Use Questions it couldn't answer to fill the gaps.

Did this help?

Related articles