What being a Meta Tech Provider means, and why it matters

What does a Tech Provider actually do?

It runs the app that other businesses connect their WhatsApp numbers through.

When a business onboards, Meta's Embedded Signup opens and asks them to authorise an app. That app belongs to the Tech Provider, and once authorised it can act on the number on their behalf: read its status, send messages, manage templates, and set where webhooks are delivered. Everything a provider offers is built on that relationship.

The status is what makes it legitimate. Meta grants it to a company with its own app on a verified Business Manager, after App Review, and it is what separates a provider from a script holding somebody's credentials.

Why does it matter who owns the app?

Because it decides whose account your client's number ends up attached to.

Tooling built on somebody else's provider account inherits that account's constraints. This is where the single connection limits come from that people hit with general purpose automation platforms: the platform holds one provider relationship and everybody using it shares it.

With our own app the connection is made directly between the client's Business Portfolio and Meta. The number stays theirs, there is no reseller holding it, and adding the next one is the same operation as the first. For an agency that is not a technical detail, it is the answer when a client asks who controls their number.

What does the status require?

A verified Business Manager, an app that passes App Review, and recorded demonstrations of the flows.

Business verification ties the app to a real legal entity, with documents Meta checks against registries. App Review examines what the app requests and why, and for WhatsApp it includes recorded videos showing the onboarding actually working end to end. None of it costs money and all of it takes time, which is the part that cannot be compressed.

This is worth knowing if you are considering building your own. Connecting a single number you own needs none of it. Connecting numbers for clients needs all of it, and the waiting is measured in weeks rather than the work being measured in days.

What does it change for the business connecting a number?

Three things, and none of them are visible in the interface.

The number is connected in their own Business Portfolio, so the relationship with Meta is theirs. Meta bills conversation charges directly to their WhatsApp Business Account, which is also why nobody in the middle can mark those up. And there is no ceiling on how many numbers one account can hold, because there is no shared provider relationship being divided.

What it does not change is the onboarding itself. Embedded Signup is Meta's own flow, the popup is Meta's, and the code scan happens in the WhatsApp Business app. A Tech Provider does not replace any of that, it is what makes it available.

Common mistakes

• Assuming every provider has its own Tech Provider status. Many are built on somebody else's, which is where connection limits come from.
• Planning to obtain it on a deadline. App Review timing is not something a company can control.
• Treating it as a badge. It is an account relationship, and it decides whose portfolio holds the client's number.

Frequently asked questions

Keep reading