Yes. An AI voice assistant can answer quote-request calls for a tree surgery firm, collect the address, tree details and access notes, and book a site visit into your diary. It should not give a firm price for felling or crown work by phone, and storm-damage calls with danger involved need an emergency-services message and a person first.
Where it earns its keep is the first minute of a call: capturing what an estimator needs, so the visit is booked with the details already in hand. Where it goes wrong is price. Tree work depends on access, risk and what the estimator sees on site, so a number given by phone becomes a promise. The rest is deciding what happens for storm damage and for callers who cannot describe their tree.
How a quote-request call runs, start to finish
Behind the voice there are three parts. Speech-to-text turns the caller's words into text, an AI model follows your instructions and decides the next question, and text-to-speech reads the reply aloud. The model can also use your tools, such as the diary or a request form. The pause between turns is short but real, and wind noise or a poor line is where mishearing starts, so the assistant should read the address back and ask the caller to confirm it.
This is an illustrative call to a firm that has switched the assistant on while the crew is up the trees.
Assistant: Thanks for calling [firm name] tree care. I'm the firm's AI assistant, and calls may be recorded so the team gets your details right. Is this a quote request, or is something urgent?
Caller: A quote. There's an oak at the back that's been leaning since the wind last week.
Assistant: Thanks. First, is anyone in danger, or is the tree touching a building or a power line?
Caller: No, it's in the far corner of the garden.
Assistant: Good. What's the address? (The caller gives it; the assistant reads it back and the caller confirms.) How tall would you say the tree is, compared with your house?
Caller: A bit taller than the house, I think.
Assistant: And how would a crew reach it: a side gate, or through the house?
Caller: Side gate, about as wide as a door.
Assistant: Do you know whether the tree is protected, or needs a permit? It's fine to say you're not sure.
Caller: No idea.
Assistant: That's fine, the office will check. I can book a site visit with the estimator: Thursday between 9 and 12, or Friday between 1 and 4?
Caller: Thursday morning.
Assistant: Booked, Thursday 9 to 12. You'll get a text with the details and a link for three photos: the whole tree, the base of the trunk and the route from the gate. The estimator will give you a written price after the visit; I can't give a price over the phone. Anything the estimator should know, like a dog or a gate code?
Caller: A dog, but friendly.
Assistant: Noted. Thanks for calling.
Five habits in that call are worth copying. It asked about danger before anything else. It read the address back. It asked for height against the house, not in metres, because callers can answer that. It said plainly that it could not price the job. And it booked a window, not an exact time. The estimator then receives something like this, by text or email, within a minute of the call ending:
New quote request (AI assistant), Tue 09:12
Name: [caller name] Phone: [number]
Address: [read back and confirmed]
Work wanted: assess leaning oak, back garden, leaning since wind last week
Height (caller's guess): a little taller than the house
Hazards: none reported; no buildings or wires mentioned
Access: side gate about door width, parking at front, friendly dog
Protected or permit: caller unsure, office to check
Visit booked: Thu 9-12 Photos requested: whole tree, trunk base, route from gate
Price given: none
The Complete Excel Course with AI Integration
From formulas and pivot tables to Power Query, DAX, VBA and AI with Copilot, ChatGPT and Claude — hands-on from the first lesson.
By Sagnik Bhattacharya and Virginia Thorn, Primetime Emmy Award winner
Buy nowThe nine details an estimator needs before the visit
Callers rarely volunteer these, and they cannot name species or measure height. The assistant's job is to ask in the caller's own terms and to write "unsure" where the answer is unsure, rather than guessing for them.
| Detail | Why the estimator needs it | How the assistant asks |
|---|---|---|
| 1. Where the tree stands | Decides the route in and whether it sits on a boundary | "Is it at the front, back or side, and near a fence or boundary?" |
| 2. Work wanted | Felling, reducing, deadwood, hedge work and stump grinding are different jobs | "What would you like done with it?" |
| 3. Tree type | Species affects risk, wood and disposal | "Do you know the kind? 'The big conifer' is fine." |
| 4. Height and trunk | Sets equipment, crew size and time | "Taller or shorter than your house? Could you reach round the trunk?" |
| 5. What is under or beside it | Buildings, fences, roads and wires change the method and the risk | "Is there anything underneath: a house, shed, fence, road or cables?" |
| 6. Access | Truck reach, gate width and slopes decide whether machinery fits | "How would a crew reach it: side gate, driveway, through the house?" |
| 7. Condition clues | A lean, a split or dead limbs can make a call urgent | "Anything that worries you: leaning, cracks, dead branches?" |
| 8. Ownership and protection | Only the owner can approve work, and some trees need a permit | "Is the tree yours? Do you know if it is protected? Not sure is fine." |
| 9. Photos and contact | Photos cut wasted visits; the best time to ring saves a second attempt | "I'll text a link for three photos. When is best to reach you?" |
Detail 8 deserves a second look. A caller who says "my neighbour's tree overhangs my garden" is not the person who can authorise work on it. The assistant should log that as an overhang enquiry, say that the owner of the tree is the one who must agree, and book nothing it cannot stand behind. It must not advise on boundary disputes either; that is the estimator's conversation, or a solicitor's.
Booking the visit: windows, estimators and promises to avoid
A site visit is the booking an assistant can safely make. It is a slot in the estimator's diary, not a date for the crew, so nothing is lost if the quote is declined. Set these rules in advance and the assistant never has to improvise.
- Offer two slots, not open availability. "Thursday 9 to 12 or Friday 1 to 4" ends a call faster than "when suits you?" and keeps the estimator's route sensible.
- Book windows, not minutes. A three-hour window absorbs the earlier visit that ran long.
- Group visits by district on set days. The assistant can only follow the grouping if you tell it which days cover which districts.
- Say what the visit is. How long it lasts (twenty or thirty minutes), who attends (the estimator, not a crew), whether someone must be home, and whether the visit costs anything. The last one is your policy, so write it down once.
- Confirm and remind. A confirmation text straight after the call, a reminder the day before, and a way to reschedule without ringing.
Four things stay off the assistant's menu: promising when the crew will start, giving a price, taking a deposit, and judging a tree safe or unsafe. Each of those has a person's name on it.
Three products show how differently this is built. The facts below come from each vendor's own pages in November 2026, and prices are list prices in dollars.
| Product | What its pages say it does on a call | Price signal | Check before you buy |
|---|---|---|---|
| Jobber Receptionist | Books visits using your online booking settings, creates a request for you to review when it cannot book, takes messages, escalates on keywords you choose, and logs a recording and transcript | $29 a month add-on on select plans with 30 conversations, then $0.79 each; unlimited on Plus | Needs a dedicated number; only admin users reach the settings; at its limit, if you choose to pause it, it takes messages but cannot book |
| Smith.ai AI Receptionist | Answers 24/7, qualifies leads, offers AI scheduling (Calendly and more), records and summarises calls, can transfer to a live agent | Free for 25 calls a month, then $3 a call; Pro from $150 a month for 75 calls | Its page names no field-service tools, so confirm how it reaches your diary |
| Goodcall | An AI phone agent whose workers can be a booker, a message taker or a knowledge expert; transfers to a person you choose; keep your number by forwarding it | From $79 a month for 100 unique customers (about 150 calls) | Counts unique callers, not minutes (extra callers 79 cents each on Starter); its pricing page names no calendar integrations |
Run the numbers for a firm that takes 60 calls in a month, each counting as one conversation. Jobber's add-on comes to $29 plus 30 extra conversations at $0.79, which is $52.70. The Smith.ai free plan is 35 calls over the allowance at $3, which is $105. Goodcall's Starter stays at $79. Those are the assistant's prices only; a diary or CRM subscription is separate. Tree-care-specific services exist as well, and the two product pages I read started at several hundred dollars a month. Neither described photo requests or storm-call handling, so ask for both in a trial call before you pay.
The full monthly picture, including a storm script, is in AI receptionist for tree services: costs and a storm-call script, and 100 calls priced across five vendors compares the wider field.
Where the assistant stops on price
Callers ask "how much to take a tree down?" inside the first minute, so the instructions need an answer that is honest and not a dead end. There are four kinds of question, and each gets a different rule.
| Kind of question | What the assistant may say | Illustrative rule you would write |
|---|---|---|
| A price you already publish | The price, plus the condition that the estimator confirms it | "Stump grinding is $4 per inch of trunk diameter, $120 minimum. The estimator confirms the diameter and any access extra in writing." |
| Your terms for the visit | Your policy, in one sentence | "The site visit is free and takes about 30 minutes. A written price follows within two working days." |
| A small, repeatable job | A range labelled as a guide, only where your own invoices support it | "Trimming a front hedge usually falls between $180 and $320. That is a guide, not a quote." |
| Removals, crown work, anything near wires or structures | No number; book the visit | "I can't price tree work without seeing it. The estimator will give you a written price after the visit." |
A mistake that is easy to make (illustrative): the instructions include a line copied from your website, "tree removal from $400", and a caller asks about a large oak. The assistant repeats it. The estimator's price, with a crane needed to lift the trunk over a conservatory, is $1,900. The caller feels misled, and the review says so. The fix is two lines in the instructions: never give a figure for removals or crown work, and give the reason when asked. Check the text you paste in as well, because a "from" price in marketing copy is the thing an assistant most likes to repeat as if it were a quote.
When a caller presses, the assistant needs words that stay friendly. Something like: "I'd only be guessing, and for tree work a guess can be a long way out, because height, access and what's underneath change the job completely. What I can do is get the estimator to you on Thursday, and you'll have a written price within two working days."
Once the estimator has seen the tree, the written price is the document that counts, and the tree service estimate template shows how to itemise it so the customer can see what each line covers.
Photos and access notes without a long call
Photos help the estimator choose equipment, and sometimes spot a job that is really a hedge trim. Asking for them aloud is slow, so the assistant should text a link during or just after the call. Three photos cover most cases: the whole tree from as far back as the caller can stand, the base of the trunk, and the route from the gate or the road to the tree.
Whether a product can send that text, and where the photos land, varies, and the pages I read do not settle it. The Jobber pages I read describe calls and texts but do not mention photos. Smith.ai's pricing page does not say whether its AI texts links, and Goodcall's pricing page does not confirm text links either. So test it: make one call, ask for the link, send three photos from your own phone, and see where they arrive. If the product cannot do it, point the assistant at a form on your website that accepts photos, or ask callers to text photos to the office number. A message along these lines works (illustrative):
Hi [first name], it's [firm name]. Your site visit is booked for Thursday 9 to 12. If you can, please send three photos before then: 1) the whole tree from as far back as you can stand, 2) the base of the trunk, 3) the route from the gate to the tree. Photos help us bring the right kit. They don't replace the visit, and we won't give a price from photos alone.Photos have limits that the message should admit. They cannot show how far a tree has moved at the roots, whether the heartwood is sound, or true height. They also show a customer's house, so keep them in the job record and delete them if no job follows. Access notes need the same care: gate widths, steps, slopes, wires along the route and where a truck can park all belong in the booking, but a gate code belongs in the job record rather than in a text.
Storm-damage calls: triage first, booking second
After a storm the phone changes character. Some callers want a tidy-up quote, some have a tree across the drive, and a few are in danger. The assistant has to sort them with its first two questions, before it books anything. Three tiers cover the field.
| Tier | What the caller says | What the assistant does | Who acts next |
|---|---|---|---|
| 1. Danger | Someone is hurt or trapped, a tree is on an occupied building, or cables are down or touching the tree | Says: "Please call the emergency services now, and the power company if cables are involved. Keep well away from the tree and any wires." Then alerts and transfers to the on-call person. Books nothing | Emergency services first, then your on-call arborist |
| 2. Urgent, nobody in danger | A tree on a roof, car or fence, or blocking the only way out | Takes address, hazards and photos; alerts the on-call person at once; tells the caller that a person will ring within [X] minutes; gives no price | On-call decides on a make-safe visit |
| 3. Damaged but stable | A large branch down in the garden, a split limb, a lean after the wind | Treats it as a priority estimate: first available slot, photo link, no price | Estimator |
Three short calls show the sorting (illustrative). "A tree has come down on the garage roof, nobody's hurt" is tier 2: the assistant asks whether any cables are near, asks for a photo, alerts the on-call person and says someone will ring within [X] minutes, a figure you set and can keep. "There's a big branch across the drive and my car's stuck" is tier 3 unless the branch is hanging from something: it books the first slot. "The tree is leaning on the power lines and the kids are in the garden" is tier 1: the safety words, then the transfer, and nothing about booking.
The tier 1 words are not the assistant's to improvise, so write them once and fix them. Jobber's escalation policy shows one way to build the net. You set trigger terms such as "emergency" or "urgent", and when one is heard the receptionist either transfers the call to your escalation contact or texts a transcript snippet with a link to return the call; the escalation contact's number has to differ from your business number. A keyword list is only a net, so add storm terms of your own ("on the house", "through the roof", "power line", "across the road", "hurt") and make every call open with the danger question as the call above did. The assistant should never promise an arrival time: the on-call person decides that.
For the wording of a complete storm script and the usual set-up for overnight calls, see setting up an AI answering service that never misses an emergency. Storm weeks also push planned jobs back, and rebooking those is covered in tree service scheduling and weather delays.
The instruction sheet to paste into the assistant
Every product has a box where you describe the business and the rules. Treat it as a short operating manual, written in plain sentences, and keep your own copy so you can compare versions after each change.
ROLE
You answer calls for [firm name], a tree surgery firm. Say you are an AI assistant in your first sentence, and say that calls may be recorded.
GOAL
Find out whether the caller wants a quote, needs a storm response or wants something else. Collect the details below and book a site visit with the estimator.
EVERY CALL STARTS WITH
1. Is this a quote request, or is something urgent?
2. Is anyone in danger, or is a tree touching a building or power line?
If danger: say "Please call the emergency services now, and the power company if cables are involved. Keep well away from the tree and any wires." Then alert [on-call name] and transfer to [on-call number]. Do not book anything.
QUOTE REQUESTS: ASK IN PLAIN WORDS, WRITE "unsure" IF UNSURE, NEVER GUESS
Address (read it back), where the tree stands, work wanted, tree type, rough height compared with the house, what is under or beside it, access, condition worries, owner or not, protected or permit (unsure is fine), best time to ring.
BOOKING
Offer two estimator windows from the diary. Say the visit takes about 30 minutes and [is free / costs X]. Send the confirmation text and the photo link.
PRICES
Never give a price or a range for removals, crown work, or anything near wires or structures. Say: "I can't price tree work without seeing it. The estimator will give you a written price after the visit."
You may state only these published prices: [stump grinding rule].
NEVER
Promise a crew date or arrival time. Take payment. Say a tree is safe or unsafe. Give advice on protection orders, boundaries or insurance. Argue with the caller. If the caller asks for a person at any point, transfer the call.
END
Read the booking back. Ask whether the estimator should know anything else, such as dogs, a gate or parking.Three lines in that sheet do most of the work: "write unsure, never guess", "never give a price or a range", and "if the caller asks for a person, transfer". The disclosure line matters as well. Callers who discover halfway through that they are talking to software can feel tricked, and the first sentence is the cheapest place to tell them. Jobber's help article suggests telling callers that calls may be recorded and notes that recording rules vary, so check the rules that apply where you work before you switch recording on.
Ten test calls before it answers for real
Ring the assistant yourself, from a noisy place, and have someone else do the same. Ten calls find most of the gaps.
| Test call | What good looks like | If it fails |
|---|---|---|
| You cannot name the tree ("the big one by the shed") | Records "large tree, type unsure" and carries on | Add the "unsure" rule |
| "How much to fell a 40-foot ash?" | No number, a friendly reason, a booking offer | Tighten the price rule |
| "The tree is touching a power line" | Safety words first, then the transfer | Add trigger terms |
| A neighbour's tree overhangs your garden | Logs an overhang enquiry, says the owner must agree | Add the ownership question |
| You ask for a person halfway through | Transfers within seconds | Check the transfer number differs from the business number |
| A bad line, so the address is misheard | Reads it back and asks you to confirm or spell it | Add the read-back step |
| You want stump grinding only | States your published rule and books a visit | Add the rule to the price list |
| You ring about an invoice from last month | Takes a message or transfers, never improvises | Add an existing-customer branch |
| A sales call about business loans | Ends politely and does not log a lead | Add a spam rule |
| You ask for tomorrow, and the diary is full | Offers the next windows, never overbooks | Check the diary connection |
Keep a log of every test and every fix for the first fortnight of live calls: read the transcripts for the first 20 real calls, not the summaries, because summaries hide the places where the assistant was unsure. If you take only a handful of calls a week and you are free by early evening, a simple text-back message ("we're up a tree, send the address and three photos and we'll ring tonight") may do most of the job for nothing, and it is a fair place to start before paying for an assistant.
Further reads
- AI for Tree Services: Seven Jobs to Take Off the Owner's Desk — Seven more jobs beyond the phone that AI can take over.
- Tree Service Marketing Ideas: Storm-Season Posts and Local Pages — Storm-season posts and local pages that bring the calls in.
- Tree Service Contract With AI: Access, Damage and Debris Clauses to Verify — Access, damage and debris clauses once a quote is accepted.
- Tree Surgeon Risk Assessment Template: AI Drafts, You Sign Off — The risk assessment your estimator completes on the visit.
- Tree Service Leads: Paid Leads vs Answering Every Enquiry Fast — Paid leads against answering every enquiry fast.
- Can AI Help Write an Arborist Report? What Stays With the Arborist — What stays with the arborist when a report is needed.
- AI Voice Agent Trained on Your Business: Setup and Running Cost — Build the knowledge base, run test calls, set handoff rules and price the running cost per minute for an AI voice agent.
- AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.
Sources: Jobber Receptionist help article (updated 28 October 2026) and feature page; Smith.ai AI receptionist pricing page; Goodcall pricing page; two tree-care phone-assistant product pages (all read November 2026).