eConsent is a TCPA consent verification platform that captures, certifies, and verifies consumer consent in real time. It provides session recordings, tamper-proof certificates with SHA-256 hashing, and identity verification for businesses that need to prove consent was obtained.

How do I install eConsent on my website?

Add one script tag to your page with your Company ID. No SDK, no build step required. Consent recording starts immediately. eConsent works on any website including WordPress, React, and static HTML.

How much does eConsent cost?

eConsent offers four plans: Starter at $199/month (1,000 retentions), Growth at $750/month (10,000 retentions), Enterprise at $1,500/month (50,000 retentions), and High Volume with custom pricing. All plans include session replay, consent certificates, and verification API. No contracts required.

How is eConsent different from other web-only providers?

eConsent provides transparent pricing, a simple verification API, real-time session replay, identity verification dossiers, Meta Lead Ads integration, and infrastructure built with Rust for performance. No long-term contracts required.

Is eConsent secure and tamper-proof?

Yes. Every certificate is SHA-256 hashed and stored in Amazon S3 with Object Lock in COMPLIANCE mode for up to 7 years. Certificates cannot be modified or deleted by anyone. All data is encrypted with TLS 1.2+ in transit and AES-256 at rest.

What is the best TCPA consent verification platform?

eConsent is a modern TCPA consent verification platform offering session recordings, tamper-proof certificates, identity verification, and Meta Lead Ads integration. eConsent offers transparent pricing starting at $199/month with no contracts, a simple one-script-tag installation, and core infrastructure built in Rust for performance and security.

Does eConsent work with Meta Lead Ads and Facebook leads?

Yes. eConsent connects to your Facebook Pages via OAuth and automatically generates consent certificates for every lead submitted through Meta Lead Ad forms. Each certificate captures the form definition, consent language, disclaimer responses, ad attribution, and includes a visual replay of the form experience.

What is a TCPA consent certificate?

A TCPA consent certificate is a tamper-proof digital record proving that a consumer provided prior express written consent as required by the Telephone Consumer Protection Act. eConsent generates these certificates automatically, including the exact consent language displayed, a full session replay, timestamp, IP address, and a SHA-256 cryptographic hash for integrity verification.

eConsent Voice

Voice consent, captured and defended.

Real-time consent classification, offshore agent tracking, and court-ready evidence for AI voice agents, BPOs, and in-house dialers.

Get your API key Read the docs

Capture

Verbal consent

Verify

Before dial

Export

Certificate

app.econsent.org/voice/consent/cst_…

Auto-detected FCC disclosures with timestamps on a captured voice consent

Voice evidence

One call. Three checks. One certificate.

Voice teams need proof at the source, proof during the call, and proof after the call. This page should read like a compliance workflow, not a product brochure.

Precall check

Check consent, revocation, and disclosure requirements before the dialer connects.

Live capture

Capture verbal permission, transcript markers, and the agent handoff while the call is still live.

Signed evidence

Export a signed certificate with disclosure timeline, audio hash, and chain-of-custody.

Live call view

Evidence bundle

Voice proof engine

Capture the call. Mark the proof. Export the record.

Voice needs a tighter layout than SMS. This section keeps the product story on the left and the evidence trail on the right so the page reads like a call ledger, not a generic feature list.

1. Precall

Check consent before the dialer connects

Call state, disclosure state, and revocation state are checked together.

2. Live call

Capture permission while the call is still active

Transcript markers and consent labels land in the same record as the call.

3. Evidence

Export a certificate with audio and disclosure hashes

The output is built for audits, partner packets, and dispute defense.

Call view

Transcript label

"Yes, I agree to receive calls about solar panel installation from SunPower."

AFFIRMATIVE

Latency

<15ms

Rules and model inference stay inside the call path.

Offshore Compliance

FCC March 2026 NPRM ready

When calls involve offshore agents, the FCC requires explicit disclosure and consent transfer. eConsent Voice tracks every agent in the call chain with location, role, and handoff timestamps automatically.

Offshore Agent

Philippines / India

Disclosure Required

Transfer

eConsent Voice API

Validates + Certifies

Chain Recorded

Handoff

Domestic Agent

United States

Compliant

Agent Chain Detail

Compliance checks in every certificate

Adversary Nation Detection

