Convert more cases from the leads you already have.
Intake Intelligence turns CSVs, web forms, and call-center exports into a prioritized queue, clear screening decisions, and the exact questions your reps should ask next.
leads_q1_export.csv
Depo-Provera protocol · 2,841 leads processed
Batch quality
2,841
leads screened with a decision on each
412
Pursue
1,093
Needs info
1,336
Do not pursue
- Most common gap not captured: diagnosis timeline
- Most common item needing confirmation: medication duration
- Most common record to request: ER records
Work first
Leads that are one phone call away from a pursue decision.
Denise R.
PursueSchedule intake
Maria K.
Needs infoAsk when she started and stopped Depo-Provera, then request ER records
Alana P.
Do not pursueNo qualifying exposure found
Next action
Start with 1,093 leads one follow-up away from a pursue decision.
You do not need more leads. You need a better way to work the ones you already bought.
The real question is not whether leads are coming in. It is whether your reps are working the right ones in the right order and asking the right questions before the lead signs elsewhere.
High lead spend
Firms spend real money to generate inbound volume, then leave conversion to whichever rep happens to pick up the phone first.
Reps guess under pressure
The queue is usually worked by arrival time, not by which lead is one follow-up away from turning into a case.
Good leads get missed while bad leads get worked
One rep spends a full call on the wrong lead while a better lead goes cold waiting for a simple follow-up or record request.
Said vs. verified gets blurred together
What the lead said, what the rep captured, and what records actually confirm are often treated like the same thing when they are not.
Upload a file. Route reps to the right next call.
Four steps, all operational. Your team uploads or connects lead data, your screening protocol runs on every row, the queue gets ordered by what to work first, and each rep opens the lead already knowing what to ask.
- 01
Upload or connect lead data
Send a CSV, Excel file, or call-log export, or connect the source you already use. Map fields once; the system remembers.
- 02
Apply your screening protocol
Your firm's criteria — diagnosis windows, exposure rules, exclusions — run on every row, the same way every time.
- 03
Prioritize the queue
Each lead gets a decision and a position in line, so reps know who to call first instead of working top-down by date.
- 04
Guide the call
Before the rep dials, they see what is missing, what needs confirmation, and the exact questions to ask next.
The rep opens the lead already knowing what to ask.
One inbound lead. Decision, what is not captured, what needs confirmation, and the exact next question to ask before the next call. Step through the stages below.
Click through the screening path
Decision, plus what is not captured, what needs confirmation, and what is verified.
- product_used
- "Depo shot"
- notes
- "friend told her to call. said it hurt after shot. went to ER once"
- diagnosis_date
- missing
- records
- none
- first_use
- unknown
- duration
- unknown
- Diagnosis timeline
- Medical records
- Duration of Depo-Provera use
- Reported ER visit (1×)
Ask when she started and stopped using Depo-Provera, then request ER records.
Not a CRM. Not lead scoring.
CRMs manage the lead. Scoring tools rank it. Neither one tells the rep what to do next on the call. That is the gap we close.
Most firms already have a CRM. What they do not have is a consistent screening layer that tells reps what to ask before the next call.
- CRMs store leads.We decide what should happen next.
- Scores rank leads.We explain what is missing and what to ask.
- Summaries restate data.Protocols turn data into action.
- Black-box automation replaces the team.Humans stay in control.
Separate what was said from what is confirmed.
What a lead says on the phone is not the same as what the rep captured, and neither one is the same as what records confirm. The system keeps those apart on every lead, every time.
Not attorney sign-off. The system helps intake teams see what still needs confirmation.
Review data handling before sharing a file.
We can provide answers on file handling, retention, subprocessors, and AI model training so firm operators and IT teams can evaluate the app before sending sensitive intake data.
- Customer files are not used to train AI models
- Anonymized samples are welcome for first review
- Security review materials available on request
- Not captured
We do not have it. The protocol asked for it; nobody wrote it down. Surfaced as a gap, never assumed.
- Captured, needs confirmation
Someone said it, but do not rely on it yet. Flagged for verification before it counts toward a decision.
- Verified
Confirmed by staff or records — a document, a callback, or a rep confirmation logged in the system.
Built for intake-heavy legal teams.
Mid-size PI firms
50–500 inbound leads per week, with teams buried in CSVs and call notes.
Mass tort intake teams
Per-tort screening protocols, applied consistently across thousands of rows.
Outsourced intake teams
Hand back to the firm a clear decision and a verification trail — not just a recording.
Lead qualification teams
See which leads need work first, and why.
Want to test it on a real intake file?
Send a sample CSV or anonymized lead export. I'll show you who to work first, which leads are one follow-up away from a case, what still needs confirmation, and what your reps should ask next.
An anonymized sample is fine. Please remove names, phone numbers, and other direct identifiers before sharing.
What happens next
- 1. Tell us what kind of intake file you want to test.
- 2. We reply with safe sharing instructions.
- 3. You see who to work first, what is missing, what needs confirmation, and what your reps should ask next.
No sensitive file upload is handled on this page.