How LegalBook works
One record from a ringing phone to the owner’s dashboard. Each step below is a part of the product; where a step depends on something not available yet, it says so.
§ 1Your number
Your number forwards into LegalBook.
Callers keep the number on your website, your cards and your reviews. The product models four ways to connect it.
Live phone service: not available yet
The number setup is built. Live calls and text messages run through a carrier connection that is not certified yet, so live phone service is in early access.
§ 2Routing
Your rules decide where every call goes.
A routing policy reads business hours and holidays, the caller’s language, whether they are a new prospect or an existing client, the office and the urgency. Overflow and after-hours behavior are part of the same policy.
- Policies are versioned: edit a draft, simulate it, then publish
- The previous version stays on record
- Recording, disclosures and caller ID are policies too, and recording is off until you turn it on
- Blocked numbers and emergency handling are configured by your firm
§ 3Reception
Reception and intake.
The receptionist accepts the call in the browser and sees your firm’s identity, the caller’s match and their matters, open requests and the playbook for the call. A receptionist serving several firms never asks which firm the caller dialled.
During the call
- Warm transfer to an attorney or team, with the caller returned if nobody answers
- Callbacks with recorded attempts, and voicemail in the same queue
- Text messages with consent and opt-out
- Notes, a disposition and proposed follow-ups at wrap-up
New prospects
- Intake questionnaires in English and Spanish
- Conflict searches, decided only by an attorney
- Flagged answers route the intake to an attorney
- Appointments booked from the call
§ 4Case operations
Every task becomes a work item.
A document to validate, a form to prepare, a client to follow up, an attorney review: each one is a work item with a queue, a service-level clock, the actions the worker is allowed to take, and an escalation path. QA samples completed work, and rework goes back with the findings.
§ 5Attorneys
The attorney exception queue.
The attorney sees the gates, decisions and escalations the firm’s rules send to a lawyer, and nothing else: reviews, decisions, conflict and intake approvals, deadlines to verify and escalations. Each has one-tap actions, and it works on a phone.
§ 6Owners
The owner dashboard.
Calls and response times, open work by service level, workload, QA trends, attorney leverage and capacity, computed from what actually happened in the product.
Owner dashboard
IllustrationCalls answered and missed
Speed to answer
Open work by service level
Workload by attorney
QA trend
Attorney leverage
Shapes only. The dashboard shows your firm’s own figures, computed from what happened in the product.
§ 7Clients
The client portal.
Clients see their tasks, uploads, messages, appointments and milestones written in client-safe language, in English or Spanish. Internal notes, QA data, AI drafts and privileged material never reach the portal.
§ 8The people
Where the people come from.
LegalBook is built for a shared workforce: trained workers with skills and languages, authorized firm by firm, who can serve several firms without ever crossing a firm’s walls. Repeat work returns to the same people where it can, so callers meet continuity rather than a call center. A firm’s own staff work in the same system.
- In product
Workers with skills and languages, authorized firm by firm, who serve several firms without crossing a firm’s walls.
You practice law. We run the operating system around you.
See how LegalBook would run your front office and case operations, with a plain account of what is available today and what is not.
LegalBook is not a law firm. It gives no legal advice and forms no attorney-client relationship. Your attorneys supervise all legal work.