The handover: what the next shift needs that the system does not store

A queue tells the next shift what is unanswered. It does not tell them what was promised, what is already escalated, or who is angry - and those three are what make the second reply of the day good or terrible.

The promise problem

"I'll check with the warehouse and come back to you within the hour." That conversation is now answered, so it drops out of the unanswered queue, and the promise lives in one person's head until they go home.

This is the single most damaging gap in shift-based messaging, because the customer experiences it as being lied to.

Write it in the conversation

Handover notes belong on the conversation they are about, not in a separate document. The next person is already there; making them read a shift log and match it up by name is a step that gets skipped at 08:05.

[internal] Promised warehouse check by 10:00.
Ref 10432, two tyres 195/65 R15. Customer already
had one delayed order this month - be generous.

The three-line handover

1. Promises with times. Who is expecting what, when.
2. Escalations still open. Who it went to and when - so the next shift chases rather than escalates again.
3. The difficult ones. Named, with one line of context. Not a judgement of the customer; a warning that this one needs care.

What not to hand over

Everything else. A handover that lists every open conversation is not read, and one that is not read is worse than none because everybody believes the information was passed on.

Closing the loop

The end-of-shift version matters as much: what was promised and delivered, what was not, and what is still waiting. A team that only hands over forward accumulates half-finished commitments nobody counts - which shows up eventually as the reopen rate.