International SMS Compliance: UK & Turkey Regulations

Modified on: Thu, 23 Jul, 2026 at 4:35 AM

SMS Compliance

Two active regulations affecting SMS senders on LC Phone or Twilio-connected accounts. If you message the UK or Turkey, act now.

Overview

This article covers two active international SMS compliance regulations that affect senders using the platform's LC Phone or Twilio-connected accounts.

United Kingdom — International long codes have been blocked for A2P SMS since June 2023. All UK long codes now require regulatory approval (RC bundle) and KYC verification.

Turkey — Effective April 1, 2026, all international A2P SMS containing URLs, hyperlinks, or shortened links are blocked by order of Turkey's BTK authority.

If you send SMS to recipients in either country, read the relevant section below and take action immediately.

Table of Contents

United Kingdom: International Long Codes Blocked

Turkey: SMS Containing URLs Now Blocked

Frequently Asked Questions

United Kingdom: International Long Codes Blocked + 2024 Compliance Requirements

If you send SMS messages to UK mobile numbers, your deliverability and compliance are at risk unless you update your sender types. Starting June 1, 2023, UK carriers began blocking international long codes for Application-to-Person (A2P) traffic. In 2024, further regulatory requirements were introduced for UK long codes themselves.

What Changed in 2023

Carrier Blocking of International Long Codes

From June 1, 2023, UK network operators started blocking SMS from non-UK long codes. These numbers were originally designed for Person-to-Person (P2P) use, but many businesses were using them for A2P traffic, which carriers now classify as abuse of P2P routes.

Impact: Any SMS sent to UK recipients from an international long code is likely to fail.

What changed in 2024. Twilio and UK regulators layered on stricter compliance requirements:

Requirement 1

Regulatory Compliance Bundles (RC Bundles)

From May 27, 2024, all new UK long codes require an approved RC bundle before they can send SMS or make calls.
From September 30, 2024, all UK long codes (new or existing) must have an approved RC bundle.

Requirement 2

Know Your Customer (KYC)

Businesses must provide documentation to verify their identity and intended use case before using UK long codes.

Requirement 3

Full Enforcement of Blocking

By mid-2024, all UK carriers had aligned to enforce these rules.
Traffic from international long codes is universally blocked.
Unregistered UK long codes will also fail.

What You Need to Do

Step 1

Stop Using International Long Codes

If you are still sending SMS from non-UK numbers to UK recipients, switch immediately.

Step 2

Use an Approved Sender Type

UK Long Code (Local Number) — Requires KYC and regulatory approval.
Alphanumeric Sender ID — For one-way traffic; brand your sender name (e.g., YourCompany).
Short Code — For higher-volume or two-way messaging; apply for a UK short code (12–16 weeks provisioning).

Step 3

Submit your Regulatory Compliance (RC) bundle in the Twilio Console.
Provide the necessary KYC documents (business name, address, use case, etc.).

Step 4

Monitor Message Logs

In Twilio Console, use Messaging Insights to filter "From Country ≠ UK" and "To Country = UK" to find non-compliant traffic.
Look for blocked or undelivered messages and update routing accordingly.

How to Buy a UK Number in Twilio

Go to: Console → Develop → Phone Numbers → Buy a number
Set Country = UK
Un-check Voice (if you want SMS-only)
Select an SMS-capable number and complete the RC bundle submission.

Buying an SMS-capable UK number in the Twilio Console

UK Timeline Recap

Date	Milestone
June 1, 2023	UK carriers begin blocking international long codes
May 27, 2024	New UK long codes require RC bundle approval
July 30, 2024	Full carrier enforcement across all UK networks
Sept 30, 2024	All UK long codes (new + existing) must have RC approval

UK Key Takeaways

International long codes cannot be used for UK SMS.
All UK long codes now require KYC and regulatory compliance.
Alphanumeric Sender IDs and short codes remain valid alternatives.
Act now to avoid message failures and regulatory issues.

Turkey: International SMS Containing URLs Now Blocked

Effective April 1, 2026

Turkey's Information and Communication Technologies Authority (BTK) has blocked all international A2P SMS containing URLs, hyperlinks, or shortened links sent to Turkish recipients. Blocked messages return error code 30007 and operators may issue fines.

