AI and WhatsApp Automation for Pakistani Businesses: Bots That Hand Over to Your Team
WhatsApp assistants, enquiry capture and workflows between your tools, with a person always one step away.
Staff spend the day answering the same WhatsApp questions and retyping orders from one tool into the next. We build the assistant that answers routine customer questions and records the enquiry, plus the connections that carry orders, leads and documents between your tools. Staff can step into any chat at any moment. Devvista is a software development company with its office in Bahawalpur.
Below you will find where automation pays off, the Meta rules we design around (read in Meta's documentation in November 2026), the fees Meta charges on top of ours, and the jobs we leave to people. To get a quote, contact us or press Get a Quote. General information, not legal advice.
Where automation pays off for a Pakistani SME
Look for work that repeats daily and follows the same steps. In small Pakistani businesses that usually means five things, listed here with the part a person keeps.
| Repeated work | What we set up | The part a person keeps |
|---|---|---|
| Customers ask the same things on WhatsApp: rates, availability, delivery to their city | A bot that replies from the price list and terms you approve, and passes the chat to staff when it is out of its depth | Complaints, bargaining, special requests |
| Enquiries arrive from the website, Facebook ads and WhatsApp at all hours | One intake that records name, city, need and budget in a sheet or CRM and names the person responsible | Choosing whom to call first |
| Order and appointment follow-ups | Approved templates for received, dispatched, rescheduled and reminder messages | Exceptions such as a changed address |
| The same order typed twice, into the store and into the accounts | A workflow that creates the record once and syncs it | Records that break your rules |
| Invoices and forms arriving as PDFs or photos | Field extraction into a draft record | Approving anything marked uncertain |
Sometimes a fixed rule or a shared inbox with saved replies is all you need, and then that is what we will suggest. A bot suits cases where customers word one question in many ways. Our global workflow automation page (English) covers the wider method.
Six Meta rules we design around
WhatsApp's owner, Meta, sets conditions on every business that uses the WhatsApp Business Platform. This table lists the conditions that change how we build, with their source.
| Condition | Meta's wording, in brief | Effect on the build |
|---|---|---|
| Webhooks | The platform "relies heavily on webhooks"; customer messages and delivery status updates both reach you that way (Cloud API overview) | Your bot, CRM or accounts system learns of a message the second it lands, so no lead waits inside someone's phone |
| Templates | Outside the customer service window only templates may be sent, and they generally need approval first (Cloud API overview) | We draft and submit the wording early and never plan a launch date around instant approval |
| Opt-in | "You must obtain user opt-in before sending message templates", naming your business and intent (Cloud API overview) | Consent wording goes into your forms, checkout and first reply, and we record when it was given |
| Consent by category, and leaving | The Business Messaging Policy asks for separate opt-in per message category and clear opt-out instructions (WhatsApp Business Messaging Policy, updated 23 September 2026) | Order updates and promotions are agreed separately, and each campaign shows how to stop |
| Bots and people | Automation is allowed while answering inside the 24-hour window, with "prompt, clear, and direct escalation paths" | We build and test the route to your staff before the answers |
| Account and number | A business number, real or virtual, sends and receives; verification status affects things like throughput (Cloud API overview) | We aim to register the account, number and verification in your company name |
One more limit: outside the service window, the documentation caps how many unique users you can reach, at business portfolio level. So a blast to an old customer list is a poor plan, and messaging people who never agreed breaks the policy.
Meta's fees come on top of ours
Our quote pays for the build. Meta bills message fees separately, so put them in the budget now. Meta's pricing page (WhatsApp Business Platform pricing, read November 2026) states the following.
Per message. Since 1 July 2025 Meta charges per message; the earlier per-conversation model was replaced. Messages fall into five categories: marketing, utility, authentication, service and Meta Business Agent. Rates depend on category and on market, and Pakistan has its own entry on the rate card.
What costs nothing. A customer writing to your business is not charged. Every business phone number also gets 1,000 service messages a month, and service messages beyond that are charged at Meta's rate card, with service pricing updates starting 1 October 2026.
Moving rates, foreign currency. The page marks Pakistan's utility and authentication rates as higher after 1 April 2026 and as an increase after 1 October 2026. Of the 16 billing currencies it lists as of 1 July 2026 (the US dollar and the dirham among them), PKR was absent when we read it, so expect Meta's invoice in a foreign currency. We print no per-message amounts here, because they change; check the live rate card against your own volumes.
Urdu, Roman Urdu and English in one chat
A single customer may write Urdu script in one message, Roman Urdu in the next and English after that, often followed by a voice note. A language model may cope with much of this and miss some, and when it misses it can still sound confident. We test on your own messages before launch, and we quote no accuracy percentage until we have read your real chats.
The method is simple. With your consent we take a batch of past customer messages, strip the names and run the assistant against them before go-live. Each failure is logged and fixed first. Answers are drawn only from what you have signed off: rates, delivery terms, hours, product facts.
Voice notes, photographed payment receipts and attached documents are separate pieces of work with their own cost, so scoping decides which ship first. If a saved-reply inbox would serve you better than a bot, we say so.
Designing the moment a person takes over
The assistant is only acceptable if staff can step in cleanly. We hand the chat to your team, history attached, in four situations.
- The question falls outside the material you approved.
- The customer sounds angry or brings up a refund, a complaint or a payment problem.
- The customer asks for a human, however they phrase it.
- The exchange runs several turns without resolving (you pick the limit).
The customer reads a brief note that a colleague will answer. Your colleague sees the entire conversation from the first message. Meta's policy asks for escalation paths, which is one reason this flow is the first thing we test.
Connecting WhatsApp to the rest of your tools
Much of the saving sits behind the chat window. A web order creates the customer and the invoice in your accounts without a second typing. A fresh enquiry reaches the CRM with an owner. A supplier PDF becomes a draft bill waiting for approval.
Simple and mid-size flows may run on n8n or on code, chosen at scoping. n8n's hosting documentation says it can be self-hosted on your own infrastructure, on-premises or in a private cloud, and lists Docker Compose as one route (n8n hosting). That matters if the data should stay on a server you control. When a tool cannot do the job, we code the link against the other system's API.
Devvista integrates with other systems, though most of that work is under NDA, so we explain the method and name no companies. If you run an ERP or Odoo system, accounting or POS software or an online store, the automation is planned around it.
We give each flow logging and an alert, so a broken step raises a notification instead of stalling quietly.
Work we keep away from the machine
Rule-based, repeated jobs suit automation. Anything involving judgment, a relationship or a legal duty does not. Our split:
| The system handles | A person approves | People only |
|---|---|---|
| Hours, order status, delivery terms, rate-card answers | Quotations, discounts, refunds, anything with tax or legal effect | Complaints and disputes |
| Copying records among store, accounts and CRM | Fields lifted from scanned paper | Hiring, dismissal, contracts |
| Reminders from approved templates, to opted-in customers | Messages to anyone whose consent you cannot show | Large negotiations |
Where automation issues or sends invoices, tax rules may apply to those documents. We would work from the FBR's published requirements for your type of business, and your accountant should confirm what applies. No tax rule is quoted on this page.
What happens to customer data
The assistant sees names, numbers, addresses and message content. Before we build, four answers go into the scope: where the data sits, which outside services touch it (messaging platform, AI provider, automation tool), how long chats are kept, and who may read them.
The right setup depends on your data and your own legal duties. We did not verify an official Pakistani data protection text while writing this page, so none is quoted; your legal adviser should confirm what applies to you, and we will build to that answer.
How a project runs, week by week
The shape is the same whether you need one enquiry flow or several linked systems.
| Stage | Activity | You receive |
|---|---|---|
| Call | The process, its volume, today's method, the tools involved | A written one-paragraph goal |
| Map | Steps drawn out and marked automated, approved or manual | A one-page map and a first-release list |
| Accounts and consent | WhatsApp Business Platform account, number, verification and opt-in wording; we aim to register platform accounts in your company name | Accounts registered to your company where possible |
| Build | We usually propose a working piece every one to two weeks, shown on video and wired to a test copy of your tools | Something to try yourself |
| Trial on real chats | Anonymised messages, odd cases, template approval | A pass and fail list |
| Go-live | One channel or process first, with error alerts | Monitoring and a route to your staff |
| Hand-over | Flows, accounts and documentation; support can be agreed | Accounts and handover set out in the proposal |
What moves the price
The same bot can hide very different work, so cost follows scope. Tell us your budget range on a short call and we will propose what fits. These move the cost most:
- The channels covered: WhatsApp, website chat, email.
- The systems to connect, and whether each has an API.
- How much answer material has to be written or tidied first.
- The volume of Urdu, Roman Urdu and English testing, and whether voice notes are included.
- Whether data must stay on a server you control.
You pay providers directly for Meta's message fees, AI model usage and any workflow-tool subscription; we list them in the plan. A bot can reply faster and capture details more reliably. Whether that turns into sales depends on your offer and your team, and we promise no leads or results.
Examples, and the limits of what we show
No client names appear here. Devvista builds integrations and Odoo systems for clients, mostly under NDA, so we describe how we work. Our published case studies (English) show how we document projects, including AI-assisted automation with a human approval step. They are not Pakistani WhatsApp bots and we do not present them as such.
What you can inspect before paying is the process: the written scope, the demo cadence, the test list and the account hand-over.
Next steps
A first conversation covers the questions your customers repeat and the person who should take over. Then we build in small pieces, test on your own messages and launch on one channel.
Related pages: custom software development, website development, mobile app development, accounting and POS software, our Bahawalpur page and the Pakistan home page. To start, contact us.
Contact Devvista
Our address and phone. Meetings are held online.
Tell us what you need and we will send a quote. Get a Quote.
Straight Answers.
Tell us about your process
Tell us which process eats your team's time or which questions customers keep asking. We reply after a short call with a proposal.
- 30-minute online call
- Honest feedback on fit
- No obligation
- Book a call30 minutes online. Tell us what you want to build.
- Get a straight answerHonest feedback on fit and scope.
- DecideYou choose the next step once the scope is clear.