Consent capture, certificate references, suppression controls, and event history help your team see what happened at intake and delivery. Lead Router keeps the consent text, timestamps, and certificate references sent with each lead. It can also capture consent itself when you set that up. You are still responsible for getting valid consent for your outreach and for setting up delivery of that evidence.
Every lead
Consent record
IP + browser + time
Captured at intake
Every touch
Audit trail
The Rules
The Telephone Consumer Protection Act (47 U.S.C. § 227) governs marketing calls, auto-dialed calls, and SMS to consumer phones. These are the obligations that land on every lead operator.
Prior express written consent. Marketing calls and SMS to cell phones using an automatic telephone dialing system or a prerecorded voice require prior express written consent from the consumer. The consent has to be clear, conspicuous, and tied to a specific disclosure about what the consumer is agreeing to receive.
Consent scope. On January 24, 2025, the Eleventh Circuit vacated the one-to-one and logically-and-topically-associated consent restrictions in Part III.D of FCC 23-107. Those vacated restrictions are not a current federal one-to-one requirement. Existing TCPA obligations still apply to the relevant calls and texts. Review the actual disclosure, seller authorization and outreach method with counsel.
National and internal DNC scrubbing. Numbers on the federal Do-Not-Call registry cannot receive telemarketing calls. Every seller also has to maintain an internal DNC list of consumers who asked that company to stop contacting them. Both lists have to be honored before a call goes out.
Calling-hours restrictions. Telemarketing calls are restricted to 8am through 9pm in the local time of the called party. Lead routing that ignores the consumer's time zone produces calls that violate this window, and state rules are often tighter.
Damages. TCPA is a private right of action. Statutory damages run $500 per violation and up to $1,500 per willful violation, with no cap. Plaintiffs' firms combine violations in class actions, so one compliance miss can quickly become seven-figure exposure.
How Lead Router Helps
Six capabilities that support the compliance work your operation has to do. These are controls, not claims of compliance on your behalf.
Lead records preserve consent fields and certificate references supplied by intake. Configure required fields and native capture for the evidence your workflow needs; a missing field is not proof of consent.
Lead Router preserves consent text, timestamps and certificate references supplied by the intake, with native consent capture available when configured. Operators remain responsible for obtaining valid consent for their outreach and configuring delivery of the relevant evidence.
Buyer-level and platform-level suppression lists filter leads before routing. SMS STOP replies are processed and recorded. National DNC integration points let you plug in a scrubbing provider and apply the result to every routed lead. Internal do-not-contact lists are honored across campaigns and buyers.
Every contract carries its own schedule: a time zone plus day-of-week and hour windows. The routing engine checks it on every decision. Set each buyer schedule to the calling hours your policy allows; the usual 8am to 9pm TCPA baseline is one way to configure it. Buyers outside their window are skipped, and the lead routes to the next eligible buyer instead of being delivered out of hours.
Every lead event (ping, sale, delivery, return, scrub, dispute) is written to an append-only log with the actor, timestamp, and payload. When you need to answer a subpoena, you pull the lead, pull the log, and export the consent fields. Nothing is changed quietly behind the scenes.
Full lead records, including consent metadata, routing decisions, and the event log, export as JSON or CSV. When counsel asks for the record on a specific prospect, the export is one query. You do not have to scrape screens, rebuild history from logs, or decode a vendor format.
These product steps support your team’s review. They do not decide whether outreach is lawful.
Capture
Lead fields
Supplied consent reference
Your source sends the required fields and evidence.
Carry
Lead record
Buyer field mapping
Keep the supplied reference attached through delivery.
Review
Record and evidence
Intended outreach
Your team reviews the evidence and the outreach plan.
Consent Certificates
Consent-certificate products sit upstream of the routing platform. Lead Router is designed to carry their output, not replace it.
Many buyers, especially in insurance and financial services, require a TrustedForm certificate or similar proof of consent on every lead they buy. TrustedForm is an ActiveProspect product that records a session on the intake page and issues a certificate URL the buyer can inspect later.
If your buyers require TrustedForm, set up ActiveProspect or LeadConduit before the lead reaches Lead Router. Capture the certificate URL on your intake form as a custom field and send it to Lead Router with the lead. Lead Router stores the certificate URL on the lead record, forwards it to buyers that expect it, and keeps it in the audit log.
Lead Router does not issue TrustedForm certificates, and it does not replace TrustedForm. The two systems work together: ActiveProspect records evidence of the consent session, and Lead Router routes the lead and keeps that evidence attached to the record downstream.
Honest Limits
TCPA compliance is a shared-responsibility model. These are the parts that sit outside the routing platform.
TrustedForm certificates are issued by ActiveProspect. Lead Router accepts and stores the certificate URL if your intake form captures one, but it does not issue certificates itself.
DNC scrubbing is an integration point. Lead Router supports plugging in a scrubbing provider and applying the result, but it does not maintain its own DNC data set or scrub by default.
The consent language, checkbox placement, and disclosure on your intake page are your responsibility. Lead Router records what the form says the prospect saw, but it cannot validate that the form itself is TCPA-compliant.
TCPA is actively litigated, and the rules keep shifting. Lead Router gives you the technical controls to support compliance. Your qualified TCPA counsel decides what compliance looks like for your operation.
FCC 23-107
Distinguish the vacated restrictions from existing TCPA obligations and your own consent policy.
On January 24, 2025, the Eleventh Circuit vacated the one-to-one and logically-and-topically-associated consent restrictions in Part III.D of FCC 23-107. Those vacated restrictions are not a current federal one-to-one requirement. Existing TCPA obligations still apply to the relevant calls and texts. Read the court opinion.
Do not treat vacatur as permission to contact every purchased record. Review the consent actually captured, applicable TCPA requirements and state rules for the intended outreach. A certificate is evidence of a session, not a legal determination.
Lead Router preserves consent text, timestamps and certificate references supplied by the intake, with native consent capture available when configured. Operators remain responsible for obtaining valid consent for their outreach and configuring delivery of the relevant evidence. Explore native consent tracking and certificates.
Frequently Asked
The questions buyers and operators ask before running traffic through Lead Router.
Lead Router preserves consent text, timestamps and certificate references supplied by the intake, with native consent capture available when configured. Operators remain responsible for obtaining valid consent for their outreach and configuring delivery of the relevant evidence.
TrustedForm is an ActiveProspect product and requires its own integration. Lead Router also offers native consent capture and certificates. Each of these needs its own setup: outside TrustedForm or Jornaya references, certificate claiming through a configured provider, and Lead Router's own consent certificate (the consentCertUrl field).
Lead records preserve consent fields and certificate references supplied by intake. Configure required fields and native capture for the evidence your workflow needs; a missing field is not proof of consent.
On January 24, 2025, the Eleventh Circuit vacated the one-to-one and logically-and-topically-associated consent restrictions in Part III.D of FCC 23-107. Those vacated restrictions are not a current federal one-to-one requirement. Existing TCPA obligations still apply to the relevant calls and texts. Lead Router keeps the consent text, timestamps, and certificate references sent with each lead. It can also capture consent itself when you set that up. You are still responsible for getting valid consent for your outreach and for setting up delivery of that evidence.
Lead Router has built-in support for internal suppression lists at the buyer and platform level, and SMS STOP replies are recorded automatically. National DNC registry scrubbing is supported through integration with a scrubbing provider. Lead Router does not maintain its own national DNC data, so operators plug in a scrubbing service and the result is applied to every routed lead.
Legal Disclaimer
This page is for information only and is not legal advice. TCPA is a busy area of federal and state lawsuits, and the rules keep changing. If you run marketing traffic, talk to qualified TCPA counsel before you rely on any technical control, vendor, or platform as a compliance defense. Lead Router provides tools that support compliance work. It does not certify any operator as compliant.
Consent Evidence Built In
Consent metadata on every lead, consent certificates carried through to the buyer, an audit log your counsel can pull on demand, and data export in a format a legal team can use.
No feature tiers. Usage is metered and billed as you go.