AI receptionist for personal injury lawyers: a 10-point checklist

An AI receptionist built for a dental office or a heating and cooling (HVAC) shop can answer the phone, take a name, and book a time. An AI receptionist for personal injury lawyers needs more than that, and some of what it needs is about what the agent must never do.

This is the checklist we're building the azlabs Front Desk intake service for personal injury (PI) firms against. If you're looking at any AI intake agent for law firms, ours or someone else's, it's a reasonable list to hold it to.

1. It says it's AI, first

The caller should know in the first few seconds that they're talking to an AI assistant for the firm. That's a fairness point, and it's also what the bar guidance we've read expects. The State Bar of Arizona's frequently asked questions (FAQ) on ER 7.3 and a draft Oregon State Bar opinion on chatbots and AI both frame inbound AI intake around disclosure, no legal advice, and a supervising lawyer. A good agent opens every call with that disclosure, in the caller's language. Front Desk is being built to do it in English and Spanish (more on that in bilingual legal intake).

2. It handles personal injury case screening as a conversation

A generic agent asks "How can I help you?" and writes down the answer. A PI agent works through personal injury case screening while still sounding like a conversation:

• Type of accident and the date it happened
• Injuries, and what treatment the caller has had so far
• The caller's understanding of fault
• Insurance on both sides, and whether an adjuster has already been in touch
• Whether there's a police report
• Location, which matters for jurisdiction

It should follow the caller's story and circle back for gaps instead of interrogating them. The firm decides which questions are required, and the agent works to the firm's script. Our piece on personal injury attorney intake explains why this call is the narrow point for small firms.

3. It collects what the firm needs for a conflict check

Before a firm can take a case, it has to know it isn't already on the other side. A good agent captures the names the firm needs (the other driver, the vehicle owner, any business involved, the insurers) so someone can run the check before anyone promises anything. The agent doesn't run the check or tell the caller the firm will represent them. Conflict-check capture is part of the PI build we're working on now.

4. It flags deadlines without giving advice about them

The agent records the accident date and flags intakes where timing could matter, so the attorney sees it at the top of the record. What it doesn't do is tell the caller how long they have to file. Deadlines vary by state and claim type, and explaining them is legal advice.

5. It gives no legal advice, ever

Callers will ask "Do I have a case?", "What's it worth?", and "Should I talk to their insurance?" A good agent has one answer to every version of that, which is that an attorney at the firm will review what they shared and follow up. It doesn't estimate case value, doesn't predict outcomes, and doesn't coach the caller on what to say to an adjuster.

6. It live-transfers serious injuries

Some calls shouldn't wait for morning. When the caller describes a serious injury, such as a hospital stay or surgery or a death in the family, Front Desk is built to live-transfer to a person at the firm during the hours the firm sets. Outside those hours it marks the lead urgent and books the earliest callback the firm allows, which is the heart of after-hours intake. The firm defines what counts as serious, and the agent follows those rules instead of making the call itself.

7. It writes the full record into Lead Docket or Filevine

This is the part we think matters most for small firms, and it's why we're building a Lead Docket intake integration (and Filevine) instead of a standalone inbox. The agent writes the complete intake into the customer relationship management (CRM) system the firm already uses: screening answers, conflict-check names, the urgency flag, language preference, a summary, and the transcript.

Lead Docket is built around taking a lead from first click to signed retainer, with automated follow-up and e-sign. A complete record at the top lets that pipeline do its job without someone re-keying a voicemail. It also means phone leads land next to the ones from your forms and chat widgets.

8. It lets the CRM send the retainer, after a lawyer decides

The agent doesn't sign anyone up. A lawyer at the firm reviews every intake and decides whether to take the case, and then the CRM sends the e-sign retainer link the way the firm already has it set up. The decision stays with the attorney.

9. It handles recording consent by state

Call-recording consent rules vary by state, and some states require every party on the call to consent. The agent should give the recording notice that fits the firm's jurisdiction, and the firm should confirm that setup before going live. We're building state-specific notice into Front Desk's PI flow.

10. It stays inbound

This one is a hard line for us. The agent answers people who call the firm, and it doesn't make outbound calls to accident victims.

There are two reasons. Outbound contact with accident victims can count as live solicitation under American Bar Association (ABA) Model Rule 7.3 and state versions of it, and it's an open question whether a real-time AI call is treated like a live person. On top of that, the Federal Communications Commission (FCC) ruled in FCC 24-17 that AI voices are an "artificial voice" under the Telephone Consumer Protection Act (TCPA), so outbound AI calls need prior express consent. Callbacks are for your staff.

This is not legal advice. Your state's rules govern, so check with your bar or ethics counsel.

How to use this checklist when evaluating an AI receptionist for personal injury lawyers

Ask any vendor to show you items 1, 5, and 10 on a live call, because those are the guardrails. Then ask to see what actually lands in your CRM after a test intake, because that's where items 2, 3, 7, and 8 either work or don't. If what shows up is an email with a name and a phone number, you're looking at a message service.

Frequently asked questions

What should an AI receptionist for personal injury lawyers do that a general one doesn't?

It should disclose it's AI, run PI screening questions as a conversation, capture conflict-check names, flag deadline risk without advising on it, live-transfer serious injuries under firm rules, and write the full intake into the firm's CRM.

Can an AI intake agent tell a caller how long they have to file?

It shouldn't. Explaining filing deadlines is legal advice, and deadlines vary by state and claim type. A good agent records the accident date and flags timing risk for the attorney instead.

Does the AI sign up new clients?

No. A lawyer reviews every intake and decides whether to take the case. After that decision, the firm's CRM, such as Lead Docket, sends the e-sign retainer link.

Should an AI intake agent make outbound calls to accident victims?

We don't think so, and Front Desk won't. Outbound contact can count as solicitation under ABA Model Rule 7.3, and FCC 24-17 treats AI voices as an artificial voice under the TCPA. This is not legal advice.

Where we are

We're building Front Desk's PI intake service to meet every item on this list: bilingual, 24/7, inbound only, writing into Lead Docket or Filevine, with live transfer for serious injuries. We don't have injury-firm customers yet. If your firm runs on Lead Docket or Filevine and this checklist matches what you'd want, we'd like to show you how it works. See Front Desk for personal injury firms.