Senders & branding
Every Verify code reaches your user as a real email or SMS, and this page shows exactly what arrives. Out of the box both channels send under Authifly, Bird's verification brand — a neutral, consistent identity operated by Bird B.V., with authifly.com reassuring recipients that Authifly delivers legitimate one-time codes on a business's behalf. You can brand the email sender with your own domain today; dedicated SMS senders are coming.
The senders live on the Configure page's Channels tab, one row per channel:
The email your user receives
On the shared sender, the code email arrives from Authifly OTP <otp@verify.authifly.com> with the subject "Your verification code". The body is a single card on a warm paper background: a "Verification · Authifly" eyebrow, the code set large in monospace type, the expiry line, and a disclaimer. The plain-text version reads:
Exemple de code
Your verification code is 482913.
It expires in 10 minutes. Don't share it with anyone — Authifly will never ask you for it.
If you didn't request this code, you can safely ignore this email.The expiry always reflects your configured code lifetime. OTP email carries no open or click tracking — there's nothing to click, and tracking pixels only hurt deliverability on transactional mail.
The SMS your user receives
The SMS leads with the code, where a glance (and the OS's code autofill) looks first:
Exemple de code
482913 is your verification code. It expires in 10 minutes. Do not share it.On the shared sender, delivery comes from Bird's managed sender pool — shown in the dashboard as Bird Shared Pool. The Authifly brand rides the sender ID, not the body: where a destination country permits branded alphanumeric sender IDs, the code arrives from Authifly; where a country requires a local number or short code, that shows instead. The message text stays brand-neutral so it reads the same wherever it lands.
Branded email sender
You can replace the shared email sender with an address on your own domain, so codes arrive from verify@yourdomain.com instead of otp@verify.authifly.com. The prerequisite is a verified sending domain in the same workspace — Verify won't send from a domain you haven't proven you own.
On the Channels tab, open the Email row's sender control, choose a local part (the part before the @) and one of your verified domains, and save. Use shared sender switches back at any time. You can also pin a different sender for a specific country in country configuration — a per-country choice wins over this default for recipients there.
Two things to know before you switch:
- Branding changes the sender, not the message. The subject and body keep the Authifly code layout shown above — message templates aren't customizable yet, and the copy is English-only today.
- The domain must stay verified. If the domain fails verification or is removed, sends from it fail, and delivery advances to the verification's next channel rather than silently reverting to the shared sender. Fix the domain or switch back to the shared sender.
SMS senders
SMS sends from the Bird shared pool only — the Channels tab shows the SMS row fixed to Bird Shared Pool, with no sender control. Registered, dedicated SMS senders (your own numbers and sender IDs carrying your verification traffic) are coming soon; until then, every SMS code is delivered under the shared Authifly identity described above.
Next steps
| Page | What it covers |
|---|---|
| Sending domains | Registering and verifying the domain a branded sender needs |
| Country configuration | Pinning senders and channel order per country |
| Sending verifications | The send and check calls and verification settings |