SMS consent records that explain how subscribers opt in
Connect each messaging opt-in to the program, disclosure, and action that creates it. ConsentVerified keeps web and keyword opt-in records with STOP and HELP handling evidence so your team can review how a recipient enters and leaves a program. Use those records for internal checks, consumer complaints, and carrier campaign review without rebuilding the subscription history from disconnected files.
Keep legal consent and messaging guidelines in view
Marketing texts can involve TCPA requirements, state law, CTIA guidelines, and carrier rules. These serve different purposes and do not become interchangeable because a campaign has a registration number. The TCPA requires prior express written consent for covered marketing texts sent using an automatic telephone dialing system. Other outreach can still face do-not-call obligations, state requirements, and carrier expectations for permission.
CTIA guidelines describe expectations for wanted messaging, clear program information, and functional opt-out and help processes. Carrier and messaging provider requirements can add program-specific conditions. Review the requirements that apply to your use case and keep the consent flow aligned with the messages you actually send. The TCPA consent verification guide explains the broader agreement and evidence questions.
- Distinguish statutory requirements from industry guidelines and carrier policies.
- Identify the program and message purpose before collecting subscribers.
- Keep consumer permission separate from campaign registration status.
Capture the web form and the affirmative action
A web opt-in needs more context than a phone number entered into a contact field. The consumer should understand which program they are joining and what messages it sends. ConsentVerified captures the disclosure text, visibility, checkbox or button action, timestamps, page URL, IP address, and user agent. A certificate ID and SHA-256 hash connect that session to its stored evidence.
Keep the disclosure close to the action that signifies agreement and review how the form appears on a phone. If a checkbox is used, avoid a preselected state that obscures whether the person makes an affirmative choice. The proof of consent workflow shows how the captured submission becomes a certificate your team can check and retrieve later.
- Identify the texting program at the point of opt-in.
- Connect the phone number to the disclosure and submission action.
- Preserve the actual wording shown when the consumer subscribes.
Preserve the invitation behind a keyword response
A keyword response carries meaning because of the invitation the consumer sees before sending it. Keep the keyword, the program it joins, and the associated opt-in disclosure together. A keyword presented for account support should not be treated as blanket permission for unrelated marketing. The surrounding invitation matters when your team explains what the consumer understands the action to mean.
ConsentVerified keeps keyword opt-in records available alongside web records. Preserve the incoming keyword event, the applicable invitation, and the confirmation evidence associated with the program. If your workflow uses an additional confirmation, keep that response as part of the history. Match the evidence to the specific enrollment flow rather than assuming that every inbound text establishes the same scope of permission.
-
Retain the keyword and the program associated with the invitation.
-
Preserve the disclosure that explains what sending the keyword means.
-
Keep confirmation evidence connected to the original subscription event.
Give your SMS consent form clear wording
An SMS consent form should make the brand or program identity, message purpose, and expected frequency clear. Include a message and data rates disclosure, opt-out instructions, and a way to get help. Link the relevant terms and privacy policy where consumers can review them before agreeing. For covered marketing texts, include the required written consent elements and the statement that consent is not a condition of purchase.
The Consent Language Checker reviews these wording elements and suggests revisions for your team to assess. Frequency language should reflect the program, including when frequency varies. Do not copy a disclosure for another channel and assume it explains recurring texts. The checker helps surface omissions, while your team confirms that the wording accurately describes the operational flow.
- Name the brand or program and describe the messages subscribers receive.
- State the frequency or explain that message frequency varies when accurate.
- Include the statement that message and data rates may apply.
- Explain how to use STOP to opt out and HELP to get assistance.
- Provide terms and privacy policy links plus relevant TCPA agreement language.
Keep evidence of how requests are handled
An opt-in record is only part of the messaging history. Preserve STOP requests and evidence of the program's response and suppression handling. A later import or purchased lead record should not silently restore a recipient who has asked to stop. Your messaging workflow must apply the relevant rules for revocation and recognize reasonable requests beyond a single exact keyword when required.
HELP evidence serves a different purpose. It shows how the program responds when someone asks for assistance and whether the response identifies the program and provides a usable support route. ConsentVerified retains STOP and HELP handling evidence for review. Connect those records to the relevant program and keep your sending system responsible for applying suppression before further messaging.
- Preserve the incoming request, timestamp, and associated handling evidence.
- Keep opt-out information connected to internal suppression processes.
- Review HELP responses as assistance interactions rather than new marketing consent.
- Reconcile later enrollment activity with the recipient's existing suppression status.
Export the consent story for campaign review
Carrier reviewers can ask how subscribers discover a program, where the disclosure appears, and what action establishes opt-in. ConsentVerified exports opt-in evidence for campaign review so your team can present the actual enrollment flow. Include the web or keyword context, the applicable disclosure, and STOP and HELP handling evidence that describes the program under review.
Use the 10DLC compliance workflow when preparing evidence for applicable A2P long-code campaigns. Registration does not replace permission and does not guarantee approval or delivery. Reviewers may request additional information, and requirements vary by use case. ConsentVerified is a compliance tool, not a law firm. The information on this page is not legal advice.
-
Present the enrollment path associated with the registered program.
-
Include the disclosure and affirmative action behind subscriber records.
-
Keep carrier review evidence consistent with the program's actual messages.
Choose a plan for ongoing messaging evidence
Plans start from $149 a month with Starter. Starter, Growth, Scale, and Enterprise all include SMS and 10DLC opt-in records. Starter retains evidence for one year, Growth for three years, and Scale for five years. Enterprise includes 7 years of retention with legal hold. Review the period with your compliance team so records remain available for the inquiries you need to address.
Compare TCPA compliance software pricing for certificate, verification, and DNC allowances alongside messaging records. Read about consent data security before assigning access to subscriber evidence or exporting it for review. Keep exports limited to the information the recipient needs and preserve the link to the relevant program and opt-in event.
Make the next opt-in explainable
Check your SMS disclosure, connect the web or keyword flow, and keep the resulting evidence with the subscriber record. Your team can review how permission begins and how later requests are handled from the same consent workflow. Create your workspace to start capturing the messaging evidence your program needs.