Cross-Channel Handoff Audit Checklist: WhatsApp, Phone and In-Person
Handoff audit checklist between channels: WhatsApp, phone and in person
A cross-channel handoff is any moment when the conversation leaves one channel and continues on another: from WhatsApp to a call, from the call to the counter, from the counter back to WhatsApp. It is not the same as passing a conversation from one agent to another within the same inbox. Here the support changes, the history is not visible on its own, and the customer has to repeat things if nobody wrote them down somewhere before hanging up.
This checklist is meant to audit that handoff. You go through it in order, check off each item and note down what failed. The idea is not for the conversation to be perfect: it is for what the customer already said not to be lost and for whoever handles it next to know what they are walking into before picking up the phone or looking the customer in the eye.
Before auditing: what counts as a cross-channel handoff
There are three types of cross-channel handoff and each one has its own leak point. The first is WhatsApp to phone: someone asks to talk by voice or the inquiry gets long and a call is scheduled. The second is phone to in person: a call ends with a commitment to visit. The third is in person to WhatsApp: the customer leaves the store and continues the conversation by message. In all three, what gets transferred is information, not the channel.
The handoff is audited based on what is written down, not on what each person remembers.
| Type of handoff | What usually travels | What usually gets lost |
|---|---|---|
| WhatsApp → phone | Name, reason for the inquiry, agreed time | The written details: quotes, photos, voice notes, links sent in the chat |
| Phone → in person | Name, what they came to do, day and time | What was said by voice and nobody wrote down: measurements, conditions, prices discussed |
| In person → WhatsApp | Name, what they took, what was left pending | The context of the visit: who they spoke with, what they saw, what raised doubts |
Stage 1: what gets transferred before hanging up or before the customer leaves
This stage is audited by looking at what was recorded in the source channel right before the handoff. If nothing was written down, there is no handoff: there are two different conversations that happen to be with the same customer.
- Identification data: full name and a contact detail that makes it possible to find the conversation again. On WhatsApp, the number; on a phone call, the number they called from or the one they left; in person, the phone number or email they left.
- Reason for the inquiry in one sentence. The full detail is not necessary: it is enough that whoever handles it next understands what it is about without asking from scratch.
- Concrete commitment: what was agreed, by when, and who does what. If there is no commitment, the handoff had no reason to exist and probably was not needed.
- What the customer has already said they do not want. This is the item that is most often omitted and the one that causes the most friction when a question the customer already answered gets repeated.
- The destination channel and the time. If the handoff is to a call, at what time; if it is in person, on what day and at which location.
A handoff without a concrete commitment is not a handoff: it is a referral. They are audited differently and it is best not to mix them in the same spreadsheet.
Stage 2: what gets confirmed in the destination channel
Confirming is not repeating. It is verifying that the information arrived and that the customer still wants the same thing. A handoff is confirmed when the person receiving it can name the reason for the inquiry without having asked, and when the customer recognizes that reason as their own.
The signal that it is OK is always the same: nobody repeats a question that already had a written answer.
| Stage | What is reviewed | Signal that it is OK |
|---|---|---|
| Reception | Whoever handles it in the destination channel has the name and the reason before starting | They can open the conversation by naming the topic, not by asking 'how can I help you?' |
| Data confirmation | The customer validates that the reason and the commitment are still valid | The customer corrects or accepts, but does not start from scratch |
| Minimum context | Whoever handles it knows what was said before and what is still pending | They do not ask again for information that is already written in the source channel |
| Closing the source | In the source channel, it is recorded that the conversation continued elsewhere | If someone looks at the chat again, they understand that it was not left hanging |
Stage 3: what gets lost and how to detect it
What gets lost in a handoff between channels is almost never a single piece of data: it's the context. The tone, the urgency, what the customer said in passing and was never recorded anywhere. It can be detected in only one way: by listening to or reading the destination channel and counting how many questions get repeated compared to the source channel.
- Repeated questions: if during the call someone asks something that was already answered in writing on WhatsApp, context was lost.
- Data the customer gives twice: name, address, reason. Every repetition is a leak.
- Commitments that don't match: on WhatsApp a time was given and on the call a different one was agreed. This usually happens when the handoff didn't leave the commitment in writing.
- Silences: the customer tells something they had already told and the person handling it doesn't recognize it. It's the clearest sign that the handoff never happened.
- Return to the source channel with no record: the customer writes again on WhatsApp because the call didn't resolve it, and in the chat there's no note that a call took place.
There is no number of repeated questions that is acceptable in the abstract. What gets audited is the trend: if the same data gets repeated in the same week, the problem is with the process, not with the person who handled it.
Stage 4: what gets written down and where
A handoff between channels leaves a trace in two places: the source channel and the destination channel. Auditing means verifying that there is something in both. If the trace is only in one, the handoff can only be half reconstructed.
The minimum acceptable is one line per handoff. Without that line, the handoff cannot be audited afterward.
| Where it stays | What has to stay | How it is verified |
|---|---|---|
| Source channel (WhatsApp) | A note that the conversation continued by call or in person, with date and time | Open the chat and see if there's a message or internal note that says so |
| Destination channel (phone) | Record of the reason and the commitment agreed | Check whether anything was written down beyond what was said |
| Destination channel (in person) | A note of what the customer took and what was left pending | Check whether there's a record of the visit, even a minimal one |
| Return to the source | If the customer writes again, it should be clear why | Read the chat afterward and see if the full sequence can be reconstructed |
Stage 5: what gets reviewed the next day
The audit doesn't end when the handoff ends. The next day you check whether the commitment was met and whether the customer asked about the same thing again. It's the only way to know whether the handoff worked or just moved the problem from one channel to another.
- Was the commitment met within the agreed time frame? If not, was the customer notified in advance, or did they have to ask?
- Did the customer write again through the original channel? If they did, was it about something new or about the same thing?
- Did the person who handled it in the destination channel have to ask for information that was already in the source channel?
- Was the result of the handoff recorded somewhere, or is it only known because someone remembers it?
- Was there any piece of information that was taken for granted and turned out to be false? For example, a schedule that was assumed and not confirmed.
If the customer asks about the same thing again, the problem isn't the channel: it's the handoff. It's worth writing it down even if it can't be fixed right away.
Examples by industry: where the handoff breaks in each business
The point of failure changes depending on the industry, because what information doesn't travel changes. These are typical cases, not rules: they help you recognize the pattern in your own business.
- Food service: the customer orders through WhatsApp, then calls to add something, and at the restaurant they don't know there was already an order. What doesn't travel is the original order and its number.
- Beauty: an appointment is booked through WhatsApp, the client arrives, and at the front desk they ask from scratch what's going to be done. What doesn't travel is the agreed service and the reference photos she sent by chat.
- Real estate: the inquiry starts through WhatsApp about a specific property, moves to a call, and the showing is for a different one. What doesn't travel is which property they had seen and why they were interested.
- Healthcare: the patient books an appointment through WhatsApp, calls to reschedule, and at reception the old time is still listed. What doesn't travel is the schedule change.
- E-commerce or retail: the inquiry about stock starts on WhatsApp, continues by phone, and the customer goes to the store for a product that wasn't reserved. What doesn't travel is the reservation.
- Education: enrollment is discussed through WhatsApp, confirmed by phone, and on the first day of class they don't know which course they're in. What doesn't travel is the course and the agreed level.
What to do when something fails
There's no single solution for a handoff that fails, because it depends on where the information broke down. What you can do is identify the point of failure and decide whether to fix it right away or escalate it.
- If the reason for the inquiry is missing in the destination channel: ask for it at that moment and write it down. Complaining about it later is useless.
- If the customer repeats information: acknowledge it explicitly and continue. Asking the same question twice without acknowledging it is what makes the customer feel unheard.
- If the commitment does not match: confirm the new one with the customer and keep a record that there was a change. Do not assume the first one still stands.
- If the handoff left no trace: write it down at that moment, even if it is late. A late record is better than none.
- If the problem repeats across several handoffs by the same person or the same shift: escalate. It is not an isolated case, it is a process problem.
- If the customer returns to the original channel because the destination did not resolve it: assist them in the original channel and note why they came back. That note is what later makes it possible to fix the process.
How long it takes to resolve a failed handoff depends on each case: on whether the customer is still available, on whether the commitment was for the same day, and on whether there is someone on the other side to pick it back up. There is no deadline that can be promised in advance.
How to build the audit spreadsheet
An audit of handoffs between channels can be done with a simple spreadsheet. What matters is that each row is a handoff and that the columns allow you to see the full journey, not just the final result.
These columns are enough to get started. If the spreadsheet grows too much, it is better to trim it than to stop filling it in.
| Column | What is recorded | What it is for |
|---|---|---|
| Date and time of the handoff | When it moved from one channel to another | Sort the cases and see if they cluster around a certain time |
| Origin channel | WhatsApp, phone or in person | Detect in which channel the most information is lost |
| Destination channel | The other channel | See if the problem is with a specific destination |
| Reason | One sentence | Compare whether the reason arrived complete or got distorted |
| Commitment | What was agreed and by when | Verify whether it was met |
| What was repeated | Information the customer had to give twice | Measure the loss of context |
| Trace | Whether a record was left in origin and destination | Know whether the handoff can be reconstructed |
| Result | Met, delayed or lost | Have a simple number to compare weeks |
Common mistakes when auditing handoffs between channels
Most handoff audits fail for the same reason: the result is reviewed, not the journey. If the customer ended up buying, it is assumed the handoff was fine, even if they repeated everything three times. That is not auditing: that is looking at the ending.
- Audit only the destination channel. The source is where the information that had to be transferred lives; if you don't look at it, you don't know what was lost.
- Confusing a handoff with a transfer. A transfer within the same channel doesn't have the same problems as a channel change.
- Logging only the cases that went wrong. Without the ones that went well, there's nothing to compare against.
- Asking the customer to repeat it to 'confirm'. Confirming means verifying that the information arrived, not asking for it again.
- Assuming the commitment was met because nobody complained. Customer silence is not confirmation.
- Auditing only once. Cross-channel handoffs are measured over time: one week says nothing, four do.
Frequently asked questions
Short answers to the questions that come up when you start auditing this type of handoff.
Frequently asked questions
How often should cross-channel handoffs be audited?+
There is no frequency that works for every business. What matters is that the sample is comparable: if few cases are audited per week, it's worth gathering several weeks before drawing conclusions. Auditing a single handoff says nothing.
What is the difference between a cross-channel handoff and an agent-to-agent handoff?+
An agent-to-agent handoff happens within the same channel and the same inbox: the person handling it changes, but the history stays visible. A cross-channel handoff changes the medium, so whatever wasn't written down before hanging up doesn't travel. The items to review are different.
Can an in-person handoff be audited if there is no written record?+
It can be audited, but with less information. In that case what's reviewed is whether the customer had to repeat information on arrival and whether the commitment was met. If there is no record on either side, the audit is limited to what can be reconstructed from memory, which is not reliable.
What do I do if the customer returns to the original channel after a handoff?+
Handle them in the original channel and note why they came back. That note is what later makes it possible to see whether the handoff failed due to missing information, an unmet commitment or because the customer preferred the original channel. Without that note, the case is lost.
Does Wando's AI help audit cross-channel handoffs?+
Wando suggests replies in the WhatsApp inbox and the team approves them, but auditing a handoff to phone or in-person depends on what gets written down in each channel. The tool helps make sure the WhatsApp-side record exists and is easy to review; what happens on the call or at the counter is audited separately.
How long does it take to fix a handoff that always fails at the same point?+
It depends on the case. If the problem is that nobody writes down the reason before hanging up, it gets fixed once the team builds the habit, and that takes a different amount of time in each business. If the problem is that the commitment isn't recorded anywhere, first you have to define where it gets recorded. There is no timeframe that can be promised in advance.
Is it worth auditing handoffs that went well?+
Yes, because they are the reference point. Without cases that went well there is nothing to compare the ones that went wrong against, and you can't tell whether the problem is with the process or with a specific case. The audit needs both sides.
Answer WhatsApp with AI
Try Wando free. No credit card required.