Resources

Designing human handoff: a checklist

When an assistant handles the first reply to an enquiry, the quality of your service depends on one moment. That is the moment the assistant stops and a person starts.

Most teams spend their time on what the assistant should say. Fewer spend time on when it should stop talking. This checklist covers the second question. Use it before you switch on any channel.

1. Decide what must always reach a person

Write the list down before you write a single answer. Start with the obvious items.

  • Anything about safety, health or money that could be read as advice.
  • Complaints and anyone who is upset.
  • Requests to change, cancel or refund something.
  • Large or unusual requests that fall outside your normal process.
  • Any message where the person asks for a human.

Add the items that are specific to your organisation. Ask the people who answer enquiries today what they would never want handled without them.

2. Decide how the assistant recognises those moments

A rule that nobody can test is a hope, not a rule. Turn each item on your list into something observable.

  • Topics: words and subjects that always trigger a handoff.
  • Repeated misunderstanding: the same question asked twice, or a reply that does not fit.
  • A direct request to speak to a person, in any wording.
  • Strong feeling in the message.
  • Signals of value, such as a large order or a senior role.

Keep the first version simple. You can add rules after you read real conversations.

3. Decide who gets it, and how fast

A handoff with no owner is a dropped enquiry. Name a person or a small group for each type of conversation. Decide how they are told, and what happens when they are away.

Decide your hours as well. If nobody is available at night, say so to the customer and set a clear expectation for the next working day. An honest delay is better than a silent one.

4. Decide what the person sees

The worst handoff is the one that makes the customer repeat themselves. The person who takes over should see the whole conversation, in order. They should also see what has already been answered, and why the assistant stopped.

Write down the one or two lines of context your team needs at the top of every handoff.

5. Decide what the customer is told

Say it plainly and briefly. Tell the customer that a person will take over, and what happens next. Give a time only if you can keep it.

Do not pretend the assistant is a person. Where the law or the platform requires you to say that people are talking to an automated system, say it clearly.

6. Test with real conversations

Take a sample of past enquiries, including the awkward ones. Run each through your setup and check where the handoff happens. Try a few that are designed to confuse it.

Look for two failures. The first is a handoff that should have happened and did not. The second is a handoff that happened for no good reason and wasted your team’s time.

7. Review on a schedule

Read the conversations that were handed off, and a small sample of those that were not. Ask what the assistant got wrong, and what the person had to fix. Change the rules, then read again.

Put the review in a calendar with a name next to it. A review nobody owns does not happen.

A short version to print

  • What must always reach a person?
  • How will the assistant spot it?
  • Who gets it, how, and when are they away?
  • What will they see?
  • What will the customer be told?
  • Which real conversations did we test?
  • Who reviews, and when?

If you can answer all seven in a sentence each, you are ready to start small and learn from real enquiries.

All resources