Direct answer
A landscaping AI receptionist keeps the number customers already call and answers when crews are on mowers or the office is closed. It sorts seasonal route work from storm cleanup, irrigation leaks, and design quotes. It books the ones that can wait and transfers the ones that match your escalate rules. The owner stays in the loop — just not as the default voicemail.
Seasonal call paths that should not share one script
New start vs existing route, weekly vs biweekly, skip this week. These should almost never page the owner.
On a structure or not, blocking a drive, occupancy. Escalate when your written rule says so. Do not diagnose tree risk.
Water running now, can they shut it off, zone if known. Geyser vs a crooked head are different jobs.
Project type, timing, and a site visit. Transfer only if design is owner-sold.
Realistic landscaping calls
“We need the first cut. The grass is past my knees.”
Seasonal start. Address, lot size if known, dogs, and gate code. Book a start. Do not invent a per-cut price unless you published one.
“A limb is on the roof after last night’s wind.”
Storm + structure. Occupancy and whether they can stay out from under it. Transfer if tree-on-structure is on your list. Pair with roofers only if you refer that work.
“The sprinkler is geysering in the front yard.”
Irrigation leak. Can they shut the controller? Address. Escalate if water is running and that is your rule; otherwise book the next irrigation window.
“We want a patio and a small retaining wall.”
Design / hardscape. Collect scope and timing. Book a site visit. Transfer if those jobs are owner-priced.
“Skip this Thursday — we have a party.”
Route change. Existing customer. Move the stop. Do not open a new-lead form.
“Do you still do snow this winter?”
Seasonal service you may or may not offer. If you do, book a seasonal contract conversation. If you do not, say so and do not take a driveway address for a service you dropped.
Season vs urgency
| Season / job | Usual AI action | Usual human trigger |
|---|---|---|
| Spring first-cut rush | Intake + book route start | Owner-priced new accounts |
| Tree on a structure | Intake + escalate rule | On-call if you do emergency tree |
| Irrigation geyser | Intake + shutoff question | If water cannot be shut off |
| Design / patio quote | Book a site visit | If design is owner-sold |
| Skip / move a mow | Route note | Rarely |
| Snow / ice (if offered) | Contract or dispatch rule you wrote | Storm nights you cover |
Write summer, fall, and winter blocks in the instruction file. One generic “yard work” script will book a mower for a downed tree and page you for a skip request.
What to tell the receptionist on day one
Cities you serve, lot-size limits, HOA work you take, and the services you do not — tree climbing, irrigation installs, lighting, snow. Then the seasonal calendar: when first cuts start, when you stop mowing, when blowouts happen, when snow contracts are sold.
Write the existing-customer rule. Write the dog and gate-code questions. Write the “do not quote hardscape from the phone” rule. If you refer pest or lawn disease, use a sentence — see pest control only as a referral pattern, not as a claim you treat insects unless you do.
Two conversations worth rehearsing
April, Monday, first-cut flood. “What is the address? Weekly or every other week? Any dogs or lockboxes? When did it last get cut, if you know?” Offer the next real start window. If the calendar is full, say the next real week — do not invent a Thursday you cannot staff. Transfer if they demand the owner or if commercial properties are owner-only.
After a storm, 8:30 p.m. Closed-hours greeting if you use one. “Is anything on the house or blocking the driveway? Is anyone home? What is the address?” If tree-on-structure is on the list and you do that work, transfer after those fields. If it is branches in the grass and nobody is at risk, morning queue.
Irrigation, lighting, and the services you do not sell
Many landscape companies answer one published number for mowing, mulch, irrigation, lighting, and “can you look at this drainage.” If you do not install lighting, the receptionist should say so before collecting a Saturday measure. If you service irrigation but do not design new systems, that belongs in the same file. Booking a truck for work you will decline is how owners start to distrust the front desk.
Drainage and grading sit next to hardscape. Collect the symptom — standing water, a sinking walk, a sump that runs all day — and whether they want a landscape visit or a plumber. Do not let the model decide the civil engineering. If you partner with a plumber on those calls, write the referral sentence; do not pretend you hold both licenses.
Commercial properties need their own block: who can authorize extra work, whether a PO is required, and whether storm debris is extra or included. A property manager calling about a downed limb is not a homeowner shopping a patio. The record should say which.
Crew notes the morning board can actually use
A useful landscape record is not “yard work, call back.” It is the address, the intent (mow start, skip, storm, irrigation, design), dogs and lockboxes, and what was promised. If a skip was accepted, the route manager should see the new day. If a geyser was booked, the irrigation tech should see that the caller already shut the controller — or that they could not.
Photos help design quotes. If you have a way to collect them after the call, say so on the call. Do not require a form before you will talk. The point of answering the published number is that the conversation happens now.
Setup, objections, and limits
Keep the published number. Forward misses to a Fix9 line. Use appointment scheduling for site visits and contractor intake if you also run construction-adjacent crews. Human escalation is a feature.
Objection: “Spring is too chaotic for AI.” Chaos is when voicemail fails. Objection: “Every yard is custom.” Custom still has a first question: mow, storm, water, or design. Objection: “We have a CSR in season.” Keep them. Add AI for overflow and the months you do not staff the desk.
Limits: AI cannot see the grade, cannot size a retaining wall, and should not promise a storm crew arrival time you did not configure. If you do not climb trees, the receptionist should say so before collecting a credit-card-free goodbye — never collect cards on the call.
Related AI receptionist guides
Frequently asked questions
Do I have to change the number on the truck and gate signs?
No. Keep Your Number. Forward unanswered or after-hours calls to a Fix9 line. Customers keep dialing the landscaping number they already saved.
How should AI handle the first-cut rush in spring?
Treat it as seasonal route demand. Collect address, lot size if they know it, last cut if any, and whether they want weekly or biweekly. Book a start window. Transfer if new-account pricing is owner-only.
What about storm cleanup?
Separate it from mowing. Ask what is down, whether a tree is on a structure or blocking a drive, and occupancy. Transfer if a tree on a house is on your escalate list. Do not have the model decide if a tree is a hazard.
Can it book a design or patio quote?
Yes. Collect the project type, photos if you have a follow-up path, and a site-visit window. These rarely need an owner transfer unless design work is owner-sold.
How should irrigation leaks be treated?
Ask whether water is running now, whether they can shut the controller or valve, and the address. A geyser in the parkway may escalate. A head that misted yesterday can book a repair window.
Keep the number people already call.
Add Fix9 as the answering layer: AI answers first, qualifies the request, books or routes the work, and transfers to you when the caller needs the owner.