Guide 05

Set up handoff to a team member

Define the reasons for handoff, the recipient, and the message customers receive while waiting.

5 steps≈ 2 min read

Before you begin

A responsible team member, their working hours, and a confirmed way for them to receive inquiries.

What to do

Define the triggers
List the reasons for handoff: a customer's request, a complaint, missing information, disputed terms, or an action outside the permitted scope. Assign a priority to each.
Assign a recipient
Assign a primary recipient and a backup for when they are off duty. Agree on a response time the team can actually meet.
Gather the context
Define what the handoff includes: a brief summary, important messages, information already collected, and the reason a person is needed. Do not make the customer repeat everything.
Prepare a reply to the customer
Agree on a clear reply for the customer: the request has been passed on, who will continue the conversation, and when to expect an answer. Automated replies must not contradict the team member or keep promising actions after the handoff.
Test the handoff
Test a normal handoff, an unavailable team member, and a repeat message from the customer. Confirm that the recipient has seen the inquiry and can take ownership; a notification alone does not mean it has been accepted.

Run the scenario with test data. Verify the result in your business system and make sure the responsible employee knows the next step.

This guide explains how to prepare and test a process. Available actions depend on your setup.