How voice AI answering works
When someone calls your business number and nobody picks up, the call can be sent to an AI receptionist. This is software that listens, understands what the caller says, and talks back in a natural voice.
There are four simple steps behind the scenes. First, the call arrives and the software turns the caller's speech into text. Second, a language model reads that text and decides what to say next, based on the rules and the script you gave it. Third, a voice engine turns the reply back into speech. Fourth, when the call ends, the software saves a summary, the caller's details and sometimes a recording, and sends them to you.
The gap between the caller speaking and the AI answering is short, but you can feel it. A good setup keeps the pauses small and lets the caller interrupt. A poor setup feels slow and robotic. This is why testing matters, and we cover it below.
Why does this matter to a tree company? Calls are expensive to lose. Invoca research found that about 27% of calls to home-service businesses go unanswered, and under 3% of those callers leave a voicemail. Many people who reach a voicemail hang up and call the next company on the list. Your crew cannot answer a phone from a bucket truck or a climbing line. An AI receptionist is one way to make sure a real conversation still starts.
It is not magic. It does exactly what its script and limits allow, and nothing more. The rest of this guide is about choosing those limits well. If you want to see one in action, try our demo.
Good jobs for an AI receptionist
Give it work that is repeatable, clear and low risk. These four jobs fit tree service well.
After-hours calls
Storm damage, a limb on a fence and a neighbor's dead tree do not follow office hours. Many callers search in the evening or on weekends after they get home and look at the yard. If you do not answer, they move on. An AI receptionist can answer at 9 pm, collect the address, the problem and a phone number, and put the request first in your queue for the morning. If you offer emergency work, it can also alert you straight away.
Overflow when your line is busy
You answer the first call. The second call comes in while you are talking, and the third comes while you are on a roof. People cannot be in two places. The AI can take the calls you cannot, so a busy morning does not turn into lost jobs. You can set it to answer only after a few rings, or only when you are already on a call.
Booking estimates
Many tree calls end in a free estimate visit. That is a simple, structured task: get the name, address, what the tree problem is, how soon they want it, and a time that works. When the AI can see your calendar or booking page, it can offer open slots and confirm one. If it cannot book directly, it should collect the details and promise a callback within a set time, then send you the request.
Triage: urgent or routine
Not every call is equal. A tree through a roof matters more than a quote for trimming a hedge next month. A script can ask a few short questions to sort calls into groups: emergency, soon, flexible and not a fit (for example, a service you do not offer or an address outside your area). Emergencies reach you fast. Routine calls wait for the morning. That alone saves a lot of stress.
Simple questions you answer often
Which towns do you serve? Do you do stump grinding? Do you offer free estimates? Are you open Saturday? If the answers are fixed, the AI can give them. It should only share facts you wrote down. If a question is not in its notes, it should say it will pass the question to you, not guess.
Jobs it should never do
This is the most important part of the guide. A voice that sounds confident but is wrong can cost you a customer, or worse. Keep these jobs away from the AI.
Pricing disputes and firm quotes
The AI should never promise a price, agree to a discount, or argue about a bill. Price depends on things only a person on site can judge. If a caller says "your last quote was too high" or "can you do it for less," the AI should say that the owner will call back, and flag the call. A made-up number from a machine is hard to take back.
Complaints and angry callers
A customer upset about damage, a missed appointment or a messy yard needs a human who listens and takes responsibility. A script that keeps saying "I understand your frustration" makes it worse. The AI should spot anger or the word "complaint," stay calm and short, take a number and hand the call to you the same day.
Legal and insurance claims
If a tree fell on a car, a neighbor says your crew damaged a fence, or someone talks about a lawyer or an insurance claim, the AI must stop. It should not say who is at fault. It should not say what is or is not covered. It should not make promises. It should record the basic facts, say that the owner will call back, and alert you. Anything said in that call could matter later, so this is a human job. If you have questions about your own situation, speak to a lawyer or your insurance agent.
Safety advice beyond the basics
The AI should not tell a caller how to deal with a hanging limb or a tree near a power line. The only safe script is simple: if anyone is in danger or a line is down, call 911 and stay away. Then alert the owner.
Pretending to be human
Do not give the AI a human name and a story about sitting in the office. Do not say "I'm Sarah, I'm at my desk." If a caller asks "Am I talking to a robot?" the answer must be a clear yes. Lying about this breaks trust fast, and in some places it may break rules too. The next section covers disclosure.
Disclosure and call recording
This is a short explanation, not legal advice. Laws differ by state and can change, so check yours before you go live.
Recording consent. In the US, recording phone calls is covered by federal law and by state laws. Some states let you record if one person on the call agrees. Others need everyone on the call to agree. Because your callers can be in any state, many businesses play a short notice at the start of the call, such as "This call may be recorded to help us serve you." Some businesses treat a caller who stays on the line as agreeing, but that depends on your state, so ask a lawyer.
Saying it is an AI. Some states and cities have rules or proposals about telling people when they are talking to a machine. Even where no rule applies, honesty is the better policy. A simple opening line works: "Hi, you've reached [Company]. I'm an automated assistant. How can I help?" That one sentence costs you nothing, and callers rarely mind.
What you do with the data. Recordings and summaries include names, addresses and phone numbers. Decide how long you keep them, who can listen and how a caller can ask you to delete theirs. Keep it simple and write it down.
Outbound calls are a different matter. This guide is about answering calls that come to you. Calls and texts you start yourself have separate rules. Read our guide on texting rules before you send marketing messages.
Writing the script
A good script is short, honest and strict about its limits. Here is a simple shape for a tree company.
- Greeting and disclosure. Company name, "automated assistant," and the recording notice if you use one.
- Safety check first. "Is anyone in danger right now?" If yes: call 911, then alert the owner at once.
- Ask what is happening. Let the caller describe it in their own words. Then ask for the type of job: removal, trimming, storm damage, stump or other.
- Collect the basics. Name, best phone number, job address, and how soon they need it. Repeat the phone number and address back to be sure.
- Book or promise a callback. Offer an estimate slot, or give a clear callback window you can keep.
- Close politely. Say what happens next and end the call. Do not let it ramble.
Then write the guardrails. List the words that trigger a handoff: "lawyer," "insurance," "complaint," "refund," "manager," "emergency," "power line." List what it must never say: prices, fault, guarantees, dates you cannot keep. List facts it may share: service area, services, hours and how estimates work.
Keep the language plain. Callers are often stressed. Short sentences work best, and so does asking one question at a time. If you want help building yours, our free AI receptionist script builder walks you through each part.
Testing before you go live
Do not let real customers be your test. Before launch, call it yourself many times, and ask your crew and family to try as well. Test these cases on purpose.
- A normal estimate request with a clear address.
- A caller with a heavy accent, background noise or a poor connection.
- A caller who talks fast, changes their mind or interrupts.
- A "tree on my house" emergency, and a "power line is down" call.
- A caller who asks "how much will this cost?" three different ways.
- An angry caller, and a caller who mentions a lawyer or insurance.
- A caller who asks "Are you a robot?"
- A caller outside your service area, or one who wants a service you do not offer.
- A caller who says nothing, or hangs up halfway.
Check three things each time: did it say something false, did it collect the details correctly, and did the alert reach you? Fix the script, and test again. Plan to test once more after any change, and again every few weeks. Calls drift as seasons change.
Measuring if it works
Do not judge it by how clever it sounds. Judge it by jobs. Track these numbers each month, using your own data.
- Calls answered by the AI. How many calls it took that you would have missed.
- Details captured. How many calls ended with a name, phone number and address you could use.
- Estimates booked. The number that turned into a scheduled visit.
- Handoffs. How many calls it correctly passed to you, and how fast you responded.
- Jobs won. How many booked estimates became paid work, and the value of those jobs.
- Mistakes. Calls where it said something wrong or confused the caller.
Listen to a handful of recordings or read summaries every week. You will spot patterns quickly. Maybe it misses the gate code, or mixes up two town names. Each fix makes the next call better. Compare booked jobs with what you used to get from the same hours, such as evenings and weekends. If you want a way to see how many calls you miss now, try the answer rate test.
Costs to think about
Prices vary a lot, so get a quote and read the details. These are the parts to ask about.
- Minutes. Many services charge for the time the AI spends on calls. Find out what is included each month, what extra minutes cost, and whether short or silent calls still count. Our Core plan includes 300 minutes a month. See pricing for the current plan details.
- Setup. Someone has to write the script, connect your phone number and calendar, and test. Ask whether that is a one-time fee or built in.
- Phone number and carrier fees. Forwarding calls and sending texts may add small monthly charges. Ask which are billed at cost.
- Your time. You will review calls and approve changes, especially in the first month. Plan for it.
- Contract terms. Look for how you cancel and how much notice is needed.
To judge if it is worth it, use your own numbers. Count the calls you miss, estimate how many would book, and multiply by your average job value. Our missed-call calculator lets you try it with figures you control. Treat any result as an estimate.
You may also ask whether to use people instead. Our page on AI receptionist vs answering service compares the two.
Pairing it with missed-call text-back
An AI receptionist and missed-call text-back solve the same problem in different ways, and they fit together.
Some callers will talk to the AI. Others will hang up as soon as they hear it, or before it picks up. A text sent within about 30 seconds gives those people another way in. They can type the address and a photo of the tree, whenever it suits them. Texting also feels low-pressure for people who do not want a voice call.
A simple flow looks like this. The call comes in. If you do not answer, the AI picks up. If the caller hangs up early, a text goes out right away. Whichever path they take, the details land in one lead inbox, and you see one clear list to follow up. Nothing gets lost in a voicemail box nobody checks.
Read our full guide on missed calls for the text-back side. And remember that texting has its own consent rules, so check them before you start.
At Lirevon, both are part of one system. See the AI receptionist service, or ask for a free audit to see how many calls you may be missing. The wider package is on our services page.
Learn the terms in our glossary: AI receptionist and call recording. For short answers, browse quick answers, or compare packages on our offers page.
Lirevon has no tree-service clients yet, and our first case studies are due in December 2026. We would rather say that than promise results we cannot show. You can try the demo and judge for yourself.