AI Receptionist for Lawn Care: Handle the Spring Sign-Up Rush

Coding Liquids tutorial cover featuring Sagnik Bhattacharya for AI Receptionist for Lawn Care: Handle the Spring Sign-Up Rush.
Coding Liquids tutorial cover featuring Sagnik Bhattacharya for AI Receptionist for Lawn Care: Handle the Spring Sign-Up Rush.

Give the receptionist a fixed sign-up script: address, rough lot size, how often, start date and extras. Have it read back a price range from your own card, then book a start week or add the caller to a waitlist. Set the overage rule and run a dozen test calls before the first warm weekend.

A rush changes the arithmetic. The same script runs hundreds of times in a few weeks, so how your receptionist is billed matters as much as what it says: per call, per conversation, per minute or per unique caller. Repeat callers checking for a slot cost very different amounts under each, and some tools let you choose what happens when the included allowance runs out. Decide that before the rush, not in the middle of it.

Follow me on Instagram@sagnikteaches

Decide what happens at the limit before the first warm weekend

Jobber's Receptionist is a useful example because its help article (updated 28 October 2026) states the rule clearly. The add-on costs $29 a month on select plans and includes 30 conversations, then $0.79 for each extra one. It is included with unlimited usage on the Plus plan. A call counts when the receptionist actively engages with the caller. A text conversation starts when it first replies and stays open for up to 24 hours. Calls identified as spam, or with no real interaction, do not count.

Connect on LinkedInSagnik Bhattacharya

The setting that matters in a rush is what happens after conversation 30. You choose in advance between two options. Continue and pay overage keeps the receptionist answering and charges $0.79 for each conversation beyond 30. Pause stops it responding to calls and texts, so callers leave a message that does not count towards the limit, and it cannot book anything until the next billing cycle starts. The warnings come early: admins get an email at 23 conversations and another at 30, and an in-app banner appears when 10 remain. In a rush all three can land in one weekend, which is why the choice has to be made before it starts.

Subscribe on YouTube@sagnikteaches

For a rush, "continue" is nearly always right. If it takes five conversations to land one weekly customer, the overage is about $4 (5 × $0.79 = $3.95) against a customer who would be worth $1,170 a season at an illustrative $45 a visit over 26 visits. Pause is for owners who would rather batch sign-ups into a callback list and accept a slower start. Whichever you pick, set it now. Other vendors do it differently, so ask each one three questions: what happens when the allowance runs out, how repeat callers are counted, and how long a "call" is billed for.

The sign-up script, field by field

The script collects the same nine fields on every call, in an order that puts the easy answers first and the one that needs thought (lot size) in the middle, where the caller is already invested.

FieldHow the receptionist asksWhy it matters
First name and mobile"Can I take your first name and a mobile number, in case we get cut off?" Read it back.A dropped call becomes a callback; also the number for texts
Permission to text"Is it all right if we text you about your start date?"Needed for waitlist offers and confirmations
Service address"What's the address for the lawn?"Area check, measuring and route fit
New or existing"Is this a new sign-up, or are you already a customer?"Existing customers go to a different path
Service wanted"Is it mowing only, or would you like edging, hedge trimming, feeding and weed treatment, or aeration?"Extras change price and time on site
Lot sizeSee the next sectionDrives the price band
Frequency"Weekly, once every two weeks, monthly, or a one-off?"Drives price and route capacity
Start date"When would you like the first visit, and is that flexible?"Decides booking or waitlist
Access"Is there a gate, a dog, or anything we should know about getting in?"Saves a wasted first visit

The script itself, written for a voice assistant with short lines:

GREETING
"Hello, [Business] lawn care. I'm the AI phone assistant. I can sign you up
for regular visits or take a message. Calls may be recorded. Are you looking
to start a lawn service?"

RULES
- Ask one question at a time. Read back the number, the address and the
  frequency in plain words.
- Never give a price except from the card below. Never promise a start date.
- Never take card numbers. Say an invoice or link will follow.
- If you do not understand an answer twice, write "unclear" and move on.

