Consent verification for every stage of the lead
ConsentVerified gives lead generators, lead buyers, call centers, and messaging teams a shared workflow for capturing and checking permission. Review the disclosure, certificate the submission, verify the lead, and retain evidence for later review. Each module addresses a specific operational question, so the team making contact can work from more than a spreadsheet field marked as consented.
Check the language before collecting the lead
The Consent Language Checker reviews a disclosure against relevant TCPA, FCC, and CTIA SMS elements. It scores the submitted wording, identifies missing elements, and suggests revised language for review. Use it when writing a new form or reviewing a lead vendor's disclosure. The result makes the gaps visible before your team relies on the form to collect permission.
Checks consider seller identification, communication channels, automated technology wording where relevant, affirmative action, and the statement that consent is not a condition of purchase. SMS checks include frequency, rates, STOP, HELP, and policy links. The TCPA consent verification page explains the legal context. The one-off checker on the home page is free to use without a card. Connected capture and retained evidence require a paid subscription.
- Read the reason behind each disclosure check.
- Review suggested wording against your actual business and outreach.
- Treat the score as a review aid rather than a legal determination.
88
Consent score
- Channel Pass
- Privacy policy link Pass
- STOP Pass
Certificate the interaction that collects permission
The JavaScript snippet records what the consumer sees and does during the form session. Each certificate links the disclosure text and its visibility to the checkbox or button action, timestamps, page URL, IP address, and user agent. A certificate ID gives your team a reference to pass with the lead. SHA-256 hashing helps check the integrity of the captured content.
This record preserves the disclosure associated with that submission even when your form changes later. It gives a buyer something concrete to inspect before accepting a lead and gives compliance staff a reference when investigating a complaint. Follow the proof of consent workflow to connect capture, certificate issuance, verification, and retention across the same lead lifecycle.
- Connect the captured action to the disclosure shown during that session.
- Keep the certificate reference alongside the lead record.
- Review the underlying evidence without relying on a vendor's general assurance.
Check the certificate before routing the lead
The Lead Verification API checks the phone match, seller named in the disclosure, age of consent, and disclosure score. Use those results in your intake workflow to accept records that meet your requirements, reject records that fail, and investigate incomplete evidence before contact. The result gives operations a specific reason to ask a vendor for clarification.
A successful certificate check does not override a later revocation or establish permission for an unrelated seller. Set your acceptance criteria around the intended outreach and keep suppression checks connected to that decision. For teams buying from multiple sources, this creates a consistent review process instead of separate assumptions for each vendor's consent field.
- Match the intended recipient to the certificate's phone record.
- Review the named seller and the age of the recorded permission.
- Route failed checks away from outbound contact until reviewed.
{
"phone_match": true,
"seller_match": true,
"consent_age_days": 2,
"disclosure_score": 88
}Keep messaging opt-ins ready for review
SMS and 10DLC records preserve the evidence behind keyword and web opt-ins, including STOP and HELP handling evidence. Connect the invitation to subscribe with the consumer's action and the messaging program involved. This helps your team explain how recipients enter a campaign and how the program handles requests to stop or receive assistance.
Use SMS consent records to review the opt-in flow, then prepare an export for 10DLC compliance review. Brand and campaign registration are carrier requirements for applicable messaging traffic. They do not replace consumer permission or guarantee message delivery. Your evidence should accurately describe the program your registered campaign actually sends.
- Keep keyword and web consent records associated with the relevant program.
- Preserve STOP requests, HELP interactions, and their handling evidence.
- Export opt-in records for carrier campaign review.
- keyword
- JOIN
- Timestamp
- 2026-10-20
- STOP
- 09:14:52 UTC
- HELP
- 09:15:07 UTC
Screen lists before they reach the dialer
DNC scrubbing checks numbers against the federal National Do Not Call Registry, state lists, and your internal suppression lists. Run checks through an upload or the API as part of preparing outreach. Keep internal suppression connected to the workflow so a request received by your team does not disappear when a fresh lead file arrives.
The DNC scrubber supports a separate decision from certificate verification. A number without a list match can still lack the permission needed for a particular call or text. A listed number may involve rules or exceptions that require legal review. Examine the relevant result and the outreach context together before releasing a record for contact.
- Screen uploaded lists before an outbound campaign.
- Use the API when records enter your intake process.
- Check internal suppression alongside federal and state sources.
| Total | 5,000 |
|---|---|
| On DNC | 508 |
| Allowed numbers | 4,492 |
Retrieve the evidence behind a disputed contact
The Evidence Vault retains captured records and provides an evidence package in PDF and JSON formats per phone number. Compliance staff can review the readable document, while structured data supports your own records process. The package helps your team answer a complaint or counsel request from the captured disclosure rather than reconstructing a page from memory.
Starter retains evidence for one year, Growth for three years, and Scale for five years. Enterprise retains evidence for seven years with legal hold. Choose retention with counsel and preserve relevant evidence when a dispute arises. The consent data security page explains storage, access, exports, and deletion. ConsentVerified is a compliance tool, not a law firm. This information is not legal advice.
- Find the evidence associated with a phone number.
- Export a PDF for review and JSON for structured handling.
- Use Enterprise legal hold to preserve records subject to a hold.
Give each team the access its work requires
Team features bring roles, SAML SSO, audit logging, API keys, and webhooks into the consent workflow according to your plan. Starter includes two seats. Growth includes ten seats and roles. Scale includes twenty-five seats, roles, SAML SSO, and an audit log. Enterprise includes unlimited seats, SAML SSO, SCIM, custom roles, and an audit log, with invoicing for account administration.
Give operations the access needed to review incoming leads and give compliance staff access appropriate to evidence work. Treat API credentials as operational access and review integrations when staff or vendors change. Plan controls help separate responsibilities while keeping the evidence connected to the workflow that uses it.
- Assign role-based access on Growth, Scale, and Enterprise.
- Use SAML SSO and the audit log on Scale and Enterprise.
- Connect intake and downstream workflows through API keys and webhooks.
- 01operations
- 02compliance
- 03review
Match the subscription to the work you handle
Plans start from $149 a month with Starter. Growth and Scale provide higher monthly allowances, and Enterprise provides the highest volume and 7 years of retention. Compare TCPA compliance software pricing for certificate limits, verification capacity, DNC scrubs, language audits, and access controls. Choose capacity for the activities your team performs rather than lead count alone.
Make consent evidence part of your daily workflow
Create a workspace, check your disclosure, and connect the forms that collect your leads. Your team gets a repeatable route from the consumer's action to verification and evidence retrieval, with the relevant record available throughout the process.