Maintaining consumer trust is one of the greatest challenges in business messaging today—and also one of our biggest opportunities for customer engagement. Consumers expect to receive relevant, timely, and trusted communications without exposure to spam or phishing threats.
At VoIPNETICS, we are committed to supporting messaging as a high-engagement channel. When you send messages through our trusted platform, you benefit from:
- High message deliverability: Your customers can rely on timely, successful message delivery.
- Strong engagement rates: 10DLC consistently achieves higher response rates than many other channels.
- Carrier-approved reputation: Your brand is viewed as a trusted participant in the messaging ecosystem.
To maintain this trusted environment, we are proactively updating our systems and policies to identify and block messages that violate mobile carrier A2P/10DLC rules—before they reach the carrier networks.
What Is 10DLC?
10DLC stands for 10-Digit Long Code—the mobile industry’s sanctioned standard for business-to-consumer messaging using a standard local phone number.
Did you know that even sending a message as simple as “hello” from the VoIPNETICS Mobile App to an off-network SMS recipient is considered A2P traffic? That’s because all VoIPNETICS messaging traffic flows through an A2P business gateway. It is not possible to technically originate P2P (Person-to-Person) messaging on the VoIPNETICS platform.
A2P vs. P2P Messaging
P2P (Person-to-Person):
Messages sent between two individuals, typically with the sender billed directly by their wireless carrier.
A2P (Application-to-Person):
Messages sent by a business or software platform to a consumer. Since VoIPNETICS traffic routes through an A2P gateway, all messages sent via our platform are classified as A2P.
10DLC Overview
10DLC is distinct from short code messaging. It uses standard 10-digit phone numbers but is registered and approved for business use.
- In 2018, the FCC deregulated SMS, classifying it as a data service.
- In 2020, mobile carriers began rolling out 10DLC programs to regulate business (A2P) traffic on local numbers.
- These programs follow CTIA guidelines and aim to prevent unwanted or abusive messaging.
- 10DLC compliance now applies to all A2P messaging across the U.S. and Canada.
Who Regulates 10DLC?
Unlike some regulations enforced by the FCC, the A2P/10DLC framework is governed by Mobile Network Operators (MNOs).
How Is 10DLC Regulated?
MNOs have appointed The Campaign Registry (TCR) to manage brand and campaign registration.
- Businesses must register both a Brand and a Campaign with TCR.
- MNOs use TCR’s verification system to determine message throughput and approval.
When Are the Regulations in Effect?
The regulations are already active.
- VoIPNETICS blocks outbound SMS traffic from any number not registered for 10DLC.
- Our messaging carrier, Bandwidth, does not troubleshoot SMS delivery issues for unregistered numbers.
Effective March 1, 2023:
- SMS/MMS traffic to the U.S. and Canada found to be in violation of 10DLC policy will be rejected before reaching the carrier network.
- API response headers may include “Message Submitted. Pending content verification for US/Canada destination numbers.”
- This will not slow down delivery.
- If content is rejected, an error code will be returned with guidance.
What’s Next for You?
- Review VoIPNETICS’s Acceptable Use Policy and Messaging Policy
- Ensure all messages you or your customers send are fully compliant.
- Understand and Accept Policy Updates
- VoIPNETICS is updating its Messaging and Privacy Policies to reflect proactive content screening.
- Continued use of VoIPNETICS messaging services confirms your acceptance.
- If you do not wish to continue, you may opt out in writing or by discontinuing use.
- Review Your Own Messaging Policies
- Confirm that your own user policies and consent practices are compliant.
- If you are an ISV, make sure your customers are informed and in compliance too.
- Check Your Applications
- We don’t anticipate issues from updated API response headers, but we recommend that your developers review any integrations for compatibility.
HIPAA Consideration
Customers with a Business Associate Agreement (BAA) in place are exempt from proactive content inspection due to HIPAA privacy rules. However, such traffic is still subject to review if:
- Complaints are filed by carriers or consumers,
- Delivery errors are unusually high, or
- Other risk indicators arise.
We will continue to keep you informed about updates, best practices, and compliance requirements to help protect consumer trust and message deliverability.
If you have questions, let us know how we can help.
Sincerely,
VoIPNETICS Team
Last Updated: 9/1/2024
