Global SMS sending: countries, senders, and regulations

Sending SMS worldwide is complex because each country has its own mix of allowed senders, required registrations, and delivery policies. At a glance:

  • Sender types you’ll encounter: long codes (standard numbers, often require A2P-style registration), short codes (highest throughput; usually application-based, country-specific), and alphanumeric IDs (brand-style, one-way in many EMEA/APAC markets; often pre-registration; not supported for US/Canada P2P).
  • What varies by country: what must be registered (brand, sender ID, campaign/templates), which sender types are permitted per use-case, throughput and filtering policies, and consent/quiet hours/content rules.
  • Lead times and changes: registrations can take from hours to weeks, and regulations evolve.

Per-country requirements

Wherever you need to send, we handle the country-specific compliance and registrations end‑to‑end so you don’t have to learn each carrier or regulator’s rules.

  • Per‑country compliance handling: We manage the required registrations (brand, sender ID, campaign, and where applicable templates) based on local rules.
  • Country‑specific sender provisioning: We choose and provision the right sender type per destination (long code, short code, or alphanumeric) for trust and throughput.
  • Template and policy alignment: We preflight content, consent language (HELP/STOP), and quiet‑hour considerations to minimize filtering.
  • Delivery optimization and monitoring: Built‑in delivery, retries, logs, and analytics to track performance and resolve issues quickly.
  • Transparent costs and support: No hidden compliance fees; responsive support to help you unblock quickly.

United States: A2P 10DLC

A2P 10DLC is the US carrier program for application-to-person SMS sent from standard 10-digit long codes. Carriers require businesses to register their brand and campaign to reduce spam and improve deliverability.

  • Required for production: Registration is mandatory to send SMS to US numbers in production.
  • Allowed for testing: You may send low-volume test messages without registration; expect limited throughput and higher filtering risk.
  • Benefits: Better deliverability and throughput, fewer carrier blocks.

How registration works with NotificationAPI

  1. In the dashboard, go to Settings -> Plan -> Upgrade to begin A2P 10DLC registration.
  2. Complete the guided form, our team will contact you and handle the rest. We request your brand and business details (legal name, tax ID/EIN) and website information. Along the way, we provide guidance on any updates you may need to make to your website, notification templates, or related policies so everything meets carrier compliance requirements.
  3. We submit to carriers, track approval, and provision a compliant number. You can focus on sending SMS.
INFO

You must have a US EIN (Employer Identification Number) to complete A2P 10DLC registration.

Sender phone numbers

Free Accounts

  • Shared numbers: Free users send using one of NotificationAPI’s shared numbers (numbers may vary).
  • Suitable for: Testing and low-volume use

Enterprise & Paid Accounts

  • Dedicated numbers: Your own phone number
  • Available types:
    • Short code: 5–6 digit SMS number assigned by carriers.
    • Long code: Standard 10‑digit phone number (US 10DLC).
    • Alphanumeric sender: Text‑based sender ID (letters/numbers) shown instead of a phone number.

Availability and the most suitable option vary by country; NotificationAPI provisions the appropriate sender type per destination.

INFO

You don’t need a third-party service like Twilio. NotificationAPI manages all telecom infrastructure, including regulatory compliance and delivery monitoring.

FAQ

Do I need A2P 10DLC to send SMS in the US?

Yes, for production traffic to US numbers you must register for A2P 10DLC. Limited testing without registration is possible but may be filtered and has lower throughput.

What information do I need for A2P 10DLC registration?

Your legal business details (name, address), website with Terms and Privacy, use case and sample messages, consent/opt‑in method, and a US EIN (Employer Identification Number) are mandatory. We will guide you through the rest.

How long does A2P 10DLC approval take?

Typically a few business days, but timelines vary by country, carrier and use case.

Which sender types can I use in the US?

US SMS supports long codes (10DLC) and short codes. Alphanumeric sender IDs are not supported for US SMS.

Can I use my existing phone number?

In many cases we can provision compliant numbers for you. Bring‑your‑own numbers may be possible depending on carrier and compliance status, contact support.

Do I need to implement HELP/STOP keywords?

Yes. US programs require HELP/STOP handling and clear opt‑out language. NotificationAPI supports these requirements.

Do I need a provider like Twilio?

No. NotificationAPI manages telecom infrastructure, compliance, provisioning, and delivery monitoring for you.