FLOW
1. Name and mobile (read back). Permission to text.
2. Address. If outside [areas covered]: "That's a little beyond where we
   work, sorry."
3. New or existing? Existing: take a message for [office] and stop.
4. Service: mowing, edging, hedges, feeding and weed treatment, aeration, other.
5. Lot size (see LOT SIZE below).
6. Frequency: "Weekly, once every two weeks, monthly, or one-off?" Repeat it
   back in words, for example "that's once every two weeks".
7. Start: "When would you like the first visit? Is that fixed or flexible?"
8. Price range from the card, with "confirmed after we measure".
9. Book a start week if [free slots] exist; otherwise offer the waitlist.
10. Read-back, then: "You'll get a text to confirm. Anything else?"

LOT SIZE (step 5)
a. "Do you know the plot size from when you bought the property?"
b. If not: "No problem. We'll measure from the satellite view once we have
   the address."
c. "If you mow it yourself, roughly how long does it take?" Record the answer.
d. "Is the lawn flat, or does it slope? Has it been left to grow for more than
   a few weeks?" Either answer yes: give no price and send to a person.
Record the caller's figure or time estimate, plus a band: small, medium,
large, very large or unknown.

Lot size: what callers can actually tell you

Most people have no idea how big their lawn is in square feet. Asking for a number produces a guess, and guesses that become prices become disputes. A better script offers four routes, in this order, and records which one it used.

  1. The paperwork figure. "Do you know the plot size from when you bought the property?" Many callers have it from the listing or the sale papers. Take it, but record it as the caller's figure.
  2. The address. If you measure from satellite imagery afterwards (pricing lawn care from satellite measurements covers how well that works), the receptionist only needs a correct address and can say the price is confirmed after measuring.
  3. A time-based hint. "If you mow it yourself, roughly how long does it take?" This is a weak signal, but it sorts small from large and costs one question.
  4. A photo. "Could you text a photo of the lawn from the house?" Useful for slopes, overgrowth and obstacles.

Whichever it uses, the receptionist records two things separately: what the caller said, and the band it was assigned. The price quoted rests on the band, and the exact price rests on your measurement. The bands should be yours, in whichever unit you quote (square metres work just as well); this set is a placeholder in square feet:

BandPlaceholder size (square feet)If the caller says
SmallUnder 3,000Courtyard, terrace house, "tiny", under 15 minutes to mow
Medium3,000 to 6,000Typical front and back lawn, around 30 minutes
Large6,000 to 12,000Big back garden, corner plot, an hour or more
Very largeOver 12,000No band; site visit and quote
UnknownNot knownTake the address, give a "from" price only

Add two yes-or-no questions that change the price more than size does: is it steep or sloping, and is it overgrown (more than a few weeks of growth)? Either answer moves the call out of the standard price card.

Price-range scripts that do not become promises

You have two safe choices: quote ranges by phone, or quote nothing and follow up by text. Ranges win more sign-ups on the call, because people who hear nothing often ring the next company. The trade-off is that a range spoken aloud is remembered as a quote, so the rules need to be tight.

  • Rule A, standard lawn, band known: give the range for that band and frequency, and say it is confirmed after measuring.
  • Rule B, size unknown: give a "from" price only ("from $35 a visit for a small lawn, rising with size") and promise an exact price by text within a stated time you can meet.
  • Rule C, steep, overgrown, very large or commercial: no price. Take the details and send it to a person.

An illustrative price card follows. Every figure is made up, so replace them with your own prices. Extras are quoted separately, never folded into the range.

BandWeeklyEvery two weeksOne-off
Small$35 to $40$40 to $45$55 to $65
Medium$45 to $55$50 to $60$70 to $85
Large$60 to $75$70 to $85$95 to $120
Very largeSite visit and written quote

Spoken, Rule A sounds like this: "For a medium lawn, a weekly cut is usually between $45 and $55 a visit, and we confirm the exact price after we measure from the satellite view. Does that sound fine for now?" If the caller pushes back, the receptionist does not bargain. It says: "I can't change prices on the phone. [Name] reviews anything outside our standard card, so I'll pass this on and you'll get a text." The record keeps the quoted range word for word, because a dispute in June starts with "you told me forty-five".

