Proof of consent from the form to the evidence file
Capture what a consumer sees, connect it to the action they take, and keep the record available when your team needs it. ConsentVerified brings disclosure checks, consent certificates, lead verification, and evidence exports into the same workflow. Your operations team gets a record to check before contact, and your compliance team gets the underlying evidence to review afterward.
-
Add the snippet where consent happens
Place the JavaScript snippet on the page that collects the lead. It records the disclosure presented during the form session, its visibility, and the checkbox or button action associated with submission. The record includes the page URL, timestamps, IP address, and user agent. This connects the consumer's action to the actual page experience rather than the wording that happens to appear on your site today.
- Install capture on the page where the consumer submits their details.
- Check the seller names, communication channels, and consent action shown together.
- Capture each submission with its own disclosure and session context.
Review the disclosure before you send traffic to the form. The TCPA consent checker identifies missing language and suggests corrections for review. A clear disclosure and a captured interaction serve different purposes, so keep both in your process. When your form changes, confirm that the capture still reflects the disclosure and action consumers encounter.
<script async src="https://consentverified.com/cv.js" data-seller="seller_01" data-form="#form_01"> </script>Captured page URL, timestamp, IP, user agent
-
Issue a certificate for the submission
When the form is submitted, ConsentVerified issues a certificate ID linked to the captured evidence. SHA-256 hashing helps your team check the integrity of the recorded content. The timestamp establishes when the system captures the event. Together, the identifier, hash, and session record give you a reference that can travel with the lead through your intake process.
- Keep the certificate ID connected to the submitted phone number.
- Preserve the disclosure version associated with that particular submission.
- Give buyers a reference they can verify before deciding whether to contact the lead.
Pass the certificate ID alongside the lead rather than relying on a vendor's general assurance that all leads have consent. A certificate documents captured activity. It does not establish that every legal requirement is satisfied, that the person entering a number owns it, or that permission remains effective forever. Those questions need the verification and suppression checks that follow.
Certificate preview PassCertificate IDCV-9TLD-4MXR-2BQESHA-256 hash4e07a91c5b2d…c83fTimestamp2026-10-20 09:14:52 UTCChannelCalls and textsSellersBrightline Home SolarPDF JSON -
Verify the lead before contact
Use the Lead Verification API to check the certificate before a lead reaches an outbound workflow. The checks cover the phone match, the seller named in the disclosure, the age of the consent record, and the disclosure score. A buyer can reject a lead that fails its requirements or route it for review instead of sending an incomplete record directly to a dialer.
- Match the certificate to the number you intend to contact.
- Confirm that the intended seller and channel fit the captured permission.
- Keep failed or incomplete records out of the contact queue pending review.
Decide what your team accepts before connecting the API to a live intake process. A score helps identify disclosure issues, but it is not a legal opinion or a universal permission to contact someone. Combine consent verification features with current revocation information and a DNC scrubber so a captured opt-in does not bypass a later request to stop.
POST /v1/verify 200{ "phone_match": true, "seller_match": true, "consent_age_days": 2, "disclosure_score": 88 } -
Retain evidence and retrieve it when needed
The Evidence Vault keeps the record available for your plan's retention period. Search by phone number and export an evidence package when a complaint, carrier inquiry, vendor dispute, or counsel request arrives. Your team works from the captured record instead of trying to recreate a form after its disclosure or design changes.
- Keep evidence available for the retention period included in your plan.
- Retrieve the relevant record using the consumer's phone number.
- Use Enterprise legal hold when required records need preservation beyond routine retention.
Retention follows your subscription. Starter includes one year, Growth includes three years, and Scale includes five years. Enterprise retains evidence for 7 years with legal hold. Choose the period with your recordkeeping needs in mind and preserve relevant records when a dispute requires them. Read about consent data security before deciding who needs access to stored evidence and exports.
(602) 555-0148- (602) 555-01482026-10-20 Pass
- (480) 555-01322026-10-19 Pass
- (602) 555-01482026-10-14 Pass
See what the certificate documents
A useful consent record answers what was shown, where it appeared, when the consumer acted, and which action the system captured. ConsentVerified keeps those details together with the certificate reference. Reviewing them helps a lead buyer distinguish a disclosure problem from a missing field or an intake mismatch. It also gives your team a specific record to discuss with the lead source.
The seller and channel matter because a certificate for one context does not establish permission for every future use of the lead. If your team buys leads, compare the captured disclosure with the intended outreach. If your team runs messaging, include the program's SMS consent records in the review rather than treating a general form submission as evidence for every text campaign.
- Disclosure text
- Disclosure text, visibility information, page URL, and captured submission action.
- Event timestamps
- Event timestamps, IP address, and user agent associated with the session.
- Certificate ID
- Certificate ID and SHA-256 hash linked to the captured record.
Give reviewers the record behind the result
The evidence package includes a PDF for human review and JSON for structured handling. The PDF helps compliance staff and counsel read the record without rebuilding an integration. The JSON carries the captured details into your own review and recordkeeping processes. Keep the package connected to the lead and the reason you retrieve it so reviewers can understand the relevant contact history.
An export supports investigation and legal review. It does not guarantee admissibility, establish that a call is lawful, or replace your own contact and revocation records. Share the relevant evidence with authorized reviewers and let counsel assess its significance. ConsentVerified is a compliance tool, not a law firm, and the information here is not legal advice.
- Export the evidence package in PDF and JSON formats.
- Review the underlying disclosure and interaction rather than a status label alone.
- Preserve related contact and suppression records in your operational systems.
Choose capacity for your consent workflow
Plans start from $149 a month with Starter. Growth and Scale increase certificate, verification, and DNC capacity, while Enterprise provides the highest volume and 7 years of retention. Every plan includes SMS and 10DLC opt-in records. Certificate capture and lead verification have separate monthly allowances, so match the plan to both the leads you generate and the leads you check.
Compare TCPA compliance software pricing for the complete limits and team controls. Starter includes 5,000 certificates and 1,000 lead verifications per month. Growth includes 50,000 and 25,000, while Scale includes 250,000 and 150,000 respectively. The subscription brings the workflow together without separate per-certificate billing within the included limits.
Build a repeatable record for the next lead
Start with the disclosure your consumers see, capture the submission, and check the resulting record before contact. The same evidence remains available for later review. Create your workspace and give operations, compliance, and counsel a shared reference for what happened at the point of consent.