Rate this page:

Bring Your Own WhatsApp Sender


Bring your own WhatsApp Sender by March 1, 2024 to continue using Twilio Verify WhatsApp. This is to comply with policy changes from Meta and to improve your end-user experience.

What do you need to know?

A WhatsApp Sender is a phone number associated with a WhatsApp Business Account (WABA).

WhatsApp Sender

Currently, Twilio Verify sends all WhatsApp messages via WhatsApp Senders managed and owned by Twilio itself. However, we need to switch to a different model where customers need to create / manage their own WhatsApp Senders that Twilio Verify then uses to send WhatsApp messages. The deadline to create your own WhatsApp Sender(s) and configure it for Verify is March 1, 2024.

Several related changes will also happen as a result of this switch to using your WhatsApp Sender(s):

Your end-users will receive improved Authentication Template messages from your own brand that feature a Copy Code button and are pre-defined by Meta:

Existing Behavior
WhatsApp Sender Name: Verify

Message body: “legacy” authentication template

New Behavior
WhatsApp Sender Name: Customer Brand or Phone Number

Message body: Authentication template with Copy Code button

verify whatsapp existing behavior
verify whatsapp new behavior

PSD2 templates, such as “Use 123456 to approve your ACME transaction of $1.00 to John Doe” will no longer be supported (this is a rare use case).

A business that does not meet Meta’s commerce policy, such as cryptocurrency businesses, will not be able to create a WhatsApp Sender, and as a result won’t be able to continue sending WhatsApp messages via Twilio Verify.

Why is this happening?

These changes were initiated by Meta to safeguard their ecosystem as WhatsApp API traffic continues to grow and are being applied to all providers of WhatsApp messaging, not just Twilio Verify. Specifically, the requirement that OTPs be delivered by Authentication Templates and the requirement that a business must send from their own WABA and phone number in order to comply with the WhatsApp Business Messaging Policy.

Besides complying with Meta policy changes, there are two benefits to your end-users. The first is that Authentication Templates contain a Copy Code button for your users to easily copy/paste the OTP into your app. The second is that your OTP messages will now come from your own brand (instead of a generic “Verify”) creating a branded and consistent end-user experience with other WA messages you might be sending.

At the same time, we acknowledge that these are major changes to Verify WhatsApp behavior and may be unwelcome news. We have provided this feedback to Meta and have tried to make this transition the least disruptive as possible.

What do you need to do?

Please complete the steps below to bring your own WhatsApp Sender to Verify WhatsApp:

Estimated time: Creating a WhatsApp Sender should take you about 1 hour. Meta’s business verification process, however, may take an average of 1-2 weeks.

  1. Login to Twilio Console for the account used for Verify WhatsApp.
  2. Check if you already have an existing WhatsApp Sender by navigating to Messaging>Senders>WhatsApp Senders.
    1. A WhatsApp Sender is a special phone number associated with a WhatsApp Business Account (WABA) that is enabled to send WhatsApp messages.
    2. If you are ok with using this existing WhatsApp Sender for sending OTP messages, skip the next step. It’s best practice to send OTP messages from a different WhatsApp Sender than marketing messages that recipients may block.
  3. Create your own WABA and associate a phone number by following the steps in self-sign up with WhatsApp.
    1. If you are unable to create your own WhatsApp Sender due to a Meta commerce policy violation, switch to an alternative messaging channel like Verify SMS.
  4. Create or use an existing Messaging Service to assign your newly created Sender.
  5. Provide Twilio the Messaging Service SID, which starts with the letters “MG", that you want Verify WhatsApp to use by submitting this form.
  6. The Twilio Verify team will provide additional instructions for how Authentication Templates will be created and how to manage the Messaging Limits of your WhatsApp Senders.
  7. If you want to send PSD2 messages or any other message that does not fit the Authentication Template format, switch to Twilio’s Programmable Messaging API.

What if you don’t take action?

After March 1, 2024, Meta may block outgoing WhatsApp messages that don't come from your brand's sender. If WhatsApp messages are blocked, Twilio Verify will handle OTP message requests via WhatsApp on a best-effort basis by sending the message via SMS channel following the configurations in the same Verify Service, even if the SMS channel is disabled.

Rate this page:

Need some help?

We all do sometimes; code is hard. Get help now from our support team, or lean on the wisdom of the crowd by visiting Twilio's Stack Overflow Collective or browsing the Twilio tag on Stack Overflow.

Loading Code Sample...

        Thank you for your feedback!

        Please select the reason(s) for your feedback. The additional information you provide helps us improve our documentation:

        Sending your feedback...
        🎉 Thank you for your feedback!
        Something went wrong. Please try again.

        Thanks for your feedback!