Europe A2P SMS regulations

Austria tightens SMS sender IDs

This matters for product, SMS operations, and connectivity teams sending OTPs, billing alerts, delivery updates, and branded texts to Austrian mobile users because Austria is moving beyond simple filtering into registry-based sender authentication and routing controls. RTR activated a public alphanumeric sender ID directory on July 1, 2026. From October 1, only registered alphanumeric sender IDs may be delivered to Austrian end users, unlisted messages must be deleted, and alphanumeric SMS sent from abroad to Austrian recipients is prohibited.

Published:08/08/2026 Updated:08/08/2026

1. Regulatory focus

Austria has moved alphanumeric SMS control from policy language to a delivery rule set. Since July 1, 2026, companies must register alphanumeric sender IDs through an appointed mobile service provider in RTR’s public directory. From October 1, only listed sender IDs may be delivered to Austrian end users, and providers must pull the directory at least daily and verify authenticity before termination. Messages using unlisted IDs must be deleted. If an ID appears in the directory but the sender’s authenticity is still doubtful, the ID may be rewritten to Unknown and the message delivered. Most notably, alphanumeric SMS sent from abroad to Austrian customers is banned.

2. Business impact

The rules materially affect how cross-border teams serve Austria. Many brands currently depend on offshore aggregators, shared international routing, and a single branded sender ID across markets for OTP and notification traffic. After October, that model can fail before the message reaches the recipient network because unlisted IDs must be deleted. The legal framework also adds planning friction: a sender ID may only be used 14 days after registration, and one end user may register no more than 40 alphanumeric IDs within six months. That reduces flexibility for last-minute brand launches, frequent renaming, and multi-brand campaign structures.

3. Operating recommendations

Teams should carve Austria out of any generic European SMS routing design now. Start by mapping every alphanumeric sender ID used for Austrian traffic, the legal sender entity behind it, the aggregator chain, and the terminating operator path. Flag any flow that originates abroad, uses an unclear delegated sender, or relies on a brand name that does not clearly identify the holder. Prepare German-language registration justifications and make sure the directory contains the holder’s own contact and address details rather than reseller data. For OTP, billing, and delivery traffic, build fallback paths such as numeric sender routes or OTT channels, and assess whether to use RTR’s one-time Excel upload window before August 24.

Frequently Asked Questions

What happens if we keep sending branded OTP traffic to Austria through an offshore aggregator
The main risk is not slower delivery but non-delivery. RTR explicitly states that alphanumeric SMS sent from abroad to Austrian customers is prohibited, and from October 1 unlisted sender IDs must be deleted. If your current path cannot show registration and validation through a compliant participating provider serving Austria, you should redesign the route now and prepare a backup channel for critical OTP traffic.
Can an aggregator register the sender ID for us, and whose details must appear in the directory
A provider may handle the filing on your behalf, but the directory must reflect the actual holder, not the intermediary. RTR’s additional guidance says each registration must include the holder’s contact and address details, and the justification must be written in German. That explanation should show why the sender ID clearly identifies the holder, such as through a trademark, company name, or documented brand rights.
Why can messages still fail or display strangely even after the sender ID is registered
Three issues are common. First, Austrian law says a sender ID may only be used 14 days after registration, so early launch plans can fail. Second, even when an ID is listed, a provider may rewrite it to Unknown if it cannot confirm the message was actually sent by or for the holder. Third, generic IDs that do not clearly identify a specific holder are not permitted.
This article is for informational purposes only and does not constitute legal advice.

Related products

Need compliance guidance?

Contact us for guidance on target markets, message scenarios, and sending routes.

Get in Touch