Case-criteria filtering, a state bar admission matrix, multi-firm caps, TCPA-aware intake, and an encrypted PII vault for medical torts. Built by operators. Jason Akatiff founded NIB Direct, a mass-tort lead-gen business that found claimants for law firms across Roundup, 3M CAPS, hernia mesh, talc, hair relaxer, NEC baby formula, Camp Lejeune, and more. Lead Router was designed with those intake needs in mind.
12+
Mass torts supported
NIB Direct
Founder operator background
50 states
State admission filtering
Encrypted
Medical PII vault
Why Legal Is Different
Ethics rules, state admission, case criteria, and medical-data privacy change what the routing engine has to do.
ABA Model Rule 7.2 and state bar rules set strict limits on lead-gen referrals: required disclosures, limits on payment structure, and bans on sharing fees with non-lawyers in some states. Every lead a firm accepts needs a clear record of the referral source, the fee structure, and the consent language the claimant saw.
Intake for Roundup is not intake for Camp Lejeune. Each tort has its own qualifying window: exposure date range, product identifier, diagnosis type, injury severity, treatment history, filing status. A claimant who matches Roundup may not match 3M CAPS even if the demographics look similar. Filters run per contract, not per lead form.
A firm can only accept a claimant from a state where the firm has licensed counsel or a co-counsel arrangement. Lead routing has to honor the state bar admission matrix per firm, and the matrix changes as firms pick up new admissions or drop states. Sending an Illinois claimant to a firm that only practices in Texas wastes the lead and raises an ethics issue.
Once a firm accepts a lead, outbound contact is governed by the Telephone Consumer Protection Act (TCPA). Express written consent, consent revocation tracking, DNC scrubbing, and call time restrictions all apply. Consent needs to be captured at the claimant level, stored with the lead, and retrievable per lead for litigation defense.
Roundup non-Hodgkin lymphoma, talc ovarian cancer, hair relaxer uterine cancer, hernia mesh revision, NEC baby formula, Paragard, and Truvada all involve sensitive health information: diagnosis date, treatment facility, physician names, medical record identifiers. Routing infrastructure that holds this data needs encrypted isolation, scoped access, and audit logging.
Law firms run on Needles, Litify, Filevine, CloudLex, Clio, or a custom intake database. Each system expects its own payload shape, its own field names, its own duplicate-detection rules. If a routing platform cannot hand off cleanly to the intake system, the firm has to enter data by hand, and cases get lost to human error.

How Lead Router Handles It
Each legal-intake rule maps to a feature in the routing engine. You do not need custom code per firm or manual spreadsheet routing.
Every contract has its own filter over the lead schema plus custom fields for the vertical. Filter on exposure date ranges (Roundup use between 1995 and 2020), product IDs (3M CAPS model number, specific talc brands, mesh manufacturer), injury type (NHL, ovarian, uterine, revision surgery), diagnosis date, and treatment history. Leads that fail the filter are rejected before they reach the firm.
Each buyer contract carries a state list representing where the firm is admitted to practice or has co-counsel. The routing engine filters leads to the admission matrix automatically. Firms that pick up a new state update the matrix and start receiving leads. Firms that drop a state stop receiving those claimants immediately.
Offers support multisell distribution, so one qualified claimant can route to multiple firms working the same tort. Per-firm daily, weekly, and monthly caps prevent any single firm from getting overrun, and distribution rules (price, priority, weight, round robin) control which firm sees the case first. Cap counters reset in your account timezone.
Sensitive health fields are stored in a separate encrypted vault with AES-256-GCM encryption, pseudonymous record IDs, and audit logging. Access is scoped per API key with a piiAccess flag, so partners who do not need sensitive fields never see them.
Consent language, consent timestamp, IP address, user agent, page URL, and TrustedForm cert URL are captured when the landing page is submitted and stored with the lead. If the consent language names the firms the claimant agreed to hear from, that naming is kept word for word. The intake page is responsible for limiting distribution to the named firms. Revocation flows update the consent record and block future contact. The result is a consent trail for every lead, ready for audit.
Lead Router delivers over webhook or REST API to any intake or case-management system with a lead endpoint. Firms often route leads into systems like Litify, Filevine, or CloudLex using their standard intake endpoints. The standard mass-tort field schema maps to the target system. The response (case ID, intake ID, rejection reason) is stored on the sale record. Supports TrustedForm cert URL passthrough, Jornaya LeadiD, and custom signal fields per tort campaign.
Mass Torts Lead Router Has Supported
NIB Direct generated claimants across these torts before Lead Router was built. The platform reflects the lessons from each.
Each tort carries its own qualifying criteria: exposure date range, product identifiers, injury type, diagnosis requirements, and state bar admission needs. Lead Router stores those criteria per campaign so intake runs the same way every time, across every firm signed to the offer.
Hand-Off To The Firm
The intake platform the firm uses determines how the case gets handled. Lead Router delivers into the system the firm already runs.
Lead Router delivers over webhook or REST API to any legal intake or case-management system with a lead endpoint. Firms often route leads into systems like Litify, Filevine, or CloudLex using their standard intake endpoints. The payload carries the standard mass-tort field schema (claimant identity, exposure criteria, injury type, consent metadata) plus custom fields for each tort campaign.
TrustedForm certificate URLs and Jornaya LeadiD tokens pass through to the intake system so the firm has the consent record it needs for TCPA defense. The response from the intake system (case ID, intake ID, rejection reason) is captured on the sale record for reconciliation and reporting.
For medical mass torts, sensitive health fields are routed through the encrypted vault path with scoped, audit-logged access.
Explore the detailed workflow and configuration requirements for each capability.