Waitlist rules when the route is full

A rush ends with more sign-ups than slots, and what happens to the extras decides whether you keep them. The receptionist needs a short rule for every case: where the slot count comes from, who goes first, what to say, and how a slot is released.

  • Capacity: the number of free weekly slots by area, kept in one place the receptionist can read (your job software or a shared sheet). If it cannot read live capacity, give it a fixed number per week and update it daily.
  • Order: existing customers renewing come first; new sign-ups go to areas where your route already runs; everyone else joins the waitlist in the order they called, grouped by area.
  • The words: "We're full for weekly starts in your neighbourhood until around [date]. I can add you to the waitlist, and we'll text you if a slot opens. There's nothing to pay to join. Is that all right?"
  • Consent: a yes to being texted, recorded on the record.
  • Release: when a slot opens, the office texts the first person in that area with a 24-hour hold. No reply, and it goes to the next.
  • No promises: never a start date for a waitlisted caller.

The release text can be short, and so can the confirmation that follows a booking. Both are written to be sent from your own number, with nothing the caller could mistake for a promise beyond what you have agreed:

WAITLIST OFFER
Hi [first name], it's [Business]. A weekly lawn slot has opened up in [area],
starting the week of [date]. Reply YES within 24 hours to take it and we'll
confirm. If we don't hear back, it goes to the next person on the list.

BOOKING CONFIRMATION
Hi [first name], you're booked with [Business] for weekly lawn cuts starting
the week of [date]. We'll measure the lawn from the satellite view and text you
the confirmed price before the first visit.

The sums stay small. If a route has 18 free weekly slots and a weekend brings 41 sign-ups, 18 are booked and 23 join the waitlist, as in the worked weekend further down. A few weekly customers will pause or leave over the following fortnight, and each opening goes to the next name in that area. Lawn care route profitability: is a new customer worth taking on? is a good companion, because a waitlist is also your chance to pick the customers who fit your routes best.

Transfer rules: the calls a person takes

Crews are mowing during the day, so a "transfer" often means a text and a callback rather than a live conversation. Write down which calls need a person and what the fallback is when that person is on a mower.

  • Commercial accounts, residents' or homeowner associations, and several properties: the quotes are bigger and the buyer is not the person on the phone. Message plus text alert to the owner.
  • Existing customers with a complaint: missed visit, damage, a bad cut. A person calls back the same day.
  • "Can you start tomorrow?": only a person knows if the route can flex.
  • Questions about products: what you apply, whether it is safe for pets or children, organic claims, licences. The receptionist should not make safety or product claims. Answering every lawn care quote request fast with AI has wording for the text answer you give afterwards.
  • Price negotiation: as above, a person reviews it.
  • Two failed attempts to understand: take the number and a note.

Jobber's text escalation carries a transcript snippet and a link to return the call, and its escalation number must differ from your business number, so an owner who uses one mobile for everything needs a second number or has to rely on texts. Whatever tool you use, test the text path as well as the live one.

Budgeting the rush in calls, not months

Take a rush month with 120 sign-up calls of about three minutes each, 360 minutes in all. Suppose 90 of those calls come from distinct callers and 30 are repeat calls from people checking on a slot. As of October 2026, the vendor pages I read price that month as follows.

Tool and planWhat it countsThe sumMonthly cost
Goodcall Starter (100 unique customers, 79 cents each over)One number once a month90 customers fit the allowance$79
Jobber Receptionist add-on (30 conversations, then $0.79)Each engaged call$29 + 90 × $0.79$100.10, plus a Jobber plan
Dialzara Business Pro (220 minutes, then $0.45)Minutes$99 + 140 × $0.45$162
Rosie Scale (1,000 minutes included)Minutes360 minutes fit the allowance$149
Smith.ai Pro, 75-call tier (then $2.50 a call)Each answered call$150 + 45 × $2.50$262.50

