Questions to ask a WhatsApp provider before you sign: who owns your account, number and templates
Three questions to put to any WhatsApp Business API provider (BSP or Tech Provider) before you sign — who owns the WhatsApp Business Account, whether you can leave with your number and templates, and who bills Meta's charges.
October 23, 2026 · 5 min read
Most WhatsApp API providers look the same on a pricing page. The differences that hurt come later: the day you want to switch, or the day the bill arrives. Three questions, asked before you sign, settle most of it. This guide gives you each question, what Meta's own documentation says, and what a good answer sounds like.
SendFromChat is an independent product and is not affiliated with Meta or WhatsApp. We are one of the providers you might be comparing, so read our answers as a vendor's. Where we quote Meta, the page and the date we read it are given, so you can check them yourself.
The short version
- Who owns the WhatsApp Business Account (WABA), and the number? It should be you, and you should be able to see it in your own Meta account.
- Can you leave, and take your number and templates? Ask for the exact steps and what does not move.
- Who bills Meta's charges, and is there a markup? Ask whether Meta bills you directly, and which message types your plan counts.
1. Who owns the WhatsApp Business Account and the number?
Your WABA holds your phone numbers, your message templates and your quality rating. If a provider created it under their business account, switching later can mean starting again.
What Meta says: for customers onboarded through Embedded Signup (the "Continue with Facebook" flow most providers use), Meta's Embedded Signup page says that "Business customers onboarded via Embedded Signup own all of their WhatsApp assets" and that they "also have full access to WhatsApp Manager". The same page says a provider cannot restrict that access. (Meta, Embedded Signup overview, read 23 Oct 2026.) Newer Meta pages call the WABA a "Messaging account"; the IDs are unchanged.
So the question is not only "who owns it" but how you were onboarded. Ask:
- Will my number and WABA be created through Embedded Signup, under my own business?
- Can I log in to WhatsApp Manager and see my numbers, templates and quality rating myself?
- Whose business portfolio is the WABA attached to?
A good answer: yes, it is yours, and here is where you can see it. A weak answer: "we manage that for you" with no access for you.
2. Can you leave, and take the number and templates?
Meta has a documented route for moving a customer off a provider. For Tech Providers, Meta's migration page says that "you can migrate a client off of a Multi-Partner Solution by instructing them to unshare their Messaging account", and that doing it via Embedded Signup "does not require business phone number reverification". (Meta, migrating customers off solutions, read 23 Oct 2026.)
The same page lists what does not come along automatically:
- "Templates are not duplicated automatically in this flow."
- "template quality ratings are not duplicated."
- Only templates "with both a status of APPROVED and quality_score of GREEN are eligible for duplication", up to the destination account's template limit.
That is Meta's rule for one particular route. Your provider's contract and tooling may differ, and other routes exist, so ask for their process in writing:
- What are the exact steps to leave, and how long does it take?
- Which templates can I export or recreate, and in what format?
- Is there an exit fee, a minimum term, or a notice period?
- What happens to my conversation history and contacts? Ask for an export.
Ask this before you sign, not at renewal. A provider that answers clearly now is likely to answer clearly later.
3. Who bills Meta's charges, and is there a markup?
There are two billing models, and Meta describes both. Solution Partners "have credit lines" and "can directly invoice their clients for the WhatsApp Business Platform services". Tech Providers "do not have credit lines"; clients "must provide their own payment method after onboarding is complete", and "Meta will then bill these clients for API usage, and the Tech Provider will bill for other services". (Meta, Solution Providers overview, read 23 Oct 2026.)
Neither model is wrong. They differ in what you should check:
- Does Meta bill me directly, or does the provider invoice me for Meta's charges? If the provider invoices, ask whether any markup is added and where it shows on the invoice.
- What does my plan fee cover? Usually the software, not Meta's per-message charges.
- Which messages count against my plan? Ask about replies, auto-replies and chatbot flows separately.
One Meta change is worth knowing before you compare quotes. Meta's pricing page (checked 23 Oct 2026) says that from 1 Oct 2026, service messages, the replies you send inside the 24-hour window, are free up to 1,000 per business phone number per month, with no rollover, and are charged from the 1,001st. They were previously free. Meta also says that without a payment method on the account, service messages past the free tier are not delivered. (Meta, pricing.) We list no prices here because Meta's rates vary by country and message type, so use Meta's own page and rate card. Our pricing guide and 24-hour window guide explain the message types.
So ask any provider: if my reply volume passes 1,000 per number, who pays, and do you show me the count?
What SendFromChat's answers are
We would rather you check us against the same list:
- Ownership: you connect your own WhatsApp Business Account and number with Facebook. Meta bills its charges to your own WhatsApp Business account, and we never mark them up.
- Leaving: see the steps above for Meta's route, and ask us for ours if you want it in writing: teamsendfromchat@gmail.com.
- Our plan: Starter $19, Pro $49, Scale $149 a month, with a 30-day free trial and no card. SendFromChat doesn't count replies against your plan. That is our plan limit; it is separate from Meta's service-message limit above.
Comparing us with others? See SendFromChat vs Twilio, vs 360dialog, vs Superchat and using Meta's Cloud API directly.
A note for EU and UK customers
SendFromChat stores data in Mumbai, India. Transfers from the EU and UK are covered by the Standard Contractual Clauses and the UK Addendum in our Data Processing Agreement, and the sub-processors are listed publicly. Read it before you decide. Ask every provider the same: where is my data stored, what is the transfer basis, and who are the sub-processors? Our GDPR guide covers consent, opt-out and records on your side.
Try it
Start the 30-day free trial (no card), connect your own number and see for yourself where your account, templates and billing live. Start free for 30 days.
Do this from your AI assistant
SendFromChat connects Claude, ChatGPT, Cursor or any MCP client to the WhatsApp Business API — templates, bulk sends, inbox, chatbots and sequences, just by asking. 30 days free, no card.
Start freeMore guides
Build a WhatsApp reply assistant with Claude (with a human hand-off)
Answer customer WhatsApp messages about your own business with the Claude API. A webhook, a restricted system prompt, a hand-off to a person, STOP respected and replies sent inside the 24-hour window.
WhatsApp appointment reminders from your app: a working example (with clock-change-safe timing)
Send WhatsApp appointment reminders from your own code with a REST API. A scheduled job, an approved template, time zones that survive the October clock change, safe retries and CONFIRM / CANCEL / STOP replies.
WhatsApp Business app vs the API: which one you need, and what happens to your number
What the free WhatsApp Business app can't do, when the API is worth it, and what happens to your phone number and chats when you move. Includes Meta's coexistence option.
WhatsApp Cloud API error codes: what they mean and how to fix them
A practical guide to the WhatsApp Cloud API error codes developers hit most (131047, 131026, 131049, 132000, 132001, 130429, 190 and more): what each means, whether to retry, and how to fix it.