How Many People Does It Take to Handle a Business WhatsApp? Formula and Sizing Table

How many people are needed to handle a business's WhatsApp

The question arises as soon as a business starts receiving more than 50 messages per day: does one person handle this or do I need to hire someone else? The answer is not a magic number; it's a formula that combines three variables: how many messages come in, how long each response takes, and how many real hours each person works. This article gives you the formula, the table to apply it without a calculator, and the edge cases that break any estimate.

The formula is based on a simple idea: the workload of customer service is the number of messages multiplied by the time each one takes. Then it's divided by a person's real capacity, which is not 8 hours because nobody spends 8 straight hours responding without breaks, shift changes, or unexpected events.

The sizing formula

The basic formula is this:

People needed = (messages per day × minutes per message) / (hours per shift × 60 × occupancy factor)

The occupancy factor is the percentage of time a person is actually available to respond. Nobody is at 100%: you have to answer calls, load orders, check stock, go to the bathroom, or simply think about the response. A realistic value is between 0.6 and 0.8. With 0.7, you're on the safe side.

Example with concrete numbers: a business receives 120 messages per day, each response takes 3 minutes, and each person works 6 hours with an occupancy factor of 0.7.

People = (120 × 3) / (6 × 60 × 0.7) = 360 / 252 = 1.43 people.

The result is always rounded up: you need 2 people. But be careful, that rounding hides a decision. If the result is 1.1, one person is enough if messages don't all arrive at once. If it's 1.9, the answer isn't to hire someone full time: it could be one person in the morning and another in the afternoon, or one full-time person and another to cover peaks.

Quick sizing table

The table covers the most common cases, but the number of messages per day doesn't tell the whole story. Two businesses with 100 daily messages may need very different teams depending on when those messages arrive and what type of response they require.

The three variables that break the calculation

The formula assumes that messages arrive evenly distributed during the shift. In practice, that almost never happens. There are three situations that invalidate the result if you don't adjust for them:

• Messages concentrated in a few hours: if 80% of messages arrive between 12:00 and 14:00, the formula gives you a number that isn't useful. In that case, calculate the people needed only for those peak hours and then decide if the rest of the day is covered by the same people or if no one is needed.
• Responses that require research: if each query involves checking stock, asking another area for confirmation, or looking up a piece of data, the time per message triples. Measure it with a stopwatch, don't estimate it.
• Messages that are conversations, not queries: a customer who asks about price, then availability, then payment methods, and then places the order is not one message—it's four. If you don't count complete conversations, you underestimate the real work.

How to measure real time per message

The hardest data to estimate is time per message. The right way to get it is not to guess: it is to measure. For three business days, note the entry and exit time of each message and the number of messages answered. Then divide the total hours by the number of messages.

Example: one person worked 6 hours (360 minutes) and answered 90 messages. The real time per message is 360 / 90 = 4 minutes. That number already includes breaks, calls, and unexpected events, so there is no need to apply the occupancy factor separately if you measure it this way.

The difference between estimating and measuring is large. If you estimate 2 minutes per message and in reality it is 4, a business with 200 daily messages goes from needing 2 people to needing 4. Measuring for three days avoids that mistake.

When a single person is enough

A single person is enough when these three conditions are met: fewer than 80 messages per day, time per message of 3 minutes or less, and messages that can wait up to 30 minutes without the customer getting upset. If any of the three is not met, you need at least another person or a tool that helps you.

There is also a physical limit: one person cannot respond to more than 120 messages per day sustainably without the quality of responses dropping. Past that number, the most common mistake is hiring someone part time when in reality you need to split the day into two shifts.

The case of seasonal peaks

Businesses with marked seasonality (restaurants on weekends, e-commerce in December, academies at the beginning of the month) cannot size for the peak because that means having people idle the rest of the time. The solution is to size for the average and have a plan for the peak: a part-time person who joins, or a tool that absorbs repetitive inquiries.

If the peak is predictable (you know that on Fridays you get 3 times more messages), the calculation is done separately for that day. The rest of the week is covered by one person, and on Friday another one is added. This is cheaper than hiring someone full time for a 4-hour peak.

How to know if your current team is overwhelmed

Before hiring someone, it's worth checking if the problem is a lack of staff or poor organization. These are the indicators that the team is at its limit:

• The average response time exceeds 30 minutes during business hours.
• There are messages left unanswered at the end of the day.
• The same question is answered differently depending on who answers it.
• The person who handles inquiries also does other tasks and leaves messages waiting.
• Customers ask twice because the first response didn't arrive.

If several of these indicators appear, the problem is not just the number of people: it's that customer service competes with other tasks. The solution then may be to separate customer service from the rest of the work, not to add another person who will also do several things at once.

The final decision table

What happens when the team is not enough and you can't hire

If the calculation shows you need 3 people but you only have 1, hiring is not the only option. There are two paths: reduce the time per message or reduce the number of messages that require human attention.

Reducing time per message is achieved with prepared answers for frequently asked questions (hours, prices, shipping, payment methods). If 40% of inquiries are the same five questions, having those answers ready to copy and paste lowers the average time from 4 to 2 minutes. That alone already halves the number of people needed.

Reducing the number of messages that require human attention is what automation tools do: AI suggests responses and the person approves them with a click, or it automatically answers the simplest inquiries. This does not eliminate the team, but it does reduce the repetitive workload. Tools like Wando (wando.online) work this way: AI learns from the business's real responses and suggests the answer, but there is always a person who approves it.

The result is that a business with 200 daily messages that previously needed 3 people can now handle it with 1 or 2, because the tool absorbs repetitive inquiries and the team focuses on those that require judgment.

Common mistakes when sizing

• Using 8-hour shifts without deducting breaks: a person who works 8 hours by the clock responds, at best, 6 hours. If you don't deduct, you underestimate the people needed by 25%.
• Counting messages, not conversations: a customer who writes 4 times in the same conversation is 4 messages but only one management task. Time per management task is what matters.
• Sizing for the average when there are peaks: if Mondays bring 200 messages and the rest of the week 50, the average is 71 but on Monday you need 3 people. Size separately.
• Not considering learning time: a new person takes 2 weeks to respond at the same speed as an experienced one. If you're about to hire, add 30% time during the first month.
• Assuming all responses take the same time: a price inquiry takes 1 minute, a complaint can take 15. If you have many complaints, the average is not useful.

Frequently asked questions

Does the formula apply to any business type? Yes, the structure is the same. What changes is the time per message: a real estate agency that sends documentation will have much longer times than a kiosk that responds with opening hours.

What do I do if messages arrive at night? If your business does not promise 24-hour attention, nighttime messages are added to the start of the next shift. You only need extra staff if you promise to respond at night.

Does an AI tool eliminate the need to hire? It does not eliminate it, but it reduces the time per message. If the AI suggests responses that the person approves, the time per message can drop from 4 to 1 minute. That can make a business go from needing 3 people to needing 1.