AI Receptionist for Tree Services: Costs and a Storm-Call Script

An AI receptionist for a tree service costs about $53 to $150 a month at 60 calls and $110 to $410 at 210 calls in a storm month. For storm callers it should ask first about danger, treat any power line as live, send people to emergency services, and promise a callback, never a crew time.

Storm months, not average months, set the bill. Storm calls run longer because of the hazard questions, and they arrive in bursts, so a plan billed per minute or in small per-call tiers can cost up to four times as much as a per-customer or large-tier plan for the same calls. Transfers matter as much as price: the plans that ring a person at 2am sit on higher tiers.

Follow me on Instagram@sagnikteaches

A quiet month against a storm month, priced on six plans

The table prices six receptionists from their own pages. A quiet month is 60 calls of about 3 minutes. A storm month is those 60 plus 150 storm calls of about 4 minutes, because each one runs through hazard questions: 210 calls and 780 minutes. Goodcall counts unique customers, so the table assumes 1.5 calls per customer, which is how its page equates 100 customers with about 150 calls. List prices in USD, receptionist only.

Connect on LinkedInSagnik Bhattacharya

Notes on the choices. Quo's call transfers are listed on its Business and Scale seats, not Starter, so the table uses a Business seat. Rosie's Professional plan at $49 lists no transfers, so the table uses Scale, which lists warm and live transfers. Smith.ai's free plan beats its $150 Pro plan at 60 calls. Jobber's figure leaves out the Jobber plan the add-on sits on, and Plus includes the Receptionist. For storm months the cheapest per call is Goodcall at about 53 cents and Quo at about 58 cents, while Smith.ai works out near $1.94 a call.

Subscribe on YouTube@sagnikteaches

For comparison, a human answering service is a different price class. Smith.ai's human plans list $300 for 30 calls, $810 for 90 and $2,100 for 300, with extra calls at $11.50, $10.50 and $8.50. A 210-call month on the 90-call plan comes to $810 plus 120 calls at $10.50, or $2,070. The tutorial on an AI answering service that never misses an emergency covers when that premium buys something, and the towing companies comparison prices the same choice for another night-call trade.

What each plan does at 2am: transfers and the limit

Price matters less than what the plan does when a caller says a tree is on the house. This table is what each vendor's pages state; any blank is a question for the vendor.

Two readings. If your on-call setup is one person's mobile, almost any plan with transfers will do, and the question becomes whether that person answers. If it is a ladder of three numbers, Rosie's waterfall transfer is the one built for it on paper; on the other plans you build the ladder from a transfer plus a text alert, as described below.

Four lanes for storm and routine callers

Before writing a script, decide how calls get sorted. Four lanes cover nearly everything a tree service hears, and every lane needs a different action from the receptionist.

Lane 1 is the one where the receptionist's job is to stop collecting job details. A caller who says a line is down and a child is outside needs one sentence and a hang-up, not an address read-back first. The rest of the script follows from that order.

A bad storm call, transcribed, and what the order of questions fixes

An illustrative transcript shows why the sequence matters. This is how a receptionist behaves when its script is a generic intake form with a greeting bolted on. R is the receptionist and C is the caller.

R: Thanks for calling [business name]. How can I help?
C: A tree's come down in the storm. It's across my fence and the cable line's hanging off it.
R: I'm sorry to hear that. Can I take your name and address?
C: [first name]. [address]. The line is sparking a bit.
R: Thank you. Roughly how big is the tree?
C: Huge. The kids are in the back garden.
R: And which way did it fall?

Every question was reasonable, and the call was still wrong. The receptionist asked for the address and the tree's size after the caller had said "sparking" and "the kids are in the back garden". Nothing told the caller to get the children away from the tree and the line, or to call emergency services. A caller in that state will answer whatever they are asked, so the script has to ask the right thing first.

With the script below, the call changes at the first "sparking". The receptionist stops the intake and says: "Please get everyone away from the tree and the line now, and keep them well back. Treat the line as live and don't touch anything it's in contact with. Call emergency services and your power company's emergency line. I'll take your number so a person can call you back." The address and the tree's size come afterwards, and only if the caller is still on the line. The bad transcript took the details of a customer; the good one protects a family first.

The storm script: fixed lines the AI repeats and never improvises

