End-of-shift checklist for messaging: what to leave in order for the next person

The end of a shift is the cheapest time to organize and the most expensive to skip. A shift that ends with unowned conversations forces the person coming in to rebuild context from scratch: reading backwards, guessing what was promised, asking on internal chat what was already resolved. That is not a team attitude problem, it is a procedure problem. This page is the list you check off at the end of the shift, in order, with the concrete signal that each item was done right.

It is designed for shared inboxes where several people handle the same WhatsApp number: small teams that pass the baton between two or three people, or larger teams with morning/afternoon/night shifts. It does not depend on any specific tool: if your inbox has labels, assignment and internal notes, you can apply everything below. If it does not, it still works, but you will end up using a spreadsheet or an internal chat as a replacement.

How to use this checklist

The typical mistake is doing the close-out from memory, in a hurry, five minutes after the end of the shift. The checklist works if you go through it in order and if each item has a binary criterion: it is or it is not, it was done or it was not. There are no items like "check that everything is fine." Each line says what to look at and how to know it is closed.

• Go through the stages in order: first what is open, then what was promised, then what was recorded.
• If an item cannot be closed, do not check it off: write it down in the handover summary with the reason.
• The close-out is not the time to resolve new cases. It is the time to leave the state clear for the person coming in.
• If the shift volume was unusually high, the close-out is still done, but the handover summary must say how many were left unattended and why.

Stage 1: open conversations

This is the part that gets skipped the most and the one with the most consequences. Before closing, you have to go through every conversation that was left without a reply from the business side, not just the last one that appeared on screen. In a shared inbox it is easy for two people to believe the other replied, or for an old conversation to be buried by new ones.

The "no reply from the business" criterion is more useful than the "unread" one, because in a shared inbox several people may have read without replying. What matters is not whether someone saw the message, it is whether the customer received a reply.

Stage 2: pending commitments

This is where anything that was promised and has not yet been fulfilled gets closed out. This is the stage that prevents the next day's complaint. If during the shift someone said "I'll send you the quote", "I'll confirm stock tomorrow" or "I'll call you in the afternoon", that has to be recorded somewhere the next person coming in can see without reading the entire history.

Stage 3: labels and statuses

Labels are the team's signal system. If they are outdated, the person coming in works with false information: they see "resolved" on something that is still open or "pending" on something that was already closed. Reviewing labels is quick if the team used them during the shift; it is slow and painful if they did not.

• Every open conversation has a status label that reflects the real situation, not the one from three hours ago.
• No closed conversation was left with a pending label: if it was closed, the status is changed.
• Priority labels (urgent, complaint, frequent customer) are placed where they belong and were not left over from a previous shift.
• If you use labels by category or by type of inquiry, every open conversation has its own.
• Labels that are no longer used are removed from the system during the weekly review, not at shift close.

Stage 4: handover summary

The handover summary is the only artifact that the person coming in reads no matter what. It has to be short and be in a fixed place. It is not a record of the shift: it is the list of what the person coming in needs to know to start without asking anything.

Stage 5: final check before leaving

1. 1Go through the inbox filtering by "unassigned" and confirm that nothing open is left without an owner.
2. 2Filter by "assigned to me" and check that none of your conversations is left with the customer's last message.
3. 3Open the handover summary and confirm that the five sections are complete or marked as empty.
4. 4Verify that the conversations you reassigned actually changed owner.
5. 5Confirm that the status labels match the real situation of each open conversation.
6. 6Notify the team's internal channel that the shift is closed and that the summary is published.

What to do when an item doesn't close

No checklist gets completed 100% every day. What sets an organized team apart isn't that it never fails, it's that when it fails, it writes it down. These are the typical cases and what to do with each one.

• There are conversations left unattended and no time to answer them: they are noted in the summary as "unattended", with the count and the time range. Don't answer in a rush just to check off the item.
• A conversation is assigned to someone who has already left and can't be reassigned: it is reassigned to the person coming in or left unassigned but marked as urgent in the summary.
• There is a complaint with no defined next step: it is escalated to the area lead before closing. If they are not available, it is noted as pending escalation for the next shift.
• The handover summary can't be completed because information is missing: it is completed with what is available and what is missing is explicitly marked. An incomplete but honest summary is better than a complete but made-up one.
• The inbox tool doesn't respond or is down: it is recorded in the internal channel and noted in the summary that the status of conversations may be out of date.
• An item repeats as a failure every day: it's not a shift-closing problem, it's a process problem. It goes to the team's weekly review, it isn't resolved on the spot.

How to know if the checklist is working

A checklist that gets checked out of habit stops being useful. There are three simple signals to know if the procedure is doing its job, and none of them requires new tools: just watching the team's behavior for a week is enough.

Frequent mistakes in shift closing

• Close by the hour, not by status: the shift ends when the status is sorted out, not when the clock hits the end time. If sorting takes ten more minutes, it takes ten more minutes.
• Confusing "read" with "replied": in a shared inbox, several people may have read without replying. The criterion is the reply, not the read.
• Leaving the handover summary in an internal chat where it gets lost among messages: it must be in a fixed place, always the same one.
• Noting only what is urgent and skipping what "will get resolved anyway": what is not noted does not exist for the person coming in.
• Reassigning without notifying: if a conversation changes owner, the person receiving it must know.
• Using the shift close to resolve new cases: the close is for sorting, not for handling. What comes in near the end is handled if there is capacity, and if not, it is noted.

Handover Summary Template

This is the minimum structure. It can be copied and pasted into the team's internal channel or a shared note. If your inbox has internal notes per conversation, the summary complements them, it does not replace them: the summary is the bird's-eye view, the notes are the detail.

• Shift closing: (morning / afternoon / night) and schedule.
• Person closing and person coming in.
• Hot conversations: up to five, with reason and expected response time.
• Commitments with deadlines: what, to whom, by when.
• Open claims: status and next step for each.
• Incidents: only if there were any. If there were none, write "no incidents".
• Volume: incoming conversations and unattended conversations.

Adaptations by team size

Examples by industry: what changes in practice

The checklist is the same, but the content of each item changes depending on what the business sells. These are four typical cases to ground the list.

• Food service: the hot conversation is the order that was taken but not confirmed. At handover you need to note orders with delivery address and time, and flag if the kitchen has already closed. An unconfirmed order at 23:00 is not answered in a rush: it is noted and the morning shift is informed.
• E-commerce: what most often falls through at handover are unresolved changes and returns. Each one must have an order number, reason and next step (return label, size exchange, refund). Without that, whoever comes in starts by searching for the order.
• Beauty: the typical commitment is the booked but unconfirmed appointment. The handover must note which appointments for the next day are unconfirmed, so the morning shift confirms them before the slot is lost.
• Real estate: the hot conversation is the visit that is scheduled or pending scheduling. At handover you need to leave the address, the time and who is handling it, plus the contacts who asked for information and got no reply.

What tools help sustain the handover

The checklist can be completed with a basic inbox and a spreadsheet, but there are three features that greatly reduce manual work: conversation assignment, status labels and internal notes per conversation. If your inbox has them, the handover is done within the same tool and the handover summary becomes a bird's-eye view. If it does not, the summary becomes the only record of status and should be treated more carefully.

Wando has those three features inside the inbox: assign conversations to a person, label them and leave internal notes. It is not the only way to sustain the procedure nor the cheapest if the team is a single person, but if you handle WhatsApp with several people on the same number, it avoids the parallel spreadsheet. You can see the details of the current plans at wando.online/pricing.