Decision matrix: when a conversation is resolved by text, when by call and when it requires an in-person visit
Most teams that handle WhatsApp support resolve everything by text by default. It's convenient: there's a record, it can be done in parallel, it doesn't interrupt. But there's a group of conversations that drag on for days over text, get answered poorly, or end in a complaint. And there's another group that moves to a call when it could have been resolved with two more messages.
This page is a table for deciding the resolution channel: when text is enough, when it's better to offer a call, and when the conversation needs physical presence. It's not a tool recommendation. It's a criterion so the operator doesn't improvise in the moment and so the team has a common rule.
The decision doesn't depend on the type of business, but on three variables: how much information needs to be exchanged, how much an interpretation error costs, and whether something needs to be verified physically. With those three, almost any conversation can be sorted.
The three variables that define the channel
Before the table, it's worth setting the variables, because they're what gets scored in each row afterward.
- Volume of exchange: if the conversation needs more than five back-and-forths to close, text starts costing more than a five-minute call.
- Cost of error: if a misinterpreted word leads to a return, a cancellation, or a complaint, written text loses against voice.
- Physical verification: if a product, a document, a place, or a person needs to be seen, no remote channel replaces presence.
- Record: if the agreement needs to be in writing (a price, a date, a condition), text wins even if the conversation was by call.
- Availability: if the customer can't talk (they're working, driving, in a noisy place), text is the only viable option at that moment.
Reference table: resolution channel by type of conversation
| Type of conversation | Signal in the chat | Recommended channel | Why | What to do if the channel fails |
|---|---|---|---|---|
| Price or availability inquiry | Specific question, one-line answer | Text | The exchange is short and the price record stays in writing | If they ask for exceptions or discounts, move to a call |
| Hours, address, or directions inquiry | Closed question | Text | It's answered with a piece of data and stays saved | If they don't understand the location, send location or move to a call |
| Status of an order or shipment | Asks for tracking of something already purchased | Text | The data exists and is copied; the call adds no information | If the customer is angry or the data doesn't appear, call |
| Change or return of a product | Explains the problem over several messages | Call | The case needs to be understood and a solution agreed on; text gets misinterpreted | If they don't answer, leave the agreement in writing in the chat |
| Complaint about a business error | Elevated tone, long messages, repetition | Call | It lowers tension and allows apologizing in real time | If they don't answer, log the complaint and give a response deadline |
| Quote for a custom service | Asks for several details, sends photos or measurements | Call | Questions and follow-up questions are needed; text becomes a questionnaire | If they can't talk, ask for the details in writing with a fixed list |
| Reservation or appointment with date and time | Chooses among specific options | Text | The date record stays in writing and scheduling errors are avoided | If it needs to be rescheduled several times, call |
| Onboarding or account setup | The customer can't find where to do something | Call | They're guided in real time and the back-and-forth of screenshots is avoided | If they can't talk, send a written step-by-step |
| Documentation for a procedure | Asks what papers to bring or sends documents | Text | The list stays written and can be forwarded | If there are doubts about a document, call or in person |
| Signing, delivery, or pickup of something | An object or document needs to be delivered or received | In person | Someone has to be physically present to deliver or sign | If they can't come, consider shipping with proof |
| Technical visit or installation | The place or equipment needs to be seen | In person | No remote channel replaces on-site verification | If you can't go, ask for photos or video and evaluate |
| Medical, aesthetic, or body-related services | Requires seeing, measuring, or touching | In person | The evaluation is physical by definition | Not applicable: the in-person appointment is scheduled |
| Training or live class | The student needs to follow a step-by-step explanation | Call or video | Voice and screen sharing resolve faster than text | If they can't, send a recording or written material |
| Closing a sale with special conditions | Installments, deadlines, exceptions come up | Call and then text | The call closes; the text leaves the agreement recorded | If there's no agreement, don't close over chat |
| Inquiry that was already answered before | The customer comes back with the same question | Text | The saved answer is forwarded and the history remains | If they come back a third time, call to understand why it didn't help |
The table is not ordered by category but by conversation type. The same business can use all three columns in the same week.
How to score a conversation in the moment
When the operator is unsure, they can score the conversation with the three variables and add them up. The rule is simple: if the volume of exchange is high, the cost of the error is high, or physical verification is needed, text loses. If two of the three are against text, it's better to switch to a call. If physical verification is needed, there's no debate: it's in person.
| Variable | Score 0 (text is enough) | Score 1 (call is better) | Score 2 (in person) |
|---|---|---|---|
| Volume of exchange | Fewer than 3 messages | Between 3 and 6 messages | More than 6 messages or something needs to be shown |
| Cost of the error | An error is corrected with another message | An error generates a complaint | An error generates physical, legal or health damage |
| Physical verification | There is nothing to see | Something needs to be seen but it can be done with photos | You have to be there in person or touch the object |
Handoff signals: when to cut the text and offer a call
The most common mistake is not choosing the wrong channel, but failing to change it when it's already clear that text won't be enough. These are the concrete signals to offer a call without waiting for the customer to ask for one.
- The customer repeats the same question in different words for the third time.
- The operator has written more than three messages in a row without a response from the customer.
- A word appears that allows two interpretations and the operator is unsure what was meant.
- The customer sends a long audio instead of writing.
- The tone escalates: capital letters, repeated punctuation, explicit complaint.
- A procedure with more than four steps has to be explained.
- The agreement involves money, dates or conditions that will be claimed later.
- The customer says they don't understand or that the chat isn't working for them.
The offer of a call has to be concrete, not a 'I can call you if you want'. It's better to propose a time slot and confirm the number. If the customer can't talk at that moment, schedule it and leave the summary in writing in the meantime.
When a conversation needs physical presence
There are conversations that cannot be resolved through any remote channel. It is not a limitation of the tool or the team: it is that the resolution depends on being there in person. These are the cases where it is best to say it from the start, without going through text or a call.
- When you need to verify the condition of a product, a piece of equipment or an installation.
- When you need to sign, deliver or pick up a document or an object.
- When the assessment depends on measuring, weighing or touching (health, aesthetics, repairs).
- When you need to show a physical space (a property, a venue, a store).
- When the customer needs to try something before deciding.
- When you need to verify identity or original documentation.
In these cases, text and calls are useful for scheduling, confirming and reminding, but not for resolving. Confusing the scheduling channel with the resolution channel is what leads to missed appointments and customers who arrive without what they need.
The cost of switching channels
Every channel switch has a cost: the operator's time, the customer's time and the risk of losing the thread. That is why the decision is best made early, not after twenty messages. This table lays out the relative cost of each handoff.
| Handoff | Cost for the team | Cost for the customer | Main risk |
|---|---|---|---|
| Text to call | Medium: you have to coordinate a time | Low if they accept, high if they cannot talk | That they do not answer and the thread is lost |
| Text to in-person | High: it involves scheduling and travel | High: they have to move | That they arrive without what they need |
| Call to text | Low: a summary is sent | Low: they read when they can | That the agreement is not clear |
| Call to in-person | High: a visit is scheduled | High: a second trip | That the visit does not resolve what was expected |
| In-person to text | Low: it is confirmed in writing | Low: there is a record | None relevant |
| Text to text with more detail | Low at the moment, high accumulated | Medium: long messages | That the conversation drags on for days |
The most expensive handoff is the one made late. If you already know that text is not enough, waiting twenty messages adds cost without adding information.
Common mistakes when choosing the channel
These are the mistakes that come up again and again in teams that handle WhatsApp and that the matrix seeks to avoid.
- Switching any long conversation to a call: if the conversation is long because the customer writes a lot but the question is simple, text is enough.
- Keeping everything in text for fear of losing the record: you can make the call and then leave the summary written in the same chat.
- Offering a call without a specific time: the customer doesn't know when and the conversation goes cold.
- Resolving an agreement by call that will later be claimed, without leaving it in writing.
- Scheduling an in-person meeting when the customer only needed an answer: a slot and a trip are wasted for nothing.
- Not saying upfront that something requires being present: the customer moves forward through chat believing it can be resolved remotely.
- Changing channels without warning: the customer receives a call they weren't expecting and doesn't answer.
How to keep a record of the channel change
When the conversation changes channels, the record must stay in the chat, even if the resolution was by call or in person. This serves three purposes: another operator understands what happened, the customer has the agreement in writing, and the team can measure how many conversations are resolved on each channel.
- 1Before the call: write in the chat 'I'll call you at X to resolve this' and confirm the number.
- 2During the call: take note of what was agreed in two or three lines.
- 3After the call: send the summary with what was agreed to the chat and ask for confirmation.
- 4If the resolution is in person: leave in the chat what the customer needs to bring and at what time.
- 5After the in-person meeting: confirm by chat that it was resolved or what comes next.
- 6If the customer doesn't confirm the summary: call again or consider the agreement not closed.
This record is also the raw material for measuring. If the team notes in each conversation which channel it was resolved on, over time you can see what percentage is closed by text, how much by call, and how much needs an in-person meeting. That distribution is what allows deciding whether it's worth adding a phone line, adjusting service hours, or reinforcing in-person service.
If the team uses Wando, the message inbox with AI suggestions and multi-agent work allow several operators to see the same conversation and leave the summary of the channel change in the same thread. The decision of which channel to switch to is still the team's: the tool doesn't make it on its own.
Operational summary
The short rule to keep handy: if the conversation is closed with a piece of data, text. If you need to understand a case, agree on a solution or explain a procedure, call. If you need to see, touch, sign or hand over something, in person. And in all cases, the final agreement is left in writing in the chat, no matter where it was resolved.
Frequently asked questions
How do I know if a conversation is resolved by text or needs a call?+
Look at three variables: how many messages it takes, how much an interpretation error costs and whether there is anything to verify physically. If the exchange is short, the error can be fixed with another message and there is nothing to see, text is enough. If two of those three are against text, it is better to offer a call with a specific time slot.
When should I move from WhatsApp to a call?+
When the customer repeats the same question for the third time, when the operator has written more than three messages in a row without a reply, when an ambiguous word comes up, when a procedure with more than four steps has to be explained or when the tone escalates. In those cases a call resolves faster and lowers the tension.
Which conversations need in-person attention no matter what?+
Those that depend on verifying something on site or on touching, measuring, signing or delivering an object or document. Also those that require showing a physical space or trying something before deciding. In those cases text and calls are useful to schedule, but not to resolve.
What do I do if the customer cannot take a call?+
Ask for the information in writing with a fixed list of questions and leave the summary in the chat. If it still does not get closed, propose another time slot. A call is not mandatory: it is an option for when text is no longer enough.
How do I keep a record of an agreement closed by call?+
Send a two- or three-line summary of what was agreed to the chat and ask for confirmation. That leaves the agreement in writing, lets another operator understand what happened and prevents later complaints. If the customer does not confirm, the agreement is not closed.
Can I measure how many conversations are resolved through each channel?+
Yes, if the team notes in each conversation which channel it was resolved through. With that distribution you can see what percentage is closed by text, how much by call and how much needs in person, and decide whether to add a phone line or adjust hours.
Does moving everything to calls improve customer service?+
Not necessarily. Specific questions about price, hours or order status are resolved faster by text and stay recorded. Moving everything to calls adds coordination time and can lose the customer who cannot talk at that moment.
What is the most common mistake when choosing the channel?+
Changing channels too late. If you already know text will not be enough, waiting twenty messages adds cost without adding information. The second mistake is closing by call without leaving the agreement in writing in the chat.
Answer WhatsApp with AI
Try Wando free. No credit card required.