These are draft lines, written for you to edit. Have your safety lead and your insurer read them before they go live, and keep them as fixed text rather than letting the AI paraphrase. Each block is what the receptionist says, in the order it says it. Wording about power lines follows the guidance that power companies publish: treat any downed line, and any tree touching a line, as live.

0. AT ANY POINT IN THE CALL
If the caller mentions someone hurt, a fire, a gas smell, sparking or a line, stop the questions and go straight to block 2 (hurt, fire, gas) or the first half of block 4 (lines).

1. OPENING
"Thanks for calling [business name]. We're taking a lot of storm calls, so you're speaking with our virtual assistant. First: is anyone hurt or in danger right now?"

2. IF YES, OR IF THERE IS FIRE OR A GAS SMELL
"Please hang up and call emergency services now. When everyone is safe, call us back or text this number and a person will arrange a crew."

3. IF NO: CAPTURE THE CALLBACK FIRST
"Thank you. What's the best number to reach you, and the address of the tree?"
[Read both back. Calls drop in storms; this is the one thing to get before anything else.]

4. POWER LINES
"Is any power line or cable down, or touching the tree, the house or a vehicle?"
IF YES OR UNSURE: "Please treat any line as live. Stay well back, keep other people and pets away, and don't touch anything that's in contact with it. If anyone is in danger call emergency services, and call your power company's emergency line. We can't cut near a line until the power company has made it safe, but I'll take your details so you're on our list for afterwards."

5. STRUCTURES AND HANGING LIMBS
"Is the tree on a building or a vehicle, and is anyone inside?"
IF THE BUILDING MAY BE DAMAGED: "If you think the building isn't safe, please go outside and call emergency services."
"Is the tree or any large branch still moving or hanging? Please keep clear of anything hanging."

6. DETAILS
"Is it one tree or several? Is it blocking a road or driveway? Can a truck reach it, and are there gates, fences or pets we should know about?"
"Did the tree come from your property, and do you own the home?"
[Note the answer. Never comment on who pays.]

7. INSURANCE AND PHOTOS
"Do you plan to claim on insurance? I can note a claim number if you have one, but I can't say what your insurer will cover."
"If it's safe, text photos from a distance to this number. Please don't go near the tree or any line to take them."

8. CLOSE
"A person will call you back by [time]. I can't promise when a crew will arrive. If anything changes, or someone is in danger, call emergency services first."

Why the order. Danger comes before everything because nothing else matters if someone is hurt. The callback details come second, because a dropped call with no number is a lost customer and a lost chance to reach someone in trouble. Power lines come before the structure questions because the instruction to stay back changes what the caller does next. The photo line says "from a distance" because the receptionist can't see where the caller is standing.

The ownership question in block 6 covers an edge case that belongs with a person. A caller whose garage was hit by a neighbour's oak, or a tenant ringing about the landlord's tree, may not be the one who can agree to the work or the price. The receptionist only records the answer. Your office works out who authorises the job before a crew is booked, and where insurance is involved, who claims is a matter for the owners and their insurers, not for your phone line.

Seven things the receptionist must never do on these calls

1. Judge whether anything is safe. It can't see the site. It repeats fixed lines and nothing else.
2. Give do-it-yourself advice. If a caller asks whether they can cut it themselves, it repeats the safety lines and offers an assessment.
3. Promise a crew time. Storm queues move. Promise a callback window, not an arrival.
4. Quote a price for emergency work. A person discusses price once the hazard is understood. If your policy is that emergency work costs more than routine work, one fixed sentence saying so is fine.
5. Promise insurance cover. It notes the claim number and nothing more.
6. Ask anyone to go closer for a photo. Photos are from a safe distance or not at all.
7. Take card details. Payment is a later, human step.

The trial plan of twelve test calls is a good place to prove these seven before the first storm.

After-hours transfer: a ladder that ends in a text, not voicemail

A lane 2 call at 2am needs a person, and people sleep through rings. Build a ladder with a timeout at each rung and a text at the bottom.

1. Ring the on-call lead for 25 seconds.
2. If unanswered, ring the second on-call person for 25 seconds.
3. If unanswered, ring the owner for 25 seconds.
4. If still unanswered, send the summary text to all three at once and tell the caller a person will call back by a stated time.

Rosie's waterfall transfer does the first three rungs on its Growth plan. On plans without it, use the transfer for the lead and rely on the text for everyone else, and test it. The timeouts are my suggestion; your own mobiles and signal decide the real figures. Switch on the ladder only after you have walked through each rung by switching each phone off in turn, because the failure that matters is silence from the last rung.

