Decision matrix: when a channel is covered by the current team, when by overtime, and when it requires a new person

Most businesses decide to add people once the channel has already broken down: unanswered messages, customers complaining about the delay, someone on the team threatening to quit. Hiring at that moment is expensive and comes too late. The decision can be made earlier with two numbers you already have: how many messages come in per day and how long it takes the team to resolve one. With that, you calculate the real load on the channel and compare it against the hours the team has available. This page is that calculation, the table to interpret it, and the edge cases that make the result lie.

The calculation: support hours needed per week

The most common mistake is looking at the number of messages and not the hours. A hundred short messages are not the same as a hundred conversations that end in a sale. The unit of measurement for the channel is the support hour, not the message.

The base formula is: messages that come in per week × average resolution minutes ÷ 60 = support hours needed per week. You get the average resolution minutes from your own operation: take a sample of conversations from the last week, measure from the customer's first message to your last one, and average it. If you have never measured it, the table below has reference values by type of conversation to get started, but the number that matters is yours.

An example with round numbers: 700 messages per week, with an average of 8 minutes of resolution, give 700 × 8 ÷ 60 = 93.3 support hours per week. That is the work the channel demands, regardless of how many people do it.

How many hours your team really has

The second half of the calculation is the supply of hours. It is not enough to multiply people by 40: out of an 8-hour workday, WhatsApp support takes up only a part. If the person also covers the front desk, processes orders, or handles administration, the channel gets a percentage of that workday, not the whole thing.

Following the example: if the channel is handled by a receptionist with front desk duties (20 hours), the owner (6.75 hours), and an administration person (4 hours), the supply is 30.75 weekly hours against 93.3 needed. The channel is covered at one third of what it requires. That gap does not disappear: it turns into unanswered messages, late-night replies, or lost customers.

The matrix: what to do based on the coverage percentage

The deciding indicator is the coverage percentage: available hours divided by needed hours. With that number, the decision stops being a hunch and becomes a table.

The 70% to 90% band is the most deceptive. It feels like one more push will get you there, and that push is sustained for months until someone burns out. The honest question is not whether the team can do extra hours for one week, but whether it can do them twelve weeks in a row without quality dropping.

When extra hours are the answer and when they are the problem

Extra hours work for peaks with an end date: a campaign, a season, a promotion, a week with an event. They have a beginning and an end, and the team knows when it ends. When the peak has no end date, extra hours stop being a reinforcement and become normal operations in disguise.

Before approving extra hours, it is worth exhausting the levers that do not cost a workday: templates for repeated replies, labels to separate what is urgent from what can wait, time-based auto-replies to let people know when you respond, and AI suggestions that reduce writing time. If after that coverage is still below 90%, the problem is capacity, not method.

When a new person is needed (and when not)

Hiring is justified when three conditions are met at the same time: coverage is below 70% on a sustained basis, volume has been growing for several months in a row, and process improvements have already been exhausted. If one of the three is missing, the answer is usually something else.

• Coverage sustained below 70%: it's not a bad week, it's the average of the last two or three months.
• Real volume growth: compare this month's messages against those from three months ago. If it's rising, the gap will widen on its own.
• Process improvements already applied: templates, labels, schedules and AI suggestions are already in use and weren't enough.
• First response time outside target: if you promise to respond within an hour and the average is four, the customer already notices.
• Repeated overtime: if the team has been doing overtime for more than two months in a row, it's no longer reinforcement.
• Absences without coverage: when someone gets sick or takes vacation, the channel is left uncovered.

The other way around: if coverage is fine but first response time is bad, the problem isn't the number of people but the organization. Adding a person to a disorganized team spreads the disorder, it doesn't solve it.

How to distribute the workload when someone new joins

1. 1Define the schedule the new person will cover. If the gap is outside business hours, the shift has to fall there, not in the same shift that's already covered.
2. 2Assign conversations by shift, not by person: whoever starts at 9 receives what was left open, and whoever leaves at 17 hands over their work before leaving.
3. 3Write down who resolves on their own, who consults and who escalates, so the new person doesn't depend on asking all day.
4. 4Measure first response time separately before and after the addition. If it doesn't drop, the workload wasn't where you thought.
5. 5Review coverage at 30 and 90 days: volume may have grown and left the channel tight again.

Common mistakes when sizing the channel

There is a case that no formula solves: the business that doesn't know how many messages it receives or how long it takes to respond. Before discussing whether a person is needed, that business needs a week of tracking. Without those two numbers, any hiring decision is a gamble.

How to know if the decision was the right one

The decision is reviewed with two indicators, not with the team's gut feeling. The first is coverage: after the measure, it has to stay above 90%. The second is first response time: it has to go down or stay within the target the business promises.

• If coverage went up but first response time didn't go down, the bottleneck is in the process, not in the number of people.
• If coverage turned out fine and the overtime disappeared, the decision was correct.
• If after three months coverage dropped again, the volume grew faster than the capacity and it has to be reviewed again.
• If the team is still working outside business hours, the calculated coverage is wrong: there are hours that are not being counted.

In Wando the inbox shows conversations with AI suggestions that the team approves with one click, and the message and campaign statistics help to see the real volume of the channel. That doesn't replace the hiring decision, but it does provide the numbers to make it with data instead of with exhaustion.