Widget conversations and human handoff
Understand where chats appear, how customers reach your team, and how previous conversations work.
In AI chat mode, the widget uses knowledge assigned to its inbox to answer questions. It can research further, ask a focused clarification, or explain what it still needs.
Find the conversation
AI-only conversations stay outside the human support queues. You can review them in the customer’s AI conversations history.
When a visitor chooses Talk to a human instead, the existing conversation becomes an unread human-support thread. Your team gets the AI history and the customer’s question together, rather than a separate disconnected ticket.
Anonymous visitors provide a follow-up email during an explicit handoff. Signed-in customers can use their verified email without typing it again.
Continue with your team
Once handed off, later messages in that visit stay with your team rather than returning to AI. Teammate replies appear while the widget is open. Human contact only follows the human-support path without an AI conversation first.
A normal AI technical failure shows an automated support update and leaves the option to contact your team. A reply-safety block is different: it retains the answer privately and routes the conversation for human review.
Browse previous conversations
Previous conversations lets verified customers browse human support threads in the widget’s inbox, including closed ones. They can open a thread, load older messages, and send a follow-up even when widget AI is disabled.
Reading a closed thread doesn’t reopen it; replying does. Private notes and unsent drafts aren’t shown. Anonymous visitors can access only a human thread authorized by their current session, not past history based on an entered email.
End a visit
Reloading the same tab can restore the current visit. Ending the conversation, switching signed customers, or 30 minutes of inactivity starts a new AI visit. The inactivity timeout does not close a conversation already handed to your team.
Browser, operating system, and time-zone details can help your team troubleshoot. They are reported context, not verified identity or a precise location.