The on-call text: what a person needs in ten seconds

When the receptionist alerts a person, the message should be readable on a lock screen. A filled-in version, with placeholders for the details:

LANE 2 | 02:14 | [first name] [number]
[address]
Oak across rear roof. Everyone out. Caller says no lines involved.
Road blocked: no. Truck access: side gate. Pets: dog, indoors.
Insurance: claim not made yet. Photos: asked for, from a distance.
Caller told: call back by 03:00. No crew time promised.

Notice what it contains. The lane comes first so the on-call person can triage from the notification alone. The line about power is the caller's statement, labelled as such: the receptionist cannot confirm that no lines are involved, and the text must not suggest it did. The last line records what the caller was told, so nobody phones back and contradicts it.

Routine calls: booking an estimate without pricing by phone

Lane 4 is most of the year. The receptionist should swap the storm script for a short intake: name, number and address; what the caller wants done (pruning, removal, stump grinding, a health check); how many trees, roughly how tall, and where they are; whether anything touches a building, fence or line; and whether the work is for a home, a landlord or a business. It then books an estimate visit and sends a text with the window and a photo request, from the ground and at a distance.

Keep price out of it. Tree jobs hinge on access, rigging and disposal, and a phone number given in the first minute becomes a promise. Say instead that a person will give a written price after the visit. The tree service estimate template picks up where this intake ends. Callers from commercial or estate accounts deserve a callback from the owner, so add a keyword rule for "property manager" or "estate" that sends them straight to a person.

What one saved storm job is worth against the plan

Run the numbers for an illustrative three-crew tree service, where a storm weekend brings 150 calls. The crews can handle about 25 jobs, so the problem is not volume but order: which callers get a person first, and whether anyone with a tree on a house is left on voicemail. Suppose an average storm job bills $1,800 and leaves $700 after crew pay, equipment and disposal.

The storm-month plans cost $110 to $410, and a quiet month $55 to $150. The extra cost of a storm month, say $200 above a quiet one, is covered by one saved job at $700 more than three times over. What the receptionist is actually buying you in a storm is sorted priorities: lane 1 and lane 2 callers in front of the queue, photos already on file for the estimator, and every caller told the same honest thing. If the AI catches even two jobs a year that would have gone to voicemail, $1,400 of gross profit covers a full year of a mid-range plan at about $760.

The caution runs the other way too. In a storm, extra calls do not mean extra jobs, because crew capacity is the limit. If you are already turning work away, the value is in the quality of the queue and the customers you don't lose to a slow callback, not in volume. The tutorial on paid leads against fast replies covers what a quick, honest answer is worth outside storm weeks.

The morning-after list: sorting the night's calls

A storm night leaves a list, and the order of the first ten calls matters more than the speed of the next hundred. Sort by lane, then by the time of the call, and have a person phone lane 1 and lane 2 callers before anyone else. A filled-in list for an illustrative night:

The first call to the lane 1 caller is a welfare check as much as a sales call. Asking whether they reached the power company and whether everyone is clear is the right opening, and it is the call you would want to be able to describe afterwards. Callbacks for lanes 3 and 4 can wait until the lane 1 and lane 2 queue is empty.

Grading the receptionist after its first storm night

The drill below proves the script on calls you wrote. The first real storm tests it on calls you didn't, so once the morning-after list is cleared, set aside an hour to read every transcript from the night. Five measures tell you whether the receptionist did its job.

1. Lane accuracy. Note the lane the receptionist chose for each call and the lane you would have chosen. Any lane 1 or lane 2 call filed lower is a script fault, however few there are.
2. Safety lines delivered. On every call that mentioned a line, fire, gas or an injury, check the fixed wording was said in full, and before the address was taken.
3. Alert speed. Compare the time of each lane 1 and lane 2 call with the time the on-call text arrived. A gap of more than two minutes needs a look at the transfer settings.
4. Read-backs. Count the wrong callback numbers and misheard addresses. Each one is a caller you can't reach.
5. Promises kept. Check that every caller was rung back by the time the receptionist gave them.

