WhatsApp Cloud API direct or via a provider: who holds the account

Every WhatsApp Business Account lives inside a Meta business portfolio, and its admin controls the number, the display name, the templates and the payment line. That person decides the rest.

With a direct setup you create the portfolio yourself, verify the business with your registration papers and add the number under your own login. With a provider, two patterns exist. Either the provider registers the account under your portfolio and acts as a partner, or the account sits in the provider’s portfolio with your number parked inside it.

The second pattern is where trouble starts. Leaving means a number migration, fresh template approvals and sometimes a new display name review, all while customers wait for replies on a number that has gone quiet. Regular buyers notice at once.

Meta hosts the Cloud API, so you run no servers for it, and you receive a phone number ID, a permanent access token and a webhook URL. The rest is yours.

Expect a receiver for incoming webhooks, a store for contacts and opt-ins, a queue for outbound sends, retry logic for failed deliveries and an inbox where agents reply. Signature checks trip people up. Budget a week for them.

Direct access suits a team that already runs a CRM or helpdesk and wants WhatsApp wired into it, or a firm that cannot let outsiders read chats.

A Business Solution Provider usually offers a shared inbox, broadcast tools, a no-code flow builder and ready connectors to CRMs such as HubSpot or Zoho. You log in on day one. Customers get answers that afternoon.

Costs differ between vendors. Meta charges for template conversations, and many providers add a monthly seat fee or a margin per message, so ask for the markup on its own line.

Check whether the console exports chats, contacts and template text, because a pretty dashboard with no export is a lock-in dressed up as a feature. See the export first.

At low volume a provider’s fee often costs less than a developer’s time, and a clinic sending appointment reminders to a few hundred patients rarely justifies a build.

At high volume the maths flips. A retailer sending dispatch alerts and invoice PDFs all day pays the markup on every message, while direct access turns that recurring cost into a build plus hosting.

A middle path works for many firms. Start with a provider that places the account in your portfolio, keep the template library and opt-in register in your own files, and stay ready to switch. Revisit the choice when the markup stings.

Ask three things, in writing. Who is admin of the Meta portfolio holding my number, can I get template text and the opt-in log in a spreadsheet, and what notice applies to a move?

A provider that answers cleanly is usually safe, while one that dodges the first question is telling you something about how an exit would go.

Print the answers, add the Meta rate card and your expected monthly sends, and set two quotes side by side on one page. Then decide.