What's Happening?

Turkish mobile operators are now blocking any international A2P SMS that contains internet addresses, URLs, hyperlinks, or shortened links. This is enforced by the Bilgi Teknolojileri ve İletişim Kurumu (BTK) — Turkey's national communications regulator.

Messages blocked under this regulation will:

Return error code 30007 (carrier-level filtering)
Fail to deliver to the recipient
Potentially result in fines from Turkish operators

Applies to Every Message Type

This applies to ALL SMS types — including order confirmations, shipping updates, appointment reminders, and one-time passcodes (OTPs).

What You Need to Do

Step 1

Immediately Remove All URLs from Messages Sent to Turkey

Remove the following from any SMS template or workflow targeting Turkish recipients:

Full URLs (e.g., https://example.com/order/123)
Shortened URLs (e.g., bit.ly/abc, hl.link/xyz)
Hyperlinked or anchor text pointing to any URL
Tracking links embedded in messages

Step 2

Update Your Templates and Workflows

Go to your platform sub-account.
Open any SMS templates, workflows, or campaigns targeting Turkish recipients.
Remove or replace all URLs. Use a phone number, email, or plain-text instructions instead.
Save and republish affected templates or workflows.
Test delivery by sending a URL-free message to a Turkish number.

If You Have a Local Turkey Business Entity

If your business is registered in Turkey and must continue sending URLs via SMS, you need a compliant local messaging pathway:

Secure a direct contract with Posta Güvercini, a BTK-licensed local messaging platform.
Authorize Posta Güvercini as your service provider via the Turkish Message Management System (IYS).
Contact Support to finalize the technical setup and routing.

Good to Know

This pathway requires a formal business registration in Turkey and a direct contract with Posta Güvercini. Without a local entity, you must remove all URLs from your messages.

No Action Needed If…

You are not sending SMS to Turkey, OR
Your messages to Turkish recipients contain no URLs or hyperlinks.

Turkey Timeline Recap

Date	Milestone
April 1, 2026	BTK regulation takes effect — all international SMS with URLs blocked
Ongoing	Turkish operators enforce error code 30007 and may issue fines

Turkey Key Takeaways

All international A2P SMS containing URLs are blocked in Turkey as of April 1, 2026.
Affected messages return error code 30007.
Remove all URLs, shortened links, and hyperlinks from templates targeting Turkish recipients.
A local Turkey entity + Posta Güvercini contract is the only approved pathway for URL-containing SMS.

Frequently Asked Questions

Q: Does the Turkey URL block affect OTPs and transactional messages?

Yes. The BTK regulation applies to all international A2P SMS regardless of message type, including one-time passcodes, order confirmations, and shipping notifications.

Q: Can I use a URL shortener to avoid the Turkey block?

No. Shortened URLs are explicitly included in the block. All forms of internet addresses — full URLs, short links, and hyperlinks — are blocked.

Q: What is error code 30007?

Error 30007 is a carrier-level filtering error indicating the message was blocked before delivery. For Turkey, it means the operator detected a URL in an international SMS. For the UK, it can also indicate the sender type is not approved for A2P traffic.

Q: Does the Turkey regulation affect WhatsApp or email?

No. This regulation applies specifically to international A2P SMS. WhatsApp, email, and other channels are not affected.

Q: Do I need an RC bundle for UK numbers on LC Phone?

Yes. If you are using LC Phone (not your own Twilio account), the platform handles the underlying carrier relationship, but you still need to ensure your phone number type is compliant. Contact Support if you are unsure about your UK number setup.

Q: How long does it take to get a UK short code?

UK short code provisioning typically takes 12–16 weeks. If you need to keep messaging UK recipients in the meantime, use a compliant UK long code (with an approved RC bundle) or an Alphanumeric Sender ID for one-way traffic.

Q: What documents do I need for KYC on a UK number?

You'll typically provide your registered business name, business address, and a description of your messaging use case as part of the Regulatory Compliance (RC) bundle submitted in the Twilio Console. Requirements can vary, so check the RC bundle prompts for the exact documentation.