What It Does
The Consent Language Validator checks the words a consumer sees when they opt in. It tests the text against the elements carriers and the TCPA expect: business identification, message types, frequency, the message and data rates disclosure, opt-out method, HELP keyword, privacy policy link, terms of service, and, for promotional programs, a statement that consent is not a condition of purchase.
Campaign reviewers compare this call to action with the opt-in described in the campaign. Missing disclosures and pre-checked boxes are frequent causes of consent-related rejections.
Who It Is For
- Businesses writing web or checkout opt-in language
- Senders fixing a consent or call-to-action rejection
- Teams documenting verbal or keyword opt-in scripts
Inputs
| Parameter | Type | Required | Description |
|---|---|---|---|
consentText | string | Required | Consent language to validate. |
consentMethod | string | Optional | checkbox, signature, web_form or sms_optin. |
Outputs
- Overall consent status
- Individual checks for each required element, with status and message
- Standard response fields: success, tool, tokenUsed, balanceAfter, results
Worked Example
From the MyTCRPlus API documentation. The request is sent to POST /v1/tools/consent-validator; the web tool in the Compliance Suite takes the same inputs.
Request
{
"consentText": "By checking this box, I agree to receive marketing texts from Acme Corp at the number provided. Message frequency varies. Message and data rates may apply. Reply STOP to cancel.",
"consentMethod": "checkbox"
}The response returns the fields listed under Outputs.
Cost
1 token per validation. Tool tokens are bought once, work across all 16 web tools, and never expire, and a free token is added every day. Tool tokens cost $3.50 to $5.00 each, depending on pack size. Compliance API calls use separate API tokens ($0.50 to $0.90 each), and professional users and resellers can ask about an optional monthly token plan.
How to Run It
- Open the SMS Consent Language Validator in the Compliance Suite and sign in, or create an account.
- Enter the inputs listed above and run the tool. One token is deducted per run unless noted under Cost.
- For automation, call
POST /v1/tools/consent-validatoronhttps://api.mytcrplus.com/v1with a JWT bearer token. See the API documentation.
FAQ
What are the 9 elements of compliant SMS consent language?
Business identification, message types, frequency, a cost disclosure such as "Msg & data rates may apply", opt-out method, HELP keyword, privacy policy link, terms of service, and for promotional programs a statement that consent is not a condition of purchase.
Can the consent checkbox be pre-checked?
No. Express written consent requires an affirmative action by the consumer. Pre-checked boxes are a common cause of rejection.
Does TCR approval satisfy the TCPA?
No. TCR approval covers carrier registration. TCPA consent obligations apply separately, and consent records should be kept.
How much does a validation cost?
One token per validation. Tokens are bought once, work across all MyTCRPlus tools, and do not expire.
Is there an API endpoint?
Yes. POST /v1/tools/consent-validator on the MyTCRPlus REST API.
Related Guides
- Express Written Consent for SMS
- TCPA Opt-In Requirements
- Checkbox Requirements
- Message Frequency Disclosure
Disclaimer
MyTCRPlus provides tools and templates to support compliance efforts but does not provide legal advice. MyTCRPlus is not a Campaign Service Provider and does not file registrations or send messages. Carrier approval, filtering and throughput remain at the discretion of TCR, the Direct Connect Aggregators and the carriers.
MYTCRPLUS.com is not affiliated with The Campaign Registry. TCR and The Campaign Registry are trademarks owned by The Campaign Registry. The use of TCR is nominative use only.
Related guide: SMS disclaimer examples
Related guide: SMS opt-in language templates