Chatter Handover Note Examples: 10 Annotated Handovers

A handover note has one reader: the person who has to answer that fan in the next few minutes. Everything in it has to change their next message, and everything that does not change it is noise that pushes the useful lines off the screen.

Below are ten worked examples: four notes, three pickup messages the fan actually receives, and three that break the thread. What a handover is for is settled elsewhere; this page is the wording. Fans are shown as Fan A, prices as [price].

What is a handover note supposed to carry?

Six fields per live fan, in the same order every time. The shift-level summary that sits above them belongs in the chatter shift schedule template, linked at the end of this page.

Field	What it records	Why the next chatter needs it
Position	How many exchanges since the last paid offer	Stops the offer being repeated too early
Bought	What was bought, at the price actually paid	The listed price and the paid price are not the same number
Refused	What was declined, and in what words	“Not tonight” and “no” need different next messages
Promised	Anything owed, with the deadline given	Unkept promises are how threads die quietly
Detail	The personal fact in play, marked used or unused	Decides whether it can be spent in the next message
Do not re-offer	One line, no explanation	The line that decides what not to send

The order matters more than the wording. A fixed order means the incoming chatter finds the position line without reading the rest, which is the difference between a note that is read and a note that is skimmed.

What does a handover note actually look like?

Four fans, four states a thread can be in at a shift change.

1. The warm thread, no offer yet.

Fan A. Position: past the tenth exchange, no offer made. Bought: nothing yet. Refused: nothing. Promised: nothing. Detail: works nights, waiting to hear this week if they keep him on, unused. Do not re-offer: n/a. Ready for a first offer this evening.

This is the note that earns its keep. Our data shows a pitch before the sixth message drops conversion by roughly a third, with the optimum after about ten exchanges, so the position line is what stops the next chatter restarting the count from zero. The full argument sits in when to pitch a sale to a fan.

2. The refusal that was not a no.

Fan B. Position: offer made earlier tonight. Bought: nothing this week. Refused: the [price] bundle, said “not tonight, maybe payday”. Promised: nothing. Detail: paid the Friday after saying that last month, unused. Do not re-offer: the same bundle before Friday.

The exact words of the refusal are quoted rather than summarised, because “not tonight” and “no” produce completely different next messages. The do-not-re-offer line carries a date rather than a ban, so nothing is lost permanently.

3. The one with a promise attached.

Fan C. Position: fresh, offer landed and paid. Bought: [price] custom, paid today. Promised: delivery Thursday, said so explicitly. Refused: nothing. Detail: n/a. Do not re-offer: anything new before Thursday delivers.

A promise with a date is the only kind worth writing down, and it is the line that has to survive every shift change intact. Selling again before an undelivered promise arrives is the fastest way to turn a paying fan into a refund conversation.

4. The handover written at 4am.

Fan D. Position: deep in the thread, warm, was about to ask for the [price] one himself. Bought: nothing tonight. Refused: nothing. Promised: nothing. Detail: mentioned a new job, unused. Do not re-offer: n/a. Hold the offer for the evening shift, not now.

The instruction at the end is the whole point of this note. Our data shows the 2am-6am window collapses conversion while evenings maximise it, so a warm thread handed over at that hour is worth more parked than pitched. Which shift owns which threads is a shift rotation question before it is a chat question.

How does the next chatter pick the thread up?

Without announcing the change. The fan should read continuity, not a status report.

5. The straight continuation.

How did the night shift go in the end? You said you’d know by today whether they’re keeping you on.

It uses the unused detail from note 1 and it uses it here, in an ordinary message, well away from any offer. That placement is deliberate: our data shows a personal callback placed at the exact moment of the pitch costs conversion, which is the most counter-intuitive result in the corpus. Spend the detail early, sell later (the personal callback mistake sets out why).

6. The pickup after a soft refusal.

Not chasing you about the bundle, it’s still there when payday lands. What have you been up to since?

It names the refused thing once so the fan knows he was heard, then explicitly removes the pressure. Nothing is re-offered, which is exactly what note 2 asked for.

7. The pickup with a promise outstanding.

Thursday for your video, still on track. Nothing else to buy from me until that’s in your hands.

The promise is confirmed before the fan has to ask, which is the cheapest trust you will ever buy. The second sentence tells him this thread is not a queue of offers.

Which notes and pickups break the thread?

Three, and the last one is the one that wastes a note that was written properly.

8. The empty note.

Fan E: chatted, seemed keen, worth following up.

Nothing here changes anybody’s next message. There is no position, so the incoming chatter counts from their own first line and pitches early. “Seemed keen” is a mood reading that will be acted on as a fact. This note is quicker to write than to read, and it hands the next shift nothing.

9. The essay.

Fan F: so he’s been talking about his ex a lot which I think means he’s lonely, we had a really nice chat about his dog, at one point he said something about work being stressful but I don’t know if that’s ongoing, anyway I think there’s something there if you’re patient with him…

Everything true, nothing usable. No position, no price, no promise, no instruction. At the start of a shift with an inbox waiting, it does not get read to the end. Length is not thoroughness here; it is the absence of a format.

10. The pickup that ignores the note.

Hey you! Been thinking about you. I’ve got something new I think you’d love, want me to send it over?

This is the expensive one, because the note was written and then thrown away. It re-offers into a live refusal, it restarts the exchange count, and it ends on a yes-or-no question at the moment of closing, which our data shows costs several points of conversion. To the fan it reads as one thing only: nobody here remembers the conversation we were having.

What do you fix in the note first?

The wording, then the message the fan actually receives.

• Quote the refusal and date the promise. Those are the two lines a paraphrase ruins: a summarised no and an undated “soon” both hand the next chatter a guess.
• Audit the pickup, not just the note. Only the fan-facing message shows whether the note was used.
• Count promises kept. Every note with a Promised line should have a matching delivery within its own deadline, or the reason it slipped.
• Give the shifts a few minutes of overlap. The note gets read while the person who wrote it is still reachable, and that is a rota decision. The grid is in the chatter shift schedule template.

The note is not admin. It is the only thing that makes a rotating team read as one person.