To keep messaging safe, trusted, and reliable for everyone, we’re making updates to the Toll-Free Verification (TFV) process. Starting on September 30th 2025, customers can begin including their Business Registration Number (BRN) as part of the submission process. Beginning January 2026, BRNs will be mandatory for all new TFV submissions.
This early heads-up gives you and your customers time to prepare—and ensures that when the new requirements go live, you’re ready to go.
Overview
This article covers everything you need to know about BRN and other optional field requirements in Toll-Free Verification:
Policy Details by Region
US-Based Organizations
- Required BRN: Employer Identification Number (EIN)
- The EIN must match the legal business name in your submission.
- If no EIN is available (e.g., a self-run business or sole prop with no employees), you may indicate this through setting the entityType to SOLE_PROPRIETOR.
Organizations Outside the US
- Provide your official business registration number as issued by a national or local business authority.
- You must also include:
- Legal business name
- Issuing country
- Name of the registration authority (e.g., Companies House in the UK, Corporations Canada, etc.)
What’s Changing?
We’re adding three fields to the TFV submission form with respect to BRN requirements:
- Business Registration Number (BRN)
- Business Registration Type
- Issuing Country of Business Registration
For now, these fields will be optional—but starting January 2026, they’ll be required for all new Toll-Free Verifications.
Optional Fields Now Supported
To improve opt-in transparency and streamline verification, we’ve also added support for several new optional fields:
Note: Some of these fields are expected to become required at a future date. We recommend populating them now to avoid delays later and to strengthen your application.
Business Identity & Classification
| Field | Description |
| legalBusinessName | Used to validate the BRN registration. |
| businessDBA | Doing Business As (DBA) name of the business, if applicable |
| entityType | Legal entity type: SOLE_PROPRIETOR, PRIVATE_PROFIT, PUBLIC_PROFIT, NON_PROFIT, GOVERNMENT |
| primaryIndustrySector | The primary industry or sector in which the business operates |
| businessContactPosition | Title or role of the primary business contact submitting the verification |
Opt-In & Messaging Flows
| Field | Description |
| optInConfirmationResponse | The automated response users receive after opting in |
| helpMessageResponse | The message returned when users text HELP |
| optInKeywords | The keywords used to trigger opt-in to the messaging campaign |
Policies & Compliance
| Field | Description |
| privacyPolicyURL | Link to the business’s privacy policy |
| termsAndConditionURL | Link to the business’s terms and conditions |
| ageGatedContent | Whether the content requires age gating (e.g., 18+) — true or false |
Populating these fields now ensures your applications are complete and ready for any future enforcement. We'll provide proactive notice before any optional field becomes mandatory.
What Should Customers Do Now?
We strongly encourage customers to:
- Begin collecting BRNs and supporting business registration documentation.
- Gather any additional details (opt-in language, privacy URLs, etc.) that can strengthen submissions.
- ISVs and partners should begin updating their onboarding flows to collect these fields from customers.
Twilio will also update in-console forms and our Error and Warning Dictionary with improved troubleshooting for BRN-related submissions.
Why This Matters
These changes are part of a broader industry shift toward greater accountability and message legitimacy. BRNs help ensure messages:
- Originate from a registered business entity
- Match known industry use cases
- Comply with opt-in expectations and content policies
They also help reduce spam, improve deliverability, and support long-term trust across carrier networks.
Stay Informed
We’ll continue to share updates as the enforcement date approaches. For now, start preparing so your verification workflows remain seamless.
If you're building against the API, be sure to check out the Twilio API Docs for code samples and detailed guidance on how to include the new fields in your Toll-Free Verification requests.