Law firm client intake: a practical enquiry workflow

Law firm client intake starts with an enquiry and a decision about who handles it. An acknowledgement confirms that a message reached a system. It does not show that someone at the firm has accepted responsibility for the next action.

That distinction gives practice managers a useful starting point for intake improvement. Trace an enquiry from the website or telephone to a named person, then to a recorded next step. Identify where ownership becomes unclear before adding new channels or AI.

Map the states staff actually use

A proposed intake workflow might use received, assigned, accepted, contact attempted and closed. The firm should define each state in terms of an observable event.

These states are an illustrative design, not a prescribed procedure. The firm’s conflict checks, authorisation and engagement process still determine how an enquiry becomes a matter.

Distinguish intake from client onboarding

Client intake is the route from a new enquiry to a decision about the next step. Onboarding covers the firm's subsequent process for opening and progressing an accepted matter. Use a clear boundary between them: staff ownership of an enquiry is not acceptance of instructions.

For each transition, write down the trigger, receiving role and evidence of completion. The firm's conflict, identity and engagement checks belong where its responsible team specifies them. A CRM, or customer relationship management system, may track enquiries, but it should not silently replace the case-management record.

If a commercial tool already supports this route, evaluate that feature before adding an integration. The practice-management decision guide explains how to compare configuration, integration and replacement.

Keep the first form focused

Start with the information staff need to make contact and route the enquiry. The firm should decide what is necessary at this point and what belongs in a later, secure process. An unrestricted document-upload box can collect sensitive material before the receiving team has established why it needs it.

Data minimisation means personal information should be adequate, relevant and limited to what is needed for its purpose. It is a practical design constraint for forms and logs. ICO: data minimisation.

Ask the firm about safe contact preferences, especially where calling, leaving voicemail or sending email could create a problem. A preference recorded on the form must remain visible when someone attempts contact.

Use routing rules where they are sufficient

If the selected practice area determines the receiving team, a simple rule can assign the task. If no team accepts it, escalate through an agreed human route. Make absence cover and failed integrations visible.

AI may be useful for suggesting a category from a message or drafting an internal handoff summary. Any suggestion should be checked where a mistaken category could delay urgent assistance. Model confidence is not a substitute for the firm’s urgency procedure.

Do not let an automatic reply imply that the firm has agreed to act, that a solicitor will attend, or that legal aid is available. Those statements need the firm’s approved wording and decision process. The SRA’s AI warning explains that professional accountability remains with regulated firms and individuals. SRA: misuse of AI.

Make failure observable

For each integration, define the system of record and how staff discover a failure. A form may have succeeded while the task creation failed. Retrying should not create several indistinguishable tasks for the same enquiry.

Before a pilot, walk through a missing telephone number, an unreadable message, an unavailable team, a duplicate submission and an out-of-hours enquiry. Staff should be able to say who receives each exception and what action they can take. Configure any response windows around real staffing and approved promises.

Measure the route to a person

Consider a fictional enquiry received at 09:10. The system acknowledges it at 09:10, assigns it at 09:11, a staff member accepts it at 09:24, and staff attempt contact at 09:31. The recorded intervals are:

If the call goes unanswered, the record still needs an owner and a next step. It cannot be counted as a completed conversation or an accepted matter. These invented times illustrate the distinction; they are not response targets or a service promise. A useful dashboard retains the timestamps, current owner, attempt outcome and next action so staff can inspect the underlying record.

Measure receipt-to-acceptance time, unowned enquiries, completed contact, routing corrections and duplicated entry. Report by channel and practice area so one busy team does not disappear inside an overall average.

Keep acknowledgement time separate from human response time. Separate qualified enquiries, consultations and instructions too. An increase in messages can coexist with a decline in useful instructions.

Use the website enquiry-journey checklist to check the form, confirmation and contact route before changing the internal handover.

The solicitors website service addresses the public journey into the firm; automation addresses repeated handoffs. Their connection should be visible in the legal hub. The first-workflow guide explains how to compare this project with document preparation or internal knowledge work.