Flags calls originating from OFAC-restricted jurisdictions so your compliance team can review before proceeding

Offshore Location Disclosure

Detects and records offshore caller disclosure in the transcript; flags certificates missing the disclosure

Right-to-Transfer Notice

Detects whether the consumer was informed of their right to a US-based representative, as required by the March 2026 NPRM

Disclosure Timeline

Every required disclosure timestamped and baked into the certificate

Evidence Packages

Every consent is a tamper-evident evidence package

Each certificate bundles the consent decision, disclosure timeline, ML scores, and agent chain into one immutable dossier. Shareable via public URL with opposing counsel.

Voice consent evidence package - public certificate

HMAC Signature

SHA-256 hash proves the certificate has not been altered since creation

Disclosure Timeline

Server-timestamped record of every disclosure delivered during the call

Compliance Score

0-100 score based on disclosures delivered, consent quality, and agent compliance

Agent Chain

Full chain-of-custody showing every agent, location, role, and handoff timestamp

01 / Evidence Comparison

You already have consent data.
Is it defensible?

A side-by-side look at what your dialer exports today versus the evidence bundle eConsent Voice produces for every call.

Without eConsent

dialer_export.csv

- phone: +1 (555) 000-1234
- timestamp: 2026-04-10 14:32:00
- consent_text: "by clicking submit"
- source: spreadsheet_row_428
- ip_address: (not captured)
- audio: (none)
- transcript: (none)
- disclosures: (none)
- signature: (none)

Plaintiff's counsel will argue

No audio, no signature, no disclosure log, no proof the consumer ever heard the terms.

With eConsent Voice

consent_bundle.json

+ consent_id: cst_mnwd5l1p...
+ phone_hash: 84d12ceb...
+ captured_at: 2026-04-10T14:32:00Z
+ uploaded_at: 2026-04-10T14:32:47Z (server-signed)
+ transcript: "Yes, I agree..." (227 words)
+ audio_sha256: 7abfe60b...
+ audio_storage: s3://econsent-voice-audio/ (Object Lock COMPLIANCE, 7yr)
+ classifier_verdict: accept_consent (0.988)
+ disclosures_detected: 7/7 FCC required
+ signature: HMAC-SHA256 (2430265984b6c2ad...)

What actually happens in court

Cryptographic chain-of-custody from recording to judge. Every field verifiable independently.

Platform-agnostic

Works with your existing stack

One REST API. Any platform that can send HTTP requests - AI voice agents, cloud dialers, or contact center suites - can integrate.

Vapi

AI Voice Platform

Retell

AI Voice Agents

Bland AI

AI Phone Calls

Synthflow

No-Code AI Agents

Ringba

Call Tracking

Five9

Contact Center

NICE

CXone Platform

Genesys

Cloud CX

Developer API

Four API calls. Full compliance chain.

Every outbound call passes through a four-stage pipeline that captures, classifies, and certifies consent in real time.

Verify consent before every dial

Before your agent connects, send a precall check. The API validates consent status, checks revocation history, verifies campaign permissions, and returns a go/no-go decision with the exact FCC disclosure script - in under 200ms.

Phone number, campaign ID, agent ID required

Returns allow, review, or deny

Consent score from 0-100 included

// POST /v1/precall
{
"phone": "+15551234567",
"calling_entity": "SunPower Solar",
"purpose": "marketing",
"call_type": "ai"
}

// Response
{
"allowed": true,
"decision_id": "dec_8f3k2m",
"consent": {
"consent_id": "cst_a1b2c3",
"type": "prior_express_written",
"ai_specific_consent": true
},
"required_disclosures": ["caller_identity", "recording_notice"]
}

Log every required disclosure

The API auto-detects required disclosures in the consent transcript - AI caller identity, recording notice, offshore-agent disclosure, opt-out instructions, and callback number - and records their position and confidence. Required disclosures vary by call type and jurisdiction (FCC February 2024, August 2024 NPRM, March 2026 NPRM, plus state-specific TCPA rules).

Disclosure types detected: caller_identity, ai_identity, recording_notice, offshore_disclosure, opt_out_instructions, callback_number

Server-side uploaded_at timestamp alongside customer-claimed captured_at

Missing disclosures flagged in certificate

