eConsent SMS
What is eConsent SMS?
eConsent SMS provides TCPA and CTIA compliance for outbound text messaging. It verifies consent before every send, processes STOP keywords automatically, enforces quiet hours, and generates signed consent certificates.
Key Features
Pre-send Verification
Before sending any message, the API checks consent status, revocation history, quiet hours (8 AM - 9 PM recipient local time), and frequency caps — returning allow/block with compliance notes.
STOP Keyword Processing
Automatically recognizes STOP, UNSUBSCRIBE, CANCEL, END, QUIT and international variants. Creates a revocation record with FCC 10-business-day honor period.
HELP Keyword Response
Responds to HELP, INFO, and SUPPORT with configurable business information, as required by CTIA guidelines.
Content Validation
Scans outbound message content for required opt-out language, sender identification, and rate disclosures. Returns a compliance score with specific issues.
Double Opt-in
Optional confirmation workflow for CTIA-compliant double opt-in. Generates a confirmation token, suggests a reply message, and tracks confirmation status.
Consent Certificates
Every consent capture generates an HMAC-SHA256 signed certificate with consent source, language, and full audit trail.
Getting Started
- Go to eConsent SMS from the product switcher or sidebar
- Complete the onboarding wizard to generate your SMS API key
- Integrate the pre-send check into your messaging platform
- Start verifying consent before every send
API Endpoints
| Endpoint | Description |
|---|---|
POST /v1/sms/pre-send | Verify consent before sending |
POST /v1/sms/capture-consent | Capture opt-in consent |
POST /v1/sms/revoke | Revoke consent |
POST /v1/sms/message-log | Log outbound messages with content scan |
POST /v1/sms/stop-webhook | Process STOP keywords |
POST /v1/sms/help-webhook | Process HELP keywords |
POST /v1/sms/confirm-optin | Confirm double opt-in |
POST /v1/sms/validate-content | Check message content compliance |
GET /v1/health | API health check |
Pricing
| Tier | Price | Pre-send Checks | Consent Captures |
|---|---|---|---|
| Free | $0/mo | 5,000/mo | 0 |
| Growth | $149/mo | 50,000/mo | 10,000/mo |
| Scale | $499/mo | 500,000/mo | 100,000/mo |
Frequently Asked Questions
How is this different from Twilio’s built-in opt-out? Twilio handles STOP at the carrier level but doesn’t verify consent existed before sending, produce court-ready evidence, track consent lifecycle, or generate HMAC-signed certificates. eConsent SMS is the compliance layer on top of any SMS provider.
Does it work with any SMS provider? Yes. Twilio, Sinch, Bandwidth, Plivo, Klaviyo, Attentive, Postscript, Braze — any platform that can make HTTP requests.
What about quiet hours? The pre-send API automatically checks the recipient’s timezone based on area code and blocks marketing messages before 8 AM or after 9 PM local time, as required by TCPA.
What are frequency caps? The API limits messages to 3 per phone number per day for marketing (10 for transactional) to prevent carrier filtering and blocking.
Did this answer your question?