Definition

handover

A handover is the written note a chatter leaves at the end of a shift for whoever takes over, recording what each active fan bought, refused or was promised, and at what price.

A handover is what travels with a conversation when it changes hands. It is not the rota. A shift rotation is the plan, who sits in which block of hours, and a flawless plan with no handover produces the same result as no organisation at all. The fan is not talking to a schedule. He is talking to someone who is supposed to remember him.

What belongs in a handover?

Six lines per active fan, not a report. Long notes do not get read at the start of a shift, and an unread note is worth nothing.

  • Where the thread stands: how many exchanges since the last paid offer.
  • What was bought, and the price actually paid, not the price listed.
  • What was refused, and how. “Not tonight” is not “no”.
  • What was promised. Content teased and never sent comes back on you fast.
  • The personal detail in play, and whether it has already been used.
  • What not to re-offer, in one line, with no explanation attached.

Everything else (mood, hunches, “he seemed keen”) clutters the note and misleads the person reading it.

What gets lost when a conversation changes hands?

Not the facts. The position. The incoming chatter can see what was said but not how deep the thread already runs, so he restarts the count from his own first message. Our data puts an offer made before the sixth message at roughly a third of conversion lost, with the optimum after about ten real exchanges. A thread handed over without its position gets pitched far too early twice in the same day, once per shift.

The personal detail is lost differently. Passed on raw, it comes back out at the worst possible spot: right at the moment of the offer. Our data is blunt here: a personal callback placed at the pitch costs points, even though it feels like the helpful thing to do. So the note has to say whether the detail has been spent, and the instruction that goes with it fits in one sentence: use it before the pitch, never during it.

Why is this a team’s weak point?

Because it is the only task nobody sees and everybody pays for later. It lands at the end of a shift, when the person writing it is tired, it does not show up in their own numbers, and its absence only shows up on somebody else’s hours. A team under pressure drops the handover first, keeps everything else, and believes it has saved time.

You pay for it in the threads: a PPV re-offered after a refusal, a first name asked for twice, a promise quietly forgotten. Each of those loses a fan faster than any clumsy follow-up ever will.

How do you know handovers are holding?

Read the starts of shifts, not the ends. The first three messages a chatter sends after clocking in tell you everything: either they continue the thread, or they reopen a conversation that was never closed. That check is the fastest one quality control runs, and it is the only measure the outgoing chatter is answerable for.

Related terms

To go further on this:

Read the full guide