Most WhatsApp chatbot projects that disappoint were scoped as a chatbot. They should have been scoped as a change to how enquiries are handled — of which the bot is one component, and rarely the hardest one.
This page sets out what a development engagement actually contains, in order, and what to verify at each stage before releasing payment.
Before Anything Is Built
Three things must be settled, and a developer who skips them is planning rework.
Which number. A WhatsApp Business API number cannot also be used in the consumer WhatsApp app. If your business has been running on a personal number for years, decide deliberately: migrate it (and lose app access on that number) or start a new one and run a transition period.
Which access route. API access is obtained through Meta's Cloud API directly or through a Business Solution Provider. The route affects cost structure, messaging limits and who holds the relationship. Ask which they are using and why.
What the bot must not do. Escalation rules written down before the build, not discovered afterwards. Complaints, refunds and anything medical, legal or financial should reach a person quickly.
Build Phases
Phase 1 — Conversation design
The actual product. Mapping what customers ask, in what order, and what a good answer looks like. Done properly, this comes from reading your real message history rather than from imagination.
Verify: ask to see the conversation map before development starts. If there isn't one, the bot is being improvised.
Phase 2 — Knowledge and logic
Loading your genuine pricing, services, policies and availability, then defining qualification logic — what the bot needs to establish before a lead is worth a salesperson's time.
Verify: check the source material. A bot answering from outdated pricing damages trust faster than no bot at all.
Phase 3 — Integrations
Where the conversation connects to everything else: CRM, calendar, order system, sheets, payment links, ticketing.
Verify: confirm each integration is two-way where it needs to be. A bot that writes to a CRM nobody reads has moved the problem rather than solved it.
Phase 4 — Testing on real traffic patterns
The phase most often skipped. Test messages in English, Urdu script and Roman Urdu, with local abbreviations, misspellings, voice notes and images — because that is what arrives.
Verify: test it yourself, in your customers' language mix, and try to break it. A bot that handles only clean English will fail on most genuine Pakistani enquiries.
Phase 5 — Template approval and go-live
Message templates for anything sent outside the customer-initiated window require Meta approval. Approvals can be rejected and resubmitted, so this belongs early in the timeline rather than on launch day.
What to Verify Before Final Payment
- The escalation path works, and a real person receives the handoff
- Conversation history is stored somewhere you can access
- You own the WhatsApp Business Account and the Meta Business Manager asset
- Someone on your team can edit responses without the developer
- Monthly running cost is documented, separate from the build fee
- Fallback behaviour when the bot does not understand is sensible, not a loop
That fourth point decides whether the system stays useful. A bot that requires a developer for every wording change gets abandoned within months.
Realistic Timelines
A focused first build — capture, answer common questions, qualify, hand off — is typically a few weeks, with template approval as the main external dependency. Deep CRM, ERP or payment integrations extend it substantially.
Projects that overrun usually did so for one of two reasons: the business could not supply accurate content about its own services, or the scope grew during the build. Both are avoidable by fixing scope and content before Phase 1.
Pakistan-Specific Build Considerations
Bilingual handling is a requirement, not a feature. Roman Urdu is how a large share of customers write. This must be tested, not assumed.
Voice notes are common. Decide early whether the system transcribes them or routes them to a human. Ignoring them means ignoring real enquiries.
Cash on delivery workflows. Order confirmation and address verification are high-value automation targets in Pakistani e-commerce and need designing into the flow.
Business hours and prayer times. Configure genuine availability, and make the after-hours experience good — that is when the bot earns most of its value.
Number reputation matters. Sending bulk template messages to people who did not opt in leads to blocks and quality-rating downgrades that damage delivery for everyone in your account. Any developer proposing bulk unsolicited messaging is putting your number at risk.
How BITSOL Marketing Builds WhatsApp Chatbots
We start from your existing message history rather than a template, because your real questions are more useful than a generic flow. Escalation rules are written into the scope, and the system is tested on genuine bilingual traffic before it sees a customer.
Build cost and monthly running cost are quoted separately. You own the WhatsApp Business Account and the Business Manager asset, and your team gets an interface for editing responses without us.
Where a simple auto-responder and better staffing would solve your problem more cheaply than a full build, we will say so.
Conclusion
A WhatsApp chatbot is worth commissioning when enquiries are being lost — after hours, in volume, or to slow response. It is not worth commissioning as a technology purchase.
Scope the conversation before the code, insist on bilingual testing, confirm ownership, and make sure someone in your business can edit it. Those four things separate systems that stay running from ones quietly switched off.
FAQ
Do I need the WhatsApp Business API for a chatbot? Yes. The free Business app supports only basic away messages and quick replies, not genuine automation or integrations.
Can I keep my existing WhatsApp number? You can migrate it, but that number can no longer be used in the consumer app afterwards. Many businesses run a transition period with both.
How much does a WhatsApp chatbot cost? Two figures: the build, and the monthly running cost driven by message volume and platform fees. Insist on both being quoted separately.
How long does it take to build? A focused first build is typically weeks. Template approval and deep integrations are the usual timeline risks.
Will it handle Urdu and Roman Urdu? Modern models handle both reasonably, but quality depends on testing. Test it in your customers' actual language mix before accepting the build.
What happens when the bot cannot answer? It should hand off to a person cleanly and quickly. Verify this works before go-live.
Can I send marketing messages to my customer list? Only to people who opted in, using approved templates. Unsolicited bulk messaging damages your number's quality rating and delivery.
Call to Action
If you want to know whether a chatbot is the right fix for your enquiry handling — or whether something simpler would do — BITSOL Marketing can review your current message flow and tell you what is actually being lost.
Author: BITSOL Marketing Editorial Team
About BITSOL Marketing: A Pakistan-based AI, digital marketing, technology and automation agency delivering WhatsApp automation, AI agents, SEO, paid media and development.