10DLC compliance evidence for your messaging campaign
Give campaign reviewers a clear account of how subscribers agree to receive your messages. ConsentVerified organizes web and keyword opt-in records, the disclosures behind them, and STOP and HELP handling evidence. Export the consent evidence for carrier review while keeping the same records available for your compliance team and subscriber inquiries.
Understand what brand and campaign registration covers
A2P 10DLC refers to application-to-person messaging over standard US ten-digit long-code numbers. For applicable traffic, carriers require brand and campaign registration through the messaging ecosystem. Brand registration identifies the sender. Campaign registration describes the messaging use case, enrollment process, and content associated with the program. Your sending provider manages the registration path and its specific submission requirements.
Registration is a carrier process rather than a government license or a TCPA determination. It does not establish that every recipient consents, and approval does not guarantee delivery. ConsentVerified supports the opt-in evidence portion of your workflow. Your team still submits the required brand and campaign information through the relevant registration process and keeps the registered description aligned with actual traffic.
- Identify the sender and use case consistently throughout the registration.
- Describe the real enrollment process for the campaign.
- Keep registration status separate from individual subscriber permission.
Make A2P compliance evidence specific to the program
A2P compliance includes more than a completed registration form. Reviewers need to understand why the recipient expects the message, what program the person joins, and how the program handles opt-out and help requests. A clear description of those facts is easier to assess than a general statement that every contact has consent. Keep the supporting records connected to the campaign they explain.
Use ConsentVerified to retain the opt-in disclosure and captured subscription activity. For web forms, the evidence includes the page context and the action associated with agreement. For keyword flows, preserve the invitation and keyword event that establish the subscription. The SMS consent workflow explains the channel-specific records that support this part of A2P 10DLC compliance.
- Connect the enrollment method to the specific messaging program.
- Preserve the disclosure consumers see before subscribing.
- Keep records that explain how the person joins rather than only their current subscriber status.
Show reviewers how permission is obtained
Carriers and messaging providers can ask for the public opt-in page, the disclosure displayed there, and a description of the enrollment steps. When the flow is not publicly accessible, they may request a clear view of the relevant screens and process. Requirements vary with the provider, use case, and campaign. Prepare the evidence that describes your own flow rather than assuming a generic description meets every review.
ConsentVerified captures the disclosure text, visibility, checkbox or button action, page URL, timestamps, IP address, and user agent for web submissions. Certificate IDs and SHA-256 hashes connect captured records to their evidence. Follow the proof of consent process to preserve the interaction that actually enrolls the subscriber and keep it retrievable after the page changes.
-
Provide the page or enrollment context associated with the campaign.
-
Explain the consumer action that signifies agreement.
-
Preserve the disclosure version and program identity behind the record.
-
Match submitted evidence to the enrollment method used in practice.
Keep the disclosure aligned with the campaign
The opt-in invitation should identify the brand or program and explain the message purpose and expected frequency. Include the applicable message and data rates statement, STOP and HELP instructions, and links to terms and the privacy policy. For covered marketing texts, the written agreement also needs the applicable TCPA elements. Campaign descriptions should not imply a narrower use than the messages subscribers receive.
Use the Consent Language Checker to review wording before submitting the campaign. It highlights missing elements and suggests revisions for your team to assess. If you change the program's purpose or enrollment flow, review the disclosure and registration information together. A stored certificate does not expand the permission beyond the agreement the consumer actually makes.
- Describe the messages and frequency accurately.
- Put the enrollment disclosure where the consumer can review it before acting.
- Reconcile changes to the program with the relevant registration requirements.
Document the path out of the program
Campaign review can include the program's opt-out and help behavior. Keep STOP request evidence connected to suppression handling so your team can show how the recipient's preference reaches the sending workflow. Preserve HELP interactions separately so reviewers can see the assistance path and program identification. These records explain ongoing program operation rather than just the moment of subscription.
ConsentVerified retains STOP and HELP handling evidence with messaging consent records. Your sending system still needs to enforce the required opt-out behavior and your teams need a process for requests received through other reasonable channels. Review TCPA consent and revocation alongside carrier policies, since a supported keyword does not settle every legal question about a consumer's request to stop.
- Preserve requests and their associated response or handling evidence.
- Keep suppression information connected to the sending workflow.
- Check that assistance information accurately identifies the program and support path.
Assemble an export around the actual enrollment flow
Prepare the opt-in evidence associated with the campaign under review. Include the disclosure, enrollment context, captured subscription action, and relevant STOP and HELP handling evidence. Your team can use the export to support the provider's submission process and answer follow-up questions about how subscribers enter the program. Review the package before sharing it so the evidence matches the campaign description.
The Evidence Vault also provides PDF and JSON evidence packages per phone number for individual record review. Keep consumer information limited to what the authorized reviewer needs. Carrier approval and message delivery remain decisions of the messaging ecosystem. ConsentVerified is a compliance tool, not a law firm, and the material here is not legal advice or a guarantee of campaign acceptance.
-
Export evidence associated with the program being reviewed.
-
Keep the captured disclosure and enrollment action connected.
-
Answer review questions from retained facts rather than recreated assumptions.
Keep campaign evidence available after registration
Plans start from $149 a month with Starter. SMS and 10DLC opt-in records are included in Starter, Growth, Scale, and Enterprise. Retention is one year on Starter, three years on Growth, and five years on Scale. Enterprise retains evidence for seven years with legal hold. The appropriate period depends on your recordkeeping obligations and the reviews your team needs to support.
Compare TCPA compliance software pricing to match certificate capture, verification volume, and team access to your program. Read about consent data security before assigning reviewers or sharing subscriber evidence. Brand registration, campaign registration, and any messaging service charges are separate from the consent evidence workflow described here.
Give your campaign review a clear consent record
Create your workspace and connect the forms and messaging records that explain your opt-in process. Keep the evidence available as the campaign operates so the same facts support registration review, subscriber questions, and your team's ongoing consent checks.