Recommended Response Times by Industry and Query Type
Response time in WhatsApp Business is not a magic number that works for everyone. It depends on the industry, the type of inquiry, and the promise the business can sustain with the team it has. This table organizes recommended ranges by industry and type of inquiry, with the logic behind each number. These are not aspirational goals: they are starting points to calibrate your own operation.
The foundation of everything is the 24-hour window imposed by the WhatsApp API. After a customer writes to you, you have 24 hours to respond within an open conversation at no additional cost. After that period, you can only contact them with an approved template (HSM), which has a conversation cost. That technical limit defines the ceiling: any response time recommendation must be less than 24 hours to keep the conversation alive.
| Industry | Inquiry type | Recommended range | Justification |
|---|---|---|---|
| Gastronomy | Reservation inquiry | 1 to 5 minutes | Reservations are lost if not confirmed quickly. The customer is comparing with other venues. |
| Gastronomy | Menu or price inquiry | 5 to 15 minutes | This is information that can be answered with a template or a quick message. It does not require research. |
| Gastronomy | Order or service complaint | 15 to 30 minutes | The customer has already eaten or waited. A reasonable delay is justified if the response includes a concrete solution. |
| E-commerce | Order status inquiry | 5 to 15 minutes | This is the most frequent inquiry. A longer range encourages rewrites and anxiety. |
| E-commerce | Product or stock inquiry | 15 to 60 minutes | May require checking availability. If the catalog is synchronized, it should be less. |
| E-commerce | Shipping or product complaint | 30 to 60 minutes | The customer needs to feel that their issue has entered a process. The initial response can be an acknowledgment with a timeframe. |
| Health | Appointment inquiry | 15 to 30 minutes | Real urgency is handled through other channels. Here, scheduling is coordinated, and delays are tolerated if there is confirmation. |
| Health | Inquiry about tests or results | 30 to 120 minutes | May require consulting with a professional. It is better to delay and respond well than to respond quickly and poorly. |
| Health | Administrative complaint | 60 to 120 minutes | Involves reviewing medical history or billing. An immediate acknowledgment with a reasonable timeframe is the correct practice. |
| Real estate | Inquiry about listed property | 1 to 4 hours | The purchase or rental decision is not immediate, but the interested party is comparing with other agencies. |
| Real estate | Appraisal inquiry | 4 to 24 hours | Requires coordinating a visit or reviewing data. The delay is justified if a concrete commitment is scheduled. |
| Real estate | Process or contract complaint | 2 to 8 hours | The customer is in a legal or administrative process. The response must include the current status of the process. |
| Academies | Enrollment inquiry | 15 to 30 minutes | Enrollment has a deadline. A quick response prevents the interested party from signing up elsewhere. |
| Academies | Course or program inquiry | 1 to 4 hours | Requires detailed information. Can be answered with a PDF or link to the program page. |
| Academies | Payment or certificate complaint | 30 to 60 minutes | These are administrative inquiries with standard responses. Delays are tolerated if the resolution timeframe is confirmed. |
| Aesthetics | Appointment inquiry | 5 to 15 minutes | The customer is looking for a time slot. If not answered quickly, they will book elsewhere. |
| Aesthetics | Treatment or price inquiry | 15 to 60 minutes | May require consulting with the professional performing the treatment. |
| Aesthetics | Result or service complaint | 30 to 60 minutes | This is sensitive. The response must be empathetic and offer a concrete solution, not an excuse. |
| Stores | Hours or address inquiry | 1 to 5 minutes | This is fixed information that should be in an automatic message. Otherwise, it is an inquiry that is answered instantly. |
| Stores | Product or price inquiry | 5 to 30 minutes | Depends on whether stock is synchronized. If you have to go to the store to check, the range increases. |
| Stores | Exchange or return complaint | 15 to 60 minutes | The return policy should be written. The response is to confirm that it applies and coordinate the procedure. |
How to read the table: the logic behind each range
The ranges are not arbitrary. They follow three criteria that can be explained and defended: the cost of losing the conversation, the complexity of the response, and the customer's tolerance according to the industry.
- Cost of losing the conversation: the easier it is for the customer to go elsewhere, the faster you must respond. In gastronomy and aesthetics, the customer can book at the place next door in five minutes. In real estate, the decision is made over days and delays are tolerated more.
- Complexity of the response: if the response requires checking stock, consulting a schedule, or reviewing a file, the range stretches. What cannot be stretched is the acknowledgment of receipt: a 'we received your inquiry, we will respond before X' should always be immediate.
- Tolerance by industry: in health, the customer understands that a professional must be consulted. In e-commerce, the order status inquiry is the most frequent and the most sensitive: the customer has already paid and expects a concrete response.
The two thresholds that define everything: 5 minutes and 24 hours
There are two numbers that matter more than the rest. The first is 5 minutes: it is the maximum range for inquiries where the customer is about to go elsewhere (reservations, appointments, hours). The second is 24 hours: it is the technical limit of the WhatsApp API. If you do not respond within the window, the conversation closes and you can only resume it with a template that has a cost.
The 24-hour limit is imposed by Meta's WhatsApp API. It is not a recommendation: it is a platform rule. After the deadline, any message you want to send outside the window requires an approved template (HSM) and opens a conversation with a cost. Meta's conversation prices vary by country.
How to measure your real response time (without fooling yourself)
The table gives ranges, but your business needs its own measurement. The most common mistake is measuring the time from when the message arrives until someone opens it or marks it as read. That is not response time: it is viewing time. The metric that matters is the time until a real response is sent to the customer.
- 1Define what counts as a response: a message sent to the customer with useful content. An 'ok' or an emoji does not count. An acknowledgment with a deadline does count, but you have to measure it separately.
- 2Measure by type of inquiry, not globally: the overall average hides everything. If stock inquiries are answered in 2 hours but complaints in 10 minutes, the average says 1 hour and is useless.
- 3Separate by business hours: messages that arrive at 3 in the morning are not answered until 9. Measure response time within the promised hours, not from the arrival of the message.
- 4Look at the distribution, not just the average: if the average is 15 minutes but 30% of messages take more than 2 hours, you have a problem that the average does not show. Look at the 90th percentile: the time within which 90% of responses are sent.
What to do when you don't reach the recommended range
If your operation does not reach the ranges in the table, it is not a failure: it is data. What follows is deciding what to do with that data. There are three paths, and all three are valid depending on the case.
- Automate what can be standardized: hours, address, return policies, order status. These are inquiries with fixed answers that do not require a human. An automatic message with that information is already a response, and it reduces the time to seconds.
- Adjust the promise to the actual team: if you have one person handling and it is not enough, the problem is not the person: it is the promise. Publish the business hours, set up an automatic response outside of hours, and establish a realistic deadline for inquiries that require research.
- Prioritize by type of inquiry: not all inquiries deserve the same time. Those that lose sales (reservations, appointments, stock inquiries) go first. Administrative complaints can wait a bit longer if the acknowledgment is immediate.
The Wando tool helps sustain these ranges: it suggests responses based on what the business has already given, and the team approves them with one click. It does not replace the decision of how many people your operation needs, but it reduces the time to draft each response.
Common mistakes when setting response times
| Mistake | Why it fails | What to do instead |
|---|---|---|
| Copying another company's SLA | An SLA from a company with 5 agents does not apply to one with 1. Real capacity defines the possible range. | Measure your current time, identify bottlenecks, and set a goal 20% better, not a number from another industry. |
| Promising 24/7 without having a team | The promise of immediate response at any hour falls apart at 2 a.m., and the customer remembers it. | Publish real hours and set up an automatic response outside hours with the promise to reply when you open. |
| Measuring only the average | The average hides the extreme cases that generate complaints. | Measure the 90th percentile and the percentage of unanswered messages. Those two numbers are what matter. |
| Not separating by type of inquiry | A single number for everything hides which type of inquiry is failing. | Label conversations by type (sales, complaints, inquiries) and measure each group separately. |
| Confusing 'read' with 'responded' | Marking as read without responding is worse than not opening: the customer sees you ignored them. | Response time is measured until a useful response is sent, not until it is viewed. |
How to adjust ranges to your specific business
The table on this page is a starting point, not a law. To adjust it to your business, you need two pieces of data you already have: the volume of messages per day and the number of people handling them. With those two numbers, you can calculate whether the ranges are achievable.
The formula is simple: if you receive 100 messages per day and have one person handling them for 8 hours, you have 480 minutes to respond to 100 messages. That gives an average of 4.8 minutes per message if the person does nothing else. If they also handle the store, take orders, or do other tasks, the effective time per message decreases. That is where the table's ranges become unattainable, and you must decide: automate the standard or add more people.
This is a capacity estimate, not an exact formula. The real time per message varies based on the complexity of inquiries and the speed of the responder. Use it for sizing, not to promise an SLA.
Frequently asked questions
What is the maximum response time in WhatsApp Business?+
The technical limit is 24 hours: it is the WhatsApp API window. If you do not respond within that period, the conversation closes and you can only re-engage with an approved template that has a cost. The recommended ranges in this table are always below that limit.
Which industry needs the shortest response time?+
Restaurants and beauty salons, for reservation or appointment queries: between 1 and 15 minutes. The customer is comparing with other venues and can go elsewhere in minutes. The easier it is to switch providers, the faster you need to respond.
How do I measure real response time without fooling myself?+
Measure the time from when the message arrives until a useful reply is sent, not until it is opened or marked as read. Separate by query type and look at the 90th percentile, not just the average. The average hides extreme cases.
What do I do if my team cannot meet the recommended ranges?+
First, automate queries with fixed answers: hours, address, return policies. Then, adjust the promise to your actual team: publish business hours and set up an automatic out-of-hours reply. Finally, prioritize: queries that lose sales go first.