10DLC Policy

At SaberTech, we believe business messaging works best when it’s built on trust. People want relevant, timely messages from the businesses they work with — and they want protection from spam, phishing, and unwanted content. This policy explains how we keep our messaging ecosystem clean, compliant, and reliable.

Why 10DLC matters to your business

When you send texts through SaberTech, you’re using a platform designed for high deliverability and carrier compliance. That means:

• Your messages reach customers when they’re supposed to
• Registered 10DLC traffic consistently outperforms other channels for engagement
• Carriers see your business as a trusted messaging partner

What is 10DLC?

10DLC stands for 10-Digit Long Code — the industry-standard method for Application-to-Person (A2P) business text messaging using local phone numbers in the United States and Canada.

Understanding your traffic type

Every text sent through SaberTech — even a basic message from the SaberTalk Mobile App to someone outside our network — is classified as A2P traffic. There is no person-to-person (P2P) texting on the SaberTech platform. All SMS and MMS messages are delivered through an A2P business messaging gateway.

The difference between A2P and P2P:

• P2P: Person-to-person messaging where the subscriber’s carrier bills them directly (like your personal mobile plan)
• A2P: Business-to-consumer messaging — this is what all SaberTech traffic is

How 10DLC is regulated and administered

Unlike FCC-regulated telecommunications rules, 10DLC is governed directly by the major Mobile Network Operators (MNOs). The MNOs established 10DLC programs — guided by CTIA — to cut down on unwanted messages, and these rules apply to every business messaging provider in the U.S. and Canada.

Registration is handled through The Campaign Registry (TCR). Every organization using 10DLC must register at least one Brand and one Campaign. TCR’s vetting process determines what use cases are allowed and what throughput levels you can expect.

Our enforcement approach for 2026

SaberTech takes a proactive stance on compliance:

• SMS and MMS will not be sent from numbers that aren’t registered for 10DLC
• We will not open delivery troubleshooting tickets with our carrier partners for unregistered numbers
• Messages that violate A2P/10DLC rules or carrier content policies are stopped before submission, with error codes provided where possible
• API responses may show a provisional status like “Submitted — pending content verification.” This won’t slow down compliant traffic — only non-compliant messages are returned for correction

Your 2026 compliance checklist

1. Review our policies — Read the SaberTech Acceptable Use Policy and Messaging Policy. Make sure every message you send — and that your customers send, if you’re an ISV — complies with these terms.
2. Acknowledge the updated terms — Our Messaging and Privacy policies make clear that SaberTech actively screens for and will not deliver messages that violate the AUP. By continuing to use SaberTech SMS/MMS in 2026, you acknowledge and accept these terms. To opt out, notify us in writing or by phone, or stop using the messaging service.
3. Verify consent and disclosures — Review your own Terms & Conditions and make sure you have proper opt-in from your recipients. ISVs are responsible for ensuring their downstream customers meet these same standards.
4. Check your application integrations — While we don’t expect major disruptions from updates to response headers and error codes, your development team should confirm that your applications handle all status and error codes correctly.

HIPAA and BAA considerations

Customers with an approved Business Associate Agreement (BAA) in place are exempt from proactive content scanning due to HIPAA privacy requirements. However, this exemption does not apply if carriers or consumers file complaints, or if we detect risk indicators such as unusually high error rates — in those cases, we may still investigate.

We’re committed to keeping you informed on industry best practices and carrier requirements so you can keep your deliverability high and your consumers protected. If anything in this policy is unclear, reach out — we’re here to help.