Verify: send your verification codes in your own email template
Verify can now send the one-time passcode in an email you designed. Build the email in Email Templates, publish it, and choose it as the body of your custom email sender. Your users get your layout, wording, and languages; Verify keeps checking codes, attempts, and expiry exactly as before. The guide Your own verification email walks through the setup, with the rules the template must meet and how to troubleshoot a refused save.
Get started
- Your own verification email: design the template, pin it to your sender, and check what your user receives
- Senders and branding: the Bird-managed and custom senders for every Verify channel
What's new
- Your template, your domain: pick a published transactional template under Email when you set up a custom sender on Verify › Configure › Channels, or for a single country in Destinations. Templates only send from an address on your own verified domain; the Bird Verify and Authifly senders keep Bird's built-in email.
- Two variables: show the passcode with
{{ code }}and the minutes it stays valid at send time with{{ expires_in_minutes }}. Add up to 25 languages; the template's default language is the fallback. - Checked when you save and when you send: every published language must show the code in the body, outside the subject and outside any link. A template that stops meeting the rules after a republish fails that email instead of sending a code-less message, and a pinned template cannot be deleted.
- Safe in your logs: the Verify log and message details keep the code masked, as they do for Bird's built-in email.
Ready to try it? Start with Your own verification email.
Related resources
Continue with the documentation, guides and examples for this topic.
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