Lead buyer consent verification before dialing
A delivered lead needs more than a consent flag. ConsentVerified helps your team verify a certificate before dialing and review whether its evidence supports the intended contact. Check phone match, seller named, consent age, and disclosure score, then connect the result to an acceptance, hold, or rejection decision in your intake workflow.
- Put verification before the calling queue
- Confirm that the phone belongs to the captured record
- Review the intended seller and contact channel
- Evaluate consent age and disclosure findings together
- Reject and return leads with a clear reason
- Keep acceptance evidence through the contact lifecycle
- Use Growth for a buyer managing several vendors
Put verification before the calling queue
Define a verification step between delivery and routing. Require the certificate ID alongside the lead record and use the Lead Verification API before your intake system sends the number to the dialer. Keep unresolved leads out of contact queues while your team reviews the evidence or requests a correction from the vendor.
Make the behavior clear when a record cannot be retrieved or a required check cannot finish. Your policy should specify whether the lead stays on hold or is rejected, who reviews the issue, and what permits a later release. Do not let an integration error silently become an acceptance decision.
Start with the evidence provider your workflow supports. If a vendor sends another provider's identifier, verify that record through the provider's supported process and agreement. A ConsentVerified certificate ID does not replace a TrustedForm certificate or Jornaya token required by a buyer contract. Keep those distinctions clear in your intake fields.
Confirm that the phone belongs to the captured record
Phone match checks whether the number delivered with the lead matches the number associated with the certificate. A mismatch means the evidence your team receives does not align with the number it intends to contact. Hold or reject the lead under your acceptance policy instead of assuming that the certificate applies to a similar record.
Record the mismatch reason and send the vendor the reference needed to investigate. The vendor may need to correct a delivery mapping or establish that the wrong certificate accompanies the lead. Any correction should preserve the original evidence and explain the change rather than overwrite the history without context.
A matching phone is an evidence check, not identity verification. It does not establish who currently controls the number, whether every submitted detail is accurate, or whether the consumer later withdraws permission. Apply your other contact controls and review the remaining checks before approving the lead.
| Lead | Phone match | Seller | Consent age | Score |
|---|---|---|---|---|
| Lead 48213 | Yes | Named | 14 days | 92 |
| Lead 48214 | Yes | Needs attention | 3 days | 71 |
| Lead 48217 | No | Named | 41 days | 88 |
| Lead 48220 | Yes | Named | 1 day | 95 |
Review the intended seller and contact channel
Inspect whether the intended seller is named in the recorded disclosure. A lead can pass through a publisher, distributor, and call center before reaching the business making contact. Your review should follow that intended business and purpose rather than assume that permission follows every resale in the distribution chain.
Check whether the evidence addresses calls, texts, or both, and whether the relevant wording appears where the consumer acts. The disclosure score can flag missing seller identification or channel elements, but the score is only part of the review. Your compliance team decides how the recorded wording applies to the proposed contact.
Buyers who saw the one-to-one requirement disappear in court should read the status of the one-to-one consent rule before relaxing intake rules. That ruling does not remove other consent obligations or make every broad partner disclosure sufficient. Review the facts, current law, and your buyer agreement when defining seller requirements.
Evaluate consent age and disclosure findings together
Consent age measures elapsed time since the recorded action. Use it against your acceptance policy, campaign context, and applicable requirements. There is no single age threshold that makes every lead acceptable or unacceptable. An older inquiry may need further review, while a recent submission can still contain a seller or disclosure problem.
Review the disclosure score alongside its underlying findings. Look at relevant automated technology wording, the statement that consent is not a condition of purchase, the affirmative action, and the intended channel. For messaging, inspect the elements relevant to the program, including opt-out instructions and other SMS consent evidence.
A passing score does not guarantee lawful contact. ConsentVerified is a compliance tool, not a law firm, and does not provide legal advice. Use the result to support a documented review, then apply suppression, revocation, and other checks relevant to the actual call or text.
| Lead | Phone match | Seller | Consent age | Score |
|---|---|---|---|---|
| Lead 48213 | Yes | Named | 14 days | 92 |
| Lead 48214 | Yes | Needs attention | 3 days | 71 |
| Lead 48217 | No | Named | 41 days | 88 |
| Lead 48220 | Yes | Named | 1 day | 95 |
Reject and return leads with a clear reason
Agree on acceptance criteria with vendors before delivery. Define which findings produce rejection, which need manual review, and what evidence resolves an issue. Then use the verification result in your intake workflow to keep failed leads out of the dialer and prepare a return request through the agreed vendor process.
- Reference the lead and the certificate used in the decision.
- Identify the failed check and the evidence needed to resolve it.
- Preserve the original result and any later correction.
- Request a credit or replacement under the terms of your vendor agreement.
ConsentVerified supports the evidence review. It does not issue vendor refunds or decide a commercial dispute. Keep return deadlines, credit terms, and escalation responsibilities in your purchasing agreement. If a vendor corrects the source form, treat later submissions as new events rather than evidence that earlier disclosures were different.
Keep acceptance evidence through the contact lifecycle
Once a lead passes your intake policy, apply the controls relevant to each actual contact. Review internal suppression, revocations, applicable federal and state do-not-call restrictions, and channel-specific obligations. The DNC scrubber supports list checks. A certificate does not establish that a later withdrawal or restriction never occurs.
Keep the certificate reference, vendor context, and acceptance reason connected in your operating records. When compliance or counsel asks about a contact, retrieve the record by phone number and export its PDF and JSON evidence package. The captured disclosure and action support review of the event rather than a reconstruction from the current landing page.
Choose retention that meets the obligations attached to the leads you buy. ConsentVerified stores evidence under the selected plan's terms. Confirm responsibility for older provider records when changing vendors or capture tools. Your data stays yours, and your retention process should preserve the evidence needed to explain past decisions.
| Lead | Phone match | Seller | Consent age | Score |
|---|---|---|---|---|
| Lead 48213 | Yes | Named | 14 days | 92 |
| Lead 48214 | Yes | Needs attention | 3 days | 71 |
| Lead 48217 | No | Named | 41 days | 88 |
| Lead 48220 | Yes | Named | 1 day | 95 |
Use Growth for a buyer managing several vendors
Growth is the recommended starting plan for lead buyers managing several sources. It costs $499 per month, or $249 per month billed yearly. It combines disclosure checks, certificate capture, verification, and evidence retention with defined monthly allowances. Compare those allowances with your expected intake and review needs on the pricing page.
Scale suits call centers and networks that need its higher allowances and team controls. Enterprise provides custom arrangements for larger or more complex requirements. Select a plan around the verification work and evidence obligations your operation actually has, including the records you need to retain after a campaign ends.
Begin by defining an acceptance policy for a lead source, connecting the verification response, and testing the hold and rejection paths before dialing. Explore the features or the workflows for insurance, solar, and mortgage to apply the same evidence standard across your campaigns.