Decision matrix: scheduled follow-up, passive wait or definitive close
What this matrix solves
A conversation doesn't end when the customer stops writing. It ends when the team decides what to do with that silence. And that decision has only three possible outcomes: scheduled follow-up (someone will write again on a specific date), passive waiting (nobody writes, but the chat stays alive because the customer has a pending reason), and definitive closure (it's archived and not resumed).
The most common mistake isn't choosing wrong among the three: it's not choosing. The chat stays open in the inbox, with no tag and no owner, and after fifteen days nobody remembers who that person was or what they had asked for. When the customer writes again, the operator has to rebuild the entire conversation from scratch, and the customer perceives exactly that: that they don't know them.
The matrix that follows serves that purpose: so that anyone on the team, looking at the last part of the chat, can assign the correct status without asking anyone. It doesn't replace the operator's judgment, but it does eliminate the gray area where everything gets postponed.
This page works on conversation states, not on the technical flow of WhatsApp's 24-hour window. If what you need is to understand what can and cannot be sent based on the time elapsed, that's a different topic.
The three outcomes, defined without ambiguity
Before the decision table, it's worth establishing what each status means, because in practice teams use them as synonyms and they are not.
- Scheduled follow-up: there is a concrete action, an owner, and a date. The chat leaves the active inbox and enters a list with a reminder. If the customer doesn't respond on that date, it's evaluated again.
- Passive waiting: the customer has something pending on their side (a decision, an internal budget, a consultation with their partner, a payment that depends on a third party). Nobody on the team has an action to execute. The chat stays alive, without an active reminder, but with a tag.
- Definitive closure: there is no reason to resume. The inquiry was exhausted, the customer bought elsewhere, explicitly asked not to be contacted, or the request fell outside the scope of the business. It's archived with a reason.
The difference between follow-up and passive waiting is not time: it's whose action comes next. If the next action belongs to the business, it's follow-up. If the next action belongs to the customer or a third party, it's passive waiting. This single distinction resolves half of all cases.
Decision matrix: which status applies
| Signal in the conversation | Next action | Status | Timeframe or reminder | What gets recorded |
|---|---|---|---|---|
| The customer asked for a price and didn't reply after it was sent | The business: retry with a new angle | Scheduled follow-up | 24 to 48 h since the last message | Product asked about, price sent, date of the retry |
| The customer said "I'll look at it and let you know" | The customer: check with the decision-maker | Passive waiting | No active reminder; review after 7 days | Who decides, what they still need to evaluate |
| The customer asked for a formal written quote | The business: prepare and send the document | Scheduled follow-up | The same day or the next business day | Requested format, missing details |
| The customer disappeared after three messages from the team | The business: one last attempt and then close | Scheduled follow-up (last) | 72 h; if no reply, it moves to closed | Number of previous attempts |
| The customer said they bought somewhere else | None | Definitive close | Immediate | Reason: bought from a competitor |
| The customer asked not to receive any more messages | None | Definitive close | Immediate, no exceptions | Reason: explicit opt-out |
| The customer is waiting for a spare part or an appointment to arrive | A third party or the calendar itself | Passive waiting | Reminder tied to the event, not to a fixed date | Estimated date of the event |
| The customer asked something that was fully answered and didn't come back | The business: one check-in message | Scheduled follow-up | 48 h, a single message | Original inquiry |
| The customer wrote outside business hours and never again | The business: resume during business hours | Scheduled follow-up | The next business day, first thing | Time of the original message |
| The customer asked for information about a category or area that isn't served | None | Definitive close | Immediate | Reason: out of scope |
| The customer sent a payment receipt and is waiting for confirmation | The business: verify and confirm | Scheduled follow-up | The same day | Receipt received |
| The customer said they'll come back "next month" | The customer: resume contact | Passive waiting | Review after 30 days, no automatic message | Approximate date they mentioned |
How to read the table day to day
The first column is the only thing the operator has to look at. They don't need to interpret the customer's tone or guess intentions: they need to identify which of those signals describes the last part of the chat. If the signal isn't on the list, it's because the case is genuinely new and it needs to be added to the team's table.
The third column is the decision. The fourth is what keeps the decision from being forgotten: a follow-up without a date is passive waiting in disguise, and passive waiting with an aggressive reminder turns into harassment. The fifth column exists so that, when the customer comes back, anyone can pick up the thread in two lines.
- 1Read the last three exchanges in the chat, not the whole history.
- 2Identify the signal in the first column of the table.
- 3If there's no clear signal, ask whose action comes next: if it's the business's, it's follow-up; if it's the customer's, it's passive waiting.
- 4Assign the corresponding status, timeframe and label.
- 5Record the data from the last column in the conversation before leaving the chat.
- 6Move the chat out of the active inbox: if it stays there, in two days it gets mixed in with the urgent stuff again.
The edge case: when there's no clear signal
The most common situation is not the customer who says "I'll look at it and let you know." It is the customer who simply stops writing after a reply from the business. There is no explicit signal there, and the operator has to decide with what they have.
The practical rule: if the business's last message contained a question or a concrete proposal, the silence belongs to the customer and calls for passive waiting with review. If the business's last message was informative and asked for nothing, then the ball was left on the business's side and a scheduled follow-up is due. In other words: the state depends on who left the conversation open, not on how much time has passed.
There is a third case that is better handled separately: the customer who writes, gets a reply, and writes again twenty days later as if nothing had happened. That chat should not have gone through any of the three states; it should have been in passive waiting with a tag, and that is why the tag matters more than the deadline. Without a tag, the operator who receives that message does not know whether the customer is new or had already inquired before.
Final closure: the four reasons that justify it
Closing makes people feel guilty, and that is why teams do not close. But a chat closed with a reason is information; an open chat with no owner is noise. These are the only four reasons that justify a closure with no going back.
- Explicit opt-out: the customer asked not to receive more messages. Never retry, regardless of the reason.
- Out of scope: the request does not correspond to the line of business, the area, or the type of customer the business serves.
- Resolved with no possible follow-up: the inquiry was fully answered and there is no reasonable subsequent action.
- Purchase from a competitor or decision made against: the customer communicated that they chose another option. Close with that reason, not with "no response."
Everything else that people close out of fatigue should be in passive waiting. The difference is that passive waiting can be reviewed in bulk once a week, whereas a closure done wrong loses the customer forever and also erases the record that they ever existed.
Explicit opt-out is the only case where there is no room for interpretation or commercial exception. If the customer asked not to be contacted, the closure is immediate and is not reviewed.
Common mistakes when assigning status
| Mistake | What happens in practice | How to fix it |
|---|---|---|
| Leaving everything in the active inbox "just in case" | Within a few days there are dozens of open chats and the team answers in order of arrival, not by priority | Any chat without a new message in 24 h leaves the active inbox with an assigned status |
| Setting a scheduled follow-up on everything | The team promises retries it later does not make, and the customer receives late, out-of-context messages | Follow-up requires a date and an owner; if neither is present, it is passive waiting |
| Closing as "no response" | The real reason is lost and it becomes impossible to analyze why conversations fall through | Closing always carries one of the four reasons on the list, never silence as the cause |
| Confusing passive waiting with neglect | The chat stays alive but nobody ever reviews it, and the customer shows up months later with no context | Passive waiting has a scheduled batch review, even without an individual reminder |
| Retrying without adding anything new | The customer receives the same message twice and reads it as automated insistence | Each retry carries a different angle: availability, deadline, alternative or new information |
| Closing conversations with active customers | A chat with an order in progress gets archived and the customer is left without an answer | Before closing, verify there is no pending action on the business side |
Examples by industry
The same matrix changes its content depending on the business. These four examples show what the decision looks like when the industry defines the reason for the pause.
- Food service: the customer asked for the menu of the day and did not confirm. The next action belongs to the business (confirm availability and delivery time): scheduled follow-up the same day, before the kitchen closes. If the customer said they will come by later, it is passive waiting with a review in 2 hours.
- E-commerce: the customer left a cart assembled and did not complete the purchase. Scheduled follow-up in 24 h with a different angle (stock, payment method, shipping). If they replied that they are waiting for their salary to be credited, it is passive waiting with a review in 15 days.
- Real estate: the customer visited an apartment and said they would think it over with their partner. Passive waiting with a tag and a review in 7 days. If they asked for a second visit, it is scheduled follow-up with a date and an owner.
- Beauty: the customer asked about an appointment and did not confirm. Scheduled follow-up in 48 h with the concrete schedule (two available time slots). If they said they will organize themselves and let us know, it is passive waiting with a review in 10 days.
How to measure whether the matrix is working
A decision matrix is not evaluated by how nice it looks in a document, but by what changes in the inbox. There are three numbers that can be checked without sophisticated tools, counting by hand once a week.
- Number of open chats without a new message in the last 48 hours: if it grows, the matrix is not being applied.
- Percentage of conversations closed with a reason other than "no response": if it is low, the team is closing out of exhaustion and not by criteria.
- Time until the first message when a customer returns after a pause: if the operator has to reread the entire history, the last column's record is not being completed.
None of these three numbers requires a dashboard. They are counted on the same inbox and serve to tell whether the decision is being made or whether it was only written down in a document that nobody uses.
If the team works with a tool that shows the inbox with AI suggestions and labels, such as Wando, the part about assigning status and recording the reason can be done without leaving the conversation. But the matrix works the same with a spreadsheet on the side: what creates order is not the tool, it is the decision rule.
Minimal template to paste into the team
If the team is not going to read this entire page, this is enough. These are the four questions that must be answered before removing a chat from the active inbox, in order.
- 1Did the customer ask not to be contacted? If yes, immediate permanent closure.
- 2Is there a pending action on the business side? If yes, scheduled follow-up with date and owner.
- 3Does the next action depend on the customer or a third party? If yes, passive waiting with a label and weekly review.
- 4Was the request out of scope or did the customer choose another option? If yes, permanent closure with the corresponding reason.
- 5If none of the four applies, the chat is not ready to leave the inbox: information is missing.
Frequently asked questions
What is the difference between scheduled follow-up and passive wait?+
The next action. In scheduled follow-up, the next action belongs to the business: someone has to write on a specific date. In passive wait, the next action belongs to the customer or a third party, and the business has nothing to execute until that happens. Follow-up carries a reminder with a date and an owner; passive wait carries a tag and a batch review.
How long can a conversation stay in passive wait?+
There is no fixed timeframe, because it depends on the reason. If the customer is waiting for a spare part or an appointment, the wait lasts as long as that event lasts. If they said they were going to evaluate it, a review at 30 days is reasonable. The important thing is that passive wait has a scheduled batch review, even if it has no individual reminder, so it doesn't turn into neglect.
When should a conversation be definitively closed?+
In four cases: the customer explicitly asked not to receive more messages, the request fell outside the scope of the business, the inquiry was fully resolved and there is no reasonable follow-up action, or the customer communicated that they chose another option. Closing for "no response" is not a valid reason: in that case, passive wait or a final follow-up is appropriate.
How many retries are appropriate before closing?+
It depends on the business's sales cycle, but a reasonable operational criterion is one retry at 24-48 hours and, if there is no response, a final message at 72 hours with a different angle. If there is still no response, it moves to close with a reason. Retrying more than twice without a new response rarely improves the outcome and increases the risk that the customer reads the messages as automated insistence.
What happens if the customer writes again after a definitive close?+
It is treated as a new conversation, but it is worth reviewing the reason for the previous close before responding. If the close was for explicit opt-out, responding or picking it up again is not appropriate. If it was for a competitor purchase or out of scope, the customer's situation may have changed and they deserve a normal response, with the context of the previous close in view.
Can the assignment of these states be automated?+
The mechanical part can be automated: moving chats with no new message in 24 hours out of the active inbox, applying tags by keyword or reminding about batch reviews. What should not be automated is the decision itself, because it depends on reading the context of the conversation. A chat wrongly closed by an automatic rule loses a customer who was about to buy.
How is the close reason recorded so it is useful later?+
With a fixed tag and a short note in the conversation. The tag has to be one of the four close categories, not free text, so they can be counted later. The note adds the specific detail: what product was inquired about, what the customer said, on what date. Without that record, the analysis of why conversations fall through cannot be done.
Answer WhatsApp with AI
Try Wando free. No credit card required.