Most frequent WhatsApp contact reasons and their standard resolution times, by industry

What this table is for

A resolution time is not the same as a response time. Response time is how long the business takes to write the first time. Resolution time is how long the reason for the contact takes to be closed: the booking confirmed, the order shipped, the appointment scheduled, the question answered without them having to ask again. Most teams measure the first and suffer because of the second.

This table orders the most frequent reasons for contact by industry and assigns each one a standard resolution time. These are not times that come from a standard or from market statistics: they are the values you should set as an internal agreement and then adjust with your own data. The column that matters is not the number, it is the 'owner': if a reason has no owner, it has no standard time, it has hope.

How to read the table

Each row has four decisions: the reason, the standard resolution time, who closes it and what data is needed to close it. The last three columns are what keep the standard time from being just an intention. A reason with no assigned owner stays in the shared inbox until someone picks it up by chance. A reason with no required data gets a half answer and comes back.

• Reason: the query as it arrives, not as you would classify it. If the customer writes 'hi, I wanted to know if you have space', the reason is availability, not 'general query'.
• Standard time: the internal resolution target, not the maximum tolerable. The maximum tolerable is another number and it should be double.
• Owner: the role that closes the reason, not the person. Roles rotate; if the time depends on a person, it falls apart when that person is away.
• Required data: what you need to ask or verify before giving the answer. If it's missing, the conversation comes back and the time doubles.

Reference table: reasons and standard times by industry

The three reasons that eat up the day in almost every industry

If you look at the full table, three reasons appear in almost every industry under different names: availability (is there any?), price (how much?) and status (where is my order / my appointment / my request?). They are the ones that generate the most volume and the ones that repeat the most. They are also almost always the ones that can be standardized the most, because the answer is limited and verifiable.

The fourth block, the one that breaks the average, is exceptions: exchange, return, rescheduling, coverage, requirements. There is no single answer there, you have to find out, and the standard time has to be different. Mixing the two types in the same inbox without distinguishing them is the most common cause of times not being met: the team handles the easy ones first and the hard ones pile up.

• Closed inquiries: they have a single, verifiable answer. They can be resolved with a template or with an AI suggestion reviewed by a person.
• Open inquiries: they require looking up information in another system or consulting another area. They need their own owner and deadline.
• Complaints: the customer already had a problem. The standard time should be shorter than that of an open inquiry, because the cost of delay is higher.
• Out-of-scope inquiries: the business does not resolve them (for example, an inquiry about a product it does not sell). Closing them quickly and well is also part of the job.

How to set the standard time for each reason

1. 1Count how many contacts for that reason you receive in a week. If there are fewer than five, do not give it its own time: group it with the most similar reason.
2. 2Measure how long it takes to close today, from the customer's first message to the last. Use the message date, not the date the contact was entered into the system: they are different things and confusing them gives you a false distribution.
3. 3Split the time into two parts: how long it takes the team to reply and how long it takes the customer to respond or provide the missing data. You do not control the second one, but you can reduce it by asking for the right data from the first message.
4. 4Set the standard at the 75th percentile of what you measured, not at the average. The average is moved by fast cases; the 75th percentile reflects what happens in most real cases.
5. 5Assign an owner by role and a required data point by reason. If two reasons share an owner and data point, they are probably the same reason with two names.
6. 6Review the standard every quarter. A standard time that is never adjusted stops being a goal and becomes a decorative sign.

What to do when the standard time is not met

A deviation is not automatically a staffing problem. Before adding people, it is worth ruling out the three causes that explain most missed targets: the reason was not identified as such, it had no assigned owner, or the required data was not requested in the first message. All three are fixed with definition, not with hours.

The required data: the column that moves time the most

Of the four columns in the table, the one with the greatest impact on actual time is the last one. A reason with an owner and without required data generates a back-and-forth conversation: the customer writes, the team asks, the customer replies late, the team picks it back up. Each round adds hours and adds no information.

The practical rule is that the business's first message should ask for everything needed to close the reason. If the reason is 'shipment status', the first message must ask for the order number and document, not ask 'how can I help you?'. If the reason is 'appointment', the first message must ask for the service and time slot. That alone already lowers resolution time without touching the team's headcount.

• For availability: what, when and how many.
• For price: what exactly and in which variant.
• For status: transaction number and data that identifies the customer.
• For exchange or return: order number, reason and evidence if applicable.
• For appointment: service, professional if applicable, and two possible time slots.
• For coverage or requirements: what is needed and under what condition.

How to measure compliance without distorting the data

To measure whether the standard time is met, the timestamp must be chosen well. The one that counts is the message's, the one the messaging platform assigns when the message comes in or goes out. The date the row was saved in the database can be very different: if there was a history import, that date is concentrated on the day of the import and any analysis of hours or duration gives a false result.

With the right timestamp, the calculation is simple: for each closed conversation, subtract the time of the customer's first message from the time of the business's last message that closed the reason. Group by reason and by category. Look at the median and the 75th percentile, not the average. And separate conversations that started within business hours from those that started outside: if you mix them, the standard becomes impossible to meet by definition.

Common mistakes when building this table

• Setting a single standard time for all reasons. A price inquiry and a return cannot have the same deadline: one is resolved with a piece of data and the other with a process.
• Confusing first response time with resolution time. The first is measured in minutes, the second in hours or days, and they are different indicators.
• Assigning the reason to a person instead of a role. When that person is not there, the reason is left without an owner.
• Not writing down what 'resolved' means for each reason. Without that definition, everyone closes when they see fit and the indicator stops being comparable.
• Measuring with the contact's creation date instead of the message date. It gives distributions that do not reflect the real operation.
• Building the table with twenty reasons. With more than ten or twelve, the team does not remember it and does not use it. Low-frequency reasons are grouped together.

How to keep the table alive

The table becomes outdated for two reasons: the operation changes (new channel, new service, new branch) or the volume changes (a reason that was marginal becomes frequent). It is worth reviewing it on a fixed cadence and with a simple rule: if a reason exceeds 10% of the period's contacts, it must be in the table with its own time and owner.

The rest of the review is hygiene. Verify that the owners exist as roles in the current operation, that the required data is still what is needed to close, and that the standard times are still achievable with the current staffing. A standard that no one meets does not motivate: it is ignored.

If the team uses an inbox with AI suggestions reviewed by a person, like the ones Wando offers, the table also helps organize the training: the frequent reasons and their closed responses are the material with which the system learns from the business's real responses. But the table works the same without any tool: it is a team agreement, written, with an owner and with a number.