$1,200
Entry scope. Core build, one role set, standard reports and exports.
View this packageIn this market the enquiry does not arrive by email, it arrives on WhatsApp. We put that conversation on the official Business API, answer what can be answered automatically, and record the rest against the customer in your own system.
| Thread | Messages | Handled by | State |
|---|---|---|---|
| Order status enquiryRepeat customer | 4 | Automated | Closed |
| Price list requestNew enquiry | 2 | Automated | Sent |
| Bulk quotationQualified, 40 units | 9 | Sales, Branch 02 | Open |
| Damaged itemPhoto attached | 6 | Support | Escalated |
Built on the official WhatsApp Business API, on your own verified number, so the history stays yours and the account is not at risk from unofficial tooling.
Your number onboarded to the official Business API with a display name and business profile. One number for the business rather than a personal handset that leaves when its owner does.
The questions asked all day — price, availability, order status, location, opening hours — answered in seconds from live data, in English or Urdu, at any hour.
Anything the rules do not cover goes to the right person by branch, product line or account owner, carrying the conversation so far so the customer never repeats themselves.
Confirmations, dispatch notices and delivery updates sent from the same records the warehouse works from, using approved message templates so they deliver reliably.
Product lists, price sheets and PDF quotations sent in the thread, generated from your current pricing rather than from a file somebody saved last quarter.
A payment link issued inside the conversation, marked against the invoice when it settles, so the customer pays where they are already talking to you.
Every thread attached to the customer record. A new enquiry becomes a lead with an owner and a follow-up date, and the sales history is visible in the same screen as the conversation.
Volume by hour, how much was handled without a person, response times, and what got escalated. Every message stored and exportable, including what an automation sent and why.
Automation bolted onto a personal WhatsApp works until the account is restricted, and the business loses the number its customers know. The official Business API is the version that is meant to be automated.
A verified business number on the official API is sanctioned infrastructure rather than something tolerated, so automation is not a standing risk to the account.
Conversations sit in your database, not on one employee's handset. When somebody leaves, the customer relationship stays behind with the record intact.
Notification templates are approved in advance and sent through the sanctioned route, so order and delivery updates arrive rather than being silently dropped.
Because it is an API, replies can read live stock, a real balance and a real order status, instead of a canned message that may already be out of date.
These are the figures a build of that shape starts at. Beyond them an engagement is quoted as one fixed figure against an approved scope, so the price does not move unless the scope does.
Entry scope. Core build, one role set, standard reports and exports.
View this packageExtended scope. Several modules and roles, an integration, and full reporting.
View this packageQuoted against your approved scope. Multi-site, multi-role or integration-heavy programmes.
Request a quotationFigures are entry prices in USD, exclusive of taxes. Hosting, gateway charges and third-party services are recharged at cost. Basic and Premium figures are clickable: they open the product page, where the full module list and the buy buttons are. See all products.
Usually yes. A number currently on the normal WhatsApp or WhatsApp Business app can be migrated to the Business API, though it stops working in the phone app once it moves, and the chat history in that app does not come with it. We check the number's eligibility and tell you what will and will not carry over before anything is changed.
Messaging is billed by Meta, separately from what we charge to build the system, and the rates depend on conversation type and country. We set the account up in your own name so you are billed directly and can see exactly what you are spending, rather than routing it through us at a markup.
They should, and we build it that way. Automated replies are useful for the questions with a factual answer; pretending to be a person is how trust is lost. Anything the automation cannot answer is handed to a human quickly and visibly, and a customer can ask for a person at any point.
If it has an API or a database we can reach, yes, and that is usually the better build. If it does not, we will tell you what connecting it would involve before you commit. Where there is no system yet, the same engagement can deliver a CRM alongside it so the conversations have somewhere to live.
Tell us the message volume, who answers today and what system the answers live in. You receive a written scope, a fixed price and a delivery schedule in return.
Submitting your enquiry