A realistic first night, for illustration: 64 calls, 61 sorted correctly and three lane 2 calls filed as lane 3. All three callers said a "big branch" or a "limb" had come "through the roof", while the script listened for a tree on the house. The receptionist heard "branch", treated it as garden debris and put three damaged roofs on the morning list instead of ringing the on-call lead. The fix took ten minutes: add "branch", "limb", "through the roof", "came through" and "hole" to the words that send a call to lane 2, then re-run the drill's third call with "a branch" in place of "the oak". Expect your own first night to turn up a gap of this kind. Callers describe damage in their own words, and the script only knows the words you gave it.

Six things the pricing pages don't say, to ask before you buy

1. How many calls can it take at once? A storm puts several callers on the line together. None of the vendor pages I read states a limit.
2. What happens if the AI service is unreachable? Calls should fall back to a mobile or a recorded message. Ask for the fallback in writing and test it by redirecting the forwarding number.
3. Can you swap in the storm script in minutes? And does the new wording apply to the next call or only after a delay?
4. Which languages work on a phone call? Rosie and Dialzara list English and Spanish, Smith.ai links a bilingual feature without saying which plans include it, and Quo's Sona pages list three languages, though one line on its Sona page says English only. A panicking caller will use the language they know best.
5. Where do transcripts and recordings go, and for how long? Smith.ai and Jobber describe recordings, transcripts and summaries, and Quo describes call summaries, transcripts and recordings too. Ask each for the retention period and who can see them, because a transcript of someone's emergency is sensitive.
6. Can you control the wording of the on-call text? The lane, the caller's own words and the line that records what the caller was told are the three fields that matter.

A storm drill: eight calls to place before the season

Run these from a second phone with the storm script switched on. Write down what each does, then fix the script until every row passes.

If any of the first four fail, fix those before the season, whatever the price of the plan. A cheaper plan with a script that fails the danger calls costs more than a dearer one that passes.

Questions tree service owners ask about AI call handling

Can I switch to a storm script only when a warning is issued?

In practice yes: keep two versions of the script, the routine one and the storm one, and swap them when a warning arrives. Quo's page says Sona can use different knowledge or greetings for business hours and after hours, but check with any vendor whether you can switch scripts on demand and how quickly the change takes effect.

What would a human answering service cost in a storm month?

Smith.ai lists human receptionist plans at $300 for 30 calls, $810 for 90 and $2,100 for 300, with extra calls at $11.50, $10.50 and $8.50. At 210 calls that is about $2,070 on the 90-call plan, against roughly $110 to $410 for the AI plans priced here. People handle distress better, so some firms keep one for lane-one calls.

What if the caller is a utility crew or an insurance adjuster?

Those callers need a person, not the storm script. Add them to your transfer rules or keyword list, such as the names of the utilities and insurers you deal with, and have the receptionist take a name and number and alert the office instead of asking hazard questions. Test it with a call from a colleague pretending to be an adjuster.

Further reads

• AI Receptionist for Junk Removal: Costs, Photo Requests and Booking — Photo requests and booking rules for a similar load-based trade.
• AI Receptionist for Tradespeople: What It Costs and When It Pays — The general cost picture for tradespeople, and when it pays.
• How to Set Up an AI Phone Agent for After-Hours Calls — Step-by-step setup of after-hours call handling.
• AI Answering Service for Contractors: 100 Calls Priced Across Five Vendors — A hundred calls priced across five vendors.
• Locksmith Answering Service vs AI: What Each Costs per Month — Monthly cost of a human answering service against an AI receptionist for a locksmith, with call-volume sums and an emergency hand-off rule.
• AI for Locksmiths: Can It Triage Emergency Lockouts and Give Quotes? — Triage questions, a phone quote script with the call-out fee stated plainly, and an ID check at the door, with a worked Friday-night lockout.
• AI Receptionist for Roofing Companies: Storm-Day Calls and Claim Questions — A storm-week setup for roofers: six call types, an inspection cap, transfer rules, claim wording that stops short of adjusting, and twenty test calls.
• Roofr's AI Receptionist: Is the Add-On Worth It for a Small Roofer? — What Roofr's AI Receptionist does, how its two pricing pages differ, a missed-storm-call payback sum and five test calls before you pay.
• AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.

Sources: the pricing pages of Smith.ai (AI Receptionist and human plans), Quo (plans and Sona), Goodcall, Dialzara, Rosie and Jobber, Quo's AI receptionist page, Jobber's AI Receptionist page, and public power-company safety guidance on downed lines and trees touching lines. Jobber's Receptionist allowance and overage come from its help centre.