Key takeaways
- Order the branches by risk: represented-person check and emergencies first, practice area and jurisdiction next, conflicts before any detail.
- Florida's ethics guidance limits nonlawyer intake to facts, with legal questions referred to a lawyer, so every leaf of the tree ends in a fact-gathering step or a handoff[1].
- Language is a branch, not an afterthought: 22% of US residents aged 5 and older speak a language other than English at home[2].
- Test the tree with scripted calls every quarter and log which leaf each real inquiry reached.
What a decision tree fixes in a multi-practice firm
A firm with one practice area can run intake from a single script. Add family law, estate planning and personal injury under one phone number and the same front-desk person has to decide, in the first two minutes, which questions to ask, who should hear about the call and how fast. Without a written tree, those choices depend on who picks up. One coordinator sends every injury call to the senior partner; another books it for next week. The tree removes that variation by turning judgment calls into a short series of yes-or-no questions with a fixed outcome at each leaf.
Most US law offices are small: 71.8% had fewer than five employees in 2023[3]. In a small office the person answering is often also billing, filing and scheduling, so the tree has to be short enough to run from memory and clear enough that a part-time hire gets the same result as the office manager.
The five branches, in the order you ask them
Sequence matters more than the number of questions. Put the branches that create ethical or safety risk first, because a call that ends early should still have passed through them.
Branch 1: Is the caller already represented on this matter?
Ask before any detail: "Do you already have a lawyer helping you with this?" If yes, the tree ends in a short, scripted path: take name and number, explain that the firm will check whether it can speak with them, and hand off to an attorney. Florida's ethics guidance on intake chatbots suggests screening questions that limit communications when the person is already represented[4], and the same logic applies to human staff.
Branch 2: Is there an emergency or a deadline in days?
Physical danger, an arrest, a hearing this week, a protective order, a statute deadline the caller mentions. A yes skips the queue and goes to the urgent route with a named backup. Danger to life goes to 911 first.
Branch 3: Which practice area does this belong to?
Use plain-language triggers, not legal labels. "Were you hurt?" and "Is this about a divorce, custody or support?" work better than "Is this a tort matter?" Allow "more than one" and "not sure" as answers.
Branch 4: Where did it happen, and where does the caller live?
Jurisdiction decides whether the firm can take the matter at all. Ask for state and county. Out-of-state matters route to a referral path, not a dead end.
Branch 5: Who else is involved?
Collect the names of opposing parties, spouses, employers or insurers for the conflict check before taking a narrative. No story until the names clear.
Every leaf ends in one of four outcomes: book a consultation, urgent handoff, refer out, or decline with a written note. If a leaf does not end in one of those, the tree is unfinished.
Branch logic by practice area
| Practice area | Trigger questions | Urgent if | Outcome and owner |
|---|---|---|---|
| Personal injury | Were you or a family member hurt? When? Was a vehicle, workplace or property involved? | Incident within days, ongoing treatment decisions, insurer pressing for a statement | Same-day attorney callback; intake coordinator books |
| Family law | Is this about divorce, custody, support or protection from someone? | Safety concern, protective order, hearing date set | Urgent route to family attorney; else consultation within the week |
| Estate planning | Are you planning ahead, or has someone passed away or lost capacity? | Recent death with assets at risk, hospitalized family member | Planning calls book normally; probate or capacity calls go to the attorney the same day |
| Not sure / multiple | In a sentence, what happened and what do you want to change? | Any deadline the caller names | Coordinator summarizes; attorney decides routing within one business day |
Keep trigger questions factual. Florida Ethics Opinion 88-6, which the Florida Bar cites as especially useful for intake, says nonlawyers conducting an initial interview must identify their nonlawyer status, limit questions to factual information and refer legal questions to the lawyer[1]. A trigger question such as "Do you think you have a case?" invites an opinion from both sides. "When did it happen?" does not.
Language and accessibility branches
Decide what happens when the caller is more comfortable in another language before you need to. More than one in five people aged 5 and older in the US speak a language other than English at home[2], and about 61% of them speak Spanish[5].
- Spanish 61%
- All other languages 39%
Source: U.S. Census Bureau, 2025[5]
Show the data
| Item | Value |
|---|---|
| Spanish | 61% |
| All other languages | 39% |
- If you have a bilingual intake person, route by language at the very first prompt, before Branch 1.
- If you do not, write the fallback: an interpreter line, a callback from a named bilingual attorney, or a referral, and the exact words staff use to offer it.
- Log the preferred language as a field so reporting shows how often the branch fires.
Example: one call through the tree
Example: A caller says her father fell in a grocery store last Tuesday and the store's insurer has phoned twice. Branch 1: no lawyer yet. Branch 2: the insurer wants a recorded statement, which the firm treats as urgent for injury matters. Branch 3: personal injury, with a possible estate-planning question later because her father is elderly. Branch 4: the store is in the same county. Branch 5: she gives the store's name and her father's name for conflicts. Outcome: urgent handoff to the injury attorney with a same-day callback, and a note that the family may also ask about powers of attorney.
The coordinator never says whether the claim is strong, never estimates a recovery and never tells her what to say to the insurer. The tree got the right lawyer on the phone the same afternoon, which is the whole job.
When intake is automated, the tree is the instruction set
If an answering service, chatbot or AI system handles part of intake, the tree becomes its instructions. California's State Bar names autonomously facilitating client intake as an example of agentic AI and says a lawyer's supervision must match the system's level of access and autonomy[6]. Write the tree so that any branch a system cannot handle safely ends in a human handoff. If you use Ava for overflow or after-hours calls, it follows the intake questions and escalation tree your firm approves, so this document is what it works from.
Five mistakes that break a tree
- Asking for the story first. A caller who has told you everything before the conflict names clear has given the firm information it may not be able to use or ignore. Names first, narrative second.
- Branches with no owner. "Urgent" means nothing unless the tree names who gets the call, by what route, and who covers when that person is in court.
- Practice-area labels the caller does not use. Callers say "my ex", "the accident" or "Dad's house", not "domestic relations" or "probate". Write triggers in their words.
- No "not sure" exit. Forcing a caller into the wrong branch is worse than parking the call with a summary for an attorney to route.
- A tree that only lives in one person's head. If the office manager is the only one who knows that immigration calls go to the Tuesday attorney, write it down before she takes a vacation.
A useful check: hand the printed tree to someone who has never worked intake and ask them to route three sample calls. Wherever they hesitate, the wording needs work.
Testing and maintaining the tree
- Write ten test scenarios that cover every branch, including one represented caller, one emergency, one out-of-state matter and one caller who answers "not sure" to everything.
- Have someone outside intake run them by phone and web form. Record which leaf each scenario reached and how long it took.
- Compare against the leaf you expected. Any mismatch is either a staff training issue or a badly worded trigger question; fix the wording first.
- Each month, sample real inquiries and tag the leaf they reached. A large "not sure" share means your triggers are too technical.
- Review the tree whenever the firm adds or drops a practice area, opens an office in another state or changes its urgent-call owner.
Keep the tree on one page. If it needs a second page, split the practice-area branch into its own sheet and leave the first five questions where everyone can see them.
Related reading: how call routing works across practice groups and a one-week intake audit.
Frequently asked questions
What is an intake decision tree?
A short, ordered set of questions that sends each new inquiry to a fixed outcome: book, urgent handoff, refer out or decline. It replaces individual judgment at first contact with a written rule the firm can test.
How many questions should the tree have?
Five core branches is enough for most firms: representation status, urgency, practice area, jurisdiction and other parties for conflicts. Practice-specific questions come after the tree has routed the call.
Can intake staff decide whether someone has a case?
No. Florida's guidance says nonlawyers doing intake should limit questions to facts and refer legal questions to the lawyer[1]. The tree routes; the attorney evaluates.
Where does the conflict check fit?
Collect the names of other parties before taking a detailed story, so a conflict can stop the conversation before the firm learns confidential facts it cannot use.
References
The Florida Bar (2024). Florida Bar Ethics Opinion 24-1 (opens in a new tab) โ
U.S. Census Bureau (2025). New Data on Detailed Languages Spoken at Home and the Ability to Speak English (opens in a new tab) โ
U.S. Census Bureau (2023). County Business Patterns 2023: U.S. detail file (cbp23us) (opens in a new tab) โ
The Florida Bar (2024). Florida Bar Ethics Opinion 24-1 (opens in a new tab) โ
U.S. Census Bureau (2025). New Data on Detailed Languages Spoken at Home and the Ability to Speak English (opens in a new tab) โ
The State Bar of California, Standing Committee on Professional Responsibility and Conduct (2026). Practical Guidance for the Use of Generative Artificial Intelligence in the Practice of Law (opens in a new tab) โ