Regulatory & Compliance Corner – October 2025
Time to read:
October 27, 2025
A recurring roundup of key telecom policy changes around the world.
We keep an eye on global changes so you don’t have to – and this month, we’ve got something special to kick things off:
Private Beta Spotlight: RCS Onboarding APIs
We’re thrilled to share that Twilio’s RCS Onboarding APIs for ISV are now in Private Beta, bringing a faster, more scalable way to onboard RCS messaging for all your customers.
These APIs make it easier to:
Register your brand and set up your RCS sender profile for Twilio RCS Business Messaging
Iteratively test your sender and message experience before going live.
Dynamically fetch and fulfill country-specific compliance requirements as you expand to new markets.
Seamlessly progress from testing to production with API-driven compliance and approval workflows.
Participation in the Private Beta requires approval and is currently limited to the U.S. and select countries in Europe.
If you’re interested in early access, reach out to your Twilio Account Executive to learn more and request inclusion.
There’s been plenty of activity across the telecom landscape these past two months. Here’s a quick look at what changed and what’s coming next:
Taiwan – Branding required in SMS content starting October 8, 2025
What’s happening
Taiwan’s National Communications Commission (NCC) now requires that all SMS messages sent to recipients in Taiwan clearly include a brand, organization, or campaign name at the start of the message body.
Correct: [MyBrand] Your verification code is 123456.
Also correct: MyBrand: Your verification code is 123456.
Incorrect: Your verification code is 123456.
Operators may begin blocking or flagging unbranded traffic as early as October 8, 2025, with full enforcement on November 1, 2025.
What it means for you
Submit your brand names for registration via Twilio’s form and update your SMS templates to include that approved branding before November 1, 2025.
For Twilio Verify/Authy users, we’ll automatically prepend [TWVerify] to OTP messages starting October 8 to keep traffic compliant. If you’d rather use your own brand name, submit it as soon as possible, as these are approved on a first-come-first-served basis.
Need-to-know links
Hungary – Caller ID enforcement for international calls (effective October 15, 2025)
What’s happening
Hungary’s telecom regulators have introduced new rules restricting the use of Hungarian phone numbers as Caller ID (CLI) on calls placed from outside the country.
Effective October 15, 2025, calls made to Hungary using fixed or geographic numbers (e.g., +36 1-9…) as CLI may be blocked by local carriers. This enforcement will expand to mobile numbers (e.g., +36 20, 30, 70…) beginning June 1, 2026.
Calls using Transit Caller ID or Verified Caller ID with a Hungarian CLI will continue to be delivered by Twilio on a best-effort basis.
What it means for you
To keep your calls to Hungary flowing without interruption:
Use Hungarian CLIs only when originating from Hungary. If you need a Hungarian CLI, you can purchase Hungarian numbers directly in the Twilio Console.
Avoid using Hungarian numbers (+36 1-9 or +36 20/30/70) as Caller ID for Transit Caller ID or Verified Caller ID calls into Hungary; these may be blocked by carriers.
If a Hungarian CLI isn’t required, switch to a non-Hungarian CLI, such as your main business or international service number. You can quickly purchase a U.S. (+1) number in the Twilio Console for this purpose.
Need-to-know links
Hungary – Update your Regulatory Compliance bundles after October 16, 2025
What’s happening
Effective October 16, 2025, all approved Hungary Local RC bundles will move to “Rejected” status to align with new carrier requirements. Existing numbers stay active, but new purchases require updated, re-approved bundles.
What it means for you
Businesses must now include:
Business registration proof
Business address and proof of address
Business registration number
Website or verified social media
Authorized representative contact details.
Individuals must provide ID, proof of address, and personal information (e.g., birth date, mother’s maiden name).
Need-to-know links
Bulgaria – Update your Regulatory Compliance bundles after October 16, 2025
What’s happening
Also effective 16, 2025, all approved Bulgaria Local RC bundles will move to “Rejected” status to help you resubmit the information listed below to align with updated requirements.
What it means for you
Updated bundle requirements include:
Unified Identification Code
Authorized representative details
Recent proof of address
For individuals: government ID and Unified Citizenship or Personal Identity Number.
Need-to-know links
Armenia – Register your Alphanumeric Sender IDs for OTP traffic
What’s happening
Armenia’s Public Services Regulatory Commission (PSRC) now requires registration of all Alphanumeric Sender IDs for SMS one-time passcodes (OTPs). Previously, Twilio could send OTPs using its own Sender IDs for unregistered senders, but that’s no longer always possible.
What it means for you
Register your Alphanumeric Sender ID using Twilio’s registration form to keep your OTP delivery uninterrupted. Each Sender ID must have its own Twilio Account SID, and registration takes about four weeks to process. If you’d prefer, you can also use Verify WhatsApp to send OTPs without registration.
Need-to-know links
United States – FCC expands “Voice Service Provider” definition (enforcement began September 18, 2025)
What’s happening
The FCC has expanded the definition of “Voice Service Provider” (VSP) for STIR/SHAKEN compliance. Businesses that place PSTN calls on behalf of others or control phone numbers may now fall under this classification.
Enforcement began September 18, 2025.
What it means for you
If you think this rule might apply to you, talk with your legal counsel to confirm whether your business qualifies as a VSP. If it does, you’ll need to meet new compliance responsibilities such as obtaining an SPC token, securing a STIR/SHAKEN certificate, and managing call attestation levels.
*Twilio is monitoring the change and can discuss feature options such as PASSPorT Pass-Through (for Elastic SIP Trunking) or BYOT (Bring Your Own Token) for Programmable Voice customers; your account team can help you explore alignment, though these do not substitute legal advice.
Need-to-know links
United States – SIP Code 603+ replaces 603/607/608 for analytics-based blocking
What’s happening
The FCC is standardizing how blocked calls are reported. The new 603+ “Network Blocked” code will replace legacy codes 603, 607, and 608 for calls blocked by analytics on IP-based networks. Carriers can adopt it now; it becomes mandatory March 25, 2026.
What it means for you
No changes needed unless your systems specifically look for 603, 607, or 608 codes, in that case, update them to recognize 603+.
Need-to-know links
Tanzania – Pre-register Sender IDs for OTP traffic
What’s happening
The Tanzania Communications Regulatory Authority (TCRA) now requires pre-registration of all Alphanumeric Sender IDs for SMS OTP messages. Unregistered senders can no longer rely on Twilio default IDs for delivery.
What it means for you
Complete the four-step registration via Twilio’s Alphanumeric Sender ID form using the TCRA-required documentation. Each Sender ID must map to its own Twilio Account SID.
Need-to-know links
Malaysia – Toll-Free bundles must have a local Malaysian address (effective November 11, 2025)
What’s happening
The Malaysian Communications and Multimedia Commission now requires a local Malaysian address for all Toll-Free RC bundles. Starting November 11, 2025, bundles without one will be rejected.
What it means for you
Existing numbers remain active, but you’ll need to update or recreate affected bundles before purchasing new Toll-Free numbers.
Need-to-know links
Italy – New rules for mobile Caller ID on international calls (starting November 19, 2025)
What’s happening
Italy’s regulator AGCOM will block internationally routed calls that display Italian mobile or geographic numbers as Caller ID starting November 19, 2025.
What it means for you
To avoid call blocking:
Stop using Italian mobile numbers for internationally routed calls.
Switch to an Italian geographic number (buy new or port existing ones to Twilio).
Need-to-know links
United States – Business Registration Numbers added to Toll-Free verification (required January 2026)
What’s happening
Twilio is adding new fields to the Toll-Free verification process for Business Registration Numbers (BRNs) (like an EIN for U.S. businesses or an equivalent number for organizations abroad). These became optional September 30, 2025, and will be required January 2026 to strengthen verification and reduce delays.
What it means for you
Start collecting valid EINs or BRNs now so you’re ready when the new fields become mandatory. U.S. businesses should provide a valid EIN that matches their legal name, while non-U.S. businesses should use their locally issued registration number and country of issuance.
Then, in Twilio Console go to → Messaging → Regulatory Compliance → Brands:
Find brands marked “2FA Required.”
Update your brand contact email, submit, and follow the Authentication+ verification email.
Unverified brands after the deadline will be unable to register or maintain campaigns.
Need-to-know links
France – Telemarketing calls move to explicit opt-in (starting August 11, 2026)
What’s happening
France is shifting from an opt-out to an opt-in model for general marketing calls. Starting August 11, 2026, businesses must have explicit, documented consent before calling consumers.
What it means for you
If you use Twilio’s voice services for marketing in France, this law may affect your operations. We recommend consulting your legal or regulatory advisors to determine how these rules apply to your business. Begin planning now to collect, store, and verify opt-in consent in line with GDPR, and ensure your permitted calling hours (weekdays 10 a.m.–1 p.m. and 2 p.m.–8 p.m.) stay compliant.
Need-to-know links
Taiwan – Updated KYC requirements for Toll-Free business numbers (starting December 9, 2025)
What’s happening
Starting December 9, 2025, new information requirements will apply for Taiwan Toll-Free business numbers to align with carrier compliance rules. Existing numbers will remain active, but beginning on this date, approved Taiwan Toll-Free bundles will be moved to “Rejected” status to allow for updates under the new policy. Any new Toll-Free purchases will require updated and approved Regulatory Compliance (RC) bundles.
What it means for you
Updated bundle requirements for Toll-Free business bundles now include:
Proof of Authorized Representative identity is no longer required.
An Authorized Representative email and phone number is now required.
A Business website is now required.
Need-to-know links
South Korea – Provider transition for Local and Toll-Free numbers (starting December 11, 2025)
What’s happening
Twilio is transitioning to a new provider for South Korea Local and Toll-Free numbers, and new documentation requirements will apply. Existing numbers will remain active, and you won’t need to re-qualify them immediately. However, starting December 11, 2025, approved South Korea Toll-Free bundles will be moved to “Rejected” status (Local bundles will not) to allow for updates under the new policy. New Toll-Free purchases will require updated and approved RC bundles.
What it means for you
Updated bundle requirements for Local and Toll-Free business bundles now include:
A document is no longer required for the Business Registration Number.
Either a Corporation Seal Verification Certificate or the CEO’s government-issued ID is required to establish Proof of Authority.
An Authorized Representative name and email is now required.
Need-to-know links
Stay secure, stay compliant, and, as always, keep building!
– Team Twilio
Related Resources
Twilio Docs
From APIs to SDKs to sample apps
API reference documentation, SDKs, helper libraries, quickstarts, and tutorials for your language and platform.
Resource Center
The latest ebooks, industry reports, and webinars
Learn from customer engagement experts to improve your own communication.
Ahoy
Twilio's developer community hub
Best practices, code samples, and inspiration to build communications and digital engagement experiences.