Round robin solves one routing question: who is next in line? A multi-office, multi-practice law firm has to answer harder questions first. Is this an existing client? Does the request require immediate escalation? Which practice should review it? What location facts are known? Can the firm support the requested language and channel? Who has appropriate capacity? What happens when no rule resolves the request?
Lead routing is an ordered policy for those decisions. Software can execute the policy, but the firm has to define the priority, evidence, authority, and fallback.
The goal is a reasoned destination with accepted ownership. A route does not decide legal merit, establish jurisdiction, resolve a conflict, or create representation. The firm’s lawyers define those decisions and the information needed for them.
Start with a routing constitution
Before building rules, write five short commitments:
- Preserve the request. Keep what the person actually asked for and the original source evidence.
- Apply higher-priority protections first. Existing-client and attorney-defined urgent, sensitive, or conflict-related paths should not be overridden by convenience.
- Route uncertainty to review. Missing or overlapping facts are not an automatic decline.
- Require acceptance. A notification or queue assignment is incomplete until a person or team accepts the next action.
- Make failure visible. No match, full capacity, absent owner, and failed transfer need owned exception paths.
These commitments let practice leaders review the design without reading automation code.
Put the rules in an explicit order
A workable sequence may look like this:
- Identify existing-client, active-matter, opposing-party, vendor, referral-partner, or other approved service paths.
- Apply attorney-defined urgent, sensitive, or special-review escalation.
- Identify the likely requested service and any overlapping-practice review.
- Collect the minimum attorney-approved location or jurisdiction facts required for routing.
- Apply supported language, accessibility, and channel requirements.
- Identify recipients eligible for that combination.
- Allocate among eligible recipients using capacity and coverage.
- Require acceptance; retry or escalate if acceptance does not occur.
- Send unresolved records to a named review queue.
This is an operating example, not a universal legal sequence. The firm’s lawyers and practice leaders should approve its own order. The key is precedence: a later “nearest office” or “lowest workload” rule must not silently override an earlier protection.
Separate routing facts from legal conclusions
Use only facts the routing layer is authorized to evaluate. “Caller selected probate” may support a preliminary queue. It does not establish the proper practice, venue, jurisdiction, legal merit, or absence of conflict.
For location, distinguish:
- caller’s current location;
- residence or business location;
- event or transaction location;
- court or agency named by the caller;
- office requested; and
- device or inferred location.
An IP address or nearest-office lookup should not stand in for the facts the firm requires. Mark missing facts as unknown and route them for clarification.
Build the matrix in plain language
Configure software only after owners approve a table like this:
Scroll sideways to review every column.Each row is shown as a labeled card.
| Priority condition | Required evidence | Primary route | Acceptance rule | Fallback |
|---|---|---|---|---|
| Existing client asks about active matter | Identity and matter/team match under approved process | Existing-client service path | Receiving team accepts | Staff review if relationship uncertain |
| New request clearly matches one practice | Person’s request plus approved minimum facts | Practice intake queue | Eligible owner accepts | Covering practice owner |
| Request may span two practices | Overlap reason recorded | Cross-practice review owner | Reviewer records direction | Intake supervisor escalation |
| Supported language requested | Preference recorded; support available for this stage | Approved language-capable path | Recipient confirms capability | Human assistance under coverage plan |
| Appropriate office has no current capacity | Practice/location eligibility already established | Approved overflow among eligible recipients | Overflow owner accepts | Capacity exception owner decides |
| No rule resolves request | Uncertainty reason | Review queue | Named reviewer accepts | Timed escalation to supervisor |
Version the matrix. Every record should show the version and rule that produced the assignment.
Work through six hard scenarios
1. Wrong-office call
A caller reaches Office A but describes a service handled through Office B. Preserve the initial record and conversation. Apply the firm’s approved practice and location review. Transfer the record with a reason and next action; do not make the caller start over or create a second inquiry solely because another office owns the step.
2. Overlapping practices
A business owner’s request may involve both employment and commercial issues. Route to an approved cross-practice reviewer. Avoid letting a form selection decide which legal team should accept it.
The firm supports Spanish during staffed hours, but an inquiry arrives after hours. The route should use accurate language about the available next step, create accepted follow-up ownership, and avoid pretending immediate language-capable review exists.
4. Existing client uses a campaign form
The form source remains useful marketing evidence, but the contact should enter the approved existing-client path once identified. The system should not report the submission as a new eligible inquiry or send a new-prospect nurture sequence.
5. Recipient is present but overloaded
Capacity allocation runs only among recipients already eligible for the request. If no appropriate capacity exists, route to a named capacity owner. Do not silently send work to an unsuitable office to protect a response-time metric.
6. No rule matches
The record enters a visible review queue with the unknown fact, current age, and next action. “Other” is a category, not an owner.
Define capacity in units the team understands
Raw record counts are a weak proxy. One inquiry may need a brief callback; another may require language coordination, attorney review, or several scheduled actions.
A firm can start with simple workload points:
- 1 point: one clear contact action;
- 2 points: multiple attempts, scheduling, or routine coordination;
- 3 points: cross-practice, language, or supervisor review;
- separate protected route: attorney-defined urgent or sensitive work.
These are hypothetical planning units, not staffing benchmarks. Compare the points with observed handling work and revise them. Staff should be able to flag when the score misses reality.
Capacity decides among eligible destinations. It should never override the firm’s higher-priority handling rules.
Make acceptance and retry explicit
For every route, specify:
- assigned destination;
- person or team authorized to accept;
- acceptance event;
- time or condition for nonacceptance;
- retry destination;
- maximum automated attempts;
- final exception owner; and
- message to the prospective client if the expectation changes.
Suppose a new inquiry reaches the business-law queue at 3:12 p.m. The assigned owner has until 3:27 to accept under the firm’s example policy. At 3:27 it offers the work to a covering eligible owner. At 3:42, if still unaccepted, it escalates to the intake supervisor. The intervals are fictional; each firm should set them from its coverage and risk decisions.
Avoid endless bouncing. After a defined number of failed assignments, a human owns resolution.
Preserve one record through every transfer
Carry the inquiry ID, original source, requested service, known facts, unknown facts, contact history, current stage, route reason, accepted owner, next action, and rule version. Limit detail by role and purpose.
Do not create a new marketing inquiry at each office. Do not overwrite the original source when a staff member reclassifies the request. Do not expose a full prospective-client narrative to teams that need only an operating category.
The technology-stack guide provides broader system-ownership context. JD-101, the companion data article, goes deeper on identity, event, retry, and reconciliation rules.
Test rules before and after every material change
Create fictional test records for:
- existing and new clients with similar names;
- missing, conflicting, and corrected location facts;
- overlapping practices;
- default and supported non-default languages;
- after-hours and holiday coverage;
- full capacity;
- absent owner and rejected assignment;
- duplicate contact event;
- failed integration and replay; and
- no-match review.
Record the expected rule, destination, acceptance, fallback, preserved fields, and reporting outcome. Then compare the observed result. Re-run the whole suite when a rule changes; a new office shortcut can break an existing-client path elsewhere.
Review routing as an operating decision
Use a weekly exception report with:
- unassigned inquiries;
- time to accepted ownership;
- repeated and corrected transfers;
- no-match and ambiguity reasons;
- capacity exceptions;
- records sent to the wrong practice or office;
- inquiries asking for unsupported service or language paths; and
- sampled caller experience.
Show counts, rates with denominators, and examples. A transfer is not inherently a failure; cross-practice review may be the correct route. A low transfer count can be bad if staff force ambiguous work into the first selected practice.
Send patterns upstream. Repeated “wrong practice” routes may reveal unclear website language or form choices. Marketing can inspect that message. Practice leaders must still define the actual boundary.
The routing packet to approve
Before launch, require one versioned packet containing the routing constitution, ordered rules, plain-language matrix, eligible-recipient list, capacity method, acceptance/retry logic, exception ownership, test cases, and reporting definitions.
If the firm’s current routing spans marketing forms, call tracking, several offices, a CRM, and case software without that packet, bring the rule exports, office/practice map, ten anonymized exceptions, and capacity view to a JurisOS conversation. Juris Digital can help map the operational and reporting problem into a proposed scope. The firm’s lawyers retain legal decisions, and the proposal should define actual systems, implementation, fees, and responsibilities.
Last updated:
