Decision matrix: when an unanswered message is retried, routed to another channel or closed as lost
A conversation left unanswered is not a customer service problem: it is a pending decision. Someone has to decide whether that conversation is retried, moved to another channel, or closed. When no one decides, the conversation is not closed: it is abandoned. And an abandoned conversation takes up space in the inbox, pollutes the statistics, and makes the team believe it is handling more than it actually is.
This page is the table you consult when that doubt arises, plus the procedure to make sure the decision is recorded. There is no single rule: the right answer depends on why the customer wrote and on the stage of the conversation. A quote requested on a Tuesday morning is not handled the same way as a complaint about an order that has already been delivered.
The three possible outcomes (and the fourth that almost no one uses)
When a conversation goes unanswered on the customer's side, there are four outcomes, not three. The first three are the obvious ones: retry, route to another channel, close as lost. The fourth is to leave the conversation on hold with an expiration date. It is the one most often omitted and the one that generates the most zombie conversations, because without a date no one looks at it again.
- Retry: the same channel, another message, with a specific reason to write again.
- Route: move the contact to another channel where a response is more likely (call, email, visit, another number).
- Close as lost: mark the conversation with a reason and remove it from the active queue.
- Pause with expiration: leave it without action for a defined period, with a date on which it returns to the queue on its own.
Closing as lost is not the same as deleting. The conversation is closed with a recorded reason; if the customer returns, the reason helps avoid repeating the mistake. A deleted conversation leaves no trace and the same problem repeats three months later.
Table 1: what to do based on the reason for the first message
The reason for the first message defines how much it is worth insisting. A customer who asked for a specific quote and did not reply has a different reason for the silence than one who wrote 'hello' and never wrote again. The table orders the frequent reasons by their commercial value and suggests the outcome.
| Reason for the first message | Retries allowed | Outcome if no response | Why |
|---|---|---|---|
| Asked for a specific price or quote | 2, separated by at least one day | Refer to a call or email with the quote attached | There is a declared interest and a specific data point to follow up on; silence is usually a lack of time, not a lack of interest |
| Asked about availability (appointment, stock, date) | 1, within 24 hours | Close as lost with reason 'did not confirm availability' | Availability changes: if they did not confirm that day, the information we gave them may already be false |
| Wrote 'hi' or a vague inquiry | 1, with a specific question that forces them to choose | Pause with a 7-day expiration | Without a declared reason there is nothing to retry; a closed question ('are you looking for this week or next month?') filters the curious from the buyer |
| Complaint about an order or service already delivered | 2, the second with a copy to a manager | Refer to a call and log the case as open | A complaint without a customer response is still a complaint; silence does not close it, it leaves it pending |
| Asked for an invoice, receipt or documentation | 1, with the document already attached | Close as lost with reason 'documentation sent without acknowledgment' | If the document was sent and there was no response, the business's obligation is fulfilled; acknowledgment is not the salesperson's responsibility |
| Inquired about a vacancy or an admission | 1, within the week | Pause with expiration at the close of registration or the process | The deadline is set by the process, not the conversation; retrying after the close makes no sense |
| Wrote outside business hours | 0 retries: respond once during business hours | Pause with a 24-hour expiration | The first message never became a conversation: the business's response has not yet happened |
| Recurring customer who always buys and this time did not answer | 1, informal and without pressure | Pause with a 15-day expiration | A recurring customer's silence is usually personal, not commercial; insisting with a sales structure wears down the relationship |
| Wrote by mistake or to ask for something we do not offer | 0 retries | Close as lost with reason 'out of scope' | Retrying someone who already said they are not looking for what we sell is spam, not follow-up |
| Incoming message from an unknown number with no text (attachment only) | 1, asking them to confirm what they need | Close as lost with reason 'attachment without context' | Without context there is nothing to respond to; the retry is a question, not a follow-up |
Table 2: signals for choosing between retrying, referring or closing
When the reason is not clear, there are five observable signals in the conversation that are enough to decide. None require guessing: all are read in the history.
| Signal in the conversation | Reading | Decision |
|---|---|---|
| The customer opened the message and did not reply (seen without response) | They read it and decided not to respond at that moment | Retry once, with new information, not with an empty reminder |
| The customer never opened the message | They may not have seen it or may have archived it | Retry through another channel; the same channel has already failed once |
| More than 7 days have passed since the customer's last message | The conversation lost momentum | Pause with expiration or close, depending on the original reason |
| The customer asked something the team did not know how to answer | The silence is the business's, not the customer's | Answer the pending question first and only then evaluate the follow-up |
| There are more than three consecutive messages from the business without a response | The conversation is already unbalanced | Close as lost and log the reason; continuing to write damages the brand |
| The customer asked to be contacted on a specific date | There is an agreed date | Pause with expiration on that date, not before |
| The customer wrote from a number that had already inquired about the same thing before | It is a repeated contact with no progress | Refer to a person on the team with first and last name; the automated channel is no longer enough |
How a retry is counted (and why almost all teams do it wrong)
A retry is not 'writing again'. It is a message with a reason to exist. If the second message says the same thing as the first in different words, it is not a retry: it is insistence, and the customer reads it as pressure. The practical difference is that the retry contributes something the first message did not have.
- New information: an updated price, an appointment that opened up, stock that came back.
- A closed question: two specific options instead of 'are you still interested?'.
- A change of format: if the first was text, the second can be a short audio or a template with the summary.
- A change of person responsible: if the first was sent by the team, the second can be signed by a person with a name.
- An explicit limit: 'I am writing to you one last time about this' closes the conversation with dignity and avoids the third message.
A retry that contributes nothing new does not count as a retry in the statistics: it counts as a sent message. The difference matters when measuring the response rate.
When to hand off to another channel and when not to
Handing off is not escalating. Escalating is passing the conversation to another person within the same channel; handing off is moving it to another channel because there will no longer be a response on WhatsApp. Handing off has a cost: the customer has to change context, and some of them won't. That's why you hand off when there's a concrete reason, not as an automatic last resort.
| Situation | Best to hand off to | Reason |
|---|---|---|
| The customer asked for a detailed quote and didn't respond to the summary | Email or call | The detail doesn't fit comfortably in a chat and the customer needs to look at it calmly |
| The customer writes from a number that isn't their usual one and responds from another | Call to the number in the history | There may be a problem accessing WhatsApp, not a lack of interest |
| The customer asked to speak with a person | Call | The chat conversation has run its course as a format |
| The inquiry requires coordinating a visit or a delivery | Call | Coordination needs confirmation in the moment, not deferred |
| The customer stopped responding after a complaint | Call from a manager, not the salesperson | An unanswered complaint is resolved with voice, not with another written message |
| The customer responded once and then only reacted with emojis | None: close or pause | There's no conversation to hand off; there's a contact who doesn't want to move forward |
Closing as lost: what gets recorded and what doesn't
Closing as lost is the most uncomfortable outcome and the one that gets postponed the most. A team would rather leave the conversation open 'just in case' than mark it lost, because closing feels like giving up. The problem is that an open conversation with no response isn't a live opportunity: it's a pending task that nobody is going to do.
The close is useful if it leaves a reason. Without a reason, the close is just one less number in the inbox and it teaches nothing. With a reason, in three months you can look at the list of closes and see whether the problem is price, response time or channel.
- Reason for the close: one of the categories in table 1, not free text.
- Number of retries made and on what dates.
- The customer's last message, even if it's an emoji.
- Channel they came in through and channel they were handed off to, if there was a handoff.
- If the customer left an alternative contact detail, even if they didn't respond.
- Close date and the agent who closed it.
A close with a reason takes less than a minute. A close without a reason forces you to reread the whole conversation every time someone asks why that customer was lost.
Pause with expiration: the exit that avoids zombies
A pause with expiration is the intermediate decision between retrying and closing. The conversation is not worked today, but it has a date on which it returns to the queue. It is useful for cases where silence is circumstantial: vacations, a process that has not yet closed, a customer who asked to be contacted later.
- 1Define the reason for the pause in one sentence: 'waiting for customer response', 'process open until the 30th', 'asked to be contacted in two weeks'.
- 2Set the expiration date. Without a date, the pause is a disguised closure.
- 3Remove the conversation from the active queue, so it does not take up space or count as pending.
- 4When it expires, the conversation returns with a single retry and the same logic as table 1.
- 5If there is still no response when it returns, it is closed as lost. The pause is not renewed twice for the same reason.
The one-renewal rule avoids the loop: there are conversations that are paused every fifteen days for a year and never get closed. That is not follow-up, it is a list that grows without anyone looking at it.
The four mistakes that make the matrix useless
| Mistake | What happens | How to fix it |
|---|---|---|
| Each agent decides based on their own judgment | Two identical conversations end in different decisions and nobody knows why | Set the matrix in writing and review it once a quarter, not on every conversation |
| Retrying without limit | The customer receives five messages about the same inquiry and blocks the number | Set a retry cap per reason and respect it even if the salesperson insists |
| Closing without a reason | The inbox empties but nothing is learned | Require choosing a reason from the list in order to close |
| Transferring without notifying | The customer receives a call they were not expecting and the conversation gets worse | The transfer message says who is calling, from what number and in what time slot |
How to know if the matrix is working
The matrix works when conversations stop piling up without a decision. There are three numbers that show it, and they can be pulled from message and campaign statistics without building a new dashboard.
- Unanswered conversations older than 7 days: if the number grows, the matrix is not being applied.
- Retries per closed conversation: if the average exceeds two, the cap is not being respected.
- Closures with a reason recorded out of total closures: if it drops below 80%, logging is being skipped.
Tracking unanswered conversations is one of the parts of customer service work where an inbox with AI suggestions helps without replacing the decision. In Wando the AI suggests the reply and the team approves it; the decision to retry, escalate or close remains with the business, because it depends on information that is not in the chat.
Before applying any deadline on this page, check the configured business hours: a conversation that comes in on a Sunday night cannot count Sunday as a day without a reply.
Frequently asked questions
How many retries should be made before closing a conversation?+
It depends on the reason for the first message. A specific quote allows two retries separated by at least one day; a vague inquiry allows one; a message that is out of scope allows none. The cap is set by reason and applies equally to all agents.
How long should you wait before retrying?+
As a reference, one day for sales inquiries and 24 hours for availability inquiries. The timeframe is adjusted according to the business's sales cycle, but it should not change from one conversation to another.
When is it better to route to a call instead of continuing to write?+
When the content does not fit comfortably in a chat (a detailed quote), when confirmation is needed on the spot (coordinating a visit) or when the customer asked to speak with a person. The routing is announced: who is calling, from which number and in what time window.
What does it mean to close a conversation as lost?+
Marking it with a reason and removing it from the active queue. It is not deleting it: the history remains and the reason helps analyze why it was lost. If the customer returns, the reason prevents repeating the same mistake.
What does pausing with an expiration date mean?+
Leaving the conversation without action for a defined period, with a date on which it returns to the queue on its own. It is used when the silence is circumstantial (vacation, an open process, a contact requested for later). It is not renewed twice for the same reason.
How is the reason for closure recorded?+
With a category from the list of reasons, not with free text. That makes it possible to count how many closures are due to price, response time or channel, and to compare between months.
What do I do if the customer never opened the message?+
Retry through another channel. The same channel already failed once and repeating the message does not change the result. If there is still no response through the other channel, it is closed or paused according to the original reason.
Does the matrix change depending on the industry?+
The timeframes change, not the logic. A business with a long sales cycle can extend the pause expirations; a business with availability that changes every day can shorten them. The four outcomes (retry, route, close, pause) are the same.
Answer WhatsApp with AI
Try Wando free. No credit card required.