A company expanding its notifications into another country needs more than translated text. The new destination can change the sender, permission, price and timing requirements for that same message.
Why does the price vary by country?
Different destination networks and sending paths have different published rates and applicable fees.
Use the destination's rate rather than estimating from geographic distance. A neighboring country does not necessarily share the rate you already use.
The SMS pricing pages and destination pages publish the available rates. Preserve the quoted currency when comparing them, so a converted estimate does not appear to be Bird's price.
Include the message's segment count and any applicable carrier fees. Registration costs belong separately in the budget because they are not charges for one delivered message.
Which sending rules can change at the border?
Sender availability, registration, consent and timing requirements can differ between destinations.
A country may support the sender type you use elsewhere but require its registration first. Another destination may require a different sender type.
Permission also depends on the message and recipient's applicable rules. Do not assume a translated promotion falls within permission collected for service updates.
Use the destination's guidance alongside consent models, sender types and quiet hours. Those decisions determine which recipients can receive the planned message.
How do I enable a destination in Bird?
You turn on the country for your workspace separately from registering the sender.
A disabled destination returns E12020. Approval for a sender does not override that workspace setting.
The destination-settings guide explains the control. Enable the markets your application needs rather than treating every available country as a sending destination.
For a configured sender, its requirements response includes destination_enabled. Check that field alongside its registration status so the two controls do not get confused.
How do I check the sender for each country?
Read the sender's requirements for that destination before sending.
bird sms senders requirements <sender-id> --country-code NLReplace NL with the destination's country code. The requirements command reports the registration program, status and next actions.
A sender approved for one destination can still need work in another. Keep that country-specific status in your release decision instead of treating registration as one account-wide flag.
How should I manage a multi-country campaign?
Group the work by destination.
Apply each group's requirements before sending it.
Inspect each group's results separately.
Localize the content before counting segments. Translated wording and inserted names can change the billable size, even when the message's purpose stays the same.
Plan submission and delivery capacity separately. Bulk SMS explains batch acceptance and per-message outcomes.
Compare failures and costs by destination after sending. A healthy campaign-wide delivery rate can hide a problem affecting only one market.
In short
Plan each destination separately.
A sender or consent process that works in one country does not establish permission in another.
Use the published price for the route.
Include applicable carrier and registration fees rather than copying one country's rate across the list.
Enable the destination in Bird.
A sender registration does not turn on the separate workspace destination setting.
Compare delivery outcomes by destination.
A campaign-wide total can hide a failing route within an otherwise successful send.