Hand-Off to a Human: What Visitors and Agents See in Talkmio

A hand-off to a human is the moment when the AI assistant stops answering and a person takes over, and in Talkmio it is designed to be quiet and complete. Mio, the assistant, hands a conversation to your team when it cannot answer from your content, when the visitor asks for a person, when the visitor complains or when the visitor asks about a specific order. The visitor is told that a person is being brought in, and your team receives the whole conversation with a clear badge. This guide walks through a hand-off to a human from both sides of the screen: what the visitor sees, what your team sees and what you can do to make the moment smooth.

The description follows the Talkmio documentation and the pricing page. It does not add behaviour that those pages do not describe.

The Four Triggers for a Hand-Off to a Human

The documentation names four situations in which Mio hands the conversation over. They are worth learning by heart, because they define what Mio will and will not try to handle alone.

Trigger	Typical example	Why a person should answer
Mio cannot answer from your content	A question about a product variant that is on no page	Mio answers only from your content and does not guess
The visitor asks for a person	“Can I talk to someone?”	The visitor has decided what they want
The visitor complains	“This is the second time my package is late.”	Tone and judgment matter more than speed
The visitor asks about a specific order	“Where is order 4821?”	It needs access to your systems and a person’s decision

Two of the four, complaints and orders, are decided by the topic. The other two are decided by the content and by the visitor. That is why the quality of your knowledge base changes your hand-off rate: the more of your facts Mio can find, the fewer questions fall into the first row. Our guide to when an AI chatbot should hand off explains the reasoning behind the triggers.

What the Visitor Sees During a Hand-Off to a Human

According to the pricing FAQ, Mio tells the visitor that it is connecting them with a person. The visitor does not have to start again: the chat appears in your Inbox with the full history, so nobody has to repeat the question. That is the first rule of a good hand-off, and it is built in.

What happens next depends on whether your team is online. If someone is online, the visitor waits for a reply in the same chat window. If the whole team is offline, the visitor is asked for an e-mail address before the first message, and when you reply from the Inbox later, the answer goes out as an e-mail. This is the same flow that covers nights and weekends. Our guide to live chat offline messages describes how to write the text that the visitor sees.

Visitors judge a hand-off by two things: whether it was honest and whether it was quick. Honest means that the assistant admits it cannot answer, rather than offering a vague reply. Quick means that you reply before the visitor gives up. You control the second, and the settings below help.

What Your Team Sees: Badge, Alert and History

On your side, the conversation gets a “needs human” badge. You receive a browser notification in the Inbox. If nobody is online, you also receive an e-mail and a push notification on the Talkmio mobile app for iOS or Android. Three details make this efficient.

• The badge separates urgent from routine. Conversations that Mio answered alone do not carry it, so a quick look at the Inbox shows what needs a person.
• The history comes with the chat. You see what the visitor asked, what Mio answered and where it stopped, so your reply starts from the right point.
• The alert follows your presence. The e-mail and push notification are used when nobody is online, so you are not flooded while the team is at the desk.

Each team member sets a status of Online, Away or Offline. Set it honestly. If you are the only person and you go to sleep with the status on Online, the visitor will wait for a reply that does not come. Our guide to live chat notifications describes how to choose what reaches you and when.

After the Hand-Off: Mio Stays Out

Once a person replies, Mio stays out of that conversation. This matters for two reasons. First, it avoids the confusing situation where a person and an assistant answer the same visitor at the same time. Second, it means the conversation is yours until you end it. If a visitor writes again later, check the conversation’s status and the filters, so that a follow-up is not lost.

It also means that the first human reply is important. Acknowledge the visitor’s problem in one sentence, answer the question and say what happens next. If you need time, say so and give a clear time frame that you can keep. A visitor who feels heard after a hand-off is often more loyal than one who never needed it.

Your Reply Toolbox in the Inbox

The documentation lists several tools that make a human reply faster and better. They are worth knowing, since they are the other half of a good hand-off to a human.

• Assign: give the conversation to a team member, so that two people do not reply to the same visitor.
• Priority and status: set Low to Urgent, and Open, Pending, Solved or Closed. A visitor who is upset or who asked about an order often deserves a higher priority.
• Convert to ticket: every conversation can become a numbered ticket, which is useful when the answer needs time or follow-up.
• Quick replies: typing a slash inserts a quick reply.
• Internal note: a note visible only to your team, for passing context between colleagues. Our guide to internal notes in live chat shows how teams use them.
• Suggest, Translate and Polish: Suggest drafts a reply from your knowledge base, Translate turns your draft into the visitor’s language and Polish fixes grammar and tone.
• Visitor details: the header shows who the visitor is, so that your reply can use context rather than start from scratch.

