Verify: choose which sender your passcodes arrive from

Verify's Bird-managed sender is now a named choice between two identities, set per channel and per country. Bird Verify puts the Bird name in front of your users. Authifly is a standalone verification brand that names no platform vendor, so nothing about your delivery infrastructure is visible to the person receiving the code.

The choice reaches every channel that has a sender. On email it decides the from-address and the branding in the body. On SMS it decides the alphanumeric sender ID, in the countries that permit one. On WhatsApp it decides which Bird-managed business number the message comes from. Telegram is unaffected: its codes come from Telegram's own verified account, which is not ours to brand.

What changed for existing configurations

Nothing, if you had already sent a passcode. Every configuration that existed before this release was pinned to Authifly, which is what it was already sending as, so no recipient sees a different sender than they did last week.

Two cases did move to Bird Verify, because they had no stored sender to keep: a workspace with no Verify configuration at all, and a send in a workspace with several configurations that did not name which one to use. If either describes you and you want Authifly, select it on the Channels tab.

Using it

Open the Channels tab and pick an identity on the Email, SMS, or WhatsApp row. To override it for one destination, set a sender on that country in country configuration. A per-country choice wins over the channel default for recipients there.

Full detail, including what each channel shows in countries that require a short code or a local number: Senders and branding.