Why WhatsApp support breaks at around 50 orders a day
One shared phone works beautifully, until it suddenly doesn't. Here's the point where WhatsApp support stops scaling, and what to change before you hit it.
Almost every growing D2C brand starts support the same way: a WhatsApp Business number on someone's phone. It's personal, it's fast, and customers love it. Then, somewhere around 50 orders a day, the same setup starts quietly costing you sales.
The maths behind the break
At 50 orders a day, a typical store sees 15–25 inbound chats a day, and each one is a conversation of 6–10 messages, not a single message. That's 150–250 messages a day. Spread over a 12-hour window, it's manageable for one person. But support volume doesn't arrive evenly. It spikes after dispatch emails go out, after a sale goes live, and late at night when people finally check on their parcels.
The result is a queue that's empty at 3 pm and 60 deep at 11 pm. Whoever holds the phone either answers at midnight or wakes up to a backlog, and replies the next morning to customers who have already raised a chargeback or left a one-star review.
Three signs you've already hit it
- Your first reply time is measured in hours, not minutes, on weekends.
- The same five questions (where's my order, how do I return, is COD available, what size should I pick, when will it restock) make up most of your chats.
- Two people are logged into the same number and occasionally both reply, or neither does.
What actually fixes it
Hiring a second person helps with hours but not with the repetition. The real fix is separating the conversations that need judgement from the ones that only need information. 'Where is my order?' needs a lookup, not a person. 'My parcel arrived damaged and I need it for a wedding on Saturday' needs a person, fast, with the order already on screen.
The goal isn't to remove humans from support. It's to stop spending them on questions a lookup can answer.
That's the split an AI agent like Onfre makes: it answers the informational questions from your own policies and order data, any time of day, and hands the judgement calls to your team with the context attached. Your team stays small, and your customers stop waiting overnight.
Before you automate anything
Export a month of chats and tag them by topic. You'll usually find that six to eight topics cover most of the volume. Write down the correct answer for each, including the exceptions. That document is your first knowledge source, and it's useful even if you never automate a single reply.