Meru AI

Where was the law firm losing calls before intake?

Client Type
Personal injury law firm
Engagement Scope
Firmwide systems integration
Operating Focus
Call routing, attribution, and case handoffs
Last Updated
November 6, 2026

The dashboard started counting too late

A personal injury firm could see how many callers its intake team answered once they reached the queue. Some callers never made it that far. To a manager looking at the dashboard, those lost calls were invisible.

We traced the route from the incoming call to the person who could answer it. Then we connected what happened next. Marketing could follow a campaign through to a signed client, and case staff could pick up the call history and documents when the matter changed hands.

Firmwide legal operations reporting view
Client profileHigh-volume personal injury law firm, anonymized under NDA
Meru's roleCall routing, system integration, and AI-assisted review
Firm scale15,000+ active cases and 350+ employees
Decision ownershipFirm staff resolve exceptions. Attorneys review legal work before release.

One caller, several incomplete records

The call platform, campaign reports, and case systems each counted a different event. A campaign could generate a call that intake never received. A call could also lead to a signed case without that outcome making it back to the campaign report. Leaders needed to know where the record stopped before they could decide whether to change staffing or marketing spend.

The same gap appeared in case preparation. A call note might already contain an insurer’s answer while the next employee was still looking through correspondence. Staff needed the answer, its source, and a way to tell whether it was current enough to use.

Three handoffs we rebuilt

From the phone line to intake
We reviewed the routing steps before and after a call entered the queue and supported the firm’s move to Genesys Cloud. Seeing the earlier losses helped managers decide where to change routing and staffing.
From a campaign to a signed client
We linked campaign sources, calls, and signed contracts across the firm’s systems. Marketing could trace which sources led to clients. That provided the case for increasing marketing spend.
From intake to the case team
We brought call notes, correspondence, and documents into a shared case view. Staff could trace a field back to its source, correct an uncertain transcript, or flag a question for follow-up. Attorneys retained the release decision.
Legal intake interface with call context and review fieldsLegal case timeline connecting records and follow-up context

Try the handoff with fictional records below. Check what the insurer already told a colleague, find the date of that call, and decide what still needs a fresh answer before the matter goes to an attorney.

Would you call the insurer again?

Avery Chen · MC-26-0418 · May 18, 2026

About this example

Fictional data. Prebuilt outputs, not live AI. No client data is uploaded and no messages or changes are sent to a client system. Interactions stay in this page until reset or reload; where offered, downloads save only the authored sample files. The interface illustrates the working patterns described on this page.

Document preparation

Meru · implementation workspace
Fictional records
One task, from question to next step

You are the records coordinator · Avery Chen · May 18, 2026

Follow up on what is still missing.

Step 1 of 3: Find existing answers

  1. Find existing answers
  2. Review the request
  3. Attorney handoff

Your tracker has five open questions. The matter file already answers three. Prepare the next follow-up with those answers in view.

Claim reference
PH-26-10482 · confirmed in the May 15 email and call.
Signed authorization
On file, dated April 13. Counsel still reviews the recipient and scope.
First provider visit
Harbor Family Clinic · April 8, recorded in intake and the visit summary.
2 follow-ups remain

Current insurer document availability; final rehabilitation records and billing.

Inspect the answers and their sources
  • D2 / D7 · May 15. The acknowledgment and 00:26 call excerpt confirm the same claim reference.
  • D3 · April 13. The signed record is present. Its intended use remains subject to scope review.
  • D1 / D4 · April 10 / April 8. Intake and the provider summary identify the initial visit.

Fictional records. Prebuilt outputs. No client systems connected.

More inbound calls reached a person

Call handling and workflow ownership at the firm.
MeasureChangeWhat it means
Share of inbound calls answered75% to 97%The firm answered a larger share of incoming calls after reviewing the full call path and adjusting how calls reached staff.
Workflow consolidation1,000+ automations to 7 workflowsThe team grouped separate automations into seven workflows it could manage together. Each workflow covers multiple tasks.

For what happened once a caller reached a representative, see Sales Intake Intelligence. It follows the qualification questions and measures how many prospects signed with the firm.

About this engagement

This case study draws on Meru's architecture and implementation work with one personal injury firm. Its results reflect changes to routing, staffing, software, and day-to-day operations together. Client identity and private records remain confidential.

About Meru and its operating experience.

Where does your team lose the thread?

Choose one handoff where someone has to call back, re-enter a fact, or reconcile two reports. We can trace that path with your team.