Legal intake is bound by two rules other businesses do not face: software must not give legal advice, and collecting the story too early can disqualify the firm. How to configure around both.
When a dental practice misses a call it loses a booking. When a law firm misses a call it loses a case, and the potential new client phones the next firm on the list within the minute. Intake is the revenue event, it arrives by phone, and it does not wait.
That makes answering every call attractive and the details unusually consequential, because two rules constrain a law firm's phone in ways they do not constrain most businesses: software must not practice law, and a firm can be disqualified by hearing too much from the wrong caller.
The first is worth answering instantly. The second is routine but requires case-specific facts that software should not invent. The third must never be handled by an intake script.
Software should handle: practice areas the firm takes and does not take, office hours and locations, whether consultations are free, what a caller should bring, taking name and callback number, scheduling a consultation against the calendar, and confirming an appointment.
A person must handle: anything with a deadline attached, callers describing an arrest or an active emergency, opposing counsel, court staff, and any caller in distress. These transfer immediately, without qualifying questions.
Nobody should be guessing: whether the caller has a case, how much it is worth, how long they have to file, or what the law says. That is legal advice, and a non-lawyer system giving it is the unauthorized practice of law. It is also how a firm ends up bound by an answer nobody at the firm ever reviewed.
The safe intake script collects who the caller is, how to reach them, and the general category of matter. It does not evaluate, reassure, or estimate.
This is the part generic answering-service advice misses, and it is the one to settle first.
Hearing confidential details from a potential new client can create a duty to that person and disqualify the firm from representing anyone adverse to them — even if the firm never takes the case and never sends a bill. An intake system that enthusiastically collects the facts of a dispute before a conflicts check has run is not being thorough. It is manufacturing conflicts.
Three requirements follow:
Write these three rules first and test them from an outside line, playing a caller who tries to tell the whole story. Everything else is configuration. This one decides whether the tool creates liability.
Intake transcripts contain exactly the material a firm is obliged to protect, so three questions have real answers before any call is routed:
A vendor that cannot answer the access question in writing is not a candidate. Confirm the specifics with the firm's own malpractice carrier and ethics counsel rather than with the vendor's sales page, including this one.
Weeks one and two: after hours and overflow only. The calls that currently reach voicemail. Read every transcript, and specifically check where callers volunteered case facts and whether the system moved them along.
Weeks three and four: daytime overflow. Calls that ring more than three times, so the intake that would have been lost gets answered while staff keep the calls they can take.
Month two: outbound confirmations. Consultation reminders and callbacks, which reduce no-shows on a calendar where a no-show costs an attorney hour.
Widen only when the transcripts are clean. The failure to avoid is switching the main line over at once, discovering on a real intake call that the system talked a caller through their whole dispute, and having to ask ethics counsel what that means.
A dedicated number, realtime conversation, transfers to you when a call needs judgment, and a transcript of every call. Plans start at $49/month.
Get started →