When you set a qualifying disposition to do so, it creates a child lead and sale for the extra case. The child keeps its own external case reference and a link to the parent. Person matching still runs, so the new case can belong to the same person.
Chained delivery can pass the case ID from the primary system to a second vendor. If you turn on disposition tracking for that recipient, it keeps its own reference and outcomes without creating another billed sale or CPA (cost-per-action) conversion.
Configure a miscellaneous cost on a transfer disposition, then record conversion revenue when the case signs. Review billed versus report-only treatment and the once-per-case guard for selected-disposition costs.
Frequently Asked
What law firm intake directors and mass-tort lead-gen operators ask before starting a campaign.
Yes. Lead Router was built for mass-tort lead gen. The founder, Jason Akatiff, ran NIB Direct, a mass-tort lead-gen business that found case claimants for law firms across Roundup, 3M CAPS, hernia mesh, talc, hair relaxer, NEC baby formula, asbestos, Camp Lejeune, Paragard, Truvada, AFFF, and more. The platform was designed around the intake needs of mass tort: exposure-date windows, product-ID filters, state bar admission matrices, and per-firm case caps.
Yes. Contracts support custom fields on the lead schema. You can filter on exposure-date windows (for example, Roundup use between 1995 and 2020), product identifiers (3M CAPS model number, mesh manufacturer, talc brand), injury type, injury severity, diagnosis date, and any other criteria for the tort. Firms see only the cases that match their criteria. Leads that do not qualify go to the next eligible firm or are rejected.
Lead Router delivers over webhook or REST API to any legal intake or case-management system with a lead endpoint. Firms often route leads into systems like Litify, Filevine, or CloudLex using their standard intake endpoints. The platform maps your standard lead schema to the fields each system expects. It also stores the response (case ID, intake ID, rejection reason) on the sale record so you can reconcile.
Sensitive health fields are kept in a separate encrypted PII vault. The vault uses AES-256-GCM encryption, pseudonymous record IDs, and audit logging on every access. Access is scoped per API key, so only parties who need the fields see them. This covers medical mass torts such as Roundup non-Hodgkin lymphoma claims, talc ovarian cancer, hair relaxer uterine cancer, hernia mesh revision surgery, and NEC baby formula.
Yes. Offers support multisell, so one case can go to several firms that all want claimants for the same tort. Per-firm monthly caps keep any one firm from being overrun. State bar admission matrices make sure a case only goes to firms licensed in the claimant state. Distribution rules (price, priority, weight, round robin) decide which firm gets the first look and which gets second.
Run Legal Intake Clean
Case-criteria filtering, state bar admission matrix, multi-firm caps, TCPA-aware consent capture, encrypted PII handling, and webhook delivery into case-management systems like Litify, Filevine, and CloudLex. Get started with a test lead.