- Home
- Skills
- Workflow Automation
- SMS 10DLC Consent Pages and Checker
SMS 10DLC Consent Pages and Checker
Carrier campaign reviewers open your opt-in URL and read the HTML.
$29
Works with the AI Agents you already use
SMS 10DLC Consent Pages and Checker
Example session with this skill installed
Our 10DLC campaign got rejected: "opt-in flow not visible, privacy policy missing required language". Set up proper consent pages for two programs (order updates, appointment reminders) in English and Spanish and make sure they can't regress.
- Read your context and instructions
- Compiled the sms 10dlc consent
Summary
Generated 13 static files for 2 programs in EN and ES, inserted the sitemap block, and added a CI check. Two gaps remain in your privacy policy; the exact sentences are below.
| Written | Path |
|---|---|
| Opt-in directory | /sms-opt-in/, /es/sms-opt-in/ |
| Program opt-in (unchecked checkbox, full disclosure in HTML) | /sms-opt-in/orders/, /sms-opt-in/appointments/ (+ /es/) |
| Master terms | /sms-terms/, /es/sms-terms/ |
| Program terms | /sms-terms/orders/, /sms-terms/appointments/ (+ /es/) |
| Manifest | /.well-known/sms-consent.json (consentVersion 2026-05-01-sms-v1) |
| Sitemap | 12 URLs with hreflang en/es/x-default between SMS_CONSENT markers |
$ node scripts/check-sms-pages.mjs config.json ./site
SMS consent validation failed (2 issues):
- /privacy.html is missing: not sold or shared with third parties or affiliates
- /privacy.html is missing: /sms-opt-in/
Add to privacy.html (then the check is clean):
Mobile opt-in data and consent are not sold or shared with third parties or affiliates for their own marketing or promotional purposes. Message frequency varies; message and data rates may apply. See our messaging opt-in.
Form handler: buildConsentRecord() wired to POST /api/sms-consent; records carry the disclosure SHA-256, source URL, locale and an IP HMAC. Test record for +13035550142 validated.
For the registration form
- Call to action URL: https://example.com/sms-opt-in/orders/
- Privacy policy: https://example.com/privacy
- Terms: https://example.com/sms-terms/orders/
- Sample messages: 3 drafted from the order-updates purpose, each ending "Reply STOP to opt out" (in samples.md)
Next steps
- Add the two privacy sentences and rerun the checker in CI (
exit 1blocks the deploy). - Bump
consentVersionif you edit disclosure wording; old records cite their version.
Connects securely to your tools. The creator never sees your data.
About this skill
Carrier campaign reviewers open your opt-in URL and read the HTML. If the disclosure is in a modal, the checkbox is pre-checked, or the privacy policy lacks the "not sold or shared" sentence, the campaign is rejected and messaging stays off for weeks.
Generator (generate-sms-pages.mjs)
From one config (brand, controller, consent version, programs with a purpose in each locale) it writes an opt-in directory, a per-program opt-in page with a separate unchecked checkbox and the full disclosure in the static HTML, master SMS/MMS terms, per-program terms, a /.well-known/sms-consent.json manifest, and a marked sitemap block with hreflang alternates. English and Spanish, canonical and x-default on every page, indexable, no JavaScript needed to read any of it.
Checker (check-sms-pages.mjs)
Exit 1 on a pre-checked or missing checkbox, a disclosure that drifted from the generator's text (consent records would stop matching), any missing required sentence (frequency varies, rates may apply, not a condition of purchase, STOP and HELP, not sold or shared, unchecked by default), missing canonical or hreflang, a stale manifest version, sitemap gaps, and the privacy-policy sentences when the policy is a file in the site. Exit 2 when it could not run.
Consent record (consent-record.mjs)
Normalizes the number, refuses an unchecked box, a filled honeypot or a stale consent version, stores the exact disclosure text with its SHA-256, method, source URL, locale, time and an HMAC of the requester's IP; a validator for auditing the store.
Reference
What a reviewer checks and where each answer lives, the verbatim sentences, the registration fields the pages map to, common rejection reasons with fixes, record retention.
Requirements
5 offline tests. Node 20+, no packages, no network. Engineering guidance, not legal advice.
English and Spanish only. Pages are unstyled. Does not handle SMS keyword flows or registration API calls. Requires Node 20+.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 19 days ago
Requires
Permissions
Shell runs node. Read files: your config, the site root (generated pages, privacy page, sitemap). Write files: the generated HTML pages, the manifest and the sitemap block under the site root you name. No network, no environment variables.