By clicking the submit button below, I hereby agree to and accept Telgorithm’s terms and conditions.
Another change is coming to A2P 10DLC Brand registration. Effective January 21, 2027, Authentication+ (Auth+) 2.0 will expand to cover all Brand entity types except Sole Proprietors, broadening The Campaign Registry's (TCR) identity verification requirements across the 10DLC ecosystem.
The update also introduces a new path for Brands that register using a non-business email address: government ID authentication.
Here's what we know so far — and what Independent Software Vendors (ISVs) and Campaign Service Providers (CSPs) can do to prepare.
Authentication+ is an additional Brand identity verification process introduced by TCR to help prevent Brand impersonation, spoofing, smishing, and other forms of messaging fraud.
Auth+ adds an identity check to the Brand registration process by requiring an authorized Brand representative to verify their identity. Under the existing process, this primarily involves providing a valid corporate email address associated with the Brand and completing two-factor authentication (2FA). A Brand must successfully complete the required verification before it can move forward with new Campaign registrations.
Auth+ 2.0 builds on the original framework by separating Auth+ verification from the rest of the Brand vetting process, rather than treating it as one bundled step. This gives providers more flexibility when resolving failed verifications, since other vetting steps can proceed while Auth+ is still pending instead of being held up by it.
The January 21, 2027 expansion takes that framework further by applying Auth+ requirements to all entity types except Sole Proprietors, and by introducing two distinct authentication paths depending on the email address used during a new Brand submission:
This is particularly important for organizations that do not have—or do not typically use—an email address tied to a corporate domain during 10DLC registration.
The January update will affect new Brand submissions across all entity types other than Sole Proprietors.
For ISVs and CSPs registering Brands on behalf of their customers, that means Auth+ should no longer be viewed as a requirement affecting only a narrow category of businesses—it may require changes to onboarding workflows, customer communications, APIs, or internal processes—particularly if your customers commonly register using free or personal email addresses.
The government ID authentication path is the most notable shift. Previously, the emphasis was on obtaining an acceptable business email address for Auth+ verification. Beginning January 21, a non-business email won't necessarily stop the process, but it will trigger an additional identity verification requirement.
Not every technical detail of the January rollout has been released yet, but providers can begin preparing now.
Review how you collect Brand contact information. Determine how frequently customers submit Gmail, Yahoo, or other non-business email addresses versus addresses associated with their company domains.
Encourage corporate email addresses when available. Brands using corporate email addresses will continue through the standard Auth+ 2FA process rather than the new government ID authentication path.
Prepare customers for an additional verification step. If a Brand needs to use a non-business email address, make sure they understand that government ID authentication may be required to complete registration.
Review your registration workflows. CSPs and ISVs that automate Brand registration should be prepared for forthcoming technical requirements that may require updates to their onboarding experience or API integrations.
Telgorithm will continue monitoring the Auth+ 2.0 expansion and share updates as more guidance becomes available.
For software platforms managing 10DLC registration at scale, the takeaway is simple: encourage corporate email addresses now, and build customer expectations around the government ID path into your onboarding early. Doing so can help minimize surprises and registration delays once the expanded requirements take effect.
Receive updates from our team including latest industry news, upcoming webinars, 10DLC tips & more.
By clicking the submit button below, I hereby agree to and accept Telgorithm’s terms and conditions.
