Changelog · back to all
WhatsApp is now a Verify channel
feature
You can now deliver one-time passcodes over WhatsApp, alongside SMS and email. WhatsApp OTPs are sent from the shared Bird Verify sender using the built-in authentication template, so there's no template or sender setup required. Support for your own dedicated senders is following shortly.
What's new
- Enable WhatsApp per country from the Verify → Countries settings in the dashboard.
- Automatic failover: if the primary channel can't deliver, Verify falls back through your configured channels before giving up.
- API & SDK:
whatsappis now a valid value for a verification'schannel, and country routes accept awhatsappkey in their per-channel settings. This is additive, with no breaking change.
Default routing change
Existing phone verifications now default to SMS → WhatsApp → email: SMS stays primary, with WhatsApp as an automatic fallback before email. Countries you've already customized are left untouched.
Related resources
Continue with the documentation, guides and examples for this topic. Resources are in English.
Explore the capabilityCustomer verificationImplementation guideVerify your first customerWatch the guideVerify phone numbers at signupUnderstand the conceptWhat does OTP mean? One-time passwords explained
Try the practice and get an implementation brief