Personal Injury LawSeptember 13, 2026

Lima Injury Firms: Stop Letting Intake Depend on Who Picks Up

Ohio keeps narrowing the race to reach accident victims. The people who contact you on their own matter more, and a custom intake CRM makes sure none slip.

By Paglow Automations

Late last month, the Supreme Court of Ohio unanimously upheld two state laws aimed at the rush to reach people after a crash. One bars healthcare providers from soliciting motor vehicle accident victims for 30 days. The other keeps victims' phone numbers in police reports out of public records.

The case was brought by chiropractic practices, and lawyers answer to their own solicitation rules. Still, the direction is plain for anyone handling injury cases in Allen County. Reaching people first keeps getting harder, which puts more weight on the ones who reach out to you on their own. Many of them only reach out once, and what happens in the next few hours decides whether that becomes a signed client.

At a lot of small firms, that first contact lands in three places: a legal pad at the front desk, a web form inbox, and a text on an attorney's phone. A custom CRM puts it in one.

Build the pipeline around how your firm signs cases

Off-the-shelf software makes you work the way its designers pictured. A custom CRM starts with how your office actually moves someone from "I got hurt" to a signed fee agreement. For a small injury practice, the stages might be new inquiry, intake complete, conflict check, attorney review, agreement sent, then signed or declined.

Every inquiry enters the first stage with a named owner and a due time. A web form that comes in at 11 p.m. on a Saturday doesn't wait for someone to open the inbox Monday. It sits at the top of the morning queue with a callback task already assigned.

The bigger win is consistency. Case value gets shaped at intake, and right now yours probably depends on who picked up. A CRM built for your firm turns the intake record into the checklist, and a file doesn't advance until the basics are there:

  • Incident date, with the general two-year filing deadline for bodily injury under Ohio Revised Code 2305.10 calculated and flagged for an attorney to confirm, since some claims run on different clocks
  • Medical treatment so far, where, and whether it's ongoing
  • Police report number, insurance on both sides, witnesses
  • Every other person involved, checked against your existing matters for conflicts
  • How they found you, so you can see which referral sources produce signed cases, not just calls

AI earns its place in one narrow job. Notes taken while someone is hurting come out messy. AI reads the staff member's rough notes or the after-hours form, fills in the structured fields, and lists what's missing: no treatment date, other driver's insurer unknown. A person reviews and confirms before anything saves. The AI never decides whether to take a case. It makes sure the attorney opening the file at 8 a.m. gets a complete one.

Keep confidential information where it belongs

In June, at the Supreme Court's request, the Ohio Board of Professional Conduct published an ethics guide on AI for lawyers and judicial officers. The rules don't forbid AI tools. But lawyers are expected to verify what those tools produce and to make reasonable efforts to prevent unauthorized disclosure of client information. Pasting an injured person's medical history into a free public chatbot is the risk that guidance is about.

A custom build handles this in the design, not in a policy memo nobody reads. A part-time assistant can see intake details without seeing settlement numbers. AI processing runs only through services whose terms bar training on your data. Every file keeps a record of who opened it. And anything the AI filled in waits for a person to confirm it.

What you have before anything gets built

When Paglow builds a CRM, the first work happens on paper. You get a CRM spec that names every stage, who owns it, and what triggers each task. You get a data model that maps how clients, incidents, medical providers, insurers and referral sources connect. One crash can produce three potential clients, and one client can have two incidents, which is exactly where conflicts hide. And you get a build plan that says what ships first, usually intake and deadline tracking, and what can wait.

Pull your last 20 inquiries that didn't sign and count how many have a complete intake record. That number tells you where to start.

Sources

Want this working in your Lima business?

Book a free AI audit — we'll show you exactly where to start.