What’s new. What’s next for you.

Get and list available numbers can now return ownership_address_area_name (for example Amsterdam) for a local number whose ownership_address_scope is number_area, meaning its ownership paperwork needs a business address inside the number's own area. The field names the area when it is known and is omitted otherwise. The buying numbers guide also now states that a number carrying ownership_address_scope is removed if its paperwork isn't approved by the registration deadline, with any setup fee credited back but its first recurring charge not refunded.

Also in this release:

• WhatsApp and Apple Messages for Business conversation labels match in any casing. Updating a conversation's labels, or filtering conversations by label, now matches your workspace's labels regardless of case, and responses return the workspace's spelling. Updating with a name your workspace doesn't have creates a new workspace label (up to 100 per workspace), unless it uses a reserved name, which now also includes archive, blocked, outbox, scheduled, and sent; labels your workspace already has keep working. Filtering by a name your workspace doesn't have matches nothing. See update a WhatsApp conversation and update an Apple Messages for Business conversation.
• 10DLC brand registration now requires your website and sign-in email to share a domain. Submitting or resubmitting a brand needs a live website whose main domain matches the domain of the email address you sign in with; an address on a subdomain or a free email provider is refused. See Register a 10DLC brand.

Labels on conversations now come from one list per workspace, shared by email mailboxes, Apple Messages for Business and WhatsApp in the dashboard. Open a conversation's labels to search the workspace's list, apply a label, or create a new one from what you typed.

• One spelling per label. Labels match in any casing, so "Urgent" and "urgent" are the same label, and every conversation shows the workspace's spelling.
• Reuse instead of retyping. The picker lists the labels your team already uses, so a conversation gets "billing" rather than a near-duplicate.
• Up to 100 labels. A workspace holds up to 100 labels. At the limit, you can still apply the labels it has. To create a new one, delete labels you no longer need under Workspace settings > Labels. Removing a label from a conversation keeps it in the workspace's list.

A guided integration for Auth0 is now available. It walks through using Bird as Auth0's Custom Phone Provider, with screenshots of each step in Auth0 and Bird and the provider code to paste.

Auth0 generates and checks each sign-in code, and Bird Verify delivers it by SMS or voice call for MFA, and by SMS for passwordless login. If your tenant also sends account notifications, such as blocked-account, password-change and password-breach messages, they go out through Bird SMS with the text from your Auth0 templates. Setup needs a Bird API key stored as an Auth0 secret, plus an SMS sender for account notifications, and no OAuth client.

Set up Auth0 with Bird.

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.

Sending most WhatsApp templates no longer requires building the components array by hand. POST /v1/whatsapp/messages now accepts a template.parameters object keyed by each variable's name (or position, for a numbered placeholder), plus fixed keys for a media header, a location header, a button URL suffix, or an authentication code. The template version's variables array lists the keys the template takes and which are required, so you can build the object from the API response instead of guessing.

A template language can also define parameter bindings: Liquid that computes a value from the parameters you send, set with PUT a template language. A binding can read a recipient's contact record, which isn't possible for a single send, so a language with contact-reading bindings returns 422 on create-whatsapp-message and instead resolves per recipient in a broadcast. A template with parameter bindings, or with named variables in a carousel card or a button URL, accepts only parameters; sending it with components is rejected. See Components and parameters for the full key reference.

Also in this release:

• 10DLC brand registration now fills in your support email automatically. The support email on a brand is the address you sign in with, and it can't be edited; free providers like Gmail aren't accepted, so sign in with an address on your business domain before registering. See 10DLC registration.