Part of Bird SMS. Check sender eligibility, registration lead times, and local rules across every market you serve.
- What you can send
- SMSWhatsApp
- Two-way messaging
- Not available
- Policy last updated
- July 13, 2026
Sender types
Compare the sender types listed for this destination, their registration requirements and recorded setup estimates. Confirm availability, throughput and timing for your use case.
| Sender | Activation | Setup time | Sender ID | Notes |
|---|---|---|---|---|
| Alphanumeric Sender ID | ActivationOptional registration | Setup time~14 business days | Sender IDThe sender ID is overwritten with a random number until registration is approved, then the approved sender ID is preserved. | NotesOne-way only. |
| Long code (phone number) | ActivationNo registration required | Setup timeNo approval wait | Sender IDThe submitted sender ID is preserved. | NotesSupports two-way replies. |
Rules & regulations
Use this recorded country reference to prepare your launch. Requirements can depend on message purpose, sender type, network and recipient location; confirm the applicable rules before sending.
All alphanumeric Sender IDs must be registered in RTR's public Sender ID register. Since 1 October 2026, messages with unregistered alphanumeric Sender IDs are blocked by Austrian operators. Each Sender ID must clearly identify the sending business and be supported by a justification (e.g. company name or trademark). RTR review takes up to 14 days, during which the Sender ID may be delivered as "Unknown".
Regulator
RTR
Consent
Opt-in required
Template approval
Not required
Quiet hours
No window recorded
What this market refuses
Sender IDs must be 1–11 characters and contain at least one letter. Only A–Z, a–z, 0–9, spaces and the characters + - & _ are permitted. Umlauts (ä, ö, ü), ß, accented letters and all other special characters (e.g. . ! @ ' /) are not allowed, nor are leading or trailing spaces. Generic names (e.g. Restaurant, Reminder, Shop, Alert) are not permitted unless backed by a registered trademark. Marketing messages require prior opt-in consent and must include an opt-out option.
Restricted content
Politicalreligiousgambling and bettingadult and unsolicited promotional contentOne API
Launch in new markets without changing your code
Send to every country from the same SMS API endpoint. Register or provision an eligible local sender, enable the destination country on your workspace allowlist so traffic can only reach approved markets, and track real-time carrier delivery receipts through signed webhooks.
Sending to Austria, answered
Common questions about sender registration, two-way replies, and compliance when launching SMS in Austria.
Do I need to register a sender before sending SMS to Austria?
Can I use an alphanumeric sender ID in Austria?
How long does sender registration take in Austria?
Can I receive replies from Austria?
Are there quiet hours for SMS in Austria?
What content is restricted in Austria?
Do I need consent before messaging someone in Austria?
What other channels can Bird reach Austria on?
The rest of the SMS platform
Provision compliant senders, lock down workspace destinations, and deliver SMS across global mobile networks from one API.
- Sender-ID registrationRegister branded alphanumeric sender IDs and phone numbers ahead of launch in countries that require carrier approval.
- RoutingProtect your budget with default-deny destination allowlists, upfront sender checks, and real-time carrier delivery receipts.
- NumbersProvision local long codes, verified toll-free numbers, short codes, and branded alphanumeric sender IDs for your markets.
- SendingSend OTPs, transactional alerts, and bulk notifications with automatic segment inspection and idempotent retries.
- Two-wayReceive customer SMS replies on the same phone number via HMAC-signed webhooks for support and confirmations.
- All destinationsCompare sender rules, registration lead times, two-way support, and consent requirements across every country Bird reaches.
Scale without losing control.
Organize teams in workspaces, control API access, and trace changes through audit logs.