Handing a customer to another manager without losing context

A handover works when four things travel with the conversation: what the customer wants, what they were promised, where you stopped, and what’s blocking the purchase. Without those four lines the new manager opens with «could you explain that again?» — and that’s where half the orders are lost.

The customer doesn’t care how many of you there are. To them it’s one shop that has just forgotten everything they agreed.

Why doesn’t conversation history do the job?

Because nobody reads forty messages before replying. At best the new manager skims the last five — and misses exactly the thing that was promised at the start.

A handover is the conversation compressed to what affects the next reply. Everything else stays in the thread as an archive, not as instructions.

1. 1

   What they want

   The specific product or job. «Looking for autumn boots, size 38, no heel».

2. 2

   What was promised

   The most important line. A discount, a date, a special condition — anything you'll have to honour.

3. 3

   Where you stopped

   The last step and whose turn it is. «Waiting on daylight photos — from us».

4. 4

   What's blocking

   Price, size, doubts about delivery. This determines the next message.

How should the handover read to the customer?

One sentence, from the new manager, demonstrating they know the context.

Works: «Hi, I’ll be looking after you from here — I know you’re waiting on the blue in a 38, it landed Wednesday.» The customer sees nothing was dropped.

Doesn’t work: «Hello, my name is Olena, how can I help?» That’s starting over with a new name attached.

Who owns the customer after the handover?

One manager, fully. Diffuse ownership is the main reason threads stall right after a handover: each person assumes the other will reply.

The simplest working rule is conversation ownership: whoever answered first sees the customer through to the order. The handover happens explicitly and once, not «as it works out».

That’s technically harder than it sounds. In the WhatsApp Business app, several linked devices work from one shared inbox: there are no roles, no permissions and no record of which team member sent which message — everyone sees everything and writes under one identity. So the ownership rule has to be held as a team agreement rather than a setting in the app.

What about your predecessor’s promises?

Honour them. Even the awkward ones, even if you’d never have promised that.

Withdrawing a condition after a handover costs more than the condition itself: the customer draws a conclusion about the shop, not about one manager. The conversation about why the promise was unwise is an internal one, held afterwards.

Customer: {name, channel}
Wants: {product/job + specifics}
Promised: {discount / date / condition — or «nothing»}
Stopped at: {last step, whose turn}
Blocked by: {price / size / doubt}