LegalVoice LegalVoice
Get started

Personal injury intake script

Build a personal injury intake script that can listen, adapt, and hand off.

A personal injury intake script should open with empathy and role clarity, identify the caller path, collect firm-approved information in conversational field groups, adapt to what the caller already shared, and end with a specific transfer, consultation, callback, message, or review disposition. It should stop and escalate when the caller needs legal judgment, reports distress, asks for a person, or reaches another firm-approved boundary.

Draft your intake script About LegalVoice
A professional team collaborating around a laptop in an office. From conversation to action
Photo by Vitaly Gariev on Unsplash
Open with empathy, purpose, and a manageable first question

A firm-approved opening can acknowledge the caller without promising an outcome: “I’m sorry you’re dealing with this. I can collect some basic information and help with the next step.” The intake should explain its role and avoid implying that the firm has accepted representation or that the conversation provides legal advice.

Confirm that the caller can speak safely and identify whether this is a new matter, an existing-client call, a provider or adjuster contact, a vendor request, or another path before beginning a personal injury questionnaire.

Move through information groups, not a rigid interrogation

For a new inquiry, the firm may approve groups for caller and contact details, what the caller reports happened, when and where it occurred, reported injuries and treatment, insurance and representation context, available reports or evidence, and the desired next step. The exact questions and conditional branches require firm and qualified review.

Ask only for information that remains missing. Reflect back uncertain dates, names, and facts rather than silently normalizing them. Distinguish the caller’s words from summaries or inferred categories.

Adapt the order while preserving the required record

A distressed caller may need a slower pace or a human. A caller who begins with a detailed narrative should not be forced to repeat it immediately. A provider or adjuster should leave the new-lead path. A returning caller should be directed to the existing-client workflow under the firm’s verification rules.

Adaptation changes sequence and phrasing; it does not authorize the intake to make a legal conclusion, give advice, promise a consultation, or skip a firm-required escalation.

Close with the exact next step and ownership

Summarize only the operational next step: a configured transfer, available consultation, owned callback, approved message, incomplete-information task, or needs-review item. Confirm the appropriate contact channel and correct errors before ending. Do not describe the intake as complete when a required handoff remains unresolved.

checklist

PI intake script review checklist

Use this checklist to review a script draft before it is used by staff, an answering service, or an automated workflow.

Empathetic opening Acknowledge the situation, state the intake role, avoid promises, and begin with one manageable question.
Caller-path branch Separate new leads, existing clients, providers, adjusters, vendors, referrals, named-person requests, and uncertain callers.
Contact group Collect only approved identity, relationship, contact, language, and follow-up preference fields.
Incident and impact groups Collect the caller’s reported event, timing, location, injuries, treatment, and immediate context using reviewed language.
Supporting context Ask approved conditional questions about insurance, representation, reports, witnesses, documents, and other firm-selected context.
Adaptation rules Define how to avoid repetition, preserve uncertainty, slow down, change caller paths, handle interruptions, and resume an incomplete intake.
Escalation boundaries Stop or hand off for safety concerns, distress, advice requests, explicit human requests, ambiguity, technical failure, or another approved trigger.
Closing disposition State the transfer, scheduling, callback, message, incomplete, or review outcome; confirm the owner and communication channel.
QA and version control Name the approvers, effective date, change log, simulation set, scorecard, and correction process.

Written by LegalVoice Editorial Team. Reviewed by LegalVoice Legal and Intake Review. Published 2026-08-20; updated 2026-08-20.