International SMS Compliance: UK Long Codes and Turkey URL Block
UK carriers block international long codes for A2P SMS and require an approved RC bundle plus KYC on UK numbers. Turkey blocks all international A2P SMS containing URLs as of April 1, 2026, returning error 30007.
Two active rules affect international SMS sent through Sparkforge Phone or a connected Twilio account. Read the section that applies to where your recipients live and act on it before messages start failing.
United Kingdom: long codes blocked, RC bundle required
UK network operators began blocking international long codes for Application-to-Person (A2P) SMS on June 1, 2023. Long codes were originally Person-to-Person numbers, and carriers now treat A2P traffic from them as abuse.
In 2024, regulators added more requirements for UK long codes themselves:
- May 27, 2024. All new UK long codes require an approved Regulatory Compliance (RC) bundle before sending SMS or making calls.
- September 30, 2024. All UK long codes, new and existing, must have an approved RC bundle.
- KYC verification. You must provide business identity and use-case documentation.
- Full enforcement. By mid-2024, every UK carrier was blocking non-compliant traffic and unregistered UK long codes.
What to do for UK SMS
- Stop using non-UK long codes for UK recipients. Switch immediately.
- Pick a compliant sender type:
- UK Long Code (local number) with KYC and RC approval.
- Alphanumeric Sender ID for one-way branded messages.
- Short Code for high-volume or two-way traffic (12-16 weeks to provision).
- Submit your RC bundle in the Twilio Console with KYC documents.
- Audit your traffic. In Twilio Messaging Insights, filter
From Country ≠ UKandTo Country = UKto find non-compliant routes.
Buying a UK number in Twilio
- Go to Console → Develop → Phone Numbers → Buy a number.
- Set Country to UK.
- Uncheck Voice if you want SMS-only.
- Select an SMS-capable number and complete the RC bundle submission.
UK timeline
| 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 enforcement across all UK networks |
| Sept 30, 2024 | All UK long codes (new and existing) must be RC-approved |
Turkey: international SMS with URLs blocked April 1, 2026
Turkey's Bilgi Teknolojileri ve İletişim Kurumu (BTK) blocks 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.
The block applies to every message type, including order confirmations, shipping updates, appointment reminders, and one-time passcodes.
What to do for SMS to Turkey
- Remove every URL from templates and workflows targeting Turkish numbers. That covers full URLs, shortened URLs (bit.ly, hl.link, etc.), hyperlinked anchor text, and tracking links.
- Open your Sparkforge sub-account and edit affected SMS templates, workflows, and campaigns. Replace links with a phone number, email address, or plain instructions.
- Save and republish, then test delivery to a Turkish number with a URL-free message.
If you have a registered Turkey business entity
If your company is registered in Turkey and must keep sending URLs:
- Sign a direct contract with Posta Güvercini, a BTK-licensed local messaging platform.
- Authorize Posta Güvercini through the Turkish Message Management System (IYS).
- Contact Sparkforge Support to finalize routing.
Without a local entity, the only path is to remove URLs.
No action needed if
- You do not send SMS to Turkey, or
- Your messages to Turkish numbers contain no URLs or hyperlinks.
Frequently Asked Questions
Does the Turkey URL block apply to OTPs and transactional SMS?
Can I use a URL shortener to bypass the Turkey block?
What does error code 30007 mean?
Do these rules affect WhatsApp or email?
Do I need an RC bundle if I use Sparkforge Phone instead of my own Twilio account?
Was this article helpful?
Thanks for the feedback.