All use cases
Business

Legal intake (solicitors)

Triage enquiries, conflict-check, book consultations

High-street solicitors burn hours on initial-enquiry phone calls where most callers turn out to be a conflict, out of scope, or in need of a different practice area entirely. The intake assistant captures the basics in a strict order (caller name, DOB, postcode, other parties for conflict, brief matter description, practice area, urgency) so reception can do a proper conflict check before booking. Never gives legal advice. Knows when to flag urgent: police-station, eviction tomorrow, deportation imminent.

How it works

Here's what a real conversation with your Legal intake assistant looks like.

Legal intake

AI assistant

Got a letter from my landlord saying I've got two weeks to leave. What do I do?
This sounds urgent and I'm not able to give legal advice, but I can fast-track you to one of our housing solicitors today. To run the conflict check first, please can I take your full name, date of birth, postcode and your landlord's name? Was it a Section 21 notice or Section 8? I'll ring you back within the hour with a fee-earner you can speak to.

What you get

Strict capture order so conflict checks are possible

Practice-area triage (family, conveyancing, housing, employment, immigration, wills)

Urgent-matter detection with explicit fast-track language

Never quotes fees off-list, defers to the fee-earner

Legal-aid eligibility mentioned without promising it

The outcome

Reception spends time with qualified callers instead of triage. Conflicts spotted before any privileged information is shared. Urgent matters reach a fee-earner the same hour.

Set it up in 5 steps

1

Use the Legal intake template

2

Fill in firm name, practice areas, fee-earner contact emails

3

Upload your fee schedule and legal-aid policy

4

Set urgent-matter escalation rules to the right partner

5

Deploy on web only at first (WhatsApp is risky for privileged matter)

How each feature helps

These are the platform features that make this use case work. Each one plays a specific role in delivering results.

Knowledge sources

You give your assistant information to learn from. Upload documents, paste URLs or connect cloud folders. The assistant reads everything, breaks it into chunks and uses the relevant bits when answering questions.

Actions

Actions let your assistant do things in the real world. Send an email, create a support ticket, update a CRM record or call any webhook. You decide which actions need human approval before they run.

Forms

Sometimes a structured form works better than a free-text conversation. You build the form once with the fields you need and it works everywhere: in the chat widget, on a standalone page and in email follow-ups. Submissions feed into your inbox and can trigger actions.

Outcome analytics

Don't just count messages. Track what actually matters: leads captured, meetings booked, issues resolved, handoffs avoided and cost per outcome. You'll see which assistants drive results and which need attention.

Ready to build yours?

Start with this example and customise it to fit your organisation. You'll have a working assistant in minutes.