The same 120 calls cost between $79 and $262.50, and none of the vendors is "wrong": they count different things. What the spread shows is that repeat callers and long scripts hurt per-call and per-minute plans, while a per-customer count absorbs them. If your phone in a rush is full of people ringing back, the billing model matters more than the headline price. Rosie's page publishes no price for minutes beyond its allowance, and Jobber's plan fee comes on top of the add-on, so the table is a comparison of the receptionist alone. More on the Jobber route is in Jobber for lawn care: quotes, autopay and the AI receptionist, and Jobber's AI receptionist pricing for a one-van business covers the add-on's economics.

The first warm weekend: 64 calls

A two-crew lawn care firm has 62 of its 80 weekly slots filled from last season, so 18 are free. Friday to Sunday brings 64 calls. The numbers are made up, but the pieces fit together the way they would on a real weekend.

Call typeCallsWhat happened
New sign-ups4118 booked into free slots; 23 waitlisted (14 flexible on start date, 9 wanting to start now)
Existing customers119 messages (renewals, skips); 2 complaints transferred as same-day callbacks
Quote requests for overgrown, steep or commercial sites5Transferred to the owner as messages with photos where sent
Questions only (price, area)4Price card answered; 2 of these callers rang back later and signed up (counted in the 41)
Spam and wrong numbers3Ended; not counted by tools that exclude spam
Total64

On Monday the owner works 18 booking confirmations, 7 callbacks (5 quote requests and 2 complaints) and a waitlist of 23 names grouped by area. A weekly customer at $45 a visit over 26 visits is $1,170 of revenue a season, so the 18 bookings represent about $21,060 of seasonal revenue, before costs. The receptionist's side of the same weekend is small. On Jobber's add-on, calls it identifies as spam or with no real interaction do not count, so if the three spam and wrong-number calls drop out, 61 conversations count: $29 + 31 × $0.79 = $53.49, plus the job software plan. Use your own prices and capacity.

A sign-up record, filled in

This is the record the owner should see on Monday, one per caller. Names and numbers are placeholders.

SIGN-UP - new weekly mowing
Name: [first name]     Mobile: [number]  (texts OK: yes)
Address: [address]     Area: [area]
Caller's size note: "about 30 minutes to mow"     Band: medium (to measure)
Service: weekly cut, edging on alternate visits
Start: first week of April, flexible by one week
Access: side gate, code [code]; small dog in back garden
Quoted (verbatim): medium, weekly, $45 to $55 a visit, confirmed after measuring
Status: booked, week of [date]   (slot 14 of 18)
Transfer: none

Sorting Monday's 23 waitlist records with a chat assistant

The weekend leaves 23 waitlist records, written as free text in call summaries. If your records already sit in spreadsheet columns, a sort does this job. If they are summaries, a general chat assistant can turn them into a list grouped by route. Paste a record ID, area, frequency, start flexibility and call time for each, and leave names, phone numbers and addresses out: the ID finds the caller in your job software.

Below are waitlist records from lawn care sign-up calls, one per line:
record ID, area, frequency, flexible start (yes/no), time of call.
Group them under these routes: [route names and the areas each covers].
Within each route, keep the order of the call time.
Count weekly and every-two-weeks requests separately for each route.
Do not add, merge or drop any record. Do not suggest start dates.
Flag any record whose frequency or area is unclear.

[paste records]

An illustrative reply, shortened:

RouteRecords in call orderWeeklyEvery two weeksFlags
MondayW03, W07, W12, W19, W2141None
TuesdayW01, W02, W09, W14, W20, W2241W14 said "biweekly": unclear
ThursdayW05, W08, W11, W1631None
FridayW04, W06, W10, W13, W15, W1851None

What you would fix: the routes add up to 21 records, not 23. W17 and W23 gave their area as "near the school", which matched no route, and the reply left them out instead of flagging them, despite the instruction. Add a line asking for an "Unplaced" group, and check the total against your own count every time, because a dropped record is a customer who never hears back. The W14 flag is the assistant doing its job: ring that caller and ask whether they meant every two weeks or twice a week. When a Tuesday slot opens, the release text goes to W01 first, then down the list.

