The number is on the van, on the shopfront, in the Instagram bio. One number. One phone. It sits in a drawer behind the counter, and whoever is holding it that day is the only person who can answer. Somebody opens it on a Saturday morning and scrolls past a quote request from Thursday.
Every owner eventually hears there is an official version of this. An API. A proper inbox on top of it. Then they try to find out what it costs and how long it takes, and the answers go vague, because most of the moving parts belong to Meta rather than to whoever is selling you the software.
Here is the sequence, what each step waits on, and where the money goes.
What the Cloud API actually is
The green app on your phone is the WhatsApp Business app. It is free. It runs on a handset, with linked devices hanging off it. It is built for one person.
The Cloud API is a different thing wearing the same logo. There is no app and no handset. Meta hosts the connection, your number sits on Meta's infrastructure, and messages flow to whatever software you point them at. Nobody logs into a phone. Several people can work the same number at the same time, and every message is on the record.
The trade-off is that the software becomes the only way in. Once a number is on the Cloud API, you cannot open WhatsApp on a handset and read that chat. Choose the inbox carefully, because it is now the whole experience. There is a longer breakdown here: WhatsApp Business app vs the Cloud API.
The sequence
A business that can be verified
Meta wants to see an organisation, not a person. In practice that means registration documents for the legal entity, a website or a real online presence, and details that match each other — the registered name, the address, the contact number. What counts as proof differs by country: a trade licence in the Gulf, a company registration number elsewhere. Where those do not match, verification stalls.
Exact document requirements vary by country and by case, and Meta has changed them more than once. Ask your provider what they are seeing this month rather than trusting a checklist somebody published two years ago.
A Meta business account
This is the container that holds the business, the WhatsApp account and the number. Meta has renamed it more than once — Business Manager, Business Portfolio — so ignore the label and look for the place where your assets live.
What it waits on: not much. This part is quick.
Choosing a provider
You do not go to Meta and ask for access. You go through a provider — a Business Solution Provider, or software connected to one. In practice the signup happens inside their product, using Meta's embedded signup flow, and you are logging into your own Facebook account partway through.
Pick this before the paperwork, not after. The provider shapes what verification looks like, what happens when a template is rejected, and whether anyone answers you when the number goes quiet.
Business verification
Meta reviews the business itself. This is the step with the real waiting in it, and the wait is not predictable. It depends on how clean the documents are, whether anything needs resubmitting, and how busy the review queue is. Anyone quoting you a fixed number of hours is guessing.
There is usually some sending allowed on a limited basis before verification finishes. The limits and what they cover have changed over time, so treat that as a question for your provider.
A number that is not already on WhatsApp
This is where most setups snag. A number lives in one place only. If your main number is currently running in the WhatsApp Business app, it cannot also be on the Cloud API.
There is a route for moving an existing number across. The steps have changed, so have your provider walk you through it before you touch anything, and expect the chat history on that phone to stay on that phone. Some businesses take the API on a new number and put a printed note by the till for a month instead. Both work. Decide before you print the next batch of cards.
A landline can be used in some cases, if someone is there to take the verification call. Check with your provider.
Display name review
The name customers see above the chat. Meta reviews it, and it needs to relate to the business as verified. Nicknames, offers and keyword stuffing get rejected. Timing varies.
Templates
Anything you send to a customer who has not messaged you recently has to be a message template, submitted in advance and approved by Meta. Templates fall into categories — marketing, utility, authentication — and the category affects both the approval and what you pay.
Rejections are usually about wording. Promotional language inside a utility template, a placeholder with nothing around it, a variable sitting at the very start or end. Rewrite and resubmit.
The 24-hour window, and why templates exist
A customer messages you. That opens a 24-hour customer service window, and inside it you reply freely — text, photos, a price list, a voice note, whatever the conversation needs.
The window closes 24 hours after their last message. After that you cannot type a fresh message to them. You send an approved template, or you wait for them to come back.
This is the rule that reshapes how a sales team works. A reply at 9pm on the day somebody asks costs you nothing extra. The same reply on Tuesday is a template, needs approval, costs money, and lands on a person who has already bought from whoever answered. Speed stopped being a virtue and became a line item.
What it costs: two separate bills
Owners keep asking for one number. There are two, and they go to different places.
Your software. The inbox, the assignment, the AI, the reporting. Go Talk IQ is free for one number, two people, 500 messages and 500 AI credits a month. Starter is $59 a month, Growth $99, Business $199, in US dollars, with 20 per cent off for paying yearly. The full breakdown is on pricing.
Meta's messages. Meta bills the business directly, on rates Meta publishes. They vary by country and by conversation category, and Meta has revised the pricing model more than once, including a change in how conversations are counted and charged. Read Meta's current published rates for your own country rather than a figure in a blog post, this one included. Free allowances have existed and have also changed; check whether any apply to you now.
Then a third thing worth asking about: some providers add their own per-message markup on top of Meta's rate. Go Talk IQ does not. Campaigns run on the official Cloud API using Meta-approved templates, and Meta's bill goes to you at Meta's own rates.
Who should not do this yet
- One person, keeping up. If a single owner answers everything and nothing is being dropped, the free app is fine. Come back when there are three people and an argument about who replied.
- Registration documents missing, or details that do not match. Fix the paperwork first. Verification will not be talked around.
- Anyone planning to message a bought list. Templates get reviewed, recipients report, and a falling quality rating gets a number restricted. The API is stricter than the app, not looser.
- Teams where nobody owns the reply. A shared inbox shows exactly who ignored the message. That is useful and uncomfortable. If nothing is going to change afterwards, it becomes another tab.
- Anyone who cannot give up the handset. This is the real one. The reason tools like this fail is not features — it is a team quietly going back to their phones.
Where Go Talk IQ fits
Once the number is live, everything above stops being interesting and one question is left: does the team use it.
Go Talk IQ is a shared inbox on the WhatsApp Business number a company already uses. Conversations get assigned, handed over, and marked up with notes, so the person picking one up on Sunday can see what happened on Thursday. An AI assistant answers only from your own material — a website URL, an uploaded document, typed notes — and says when it does not know. A person can take a conversation over at any time, or edit a drafted reply before it goes. Arabic and English both work. Business hours with an after-hours auto-reply. Push a lead into Zoho or HubSpot from the chat. Roles and permissions, an audit log, two-factor authentication.
If you are earlier than that and still working out whether the API is the actual problem, start here: sharing one number with multiple users.