For Pakistani businesses fielding WhatsApp messages outside business hours, which, given how much of the country communicates on WhatsApp, is most of the time, a chatbot means a customer gets an immediate response at 11pm asking about delivery areas, instead of waiting until morning and possibly buying from a competitor who replied faster.
How the chatbot flows work
Most chatbot setups start with a menu-based flow: the customer sends any message, gets a quick menu of common options (Track My Order, Store Hours, Talk to an Agent, Browse Catalog), and taps through using WhatsApp's native button/list interface rather than typing free text. For more advanced setups, keyword and intent matching can handle open-ended questions without a rigid menu, escalating to a human whenever the bot doesn't have a confident answer, which matters more than trying to automate everything, since a bot that confidently gives a wrong answer is worse than one that hands off promptly.
Where a chatbot earns its keep
Order status lookups (pulling live status from your order system rather than making the customer wait for a reply), FAQ handling (delivery areas, return policy, payment methods), appointment or reservation booking for service businesses, and catalog browsing for retail, where a customer can look through products and add to a request without a human ever typing a reply. Each of these is a genuinely repetitive task that a bot handles instantly and consistently, at any hour, in a way a small support team simply can't match around the clock.
Handoff to a human agent
The chatbot and the chat portal are meant to work together, not compete: when a conversation needs a real person, a complaint, a custom order, anything outside the bot's defined flows, it hands off into the shared team inbox with the full conversation history attached, so the agent isn't starting from zero. This is the same underlying WhatsApp Business API infrastructure as the chat portal, just with an automated first layer in front of it.
Building your first flow
Setup starts with mapping out the 4–6 questions your business gets asked most often, building a simple menu around those, and connecting any live data sources (order status, inventory) the bot needs to answer accurately. Most businesses start with a narrow, well-tested flow covering their top questions and expand it over time, rather than trying to automate every possible conversation on day one.
Why menu-based beats free-text for most businesses
It's tempting to want a chatbot that understands anything typed at it, but in practice, a well-designed menu of buttons gets a customer to the right answer faster and with fewer misunderstandings than open-ended text matching, especially across a customer base messaging in a mix of English, Urdu, and Roman Urdu. We generally recommend starting with tap-to-select menus for the most common paths, and reserving free-text handling for the smaller set of questions that genuinely need it.
Multilingual handling
Since WhatsApp conversations in Pakistan regularly mix English, Urdu, and Roman Urdu within the same chat, flows can be built to recognize common phrasings across all three rather than assuming customers will type in one consistent language, which matters for keeping the bot's automated first-response layer genuinely useful rather than something customers learn to route around.
Frequently asked questions
Is this different from the WhatsApp Chat Portal?
Yes, the chatbot handles automated first-response conversations, while the Chat Portal is the shared inbox human agents use. They work together: the bot catches routine questions and hands off anything complex to the portal.
What happens if the bot can't answer a question?
It hands off to a live agent with the full conversation history attached, rather than leaving the customer stuck in an automated loop.
Can the bot check my order status automatically?
Yes, if it can connect to your order or inventory system, it can pull live status rather than giving a generic response.
How long does it take to set up a chatbot flow?
A basic flow covering your most common questions is typically ready within a few days; more advanced setups with live data integration take longer depending on what systems need connecting.
Related services