Twelve test calls before the rush

Ring it from two phones, twice each, and read the transcripts. The awkward calls are the ones that appear on the first sunny Saturday.

#What you sayA pass looks like
1"No idea how big the lawn is"Offers the paperwork figure, then the address route; records "unknown"
2Give the size in acres, not square feetRecords it as stated and assigns a band, or flags it for measuring
3Ask for weekly cuts, hedges and weed treatmentNotes extras separately; quotes only the cut
4"Can you start tomorrow?"Transfers or takes a callback; no promise
5Give an address outside your areaPolite decline
6"Is the treatment safe for my dog?"No claims; sends to a person
7Existing customer asking to skip a weekMessage to the office; no sign-up questions
8"What's the price?" before giving an addressAsks for the address, then applies Rule A or B
9"That's too expensive, can you do $35?"No bargaining; passes it on
10"Can I give you my card number now?"Declines card details; says an invoice or link will follow
11Route full for your areaWaitlist wording, text consent recorded, no start date
12Ring three times in two daysTreated sensibly, and you know how the tool bills it

For the general parts of a go-live check, how to write call scripts and escalation rules for an AI receptionist lists the escalation tests that apply to every business.

A slip to look for: the weekly price on a fortnightly request

A mistake that is easy to make, framed as a hypothetical. Callers say "every other week", "fortnightly", "every couple of weeks" and "biweekly", and a receptionist built on a loose instruction records "weekly" for some of them. The word "biweekly" is the worst offender, because it is used to mean both every two weeks and twice a week. The quoted price then belongs to the wrong frequency, and the customer finds out on the first invoice.

The fix is a two-step rule: the receptionist repeats the frequency back in words that cannot be misread ("that's once every two weeks, so about 13 cuts over the season"), and the quoted range in the record names the frequency. Add a test call for each way people say it, and read the transcript, not just the summary, because the summary may tidy the mistake away.

After the first fortnight: booked, waitlisted and unknown counts

When the first two weeks of the rush are over, pull three counts from the sign-up records and set your own bar for each before you look. The first is the share of sign-up calls that ended booked or waitlisted rather than as a bare message. If many end as messages, the script is losing callers somewhere, and the transcripts show where: usually at the lot-size question or the price. The second is the share of records whose lot-size band is "unknown". A high share is fine if you measure every address from satellite imagery anyway, and a problem if you price from the caller's figure. The third is conversations per new customer, which is what you pay for on a per-conversation plan. Repeat callers checking on a slot push it up, and a waitlist text that says when you will next be in touch tends to pull it down. If the third count climbs week on week, fix the waitlist wording before the next warm weekend, because once the allowance is used, every repeat call to ask "any news?" is another billed conversation.

Questions lawn care owners ask before the rush

Should the receptionist take card details or a deposit?

It should never collect card numbers by voice. If you take deposits, have it text a payment link or tell the caller an invoice is coming, and record only that the caller agreed. Keep payment handling inside your job software, where card data is stored properly, not in call transcripts.

How are repeat callers counted during a rush?

It depends on the vendor. Goodcall's page counts one phone number once a month, so five calls from the same person are one customer. Smith.ai counts every answered call, Jobber counts a call when the receptionist actively engages, and minute-based plans count minutes. Ask how repeats are billed before you pick.

What should it say when the route is full?

Be honest and specific: you are full for weekly starts in that area until a date you can stand behind, the caller can join a waitlist, and they will get a text if a slot opens. Ask for permission to text, never promise a start date, and record the area so the next opening goes to the right person.

Further reads

Sources: Jobber's Receptionist help article (updated 28 October 2026) and features page; Smith.ai, Goodcall, Dialzara and Rosie pricing pages. Read on 29 October 2026.

Want your rush script tested before spring?

On a 1:1 call we can write your sign-up questions and price-range wording, set the waitlist and transfer rules, and work out which receptionist billing model suits your busiest weeks.

Book a 1:1 call with me