A WhatsApp shift handover checklist that saves the next agent time

The next agent should not have to read an entire chat to discover that the customer is waiting for a revised delivery date. A good handover records the current state of the work, especially what the business has already promised.

This guide is published by the team behind Flas CRM. We sell one of the products in this category, so treat it as a vendor's checklist — the criteria are written to be useful whichever tool you end up choosing.

Write for someone who was not present

Start with the customer's current requirement, not a chronological summary of every message. Then record the unresolved question, the latest relevant document and the next action. Use specific nouns and dates instead of “this,” “that” and “tomorrow” when those could become ambiguous.

For example: “Customer needs twenty chairs for one office. Revised quotation Q-104 sent. Delivery date needs operations confirmation. Maya will check by Thursday afternoon.” This is an illustrative internal note, not a real customer record.

Use five handover fields

1. Current requirement: what the customer wants now.
2. Commitment: what the business has promised to do.
3. Reference: the relevant quotation, invoice or opportunity.
4. Next action: the specific task still outstanding.
5. Owner: who has accepted responsibility for it.

If there is no remaining action, close the work according to your process. If it is waiting on the customer, say exactly what is awaited. A vague “pending” note forces the next shift to investigate from scratch.

Transfer responsibility, not just visibility

A shared inbox means colleagues can see the conversation; it does not mean someone has accepted the next step. In Flas, use the assignment and status capabilities described on the feature page and confirm that the receiving agent knows the handover exists.

For sensitive or complex exceptions, add a brief direct internal briefing through your normal team process. Keep the durable facts in the record so the handover does not depend entirely on a private conversation.

Include what should not be assumed

If a price is awaiting approval or a delivery slot is unconfirmed, make that explicit. The next agent may otherwise treat a suggested option as a promise. Distinguish what the customer requested from what the business accepted.

Likewise, identify any current chatbot involvement. The receiving person should know whether an automated response is still active and what the customer has already been told.

Review a small sample at shift change

Have the incoming agent explain the next action for a few handed-over conversations. If they cannot, improve the notes immediately. This is a practical quality check and a useful way to train new staff without creating a long manual.

Use the daily inbox review to catch unowned work and the quotation revision guide for document-heavy handovers. The handover succeeds when the customer can continue naturally with the next person.