Criminal law client intake: design the urgent handover
Design criminal-defence client intake around urgent contact, named staff acceptance and failed-contact escalation, using the firm’s actual arrangements.
An urgent enquiry needs to reach somebody who can act on it. A completed form, an automated acknowledgement and a notification delivered to a phone are three different events. None proves that a solicitor has accepted the next step.
A useful first system for a criminal-defence practice can track that handover. It can collect the necessary callback facts, create a task and expose an unanswered alert. The firm's people determine availability, conflicts, representation and advice.
Design the route with the people who answer
Map the firm's actual telephone, website and out-of-hours arrangements. Establish who receives each type of enquiry, how they acknowledge responsibility and what happens if they cannot respond. Do not advertise continuous availability unless the firm has confirmed and supports it.
Official guidance explains the right to free legal advice after arrest and before questioning at a police station, including asking the police to arrange advice. That is distinct from a particular firm's availability or acceptance of an enquiry. Public information should make the official route clear where appropriate, using wording the firm approves. GOV.UK: legal advice at the police station.
The workflow below is a proposed operational design. It is not a replacement for the police-station advice arrangements or an emergency service.
Collect enough to make the handover
Ask the firm which initial facts are necessary. Candidates include the caller's name, who needs assistance, a safe contact route, reported location and any stated timing. Preserve what was reported without turning it into a verified fact.
Avoid inviting a detailed account of allegations into a general marketing form. The firm should determine where sensitive information belongs, who may receive it and how it is retained. The supplier confidentiality guide explains the questions to settle before a new system handles matter information.
Distinguish delivery from acceptance
- 01Enquiry received
- 02Alert delivered
- 03Staff acceptance required
- 04Contact attempt recorded
- 05Unanswered work escalated
- 06Next action owned by a person
| Event | Evidence the workflow should retain | What happens next |
|---|---|---|
| Enquiry received | Channel, receipt time and necessary callback facts | Apply the firm's routing rules |
| Alert delivered | Delivery result for the intended recipient | Wait for explicit staff acceptance |
| Staff member accepts | Named person and acceptance time | That person determines the next action |
| No acceptance | Visible pending state and elapsed time | Use the firm-approved escalation route |
| Contact attempted | Attempt and outcome recorded by staff | Follow the approved next step |
Set escalation timing with the firm. A timer can expose an overdue action; it should not invent a service promise or decide that an unacknowledged enquiry has been handled.
Separate urgent intake from ordinary follow-up
An urgent police-station contact and a routine request for a future appointment should not share an indistinguishable queue. Give staff the original message, reported location, callback route and the reason the route was chosen. A broad category is not a legal assessment of urgency.
If a caller cannot safely receive voicemail, carry that instruction into the task shown to the recipient. In a fictional failure exercise, have the main recipient decline the task. Check that it stays open, reaches the agreed backup and records who ultimately accepted it.
Before buying criminal-law intake software, ask whether the current telephone and matter systems already support this handover. Evaluate the complete route; a delivered notification alone does not establish that it works.
Use AI only where it adds a checkable step
Straightforward routing may need only rules. AI might propose a short internal summary from permitted input, but staff should be able to see the original message and correct it. An uncertain classification should not suppress an urgent route.
Do not let generated text confirm representation, promise attendance or provide case-specific advice. Approved acknowledgements should accurately explain the firm's process and avoid presenting receipt as acceptance.
Rehearse failure before launch
Use fictional enquiries to try an invalid number, a full mailbox, an unavailable recipient, a duplicate message and a caller who cannot safely receive voicemail. Confirm the pending task remains visible and staff can take over manually.
Measure receipt-to-acceptance and receipt-to-first-attempt separately. Review unanswered tasks and routing corrections individually. A faster acknowledgement is not evidence of a faster human response.
The general enquiry ownership guide provides the wider state model. The legal hub connects this first handover with later document preparation and firm operations.