Senders & branding

Every Verify code reaches your user as a real email, SMS, or WhatsApp message, and this page shows exactly what arrives. Out of the box every channel sends under Authifly, Bird's verification brand: a neutral, consistent identity operated by Bird, 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 and WhatsApp senders are on the roadmap.

The senders live on the Configure page's Channels tab, one row per channel:

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 carries the same three beats:

Your verification code is 123456.

followed by the expiry window with a warning never to share the code (Authifly never asks for it), and a closing line that the email is safe to ignore if the code wasn't requested.

The expiry line shows how long the code actually remains valid: the configured code lifetime on the first send, the verification's remaining window on a resend. OTP email carries no open or click tracking: there's nothing to click, and tracking pixels only hurt deliverability on transactional mail.

The SMS leads with the code, where a glance (and the OS's code autofill) looks first:

123456 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.

On WhatsApp the code arrives from the Bird-managed Bird Authifly business number as an authentication-template message. WhatsApp fixes the layout for authentication templates, so the body leads with the code and offers a one-tap Copy code button:

123456 is your verification code. For your security, do not share this code.

The code is the only variable, and the copy is fixed by WhatsApp's authentication-template format, so it reads the same in every country. Delivery is an ordinary WhatsApp template send, so the recipient needs WhatsApp on that number; where they don't, or the message can't be delivered, the verification advances to its next channel.

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:

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 on the roadmap; until then, every SMS code is delivered under the shared Authifly identity described above.

WhatsApp sends from the Bird-managed Bird Authifly business number for your workspace's region; like SMS, the channel has no sender control and shows Bird Shared Pool in the Channels tab. Dedicated WhatsApp senders (your own WhatsApp Business number carrying your verification traffic) are on the roadmap; until then every WhatsApp code is delivered under the shared Authifly identity.