Spain is now blocking unregistered branded SMS and RCS sender IDs

The deadline is no longer future tense

Klaviyo's guidance says Spain's telecommunications regulator, the CNMC, requires businesses sending SMS or RCS to Spanish phone numbers with an alphanumeric branded sender ID to register that sender identity in the national registry. Starting September 15, 2026, unregistered sender IDs are blocked by Spanish carriers.

Klaviyo says the rule applies regardless of where the sending business is based. Numeric sender IDs such as short codes and long codes are outside the scope described in the guidance. SMS and RCS registrations are separate even when the same brand name is used for both channels.

Sources: Klaviyo Spain sender-ID registration guidance

Make registration status part of release control

A lifecycle team should not rely on a spreadsheet note that registration was submitted. For every Spanish sending identity, record the channel, exact sender ID, legal entity, submission path, submission date, CNMC status, confirmation owner and the platform state that determines whether traffic is allowed. Klaviyo describes states including not submitted, pending, active and rejected for branded SMS sender IDs.

The operating control should run before audience activation. If the sender is not active, the campaign or flow should stop, switch to an approved alternative channel where appropriate, or enter an exception queue. The fallback must preserve consent, suppression and message-purpose rules rather than treating email, push or another SMS identity as interchangeable.

Check channel and identity scope

Registration is not a brand-wide blanket approval. Klaviyo says SMS and RCS sender IDs require separate registrations. Teams with several sender identities should maintain one record per sender and channel, including exact spelling. That becomes especially important when regional workspaces or business units reuse similar brand names.

Klaviyo also notes that customers can register directly with the CNMC or submit through Klaviyo, with different process ownership. Whichever route was used, the internal release record should identify who can verify approval and who owns escalation if the registration is rejected or still pending.

• List every alphanumeric sender used for +34 recipients.
• Record SMS and RCS registrations separately.
• Require an active registration before launching a Spanish send.
• Test the platform behavior for pending, rejected and missing registrations.
• Keep consent and suppression checks independent from sender registration.

What to review this week

Pull the last seven days of Spanish messaging attempts by sender identity and channel. Reconcile delivered, blocked, paused and retried traffic with registration status. Investigate any campaign or flow that expected Spanish delivery after September 15 while the sender was not active.

Then make the control durable: add sender-registration status to the launch checklist, assign a renewal or regulatory review owner, and document the approved fallback. The regulation is external, but the failure mode is operational: a campaign can look healthy in planning while an entire market is unable to receive it.

Registration status now belongs in lifecycle release control

Because the September 15 enforcement date is now in effect, a sender-registration field should be treated like any other launch prerequisite for Spanish SMS or RCS. Keep the exact sender string, channel, registration route, submitted date, current status, evidence link and owner in one operating record. Klaviyo’s guidance says SMS and RCS are registered separately, so a brand using the same visible name in both channels still needs distinct channel-level status rather than one generic approved flag.

A lifecycle team should also separate regulatory delivery readiness from consent and audience eligibility. A registered sender does not replace opt-in, suppression, frequency or content controls, and a consented recipient does not make an unregistered sender deliverable. The pre-send gate should evaluate those conditions independently so a campaign cannot be marked ready merely because one side of the control passed.

For existing programs, audit Spanish traffic around the enforcement boundary instead of waiting for campaign owners to report a drop. Group attempts by sender identity and channel, then reconcile delivered, blocked, pending and retried activity with the registration record. If the workflow uses a fallback sender or channel, document when that fallback is permitted and how customer preference is preserved. That turns a carrier block into a visible operating exception rather than an unexplained decline in messaging performance.

Make sender registration a deployable control

The practical control is a market-and-channel readiness table that can be checked before a campaign or flow is enabled. For Spain, record the sender identity exactly as configured, whether it is SMS or RCS, the registration status, evidence link, owner and last verification date. A lifecycle release should fail closed when a required sender is not active instead of relying on a campaign owner to remember a regulatory deadline.

After enforcement begins, keep delivery diagnostics separate from audience diagnostics. A drop in delivered messages can come from registration, consent, suppression, invalid numbers, routing or other causes. Reconcile provider status codes and sender identity first, then evaluate audience behavior. That distinction prevents teams from treating a blocked sender as weak engagement or changing segmentation when the actual failure is infrastructure readiness.