Forum Discussion
4 Replies
- PestFreeCanadaVerified Community Coach
Once AI started being able to dictate a conversation and add their name, address and relevant information to a lead, I was sold!
- olliehContributor 2
AI for inbound is a smart move, but one thing worth checking before you invest in it: are your outbound numbers clean?
We scanned ~200 HVAC companies across 5 cities and 43% had at least one outbound number flagged as "Spam Likely" on the customer's screen before the call connected. AI or not, if your number shows spam, homeowners don't pick up — and your follow-up calls never land.
Worth running a quick check on your outbound lines alongside whatever phone system you're evaluating.
- DanGContributor 2
For landscaping it works best if you keep the AI's job narrow at first. Things I'd set up before letting it touch the schedule:
- Have it collect name, address, service type (mowing, cleanup, install, irrigation), property size if they know it, and best callback time. That covers most of what you need to quote.
- - Decide what it can book directly (recurring mowing, estimate visits in set windows) vs. what it just captures for you to call back (bigger installs, anything needing a site visit with pricing talk).
- - Give it your service area so it politely turns away out-of-zone calls instead of filling your calendar with drives.
- - Push every call summary into Jobber as a request so nothing lives only in a phone app.
Start it on after-hours and overflow only, listen to a week of recordings, then widen it. Spring rush is where it pays off, when you're on a mower and the phone rings 30 times. We use https://firstdeploy.ai for this if you want something to compare against.
- Sam_AshbornContributor 2
DanG already laid out the guardrails well — keep the scope narrow, gate by service area, and push every summary into Jobber. Two things that tend to trip up landscapers specifically, and one thing worth doing before you go live:
1) Landscaping intake questions look different than other home services, and that's where AI either earns its keep or makes you more work.
When a homeowner calls about mowing, cleanup, irrigation, or a small install, the answer to "can we quote this today?" usually depends on a few details most callers don't lead with: acreage / lot size, whether there's a gate code or pet on the property, one-time vs. recurring service, and access notes (back gate, HOA rules, sprinkler shut-off location, fence, tight turnaround).
If the AI is only trained to collect name, address, and "what do you need," you'll get a clean lead that still can't be priced or routed without a second call. The useful extra is not more questions — it's a tighter set of the ones that actually decide the estimate. A good rule: every extra field you add should either change the quote, change the dispatch, or save you from driving to the wrong place. Name the field, give the AI one clear example of what a good answer sounds like ("about half an acre" counts, "big yard" doesn't), and accept "not sure" without looping.
2) "Answer the phone" is the easy win. "Schedule customers" is the part to take slowest.
For a landscaper, a missed appointment is a wasted drive and a frustrated customer — so the scheduling side is higher-stakes than the answering side. Most shops that do this well draw a real line:
- The AI books what's repeatable and low-risk on its own: recurring mow windows, follow-up tune-ups, and estimate visits inside time bands you've already defined (same route, same crew, recurring slot).
- Anything that touches pricing, a site visit, or a new customer gets escalated: the AI captures the details and sets a callback, you (or a dispatcher) confirm and book.
- Weather and seasonality drive most re-schedules in landscaping, so set up the re-schedule path before it hits — a two-sentence "what changed" recap (date/time moved, reason, new window) so the customer isn't surprised and Jobber stays in sync.
3) Before you let it run, run a one-week listening check, not a rollout check.
Launch after-hours / overflow only (as DanG noted), then treat the first seven days like a QA window:
- Score a handful of calls each day on three things: did it ask what it was supposed to ask, did it capture the answer (not just "they said yes"), and did the thing that got booked/escalated actually match what the customer wanted.
- You or one operator listens to five calls a week and tweaks the prompts. AI phone tools drift when the wording is a little off, and listening is the fastest way to catch "it sounded polite but captured the wrong service type" before it books.
- At the end of week one, compare three numbers: how many calls went straight to a booked slot vs. escalation, how many booked appointments had to be re-handled (wrong service type, wrong window, missing access info), and how many estimate calls went un-callbacked past 24 hours. If the re-handle rate is high, tighten the intake questions before you widen it to daytime.
A few practical guardrails that show up across trades when AI touches the schedule:
- Every call gets a 60-second summary into Jobber (name, address, service type, property/access notes, one-time vs. recurring, what's booked vs. what's escalated, next action and owner). Treat that summary as the source of truth for who owns the next step.
- Publish a stated callback promise for estimate/escalated calls (24 hours in business hours is common and customers will notice if it's not met). If the AI owns the callback, it needs a clear handoff to the person actually calling — otherwise "we'll call back" becomes the missed call.
- When it says "yes," it still needs to confirm. A short confirmation message that recaps the right date/time, the right service ("mow," not "cleanup"), and the right address catches a lot of booking drift.
- Seasonal peaks expose the weakest part of the setup fastest. If your busiest two weeks already have a queue, that's the moment to start it — but only if the escalation path (real person, real time to pick up) is already tested.
Bottom line for landscaping: use the AI to remove the phone-as-bottleneck during the day (after-hours and overflow), keep its job to answering and capturing until the intake questions are tuned to your actual services and access quirks, and let a human own the schedule for new jobs and anything that prices on the visit. The scheduling piece is where it either protects you from drive-waste or creates it — take that one slower than the answering.