Live Handover Etiquette: How Your Team Should Take Over From the AI Assistant

Designing when the AI hands over is half of a good handover. The other half is what your team does when they arrive. A visitor who has been chatting with an assistant and then meets a person is in a delicate moment. If the person says 'How can I help?' as though the conversation never happened, the visitor feels ignored. If the person is slow, curt or contradicts what the assistant said, trust drops. If the person reads the history, greets them by name, picks up the thread and solves the problem, the visitor remembers the business as helpful and organised. This guide is for the people who take over: what to check before you type, how to greet, how to handle mistakes made by the assistant, how to keep the right tone, how fast to respond, how to close the loop and how to train and review your team.

Before you type: read the conversation

1. Read the whole conversation, not just the last message.
2. Note the visitor's name, the problem in their own words and what they already tried.
3. Check what the assistant told them: prices, times, promises.
4. Note the reason for the handover: request, complaint, sensitive topic or unanswerable question.
5. Check any contact details captured.
6. Decide what you can do and what you need to find out.

Thirty seconds of reading prevents most of the mistakes that make handovers feel bad.

Greeting that shows you have read it

• Use their name.
• Say who you are.
• Show that you know the situation.
• Acknowledge feelings when relevant, briefly and sincerely.

Speed and expectations

Handover is a promise: a person is coming. Keep it. Reply within the time the assistant stated, and if you cannot solve the problem immediately, say what you will do and when. A quick 'I am checking this now and will reply in ten minutes' is far better than a long silence. If you are the wrong person, say who will take over and pass the conversation on properly.

Correct the assistant without blaming it

The assistant may have said something wrong or incomplete. Correct it plainly: 'I need to correct something. The price I see for that service is $95, not $85.' Do not blame the software or the customer, and do not make a fuss. Then record the error so the knowledge base can be fixed. See how to review your chatbot's conversations each week.

Tone

• Warm and plain, like a good receptionist.
• Short paragraphs; avoid jargon.
• Match the customer's level of formality, within your brand.
• Do not over-apologise, but do own real mistakes.
• Never argue; stay calm when someone is angry.
• Avoid canned phrases that ignore what the customer said.

See de-escalating frustrated customers with AI guardrails.

Privacy and sensitive information

• Do not ask for sensitive details in an open chat; move to a secure route.
• Verify identity before discussing account details, where relevant.
• Do not copy the conversation into unsecured places.
• Follow your privacy policy for how long chats are kept.

Closing the loop

1. Confirm the outcome: what was done and what happens next.
2. Ask whether there is anything else.
3. Record the outcome in your system: resolved, booked, follow-up needed.
4. If a follow-up is promised, put it in your task list, with a time.
5. Note anything the assistant should learn for the future.

A handover that ends with 'thanks, bye' and no record leaves the next person without context.

Hand back to the assistant, or not

Decide with your team whether the conversation returns to the assistant after you finish, or ends. If it returns, say so: 'I will let the assistant help you with booking, and I am still here if you need me.' If you take over, keep control until the end so the visitor does not hear two voices.

Handling out-of-hours takeovers

When a handover arrives outside your hours, the first person in the next morning should start with an apology for the wait if the assistant promised a time, and with the conversation history in front of them. Prioritise by urgency: emergencies first, then complaints, then routine requests. See live human handover flow design for how to design the process around it.

Training your team

• Practise with three real past conversations: read, greet, resolve, close.
• Agree a standard for greeting and response times.
• Share examples of good handovers and bad ones.
• Make it easy to record assistant errors.
• Review a sample of handovers each week for the first month, then monthly.

A sample handover

Measure handover quality

A one-page handover checklist

• Read the full conversation.
• Greet by name and say who you are.
• Show what you have understood.
• Correct any mistake the assistant made, calmly.
• Say what you will do and by when.
• Do it, and confirm the outcome.
• Record the result and any content fix needed.
• Ask whether there is anything else.

Print this and keep it beside the screen for the first month. Once the routine is habit, the handover feels natural and the customer barely notices the join between assistant and person.

Common mistakes

• Starting with 'How can I help?' as if nothing was said.
• Contradicting the assistant without explanation.
• Leaving the visitor waiting with no update.
• Asking for information already given.
• Forgetting to record the outcome.

When the visitor has left

Sometimes a visitor closes the chat before you arrive. Use the contact details the assistant captured to reach them, by the method they chose, and refer to the conversation: 'You asked our assistant about moving your appointment; I have done that for you.' If no contact details exist, record the case so you can respond if they return.

Frequently asked questions

See the human handover feature, try a handover in the playground and read emergencies in automated chat.

Further reading

• Google Search Central: creating helpful, people-first content: What Google looks for in useful pages.