RETAINERREACH
All articles
June 7, 20265 min readRideshareIntake

Why Rideshare Cases Slip Through PI Firm Intake

By Brittany Winters, Director of Client Relations

A million-dollar rideshare case and a minor fender-bender can sound almost identical on an intake call. Same "I was in a car accident," same vague description, same shaken caller. The difference between them is a single question that most intake scripts never ask — so the case gets misjudged, mispriced, and sometimes lost.

Let me walk through where it goes wrong.

The question that decides the case

When a rideshare is involved, the available insurance depends entirely on what the app was doing at the moment of the crash:

  • App off — the driver’s personal auto policy. Modest limits.
  • App on, waiting for a request — limited contingent liability coverage.
  • En route to a rider or on an active trip — a commercial policy up to $1 million.

That’s a swing from a small personal policy to a seven-figure commercial one, decided by one fact. If your intake doesn’t establish it, you’re guessing at the value of the case — and a guess on the low side means you treat a major case like a minor one.

Why standard intake misses it

Most intake scripts were built for standard car wrecks. They ask about injuries, fault, and vehicles. They don’t ask whether anyone involved was driving for Uber or Lyft, and they certainly don’t ask what the app’s status was. So three things happen:

  • The rideshare angle never surfaces, and the case is worked as an ordinary MVA.
  • The caller — who doesn’t know app status matters — never volunteers it.
  • A potentially high-value case gets the same low-urgency treatment as a soft-tissue claim, and the caller drifts to another firm.

None of that is the intake rep’s fault. They’re running the script they were given. The script is the problem.

The fix is a few questions

You don’t need to rebuild intake. You need to add a short rideshare branch to it:

  • "Was anyone involved driving for Uber, Lyft, or another rideshare service?"
  • If yes: "Were you the passenger, the rideshare driver, or in another vehicle?"
  • "Do you know whether the driver had the app on and was picking someone up or on a trip?"

Those three questions move a rideshare case out of the generic pile and let you price and prioritize it correctly — while the caller is still on the phone, before they call the next firm.

Speed still matters

Qualification doesn’t help if you’re slow. The firm that answers first and asks the right questions signs the case; the one that calls back tomorrow gets voicemail. Rideshare cases reward both speed *and* the right script — which is the whole point of managed intake built for these cases.

Want to see what slow or generic intake is costing you across all your leads, rideshare included? Run it through the Case Leak calculator.

Frequently asked questions

Why do rideshare cases get misjudged at intake?

Because standard intake scripts don’t ask whether a rideshare was involved or what the app’s status was — and that status determines whether a small personal policy or a $1M commercial policy applies. Without the question, a high-value case can be worked like a minor one.

What questions should be added to intake for rideshare cases?

Whether anyone involved was driving for Uber or Lyft, whether the caller was the passenger, rideshare driver, or a third party, and whether the app was on and the driver was picking up or on a trip. Those establish which coverage applies.

Does speed-to-lead matter for rideshare cases too?

Yes. Even with the right questions, a slow callback loses the case. Rideshare cases reward answering first and qualifying coverage in the same conversation, before the caller reaches another firm.

Want this run for your firm?

See exactly where your retainers are leaking — then decide. One firm per metro.

Calculate your case leak