How many enquiries can a WhatsApp chatbot handle?

A WhatsApp chatbot can handle all your inbound customer conversations at the same time, with no practical upper limit on volume. It does not work through a queue. Each conversation gets its own reply in under 5 seconds, regardless of how many others are happening at that moment.

This is the core difference between a bot and a person. A human agent works through one chat at a time. During a busy period, the queue grows and response times stretch. A bot works across every conversation simultaneously. The fiftieth person to message you at 11 PM gets the same speed as the first.

What makes parallel handling possible

A bot does not allocate attention the way a person does. When a customer sends a message, the bot reads it, searches your knowledge base, and writes a reply, all in one automated step that takes a few seconds. That step runs independently for each conversation. One hundred conversations happening at the same moment each complete that same step on their own, without waiting for the others to finish.

There is no tiredness, no distraction, and no working hours. The bot runs the same process at 2 AM on a public holiday as it does at 10 AM on a Tuesday.

What the bot handles well

The chatbot is built for repeated, predictable questions. These come up in almost every SME inbox:

• Pricing and package details
• Operating hours and location
• How to book, reschedule, or cancel
• Order status and delivery timelines
• Product specifications and availability

A Penang florist getting 60 “do you deliver to Bayan Lepas” messages a day does not need a human to answer each one. The bot answers all 60, in parallel, while the team focuses on arrangements.

Speed matters beyond just convenience. Research published in Harvard Business Review found that leads contacted within 5 minutes are 21 times more likely to qualify than leads followed up after 30 minutes. Polaris answers in under 5 seconds. A human catching up on a busy inbox an hour later cannot match that, and by then the customer may have already messaged a competitor.

What still needs a person

Volume capacity is not the same as judgment. There are conversations where a human is the right answer, and a good chatbot setup routes those cleanly:

• Complaints that need empathy and a personal resolution
• Pricing negotiations or custom quote requests
• Sensitive matters, such as medical questions or disputes
• Anything requiring access to information the bot does not hold
• Customers who explicitly ask to speak with someone

Polaris routes these to your human team in a shared inbox. The handoff is smooth. The customer does not repeat themselves, and your team picks up with full context. You can read more about how that handoff works in the post on whether customers can still reach a real person.

Where WhatsApp does have limits

The one area where Meta does impose caps is outbound messaging. This covers proactive messages sent to customers who did not initiate the conversation, such as campaigns, appointment reminders, and promotional blasts. Meta sets these outbound tiers based on your account’s quality record and conversation history. Accounts with good standing see those tiers increase over time.

For normal inbound conversations where customers message you first, no such cap applies. For most SMEs, the volume of inbound enquiries sits well within the range the platform handles without restriction.

If your business runs frequent outbound campaigns, it is worth understanding how Meta’s tier system works and keeping your message quality high to avoid restrictions. But that is a separate concern from your chatbot’s ability to answer enquiries.

What happens during a spike

Promotions, seasonal rushes, and viral posts can send message volume up sharply and suddenly. For a human team, that creates immediate pressure: longer wait times, missed messages, and replies that feel rushed.

A bot does not behave differently under a spike. A solo salon owner who runs a flash discount on a Friday afternoon and gets 200 WhatsApp messages in an hour does not need to hire extra staff or let messages pile up overnight. The bot answers all 200 at the same speed it would answer 20.

This is also why volume capacity matters more than it might first seem. The question is not just “can it handle my normal load” but “what happens when something goes well and demand suddenly jumps?” The answer with a bot is: nothing changes.

How this fits into a broader operation

A chatbot handles volume. A human team handles judgment. The two work together, not as replacements for each other.

Multiple staff members can work inside one shared WhatsApp inbox through Polaris, so the handoffs from bot to human are visible to everyone and do not fall through gaps. And as your business grows and enquiry volume climbs, the bot scales with you without adding headcount for the repetitive work. You can see how that fits into a broader customer service setup in the post on scaling customer service through automation.

The practical answer to how many enquiries a chatbot can handle is: more than you will realistically receive. The question worth asking instead is which enquiries it should handle, and how you set up the handoff for the ones it should not.