WhatsApp Tech Provider Program FAQ

You can use either a Twilio phone number or a non-Twilio phone number to register a WhatsApp sender.

• The phone number must meet the WhatsApp compatibility requirements.
• The phone number must not already be registered with WhatsApp. Learn how to check if a phone number is registered with WhatsApp and how to use an already registered phone number.
• If the phone number is non-Twilio, it must be able to receive SMS or voice calls.
  • If the phone number is registered with an Interactive Voice Response (IVR) system or a computer-operated phone system, you can't receive One-Time Passwords (OTPs).
  • If the phone number is only available for outbound messages or calls, you can't use it to register a WhatsApp sender because Meta can't deliver OTPs.

Pricing doesn't change. The Tech Provider Program is free. Meta bills Twilio, and you'll pay Meta and Twilio fees per Twilio's pricing or your contract. Meta doesn't bill ISVs directly.

After you verify your Meta Business Manager account and complete Access Verification, you can access Meta's Direct Support forum. Twilio can also assist with Meta escalations.

You'll agree to these terms as a Tech Provider:

• Tech Provider Terms
• Facebook Terms for WhatsApp Business
• Meta Hosting Terms for Cloud API
• Meta's government and political use restrictions

Make sure you review Meta's terms and policies yourself.

Try one of the following solutions:

• Use the same Meta Business Manager that you used for Self Sign-up.
• Create a Meta app, add the WhatsApp product, and submit business verification.

As an ISV, you can onboard up to 200 new customers in a rolling 7-day window after completing business verification, App Review, and Access Verification. Only new WhatsApp Business Platform customers count toward this limit.

In WhatsApp Manager, under Partner overview, check your current usage limit. Meta'll email you if you get close to the limit.

Meta's Embedded Signup flow works in most languages Meta apps support. It'll localize automatically based on the end client's Facebook language.

Meta standardizes the popup user flow for desktop and mobile browsers, but you can customize the experience before and after the flow.

Meta has two embedded login features: Facebook Login and Facebook Login for Business.

Use Facebook Login for Business for Embedded Signup. It lets you set access token type, assets, and permissions, so Tech Providers can't access info that's not needed for WhatsApp. Learn more about Facebook Login for Business.

If you only see Facebook Login in your Meta app, you'll need to create a new Meta app to switch to Facebook Login for Business.

Customers need to create a new WhatsApp Business Account (WABA) for Twilio. Then, they can enter the phone number like it's a new registration.

• Do not use any Meta logos or trademarks on your Meta app icon (e.g. "WA", "WhatsApp"). Learn more in the Meta's App Review - Best Practices guide..
• Privacy Policy link is invalid or only accessible to users in a certain region (i.e. "geofence").
• Ensure the "Facebook Login" button adheres to Meta's brand guidelines. See Meta's docs for additional tips.

See Migrate phone numbers and senders.

Use a different Business Manager than the one linked to your Meta app. If you need a new one for testing, use your company's name + "Test" and go through the same verification process.

Make sure the following:

• The business has completed verification if they want to onboard more than 2 numbers.
• The account isn't disabled. Check the WABA for alerts. Meta checks accounts in the background, and if the commerce policy isn't met yet, you'll get an email and a WABA notification.

Make sure you enabled OAuth login for your app.