Loading
WhatsApp Business API is not an app you install. It is a Meta Business account, a verified business, a phone number that can no longer be used in the WhatsApp app, a set of templates Meta has to approve, and somewhere for your team to actually read and answer the messages. Novamind sets up all five, and runs the API in production for our own platform, so this is not a service we are describing from documentation.
Businesses already answering customers on WhatsApp from one or more personal phones, and feeling every limit of that at once.
The usual trigger is a number of small failures arriving together. Two people cannot answer the same WhatsApp number. Nobody can see what a colleague promised a customer last week. The conversation history lives on a handset that leaves when its owner does. There is no way to send a booking reminder to four hundred customers without being blocked. And nothing connects to the system where the order actually lives.
The API fixes all five, and introduces its own constraints in exchange: you can only start a conversation using a template Meta has approved, you pay Meta per message, and the number you move onto the API cannot be used in the normal WhatsApp app again.
That trade is worth making for most businesses with more than one person answering messages. It is not worth making for a business where one owner answers everything personally, and we will say so rather than sell you a setup you will resent.
Five pieces. Skipping any one of them is how a business ends up on the API and unable to message anyone.
A WhatsApp Business Account under your own Meta Business portfolio, with business verification and the display name review, and a phone number migrated onto the API or provisioned new. The account is yours, registered to your business, not held inside ours. If you want to leave us, the account stays.
Templates are how you start a conversation, and Meta reviews each one and assigns it a category that determines what it costs. We write them, submit them in both languages, handle rejections, and structure the variables so one template covers many cases rather than submitting twenty near-identical ones.
Somewhere multiple people read and answer the same number, with assignment, a record of who replied, and the time remaining in the customer service window visible while they are typing. We build this into a tool you already use, or into our own platform Ignis, or as a plain queue if that is all you need.
Most WhatsApp questions are answered from somewhere else: an order status, a balance, an appointment, a delivery slot. We connect the inbox to that system read-only so the agent has the answer in front of them, rather than switching tabs and retyping it.
Meta rates your number on how recipients react and caps how many unique people you can message in a day, raising the cap as you behave well and lowering it when you do not. We set the number up to earn increases and alert you when the rating moves, because a number that quietly drops to a low tier is a number that stops reaching your customers.
Two separate bills, and conflating them is the commonest misunderstanding we meet.
You pay us once to set it up, from AED 8,000 depending on how many templates, which integrations and which inbox. You pay Meta continuously, per message, at a rate that depends on the country you are messaging and the category of the message.
We do not resell Meta messaging and we take no margin on it. Your messaging bill goes to Meta on your own payment method, which means you can see exactly what you are spending and nobody is marking it up.
Meta prices per country and changes its rate card, so the current figures live on our calculator and our pricing guide rather than on this page, where they would quietly go out of date. Both cite Meta’s own documentation and are updated when Meta changes it.
None of these are our policies. They are Meta’s, they apply whoever sets you up, and knowing them before you start changes what you build.
You cannot message a customer first in free text. Starting a conversation requires an approved template. Once the customer replies, a customer service window opens during which your team can write freely, and when it closes you are back to templates.
The number is one-way. A number moved onto the API cannot go back to being used in the WhatsApp or WhatsApp Business app. If the number currently in use is also someone’s personal line, that is a decision to make deliberately, and often the right answer is a new number.
Bulk messaging is rate-limited by a tier Meta sets per number, and it rises and falls with how recipients treat your messages. Marketing templates to a list that did not expect them is the fastest way to lose the tier you have earned.
Consent matters commercially as well as legally. The per-country data protection position for the UAE, Saudi Arabia, Kuwait, Oman, Qatar and Bahrain is documented with sources on our conversational AI page, and it governs this work too.
The API and a chatbot are two decisions, and most businesses are better off making them in that order.
Plenty of businesses get everything they wanted from the API with no automation at all: a shared inbox, several people answering, history that survives, reminders by template. That is a complete project and a good one.
Automation is worth adding once you can see from the inbox which questions actually repeat. Guessing at that before launch produces a bot answering questions nobody asks, which is the commonest way a WhatsApp chatbot project disappoints.
When you do want it, automated answering on WhatsApp is our conversational AI service, and an assistant answering from your own documents is our AI agents service. Both are priced separately from this setup.
Including two things no vendor can honestly promise.
Your Meta message fees. Those are billed by Meta on your own payment method. We do not resell messaging and take no margin on it.
A guarantee that Meta approves your business verification, your display name or any given template. We prepare each submission properly and handle rejections; the decision is Meta’s.
A guaranteed messaging limit tier. Meta sets it per number based on how recipients react, and it can go down as well as up.
Purchased contact lists, or messaging people who did not opt in. We will not build that, and it is the fastest route to losing the number.
We are not a Meta Business Solution Provider and we do not resell WhatsApp as a reseller would.
On-site work. Setup, template writing, testing and handover all happen remotely, against a number you can message during the build.
We run the WhatsApp Business API in production on our own platform, which is the most direct evidence available.
Ignis, our social media platform, connects a WhatsApp number through a self-serve flow and carries it in a shared per-client inbox alongside Instagram DMs and Messenger, with message templates and their quality ratings, and the remaining customer service window shown to whoever is replying. That is a production WhatsApp number carrying real two-way traffic, not a sandbox.
Our WhatsApp cost calculator and pricing guide are built on Meta’s own published rate card and messaging rules, with every figure cited, which is the same material a setup project is planned against.
We have not published a named client WhatsApp case study, and we would rather say that than describe one without naming it.
The questions we hear before a whatsapp business api project starts.