AI Receptionist
Call Routing and Escalation Rules Every Law Firm Needs
An AI receptionist is only as good as its routing rules. The firms that get the most from the technology aren’t the ones with the most natural-sounding voice. They’re the ones that thought carefully about which calls go where, who gets interrupted and when, and what happens when something genuinely urgent comes in at midnight. This guide covers the call routing and escalation rules every law firm needs before putting an AI on the phones.
Start with your call types
Every law firm gets the same handful of call types, in roughly this order of frequency: new client intake, existing client calling about their matter, scheduling and rescheduling, other professionals (opposing counsel, courts, process servers), vendors and solicitors, and wrong numbers.
Each type needs a defined path. New client intake goes through the full intake script and books a consult. Existing clients get identified and routed to the handling attorney’s team, or get a status update if one is available. Scheduling goes to the calendar. Professionals get a professional message or a direct transfer during business hours. Vendors get a polite deflection. Wrong numbers get a quick goodbye.
Write these paths down before you configure anything. The routing rules are a business decision, not a technical one, and they should reflect how your firm actually wants to treat each caller.
The escalation ladder
Escalation is about urgency tiers, not just “transfer to a human.” Build three:
Tier 1: Handle now. The AI completes the task itself: intake, booking, status updates, messages. Most calls live here.
Tier 2: Warm handoff. The AI recognizes the call needs a person, stays on the line, and transfers with context: “I have Maria Lopez on the line regarding her custody hearing tomorrow.” The receiving person gets a summary, not a cold transfer. Use this for existing clients with matter-specific questions and professionals who need a substantive answer.
Tier 3: Urgent interrupt. The AI pages or calls the attorney directly, any time. Reserve this tier for a short, explicit list: a client with a hearing or deadline within 24 hours, someone in custody, a credible emergency related to an active matter, a court calling. Everything else waits. A well-designed after-hours escalation workflow is the difference between sleeping through the night and getting woken up for a wrong number.
Time-based routing
Your rules should change with the clock. During business hours, the AI can attempt warm transfers to staff who are actually at their desks. After hours, it shifts to intake-plus-message mode, with only Tier 3 calls breaking through to the on-call attorney.
Define “business hours” precisely, including lunch coverage and holidays. The most common routing complaint from law firms is the AI transferring to an empty office at 12:15 because nobody told it about lunch. Fallback chains handle the rest: if the first transfer target doesn’t answer, the AI tries the next one, then takes a detailed message, then confirms the message was received. No call should ever end in silence.
Attorney-specific rules
In a multi-attorney firm, routing gets personal. Each attorney has preferences: who takes their overflow, which matters warrant an immediate interruption, which clients always get through. Capture these per-attorney, and review them quarterly, because preferences change and nobody updates the phone system.
Also plan for absence. Vacations, trials, conferences: the AI needs to know who’s out and who’s covering. A shared “coverage calendar” the AI reads is simpler and more reliable than trying to update rules for every absence.
VIP and sensitive caller handling
Some callers need special treatment: major clients, referral partners who send you business, co-counsel. Give the AI a VIP list with instructions: these callers get a warm transfer attempt first, and if no one’s available, a personal callback commitment with a specific timeframe. The AI should never make a VIP feel like they’re in a phone tree.
Similarly, define how the AI handles callers who are upset, confused, or hard to understand. The rule should be simple: when in doubt, escalate to a human. An AI that keeps a frustrated caller in a loop is worse than no AI at all.
Test like a caller, not like an administrator
Before going live, call your own number and try to break the routing. Call after hours. Pretend to be an existing client with an urgent matter. Pretend to be a vendor. Call from a blocked number. Each test should produce the behavior you designed. Fix what doesn’t, then test again.
Repeat the test quarterly. Routing rules decay: staff change, hours change, the on-call rotation changes. A fifteen-minute test call every few months catches the drift before your clients do.
Routing isn’t glamorous, but it’s the skeleton everything else hangs on. Get the rules right, and the AI receptionist feels like the most competent front desk you’ve ever had. Get them wrong, and it’s a very polite way to lose calls.
I write the agents that run on clinic phone lines and inboxes: the conversation engine and the booking logic behind them, plus the integrations with Pabau, Fresha and Phorest. Everything here comes out of systems we have actually shipped, not a content plan.
