A tree service phone carries two kinds of call that look identical for the first ten seconds. “There’s a tree down” might mean a maple across a back fence that can wait three weeks, or a limb resting on a service drop that could hurt somebody in the next ten minutes. The caller usually cannot tell you which one they have — that is why they are calling — and the sorting question is one almost no generic answering script asks.
The rest of the line looks nothing like the emergency. Most tree revenue is planned work: removals booked weeks out, pruning, stump grinding, lot clearing — jobs that get estimated on site, scheduled around crew and crane availability, and won or lost on whether the estimate visit actually got booked while the homeowner was still deciding.
For transparency, since it shapes the framing: Reign AI builds an AI receptionist on human-grade voice AI, which is one of the options weighed here. The page is written to stay useful to an operator who reads it and chooses differently.
The one question that sorts the line
Is anything touching a wire?
Every intake flow in this trade should fork on that question, asked early, and the fork it opens is not a scheduling lane — it is a safety script. A tree or limb in contact with a power line can energise everything it touches, including a chain-link fence forty feet away, and the correct instruction to the caller is the same every time: stay away from it, keep everyone else away from it, and call the utility. The tree company’s turn comes after the line is cleared.
This is worth dwelling on because it is the clearest example on this site of why “answering the phone” and “answering the phone correctly for the trade” are different products. A human answering service working from a generic contractor script will cheerfully book the energised-fence caller for Thursday. An AI agent will do exactly the same thing — unless someone who knows the trade configured the fork. The technology does not supply the judgement; the configuration does.
The same discipline applies one step down the severity ladder. A tree on the house is not a utility call, but it is also not Thursday’s booking: it needs tarping-and-mitigation questions and a same-day look. A tree near the house that has stood dead for two years is a normal estimate. The facts that separate these — contact with wires, contact with structure, fresh movement, what is underneath — are exactly the kind of checklist an agent asks in the same order on every call, storm week included.
Storm week, and why it is different from a roofer’s
Tree companies share storm week with roofers — the same wind event fills both phones — and the roofing page works through what that spike does to call coverage. The dynamics rhyme but the mix differs in one way that matters for phone configuration: a roofer’s storm calls are mostly quotes with a few emergencies buried in them, while a tree company’s storm calls include a real hazard fraction, and the hazards are the ones where a wrong answer has physical consequences. The busiest week of the year is exactly the week the sorting question earns its place.
Work through the volume honestly, with every assumption stated so you can substitute your own:
- A wind event crosses your area overnight. Say 40 calls arrive over the next three days — a figure a two-crew outfit would recognise, and one you should replace with yours.
- Every crew is cutting. Say 12 calls get answered live, mostly from the truck.
- Of the other 28, say 6 leave voicemail. The rest ring the next company on the list, because a homeowner with a tree on the garage is not waiting for a callback.
Most of those 28 were never your jobs — some are outside your area, some want a price you would not take the work at, and honest arithmetic says so. But storm work is the highest-margin week in the trade, and losing the callers you never heard from is the expensive version of losing. Those are worked figures from stated assumptions, not a claim about your business. If you want the number for your own shop, the method in what missed calls actually cost transfers directly: swap in your average removal value and a realistic storm close rate.
What tree service intake needs to capture
- Contact with wires — first, always. See above. The fork everything else hangs off.
- What the tree is on or over. House, garage, vehicle, fence, nothing. This is the severity ladder and the equipment question in one answer.
- Whether it has moved recently. A lean that appeared this week is a different object from a lean that has been photographed by the street-view car three years running.
- The address and where the tree stands on the lot. Front-yard access and a backyard behind a pool fence are different jobs with different machines and different prices.
- Rough size, in landmarks rather than feet. “Taller than the house” and “I can get my hands around the trunk” are honest data; a caller’s guess in feet is not.
- Why now. Insurance letter, sale closing, neighbour dispute, storm damage, or it finally looks scary. Each one carries its own deadline, and the deadline is what your scheduler actually needs.
- Whether they want the wood and the stump handled. It changes the quote and the crew, and asking it on the first call marks you as the company that knows its trade.
An agent asks all of these in the same order on the fortieth storm-week call. A crew member answering from a bucket asks whichever two come to mind, which is not a criticism of the crew member.
How the options hold up
| Crew answering | Human answering service | AI receptionist | |
|---|---|---|---|
| Storm-week volume | A fraction | Queued | All at once |
| The power-line fork | Yes — they know the trade | Only if scripted, rarely is | As configured |
| Hazard vs booking sorting | Well, when reachable | Message-level | As configured |
| Booking the estimate visit | Yes | Sometimes | As configured |
| Cost during the spike | Lost cutting time | Rises with volume | Flat |
The pattern across these columns is the one this whole page turns on: in tree service the scarce thing is not phone coverage, it is trade judgement applied at the phone. A crew member has it and no time; a generic service has time and none of it; an AI agent has whatever was configured into it. The four-way comparison sets out the general trade-offs; for this vertical, weight the rows about configuration heavily. The broader case for coverage outside working hours is the after-hours guide — read it with this trade’s caveat from the FAQ: capture is the value at night, not dispatch.
Adjacent-trade note: landscaping companies field tree-work requests constantly and mostly turn them away — the landscaping page treats declining out-of-scope work as a configuration skill, and it is the mirror image of this page. If you run both lines of business, the two intakes should know about each other.
What AI answering does NOT solve for a tree company
- It cannot assess a tree. Species, decay, lean, load, targets — that is the estimator’s entire job, and it happens standing under the tree. The agent’s job ends at collecting an accurate description and booking the visit.
- It cannot price. See the FAQ. Anyone who has watched a “simple removal” turn into a crane job knows why phone prices in this trade are either padded or wrong.
- It is not an emergency service. The power-line fork routes people away correctly, but the thing that makes the site safe is the utility and your crew — the phone just has to not get it wrong.
- It does not add crews or crane days. If storm week ends with forty well-captured leads and capacity for fifteen jobs, answering has converted lost calls into a triage list. Better problem, still a problem.
- It will not know that you stopped taking stump-only jobs, or that the crane is booked out three weeks, unless somebody configured and updates that.
- A badly-configured agent is worse than voicemail in this trade specifically, because the failure mode is not a lost lead — it is confident scheduling of a call that needed the safety script.
Before you buy anything, run this test
Call whatever you are considering and behave like a storm-week caller:
- Say a big limb came down in last night’s wind and it is resting on the wires to the house. The only acceptable response starts with staying away from it and the utility — anything that books you for Thursday is disqualifying.
- Say a tree fell on the garage roof. Does the handling change from the wires call, and does it change from a routine estimate?
- Ask what removing a large maple costs. Does it hold the line on site-visit pricing or invent a range?
- Ask for a trade you do not offer — lot clearing, firewood delivery — and see whether it declines cleanly.
Then read what arrived on your end. The notification is the product: address, what the tree is on, wire contact yes or no, movement, why now. If that summary would let your estimator sequence tomorrow morning from their phone, it works. If it says “caller has tree issue,” it does not — and in this trade the gap between those two summaries is where both the money and the safety live.
Common questions
Can an AI receptionist quote a tree removal over the phone?
No, and in this trade the reasons are physical rather than commercial. A removal price depends on height, lean, what the tree can fall on, what equipment can reach it, and whether it comes down in pieces or in one cut — none of which a caller can assess and all of which change the day rate. The workable configuration says plainly that pricing follows a look at the tree, captures what the caller can describe accurately (location, what it is near, why now), and books the estimate visit. Callers in this trade already expect that; the ones who push hard for a phone number are usually price-shopping every listing anyway.
What should it do when a tree is on a power line?
Stop being a booking call and become a safety call. The configured line is short: do not approach the tree, do not touch anything in contact with it, and call the utility — a line brought down or loaded by a tree is the utility's emergency before it is a tree company's job. Capturing the address and calling back after the utility clears it is the correct business outcome. An answering setup that treats this caller as a lead to be scheduled has been configured by someone who has not worked in the trade.
Can it tell a hazard from a removal that merely feels urgent?
It can ask the questions that separate them, which is most of the job: is anything in contact with wires, is the tree touching or over the house, has it moved or cracked since the caller first noticed, is anything beneath it that cannot be moved. A leaning dead ash that has leaned for three years is a booking; the same tree with fresh root heave after a storm is today's problem. The agent does not make that judgement — it collects the facts in the same order every time so the person who does make it can do so from a text summary instead of a callback round.
Is after-hours coverage worth it for a tree company?
Less than for a plumber, and it is worth being honest about why: most tree emergencies at night are really utility or insurance calls first, and most other after-hours callers are happy to be booked for a daytime estimate. The realistic value is capture rather than dispatch — the storm-night caller whose tree is on the garage books with whoever answered, even though nobody is cutting anything before daylight. If your area gets real storm traffic, that capture window pays; if it does not, daytime overflow is the honest case.