Shift handoff checklist: what needs to be written down when closing the service shift

Why a shift handover is not a summary

A poorly done shift handover shows up the next day: the person coming in doesn't know if the client already paid, if you promised to call them at 18:00, or if order 45 is still waiting for a reply. The problem isn't lack of memory: it's that the context lives in the head of whoever handled it, and when they leave, it leaves with them. A handover checklist solves that, but only if it's written down and verifiable. This material is for teams that handle WhatsApp and need a procedure that doesn't rely on anyone's goodwill.

What must be written down when closing the shift

Before starting with the list, one rule: everything written in a handover must be useful for someone who wasn't in the conversation. If a sentence doesn't help a colleague make a decision, it doesn't go in. The handover is written for the person coming in, not for the one leaving.

Checklist by stage: what to review and how to know it's done right

The following list can be printed or copied to a shared document. Each item has the signal that it's done well, not a generality. We grouped it by stage: before closing, during documentation, and when handing over.

• Review the message inbox: don't leave any conversation unanswered or unmarked as pending. Signal: no messages older than 2 hours without a reply, except those on the explicit pending list.
• Identify active conversations: mark which ones require follow-up the next day. Signal: each active conversation has a label or status saying 'pending', 'on hold', or 'resolved'.
• Document promises made: record what was promised to each client (call, send quote, confirm stock). Signal: each promise has a date and time, and the person responsible for fulfilling it.
• Verify payments and collections: if Mercado Pago or a payment link was used, confirm which transactions are pending credit or confirmation. Signal: the handover includes the amount, the client, and the status of each payment.
• Note templates or sent messages: record which HSM templates were sent and if any are pending approval by Meta (up to 48 hours). Signal: the list of sent templates is up to date, and pending ones have a send date.
• Escalate incidents: if something broke (API down, webhook error, Sheets integration issue), leave it noted with details and who was notified. Signal: the incident has a ticket or a message in the internal support channel.
• Update contacts and labels: if a client asked not to be contacted anymore, or if their number changed, reflect it in the database. Signal: the contact has the 'do not contact' label or the corrected number.
• Leave the handover in a visible and accessible place: the shared document, spreadsheet, or Slack channel where the team always reads it. Signal: the file is updated with the date and time of the shift close.

How to put together the handover document (template)

You don't need a complex system: a shared spreadsheet or a document with the following sections is enough. The key is that it's always the same place, so nobody wastes time looking for it.

• Date and time of shift closing, and name of the person handing over.
• List of pending conversations: client, subject, last action, next action.
• Promises made: what, to whom, by when.
• Pending payments and collections: amount, client, status.
• Technical incidents: what happened, when, who was notified.
• Notes for the next shift: something the team should know (upset client, urgent order, etc.).

What to do when something goes wrong with the handover

Even if the checklist is in place, things will happen: the person leaving doesn't document, the person coming in doesn't read, or the file gets lost. These are the most common failures and how to resolve them.

• Failure: the person leaving doesn't complete the handover. Solution: establish a team rule: the shift is not closed without the completed document. If necessary, the leader reviews it before they leave.
• Failure: the person coming in doesn't read the handover. Solution: the first 10 minutes of the shift are for reading the document and asking questions. No customer service until it has been read.
• Failure: the handover is incomplete. Solution: use the checklist as a mandatory template, not optional. If a section is missing, it's returned to the person who wrote it.
• Failure: the information contradicts itself (a payment appears as pending and as credited). Solution: when in doubt, consult the person who handed over or the client directly, and correct the document with the correct version.
• Failure: the file is not available. Solution: have a backup copy in another place (for example, on the drive and in a Slack channel). If the tool goes down, the handover is done anyway in a new document.

How to measure if the handover is working

A handover isn't implemented and that's it: you have to measure whether it really reduces errors. Two simple metrics:

• Number of conversations left unanswered at the end of the shift. If the number is high, the handover is not capturing everything.
• Number of times a customer repeats an order or a query because the person who handled it didn't have the context. This can be tracked with tags or simply by asking the team.

Common mistakes when putting together a handover (and how to avoid them)

• Writing a narrative summary instead of an actionable list. A handover is not a story: it is a list of pending items with owners and dates.
• Putting sensitive information (passwords, card data) in the document. That goes in a password manager, not in a handover.
• Mixing personal tasks with team tasks. The handover is for the team, not for one person.
• Not updating the document during the shift. If you wait until the end, you forget half of it. Better to jot things down as you go.
• Not reviewing the previous shift's handover. If nobody reads it, it's useless. Make reading it part of the routine.

Conclusion

The shift handover is the moment where the continuity of service is at stake. With a clear checklist, a single document, and simple rules, context is not lost and the customer doesn't have to repeat their story. No special tool is needed: a shared document and the discipline to use it are enough. If the team follows it, the incoming shift starts with the information it needs, and the outgoing one ends with the peace of mind that no loose ends were left.

Edge cases: what to do when the handover is not enough

There are situations where the checklist is followed to the letter but things still get complicated. For example, a customer who insists on speaking with the same person from the previous shift, or an order that depends on data only the owner knows. In those cases, the handover is not the problem: it's the limit of what a document can solve. What you can do is leave a note with the name of the person who has the context and the best time to contact them, so the incoming person doesn't waste time guessing.

• Customer who only wants to talk to a specific person: note in the handover the name and usual schedule of that person, and whether the customer accepts alternatives.
• Order that depends on external data (supplier, stock, shipping): leave the supplier contact or the order reference, not the full detail.
• Conversation that was cut off in the middle of a sale: record the exact point where it stopped (for example, 'quote sent, waiting for shipping confirmation'), so the next person doesn't repeat what was already said.

Handover when there is more than one channel: WhatsApp, Instagram, and Messenger

If your team handles more than one channel, the handover gets complicated: it's not enough to check the WhatsApp inbox. The rule is that the document must indicate, for each pending conversation, which channel it was left on. This way, the person taking over knows whether they need to respond via WhatsApp, Instagram, or Messenger, and doesn't assume everything is in the same place.

Tough questions no one answers about the handover

Three questions that often go unanswered and that are worth clarifying before implementing the checklist:

• Who is responsible if the handover wasn't done? If there's no process owner, the checklist becomes dead letter. Assign a responsible person per shift (it could be the leader or the one closing) and that person validates that the document is complete.
• What happens if the handover is done but no one reads it? Mandatory reading is as important as writing. If it's not read, the handover is useless. Make reading a rule, not a suggestion.
• When is the handover updated? During the shift, not at the end. If you wait until closing, information is lost. Writing it down at the moment is the only way for the document to reflect what happened.