How to build a voice agent for a law firm
Treat the firm as a client brief, not a prompt. Map its calls, write the rules, check compliance and plan for the busy hour. Then sell the same build to the next firm.
Angel’s Tuesday, 8 AM to 10 PM
Story example. Shaded: after hours.
A firm loses clients on the phone
Angel runs a family law firm in Toronto. Two lawyers, one assistant, one phone line.
When she is in court, the assistant answers. When the assistant is at lunch, nobody does. After 5 PM, calls go to voicemail.
People who need a family lawyer rarely leave a message. They call the next firm on the list.
This guide shows how to build the agent that answers those calls, and how to sell it to firms like hers.
One week of Angel’s calls
- New client asking for help 38%
- Existing client wanting an update 27%
- Courts, lawyers and other firms 14%
- Bills and payments 9%
- Sales calls and spam 8%
- Urgent: safety risk, hearing today 4%
Story example. Your firm’s mix will differ.
Listen before you build
Most voice agents go wrong because the builder starts with the prompt. Start like a business analyst instead.
Sit with the person who answers the phone for a day. Write down every call: who called, what they wanted, what happened next.
By the end of the week you have a list of call types and how often each one comes in. That list is your spec.
The smallest row matters most here. Urgent calls are rare, and they are the ones a firm can’t afford to miss.
Call type to job
- New client Intake questions, conflict check, book a consult
- Existing client Take a message, give a callback time
- Courts and lawyers Take a message for the right lawyer
- Bills Send the payment link by text
- Spam End the call politely
- Urgent Hand to the on-call lawyer now
Every call: the agent never gives legal advice.
Give each call type one job
Each row in the list becomes a rule the agent follows. Keep the rules plain and exact.
New clients get intake questions and a consult on the calendar. Existing clients get a message taken and a callback time. Anything urgent goes straight to a person.
Then add one rule above all the others: the agent never gives legal advice. It collects facts and books time with a lawyer.
Agent brief: Angel’s firm
Signed offMust
- Say the call is recorded
- Run the conflict check
- Book consults in open slots
- Read back names and numbers
Never
- Give legal advice
- Quote fees beyond the list
- Confirm who is a client
- Promise an outcome
Hand off
- Emergency custody order
- Safety risk
- Court date today
- Caller asks for a person
Write the brief before the prompt
Put the rules in a one-page brief the lawyer can read and sign. Three lists: what the agent must do, what it must never do, and when it hands the call to a human.
The lawyer knows her firm. You know the agent. The brief is where the two meet.
It is also what you test against later, and what you point to when the firm asks for a change.
New client intake
- 1Caller’s name and number
- 2The other party’s name
- 3Conflict check against the firm’s client list
CLEAR
Short summary, then book a consult
MATCH
Polite close. A lawyer calls back.
The conflict check comes first
A firm can’t take a client whose opponent it already represents. So intake asks for the other party’s name before it asks for the story.
The agent passes both names to a tool that checks the firm’s client list. On a match, it thanks the caller and says a lawyer will call back. It never says why.
Order matters. Asking for the story first puts confidential facts from the wrong person into the firm’s records.
Bring these answers to the first meeting
- Where call data lives. On servers the firm controls
- Who can read transcripts. Only the people who need to
- Recording notice. In the first sentence of every call
- Legal advice. Never. The agent books a lawyer.
- Urgent calls. Handed to a person at once
- How long data is kept. Set with the firm, in writing
A checklist for the conversation, not legal advice.
What the lawyer will ask about compliance
Lawyers read the fine print. Have the answers ready before the first meeting.
Confidentiality. Call audio and transcripts hold privileged facts. Keep them on servers the firm controls, and limit who can read them.
Recording. Say the call is recorded, and why, in the first sentence. Canada allows one-party consent, but privacy law still expects notice. Some US states need every party to agree, so set the greeting by where callers are.
Advice. The lawyer stays responsible for the work. Give her the transcripts and a way to change the rules. The firm’s law society has the final word on all of this.
Test calls, run after every change
- “Should I sign this agreement?” Declines, books a consult
- Gives a name that is already a client’s opponent Polite close, lawyer calls back
- Calls at 11 PM about an emergency custody order Hands to the on-call lawyer
- Talks over the agent, upset Stops, listens, repeats back
- “Can I talk to a real person?” Hands off at once
Test it like a nervous caller
Before go-live, call the agent the way real people do. Upset, interrupting, half the facts, a bad line.
Write a test call for every line in the brief, plus the hard ones: a caller who wants advice, an opponent posing as a client, a crisis at night.
Run them after every change. When a test fails, fix the rule, not the test.
How many calls at once?
1
Calls at once
2
Plan for
1
Servers
Plan for twice the busy hour. 16 calls per server.
Plan for the busy hour, not the day
Calls don’t arrive evenly. Monday mornings and lunch hours bring bursts, and every call in a burst needs its own agent at the same moment.
Work it out: calls in the busiest hour, times the average minutes, divided by 60. That is how many calls run at once. Double it for headroom.
One server goes a long way. In our load test on AWS, one c7i.xlarge held 16 calls at once with a median reply of 0.6 seconds, and refused new calls at 32. A small firm needs a fraction of it.
Treat that as a starting point, not a promise. Your models, voices and call length change the number, so load test your own setup before you sign a firm.
100 calls at once
Mahimai Labs load test, AWS c7i.xlarge.
One install, many firms
Once the agent works for Angel, the same build works for the next firm. Each firm is its own client project, with its own number, brief and calls.
Plan servers on the busy hours across all your firms, not on their daily totals. Even 100 calls at the same moment fit on about 7 servers.
The analyst work changes from firm to firm. The agent underneath stays the same.
Margin on one firm, per month
Example numbers. Put in your own.
Run it as a business
Firms pay for answered calls, not for software. Price by the minute or by the month, and bill each firm from your own Stripe account.
Your cost is the models, the phone line and the servers. Your price is what an answered call is worth to the firm. The gap is your margin on every minute.
Charge a setup fee too. The listening, the brief and the test calls are where the firm sees the value first.
Your first week
- 1A day on the firm’s phone
- 2The call list and the brief, signed
- 3The agent, built from the brief
- 4Test calls, then go live
Start with one firm
Pick one firm you know. Spend a day on its phone. Write the brief. Build the agent from it.
ShipVoice Pro gives you the agent, the client console, billing and phone numbers, already wired. You bring the firm.