// Disclosure detection is built into /v1/capture-verbal
// Response includes:
"disclosure_summary": {
"caller_identity": true,
"ai_identity": true,
"recording_notice": true,
"offshore_disclosure": true,
"opt_out_instructions": true,
"total_detected": 7
}

// disclosures_detected[] with position + confidence
[
{
"type": "ai_identity",
"text": "I am an AI-powered assistant...",
"at_seconds": 9,
"confidence": 0.90,
"auto_detected": true
}, ...
]

Classify verbal consent in real time

Send the consumer's transcript segment and the ML classifier returns a consent decision with confidence score. Works across English, Spanish, French, and Portuguese in under 15ms.

Three outcomes: affirmative, ambiguous, declined

Confidence score 0.0 - 1.0 on every classification

Ambiguous results flagged for human review

// POST /v1/capture-verbal
{
"phone": "+15551234567",
"calling_entity": "SunPower Solar",
"transcript": "Yes, I agree to receive calls about solar panel installation.",
"captured_at": "2026-04-13T14:32:47Z",
"audio_segment_url": "https://cdn.example.com/call-4271.mp3"
}

// Response - 11ms inference
{
"consent_id": "cst_a1b2c3d4",
"signature": "2430265984b6c2ad...",
"classifier_result": {
"verdict": "accept_consent",
"affirmative_consent_score": 0.97,
"coercion_score": 0.03
},
"evidence_url": "https://verify.econsent.org/c/cst_a1b2c3d4"
}

Seal the evidence package

After the call, finalize the session. The API bundles the consent decision, disclosure timeline, ML scores, and agent chain into an immutable certificate. SHA-256 hashed. S3 Object Lock. 7-year retention.

Returns public verification URL

Webhook fires with certificate payload

Audio archived in S3 Object Lock COMPLIANCE mode - any alteration invalidates the HMAC signature

// POST /v1/post-call
{
"consent_id": "cst_a1b2c3d4",
"call_duration_sec": 187,
"agent_chain": [
{ "role": "offshore", "location": "PH" },
{ "role": "domestic", "location": "US" }
]
}

// Response
{
"consent_id": "cst_a1b2c3d4",
"evidence_url": "https://verify.econsent.org/c/cst_a1b2c3d4",
"audio_sha256": "e3b0c44298fc1c14...",
"compliance_score": 95,
"retention_until": "2033-04-13"
}

Pricing

Voice pricing

Per-product subscription with monthly quotas. Overage draws from your wallet at standard rates when quota runs out.

Free

Monthly only

$0 /mo

100 precall checks/mo

25 verbal captures/mo

All compliance features
Single seat

Growth

Frequently asked questions

Add a precall HTTP request before your agent connects. Send the phone number, calling entity, purpose, and call type. The API returns an allow/deny decision with any required disclosure scripts. During the call, your transcribed consent is captured and classified. After the call, the evidence bundle is finalized. We provide SDKs for Node and Python, or use any HTTP client.

When the classifier's verdict is review_consent, the consent is not accepted outright - no valid certificate is issued. The request returns the transcript, classifier scores, and reasoning so your workflow can trigger a supervisor review, re-ask the consumer, or route the call differently.

eConsent Voice is designed around three FCC actions: the February 2024 one-to-one consent requirement, the August 2024 NPRM extending TCPA to AI-generated voice, and the March 2026 NPRM on offshore agent disclosure. Certificates capture the evidence typically needed to demonstrate consent and required disclosures. eConsent does not provide legal advice - defense strategy and admissibility remain decisions for your counsel.

By default, the classifier runs server-side on our infrastructure with quantized ONNX models for deterministic latency. On Custom plans, we offer on-premise deployment options where the model runs within your infrastructure for data sovereignty requirements.

7 years using AWS S3 Object Lock in COMPLIANCE mode. Every certificate is SHA-256 hashed at creation. The hash, along with all evidence data, is immutable and cannot be altered by anyone including eConsent. This exceeds the 4-year TCPA statute of limitations.

Yes. The API is platform-agnostic. Add precall checks in your agent's server-side function, send disclosure events during the conversation, capture consent from the transcript, and finalize after the call ends. Any system that can make HTTP requests works.

Start verifying consent before your next dial

Get your API key in under 5 minutes. 14-day free trial with 100 precall checks. No contracts.

Get your API key Book a demo