Pre-register your brand name so international texts deliver.
Deliver verification codes, order alerts, and notifications with your company name at the top of the message instead of an unfamiliar phone number. In countries where carriers block or overwrite unregistered alphanumeric sender IDs, Bird shows you the local rules, submits your registration, and exposes approval status in the dashboard and API before you launch.
FIELDNOTES
Alphanumeric
Create the brand sender in the workspace.
Country requirements
| Status | Country | Category | |
|---|---|---|---|
Approved | India | Transactional | |
Approved | Singapore | Transactional | |
Not required | Germany | All categories | |
Not required | Netherlands | All categories | |
Registration optional | United Kingdom | All categories |
Ready to send · India
Approved, and the destination is enabled.
FIELDNOTES
Alphanumeric
Create the brand sender in the workspace.
Country requirements
| Status | Country |
|---|---|
Approved | India |
Approved | Singapore |
Not required | Germany |
Not required | Netherlands |
Registration optional | United Kingdom |
Ready to send · India
Approved, and the destination is enabled.
FIELDNOTES
Alphanumeric
Create the brand sender in the workspace.
Country requirements
| Status | Country |
|---|---|
Approved | India |
Approved | Singapore |
Not required | Germany |
Not required | Netherlands |
Registration optional | United Kingdom |
Ready to send · India
Approved, and the destination is enabled.
Why do some countries require sender registration?
Carriers and national regulators in many markets require businesses to register alphanumeric sender IDs in advance to stop brand impersonation and phishing. If you send to those countries without an approved registration, mobile networks either drop the text or replace your brand name with a generic number. As part of SMS compliance on the Bird SMS API, Bird manages these country-level filings in one place so your messages arrive under the name your customers recognize.
Launch a branded sender in new markets.
See local carrier rules, submit your registration details in one place, and confirm approval before you send.
- 01
See which countries require pre-registration.
Claim your brand string once in your workspace and immediately see how each destination handles it. Bird shows whether a country requires pre-registration, supports dynamic alphanumeric senders right away, offers optional registration to preserve your brand name, or requires a phone number instead.
- 02
Submit country registrations in one place.
Start a registration for a target country and message category, such as transactional or marketing traffic, right from the dashboard or CLI. When a local regulator or carrier program asks for business details or supporting forms, you complete them inside the same workflow and Bird files the submission.
- 03
Track carrier review and estimated timelines.
Follow each country registration as it moves from Bird review to carrier approval, complete with estimated business-day timelines where destinations publish them. If a registry requests corrections, Bird surfaces the rejection reason so you can update your details and resubmit.
- 04
Use the right compliance path for each sender type.
Country sender-ID registration covers branded alphanumeric names (3 to 11 characters) and international long-code registrations. For markets that do not support alphanumeric senders, such as the United States, Bird guides you through A2P 10DLC, toll-free verification, or short-code provisioning instead.
Verify a country is ready before you send traffic.
Approval in one country does not mean your sender is cleared for other destinations. Query your sender's country requirements over the API to confirm both that local carrier registration is approved (or not required) and that the destination country is enabled in your workspace allowlist before your application starts sending.
// The sender surface is not on the SDK yet, so read it over HTTP with a key
// carrying the sms_management:read scope.
const res = await fetch(
`https://eu1.platform.bird.com/v1/sms/senders/${senderId}/requirements`,
{ headers: { Authorization: `Bearer ${process.env.BIRD_API_KEY!}` } },
);
const { data: countries } = await res.json();
// Registration is decided per destination, so there is one row per country
// this sender can reach — never a single status for the sender itself.
const india = countries.find((c) => c.country_code === "IN");
// approved and not_required are the two statuses that satisfy a country.
// destination_enabled is a separate axis: a fully registered country still
// refuses the send while the workspace has it switched off.
if (india.status === "approved" && india.destination_enabled) {
// safe to send from this sender ID to India
}
Pair branded one-way alerts with two-way numbers where needed.
Pre-registration protects alphanumeric sender IDs so one-way texts like login codes, shipping updates, and appointment reminders arrive with your brand name instead of a random number. Because recipients cannot reply to an alphanumeric sender, you can use registered brand names for outbound notifications and pair them with local or toll-free numbers in markets where customers need to text back.
Questions about registration and sending
Is claiming a sender ID the same as registering it?
What should I check before sending?
How long does registration take?
Other compliance topics
Combine international sender registration with US carrier vetting and automated opt-out handling.
Scale without losing control.
Separate production and sandbox traffic into dedicated workspaces, scope API keys to the exact channels each service or agent needs, and track permission changes in the audit log.