How Many Calls Does a PI Case Actually Generate? (And Why It's Breaking Your Team)

Ask a case manager how many calls they handle in a day and you'll get a tired laugh. Ask them how many of those calls actually move a case forward and you'll get a longer pause.
The call volume in a PI firm isn't a scheduling problem. It's a structural one. Most firms have never counted the calls a single case generates — or what they cost the people handling them.
This post does that math. Here's where the calls come from, what they cost, and why the current approach isn't built to handle it.
Where do the ~150 calls come from?
A typical personal injury case generates around 150 calls over its lifetime. That number surprises most people the first time they see it. It stops surprising anyone who's run a busy PI firm.
The calls don't come from one place — they're distributed across every party touched by the case. Here's how they stack up across the case lifecycle.
Intake and onboarding (calls 1–10)
The case starts with intake — and intake is already a multi-call process. First contact, follow-up to collect documents, calls to verify insurance, calls to confirm representation. By retainer signing, a case manager has typically fielded 8–12 calls before any real legal work begins.
Client check-ins (calls 11–60)
Clients call. Frequently. They want to know the case status, when they'll get paid, and whether their file is active.
A case on a 12–18 month timeline generates a client status call roughly every 2–3 weeks. Across the case lifetime, that's 20–30 calls from the client alone. None require a legal decision — all land on a case manager.
Medical providers (calls 61–90)
Medical providers are a constant source of inbound volume. They call to confirm records were requested, again when records are ready, and once more to verify lien agreements. Three calls per provider, per case, is a conservative estimate.
A case involving multiple treatment providers — primary care, physical therapy, specialist, imaging — can generate 10–20 calls from medical providers alone. These calls are purely administrative. They rarely require anything beyond confirmation and logging.
Insurance adjusters (calls 91–120)
Insurers operate on their own timeline and their own follow-up cadence. Adjusters call for claim status, to request additional documentation, to confirm coverage details, and to push back on demand calculations.
A contested PI case can generate 15–25 calls from insurers across pre-litigation and litigation phases. Every one of those calls requires someone to pick up, answer accurately, and document what was said. Most of them do not require a lawyer.
Lien holders and vendors (calls 121–150)
The back half of a PI case generates a steady stream of lien holder and vendor calls. Medical lien companies verify balances, health insurers confirm subrogation amounts, and vendors follow up on schedules or billing status.
These calls are transactional in nature. They have a right answer — a balance, a date, a confirmation. But they land in the same queue as everything else and get handled by the same overloaded case managers.
What 150 calls per case actually means for your team
The math gets uncomfortable fast.
A case manager carrying 100 active cases is managing roughly 15,000 calls per year across that caseload. That's not a theoretical number — it's the product of a typical PI caseload and a typical per-case call volume. At 200 working days a year, that's 75 calls per day, per case manager.
Not 75 calls total. 75 calls per case manager.
Firms with 5 case managers at that caseload are fielding 375 calls a day across the team. Most cluster in the same 3-hour window — 10 AM to 1 PM — when everyone checks in at once.
The 70% that don't require a human
Here's the harder number to sit with: roughly 70% of those calls don't require a human decision. They require a consistent, accurate response.
A client asking for a status update needs the case stage and next expected milestone. A medical provider confirming records were received needs a yes or no with a date. A lien holder verifying a balance needs the number in the file.
None of these calls require judgment. None of them require a lawyer. All of them are consuming the time of someone who was hired to do substantive legal work.
The 35–50% that go unanswered
There's a second problem layered on top of the first. Firms miss 35–50% of inbound calls during business hours. Not after hours — during business hours, when case managers are already on other calls or handling files.
A missed call from a client becomes a follow-up call, then a complaint. A missed call from an adjuster delays a demand response. A missed call from a medical provider delays records — every missed call creates downstream work.
A single missed PI intake call is a $50,000+ contingency fee walking to the next firm in the search results. Multiply that by the missed leads in a month and the number gets large quickly.
Why the current setup isn't built for this volume
Most PI firms handle this with one of two approaches: an in-house team or a virtual receptionist service. Both have the same ceiling.
In-house case managers are expensive, and their time is genuinely valuable. Using them to confirm lien balances and tell clients their case is "still in the demand phase" is a poor allocation of that value. It also burns out good people — being a human queue for 75 calls a day isn't a sustainable job description.
Virtual receptionist services — Ruby, answering services, hybrid models — pick up the phone. But they escalate everything substantive back to the team. That means a receptionist took the message — and the case manager still has to return the call.
The call volume doesn't go down. It gets logged twice.
Neither model resolves the calls. They just route them.
What resolution actually looks like
Resolving a call means the call ends with the caller's need met — not with a message sitting in someone's voicemail.
A client calls for a case status update. They hear the current stage, the next expected milestone, and confirmation the team has their file. Call ends — no callback required, nothing logged manually.
A medical provider calls to confirm records were received. They get a yes or no with a date — the confirmation writes automatically into the case file. Call ends.
A lien holder calls to verify a balance. They get the number — a note appears in the file. Call ends.
That's what 70% of PI calls look like when they're resolved rather than routed. The case manager never touches them; the call writes directly into the case file. The 30% that genuinely require judgment still go to the right person, with context already loaded.
The operational data problem
There's one more cost that doesn't show up in a headcount budget: the firm has no visibility into what's happening.
Which clients haven't been called back this week? Where are cases stuck because a medical provider hasn't been followed up with? Which adjusters have gone quiet on a demand sent 30 days ago?
A case manager fielding 75 calls a day can't track all of that. A virtual receptionist service doesn't write into your case file. The data sits in call logs, voicemails, and individual memory — none of it surfaces in a report.
The firms that close cases fastest are the ones that can see where cases are stalling. That visibility only exists if every call is captured, logged, and tied to the case file automatically.
The bottom line
A PI case generates around 150 calls; a case manager with 100 cases is fielding 15,000 a year. Roughly 70% don't require human judgment. And 35–50% go unanswered during business hours anyway.
That's the problem. It's not a staffing problem — you can't hire your way out of a structural volume issue. It's not a motivation problem — case managers are working hard. It's a systems problem, and the current setup wasn't built for this.
HelloCounsel is built specifically for it. It resolves the 70% that don't require a human and writes every call directly into the case file. Book a 20-minute demo and we'll show you the math on your actual caseload. Two weeks to test it, no long-term contract required.
Share this article