The sequence for a typical hand-off is short: open the conversation, read the history, assign it to yourself, check the visitor details, use Suggest for a first draft, edit it into your own voice and send. For a visitor who writes in another language, Translate and Polish save time without lowering quality.

Two Paths: Team Online or Team Offline

The same trigger leads to two different experiences, depending on who is present. The table summarises them.

	Team online	Team offline
Visitor sees	That a person is being brought in; waits in the same chat	A request for an e-mail address before the first message
Your team gets	Browser notification in the Inbox and the “needs human” badge	The badge, plus an e-mail and a push notification on the mobile app
Reply goes out	In the chat window	As an e-mail from the Inbox
Best practice	Reply within your response time target	Reply first thing, starting with complaints and orders

SLA settings help here. Conversations without a first reply within your target time get an “overdue” badge, which you set under Settings, Response time target. Choose a target you can keep in practice, and review it when your team changes.

Shape What Gets Handed Off

You do not have to accept the default behaviour as it is. Two tools let you shape it.

Business Instructions

The business instructions tell Mio what you sell, which tone to use and what it must never promise. The documentation gives an example: never quote delivery dates, and hand order questions to the team. If a topic is too sensitive or too variable for an assistant, write a rule that sends it to a person. Keep the rules short and specific, and test them in Try Mio.

Content

Most avoidable hand-offs come from missing content. Review the conversations that Mio handed over and ask: was the answer actually available on our website? If it was, why did Mio not find it, and is the page clear enough? If it was not, add the fact. Each one you fix reduces future hand-offs and improves the assistant for everyone. Our guide to the AI chatbot hand-off rate explains how to judge whether the number is healthy.

Review Hand-Offs Every Week

A weekly review takes fifteen minutes and pays for itself. Open the Inbox and filter for conversations that Mio handed to your team. Read ten of them. For each one, write down the reason: missing content, unclear content, a topic that should always go to a person, or a visitor who simply wanted a human. Then open Reports and look at the hand-offs figure beside the share answered by Mio alone. If hand-offs rise when you launch a new product or change a policy, the cause is usually content that has not caught up. Add it, use Re-read so Mio reads the new pages, and check again the following week.

The aim is not to reduce hand-offs to zero. Some questions should always go to a person, and a good customer service setup treats them as a feature. The aim is that every hand-off is for a good reason, and that nothing that a page could have answered is left to a person.

Common Mistakes With a Hand-Off to a Human

• Leaving the status on Online: visitors wait for people who are not there.
• Ignoring the badge: if nobody checks the Inbox, the hand-off is just a delay.
• Replying without reading the history: the visitor has already explained once, and a repeated question feels careless.
• Using the same tone for everyone: a complaint needs a different first sentence from a routine question.
• Not feeding back into the content: without a weekly review, the same questions come back every week.

A short test makes all of this concrete. Open your site in a private window, ask a question that your pages do not answer and watch the flow from both sides. Then ask about an order and ask for a person. Three minutes of testing will show you what your visitors see, and it is the best way to know whether your texts are clear. For the general idea of an AI assistant that passes work to people, the principle is the same everywhere: let the software handle what is written down, and let people handle what needs judgment.

Frequently Asked Questions

When does Mio hand a chat to my team?

According to the documentation, Mio hands over when it cannot answer from your content, when the visitor asks for a person, when the visitor complains and when the visitor asks about a specific order. The conversation then shows a needs-human badge in your Inbox.

Does the visitor have to repeat the question?

No. The chat appears in your Inbox with the full history, so your team sees the whole conversation. The visitor is told that Mio is connecting them with a person, and does not need to start again or explain the problem a second time.

What if my team is offline during a hand-off?

The visitor is asked for an e-mail address before the first message. You receive the conversation in the Inbox, with an e-mail and a push notification on the mobile app if nobody is online, and your reply from the Inbox goes out as an e-mail.

Will Mio keep answering after a person replies?

No. Once a person replies, Mio stays out of that conversation, so the visitor does not get two answers at once. The conversation remains yours until you close it or assign it to a colleague, so reply promptly.

Can I decide which topics always go to a person?

Yes, through the business instructions. They tell Mio what you sell, which tone to use and what it must never promise. The documentation gives the example of never quoting delivery dates and handing order questions to the team.

How do I reduce unnecessary hand-offs?

Review the handed-off conversations weekly and add the missing content: pages, question and answer pairs or files. Use Re-read after changing a page and test the questions again in Try Mio. Keep topics that need judgment, such as complaints, as deliberate hand-offs.

The Bottom Line

A good hand-off to a human is honest, complete and quick: Mio admits what it cannot answer, the history travels with the chat, your team gets a clear badge and alert, and Mio stays out once a person replies. Set your status truthfully, write rules for topics that need judgment and review hand-offs every week. Start free with Talkmio, run the three-minute test in a private window and see the hand-off from your visitor’s side before it matters.