01Who this is for
- Marketing agencies that send client campaigns to the UK and Turkey need to ensure sender eligibility and content compliance.
- Ecommerce businesses that deliver order confirmations and OTPs internationally must avoid blocked routes and prohibited links.
- Fintech startups using SMS for authentication must meet UK KYC requirements and remove URLs from Turkish messages.
02International SMS compliance, explained
International SMS compliance defines the country specific rules for Application to Person messaging. In the United Kingdom, carriers only accept messages sent from registered UK long codes, alphanumeric IDs, or short codes that have an approved regulatory bundle. HighLevel stores the required KYC data and bundle linkage in the Regulatory Bundle / Address tool under the Phone System settings.
Turkey introduced a rule on 1 April 2026 that blocks any international A2P SMS containing a URL, a shortened link, or a tracking link, regardless of message purpose. Users must edit templates, workflows, and dynamic values to remove URLs and comply. Errors returned by carriers (21612 for unsupported US to UK routes, 30007 for generic filtering) help identify compliance failures.
All configuration lives inside the HighLevel platform for LC Phone managed numbers, while Twilio connected accounts handle registration directly in the Twilio Console.
03How businesses use international SMS compliance
- Ecommerce retailer. The retailer creates a UK long code in LC Phone, opens Settings > Phone System, submits the required KYC data in the Regulatory Bundle / Address, and links the approved bundle to the number. This lets the store send order updates to UK customers without triggering error 21612.
- Fintech company. The fintech firm uses a connected Twilio account to purchase a UK sender, completes the UK Regulatory Compliance bundle in the Twilio Console, and monitors any failed messages. This ensures OTPs reach UK users while staying compliant.
- Digital marketing agency. The agency reviews all SMS templates that target Turkish recipients, removes any URLs, shortened links, or tracking parameters, and then tests the messages. By doing so, the agency avoids error 30007 caused by Turkey’s URL restriction.
04The numbers and rules that matter
- June 1 2023, UK carriers began blocking international long code A2P traffic.
- May 27 2024, New UK long code purchases require an approved Regulatory Compliance bundle.
- July 30 2024, Full carrier enforcement for international long code traffic was established across UK networks.
- September 30 2024, All new and existing UK long codes must be connected to an approved UK Regulatory Compliance bundle.
- Effective April 1 2026, Turkey blocks international A2P SMS containing URLs, shortened URLs, tracking links or any internet address.
- Error 21612, Returned when a US number tries to send SMS to a UK recipient.
- Error 30007, General carrier filtering error that can indicate a blocked URL for Turkey but may have other causes.
05Before you start
- A UK phone number must be either managed by LC Phone or belong to a connected Twilio account.
- You need access to Settings > Phone System in HighLevel.
06How to set up and use international SMS compliance in HighLevel
Register a UK number managed by LC Phone
- Navigate to Settings > Phone System.
- Select the Regulatory Bundle / Address option.
- Create a new UK regulatory bundle or open an existing one.
- Enter the required KYC details and upload any requested documents.
- Submit the bundle for review by the regulator.
- Link the approved bundle to the UK long code you intend to use.
Register a UK number with a connected Twilio account
- Log in to the Twilio Console.
- Create and submit the UK Regulatory Compliance bundle within Twilio.
- Provide all mandatory KYC information and supporting documentation.
- Purchase or configure a UK sender that meets the compliance criteria.
- Watch for failed messages and adjust any non compliant routes as needed.
07What it looks like in HighLevel
08Settings that matter
- Regulatory Bundle / Address. Controls the collection of UK KYC data, the upload of verification documents, and the association of an approved compliance bundle with a HighLevel managed UK long code.
09Things to know before you rely on it
- UK carriers only accept messages from UK registered long codes, alphanumeric IDs, or short codes; US to UK routes are blocked and may return error 21612.
- All UK long codes, new and existing, must be linked to an approved UK Regulatory Compliance bundle.
- Turkey blocks any international A2P SMS that includes a full URL, shortened link, tracking link, or dynamic URL value as of 1 April 2026.
- Error 30007 signals carrier filtering but does not exclusively indicate a Turkish URL violation.
10If something goes wrong
- Error 21612 when sending to the UK. Verify that the message originates from an eligible UK sender rather than a US number and adjust the route accordingly.
- UK long code not delivering messages. Confirm the number type is eligible and that the UK KYC bundle has been approved and attached to the number.
- Error 30007 when sending to Turkey. Inspect the SMS content for any URLs, shortened links, tracking links, or dynamic fields that resolve to a URL and remove them.
11How it connects to the rest of HighLevel
- Configure sender type compliance and opt out handling SMS compliance settings
- Review common delivery errors and their meanings SMS delivery errors
- Follow best practices to avoid carrier filtering SMS deliverability guide
- Calculate outbound SMS costs for budgeting SMS cost estimator
Michael's take

International SMS compliance can feel like a minefield, especially when carrier rules change and suddenly block your messages. Skipping the required UK registration or slipping a link into a Turkish SMS will generate error codes that waste time and confuse your team.


