Miami Landscaping Companies: Why Maintenance and Install Calls Need Different Receptionists

The Two Kinds of Landscaping Calls

Every landscaping company in South Florida handles two fundamentally different types of inbound work, and they require completely different responses on the phone.

A maintenance call is a $80–$300 transaction with a known scope. The customer says what they want, you book a recurring slot, and a tech shows up with a mower. Twenty minutes of phone call = job booked.

A project call is something else entirely. "Plant some shrubs" can mean three azaleas ($300) or thirty mature plumeria with custom bedding ($8,500). You can't quote that on the phone. You need to see the property, take measurements, talk through what the customer actually wants, then write a real estimate.

The Mistake Every Generic Receptionist Makes

That's the dispatch failure. The AI just booked a service appointment for a project that requires an estimate. When the tech arrives, one of three things happens:

• Tech doesn't have the right materials, can't do the job, has to reschedule
• Tech tries to quote on the spot, lowballs or overprices, customer feels jerked around
• Tech does a small piece of the work without a proper agreement, and there's a billing dispute later

All three outcomes lose the job. And the customer's review usually mentions "they didn't seem to know what they were doing." That review is wrong about the company — but right about the phone system.

Why Most AI Receptionists Get This Wrong

The current generation of AI receptionists is trade-blind. They have one prompt that handles every business. The same dispatcher logic running for a plumber runs for a landscaper — but plumbing is mostly service work and landscaping is half service, half estimate.

Here's what a trade-blind AI typically does when it gets a landscape install request:

• Treats every call as a bookable service
• Doesn't ask scoping questions before "booking"
• Promises arrival times and pricing it has no business promising
• Books the job into the calendar where it sits as a confirmed appointment
• Sends an SMS confirmation that the customer trusts
• Sets up a tech for failure when they arrive on site

It looks like a successful booking on every screen. It only falls apart when somebody physically arrives and discovers the AI booked a job that needed an estimate first.

What Trade-Aware Routing Looks Like

A trade-aware AI for landscaping knows the split before the call ever connects. It loads a different conversation flow than it would for plumbing or HVAC. The first question it asks isn't "what's your name" — it's "are you looking for maintenance, an install, or an estimate?"

Then it routes:

That single piece of intelligence — the difference between booking and estimating — changes the outcome of every project-tier call a landscaping company gets.

What This Is Worth in Real Money

A typical Miami landscaping company gets a rough split of inbound calls that looks like this:

The 60% maintenance bucket is high-volume, low-margin. Lose one of those, you lose ~$120 that week.

The 25% project bucket is the business-changing tier. A new front-yard landscape install is $4,000–$15,000. A paver patio is $6,000–$20,000. An irrigation system is $3,000–$8,000. Those calls aren't volume — they're individually worth more than ten mowing jobs combined.

A landscaping company that loses 25% of project-tier calls because of bad phone routing is leaving six figures on the table every year. The math is brutal:

• 50 inbound calls per week, 25% project tier = 12 project calls weekly
• Average project ticket of $7,500
• Industry close rate on properly-quoted projects: ~30%
• 12 × 30% = ~4 closed projects per week from properly-handled calls
• ~$30,000/week × 52 = $1.5M+ in annual project revenue at risk
• Even a 20% leakage rate from bad phone routing = $300K+ lost

The numbers vary by company size, but the ratio holds. Project work is where the money is. Project work is also where most AI receptionists fail.

What Aubern Does Differently

Aubern's AI loads a trade-specific conversation flow at call time. For landscaping, that means it knows the bucket split before it answers, asks scoping questions before booking anything, and defaults to scheduling an estimate when the scope is unclear.

The same intelligence runs for HVAC (where full system replacement is an estimate but a refrigerant top-off is service), roofing (where most calls should be estimates), electrical (where panel upgrades are estimates but breaker repair is service), and ten other trades — each with their own service vs. estimate logic.

The demo at the top of this post lets you try the landscaping logic yourself. Tell it you want recurring lawn care. Then call again and tell it you want a paver patio. Same AI, two completely different paths. Both end with a real booking that makes sense for the work described.

The Practical Test

If you're a landscaping business owner evaluating AI receptionists, the quickest test is the install scenario. Call any AI service and tell it you want shrubs planted. If it offers you a service appointment for tomorrow morning, you've found one that will lose you project-tier work. If it asks one or two clarifying questions and schedules an estimate visit instead, you've found one that understands your business.

The demo above does the second one. That wasn't a marketing decision — it was the difference between a system that works for landscaping and one that doesn't.