Maintaining consumer trust is the biggest challenge in business messaging today — and our biggest opportunity for customer engagement. Consumers expect wanted, personalized communications when and where they need them, while remaining protected from spam and phishing.
Here at eTech, we support messaging as a high-engagement channel. Sending messages through a trusted platform like ours ensures you can depend on:
High message deliverability — Your customers can count on messages arriving when they expect them.
Sustained engagement from end users — Properly registered 10DLC traffic continues to see higher response rates than most channels.
A strong reputation with carriers — Your business is viewed as a partner that prioritizes consumer trust.
To maintain a high-deliverability ecosystem, eTech continuously updates systems and policies to proactively identify and block messages that violate Mobile Network Operators’ A2P/10DLC requirements before they reach carrier networks.
What is 10DLC?
10DLC (10-Digit Long Code) is the sanctioned standard for Application-to-Person (A2P) business texting over local numbers in the U.S. and Canada.
Important context about traffic type
Even a simple “hello” sent from the eTech Mobile App to an off-net recipient is A2P. All eTech SMS/MMS is delivered via an A2P business messaging gateway; P2P origination is not available on the eTech network.
P2P (Person-to-Person) — Subscriber is billed directly by the carrier (e.g., your personal cell plan).
A2P (Application-to-Person) — Messaging between a business and a consumer. All eTech traffic is A2P.
10-Digit Long Code vs. Short Code — Local numbers used for registered business messaging.
MNOs formalized 10DLC programs (guided by CTIA) to reduce unwanted messages.
A2P/10DLC compliance applies to all U.S./Canada business messaging providers.
Who regulates it?
Unlike FCC-regulated mandates, A2P/10DLC is governed by the major Mobile Network Operators (MNOs).
How is it administered?
MNOs use The Campaign Registry (TCR) to manage brand/campaign registration. Every organization must register a Brand and at least one Campaign. TCR vetting influences allowable throughput and use cases.
eTech blocks outbound SMS/MMS on numbers not registered for 10DLC.
Our carrier partners do not troubleshoot delivery for unregistered numbers.
Messages identified as violating A2P/10DLC or carrier content policies are rejected pre-submit with descriptive error codes where available.
API responses may include provisional states such as “Submitted — pending content verification.” This does not delay delivery for compliant traffic; non-compliant messages are returned with an error for correction.
Review policies
Read eTech’s Acceptable Use and Messaging policies. Ensure all messages you (and your customers, if you’re an ISV) comply.
Acknowledge updated terms
Confirm consent & disclosures
Review your Terms & Conditions and obtain appropriate opt-in. For ISVs, ensure downstream customers meet these standards.
Audit your applications
While we don’t anticipate adverse impact from header/response updates, have developers validate handling of status and error codes.
HIPAA/BAA note
Customers covered by an approved Business Associate Agreement (BAA) remain exempt from proactive content analysis due to HIPAA privacy constraints. However, they are still subject to investigation if carriers/consumers report complaints or if risk indicators (e.g., unusually high error rates) arise.
We’ll keep you updated with best practices and industry requirements so you can maintain deliverability and protect consumers. Thank you for doing your part — and if anything is unclear, tell us how we can help.
Sincerely,
Team eTech