Resources / AI assistants
A useful conversation starts with a clear boundary.
Plan a law firm chatbot around the questions it can answer, the information it needs and the moment a person should take over.

Decide what the conversation is for.
A website assistant can help a visitor understand whether the firm handles a particular service, find opening hours or reach a booking route. Those are different jobs from assessing a legal claim or telling someone what to do about an urgent deadline.
Write the purpose in a single sentence and list the questions it is permitted to answer. If the main need is to route five common enquiries, a carefully designed menu may do the job. An AI system should earn its additional complexity through a useful, testable capability.
Define answers and handoffs together.
| Visitor request | Appropriate design response |
|---|---|
| Do you offer this service? | Answer from the approved service catalogue and link to the relevant page. |
| How much will it cost? | Use approved fee information and explain when a quote requires review. |
| Can you guarantee my outcome? | Avoid outcome promises and offer the firm’s consultation route. |
| I have an urgent deadline. | Use an approved urgency message and direct contact route. |
| Here is my full case file. | Explain the appropriate secure channel and avoid unnecessary collection. |
| Your answer seems wrong. | Provide a simple route to a person and record the issue for review. |
Make the handoff real.
A button labelled “speak to a person” needs an actual destination. Define where the enquiry goes, what the recipient sees and what happens outside the firm’s staffed hours. A chat interface should not imply that someone is watching when no such service exists.
In a proposed pilot, a visitor might choose a service category, receive a short approved explanation and opt to leave contact details through the firm’s normal enquiry channel. The receiving team should get enough context to respond without the assistant inventing an assessment of the matter.
Test the awkward conversations.
Test unsupported services, unclear questions, fee requests, repeated messages, spelling errors and requests to ignore the assistant’s instructions. Include keyboard use, mobile screens and a failed network connection.
Use synthetic examples for early testing. Check the words displayed to the visitor as well as any records sent to a connected system. A friendly answer is not a successful result if the handoff disappears or the system records the wrong service.
Set a route to disable the assistant while keeping ordinary contact methods available. A narrow pilot with a reviewer is easier to correct than an unrestricted launch.
Measure completed journeys and corrections.
Track whether people reach the correct service page, complete a handoff and receive a useful response from the firm. Review unanswered questions and inaccurate answers as a source of maintenance work.
A high conversation count alone says little about enquiry quality. Equally, time saved should include the work needed to review conversations and keep the approved information current.
Compare the law firm chatbot service with AI agents and business automation. A chatbot handles a conversation; a connected workflow may also perform actions, which need their own permissions and checks.
Sources & further reading
Primary references checked on 6 September 2026.
Let's put your firm
in the conversation.
Bring your website, your priority practice areas and the work you want to make easier. We'll start there.
Book a strategy call Free 30-minute consultation

