Lawn Care Letter to Customers: Welcome and Delay Notes With AI

A welcome letter confirms the first visit, how the service works and how to reach you. A delay note gives the new day, the reason in one line and what the customer needs to do. A season-end note thanks them, says when service stops and offers renewal. AI can draft all three from a short facts sheet.

AI drafts well and promises badly. Left alone it will offer "first thing tomorrow" or "rain or shine" because those phrases sound reassuring, and you will be the one held to them. The fix is a facts sheet the draft must stick to, a voice sample so it sounds like you, and a read-through before anything goes out.

Follow me on Instagram@sagnikteaches

Most of a letter's value is the calls it prevents. In the first fortnight, the office phone of a lawn care company tends to carry the same few questions: when are you coming, what do I do about the gate, what happens if it rains, how do I pay. A letter that answers them in advance saves the call and makes the customer feel looked after.

Connect on LinkedInSagnik Bhattacharya

Before: three crews and letters written in a hurry

The business here is a three-crew lawn care company with about 180 weekly and fortnightly customers and one person in the office, who also does the invoicing. Its letters get written when something goes wrong: a rain note typed on a phone at 7am, a welcome email pasted from last year with the wrong crew day still in it, and no season-end letter at all because by October nobody has the time.

Subscribe on YouTube@sagnikteaches

The owner's goal is modest: six reusable letters, each ready in about three minutes with checked facts. The six are a welcome letter for new customers, a same-day weather delay text, a multi-day delay email, a missed-visit apology, a route-day change notice and a season-end letter that thanks customers and asks them back. The first build takes an afternoon. After that, each letter is a prompt, a quick edit and a send.

The facts sheet and voice sample every letter starts from

Two short documents do most of the work. The facts sheet holds everything a letter may state as true. The voice sample holds three or four messages you wrote yourself and liked, so the draft sounds like a person from your company and not a brochure. Store both in a ChatGPT or Claude project (a shared workspace that remembers files and instructions) so you do not paste them again each time.

FACTS SHEET: [company name]
Service days: Monday to Friday; each customer keeps one fixed crew day
Standard visit: mowing, edging, blowing off paths and driveway
Weather rule: if we cannot mow, we text that morning with a new day;
  missed visits are made up within 3 working days, no extra charge
Billing: invoice on the 1st, pay by card link or bank transfer
Customer to-do: leave side gates unlatched, secure pets, clear toys and hoses
Contact: text or call [number], 8am to 5pm Monday to Friday
Season: first visits [date], last visits [date, may move with the weather]
Renewal: reply "same again" by [date]
Never state: product names, treatments, guarantees, response times not above

VOICE SAMPLE: [three of your own messages, 40 to 80 words each]

Season dates and policies belong on the sheet because they change by climate and by company. The draft must never guess them. The "never state" line matters too: it stops the AI adding claims about eco-friendly practices or premium equipment that you cannot back up. Keep customers' names, addresses and phone numbers out of the project. Letters carry merge fields such as [first name] and your software fills them in at the moment of sending.

Spring: the welcome letter that answers week-one questions

A good welcome letter answers eight questions before the customer asks them: when is the first visit, how long is the window, do I need to be home, what should I do with the gate and pets, what does a visit cover, what happens in the rain, when and how do I pay, and who do I contact. Here is the prompt that produced the first draft in our made-up business.

Write a welcome letter to a new lawn care customer, under 200 words.
Use only the FACTS SHEET and match the VOICE SAMPLE.
Tone: warm, plain, first name, no exclamation marks.
Include: first visit [day, date, window]; the customer's to-do list; what
a visit covers; the weather rule; billing; contact details.
Do not promise arrival times beyond the window. Do not add claims about
equipment, products or results. Use merge fields: [first name], [day],
[date], [window].

The draft came back at 310 words against a 200-word limit, and three lines needed fixing. It said "rain or shine, our friendly team will be there", which contradicted the weather rule. It promised "first thing Tuesday morning" when the window was 8am to 1pm. It also described "premium, eco-friendly equipment", which nobody had told it. After cutting, the letter read:

Hi [first name], welcome, and thanks for choosing [company name] for your lawn. Your first visit is on [day], [date], some time between [window]. After that we come every [week or fortnight] on [crew day]. You do not need to be home. It helps if side gates are unlatched, pets are inside and toys and hoses are off the grass.

Each visit covers mowing, edging and blowing off the paths and driveway. If rain or a breakdown stops us, we text you that morning with the new day and make the visit up within three working days at no extra charge. We invoice on the 1st of each month; you can pay by card link or bank transfer. Questions, changes or a pause: text or call [number], 8am to 5pm, Monday to Friday. Thanks again, [your name].

That is 137 words, with every statement traceable to the sheet. Anything stricter belongs in the service agreement, not the letter; the lawn care contract clause checklist covers what that document should hold, so the welcome letter can summarise it without contradicting it.

Summer: delay notices at three levels

A delay notice has one job: tell the customer the new day before they wonder. What they care about is the new day, whether they need to do anything and whether it costs them. The reason matters least, and a long apology matters not at all. Match the weight of the message to the size of the slip.

Level 1 should fit in a text message that nobody has to scroll:

Morning [first name], rain has put [company name] a day behind. Your lawn will be mown by the end of [day]. Nothing you need to do. Questions: [number].

Level 2 deserves a subject line that does the work on its own, because many customers will read only that:

Subject: Your lawn visit moves from [old day] to [new day]

Hi [first name], a run of wet weather has pushed our schedule back, so your visit on [old day] will now be on [new day]. Please keep the side gate unlatched as usual. If that day does not work, reply and we will find another. [Policy line: billing date unchanged / visit made up at no extra charge.] Thanks for your patience, [your name].

Level 3 is a call first, because an email alone reads as hiding. The written follow-up should say what happened, in one plain sentence:

Hi [first name], thanks for taking my call. As I said, one of our mowers is out of action while we wait for a repair, so we missed your visits on [dates]. We will be with you on [date] with a replacement machine, and that cut will be billed as one visit. I am sorry for the gap. If you would rather pause until we are back to normal, tell me and I will arrange it. [your name]

Here is what an over-apologetic draft looks like before editing, and after. The first is the sort of thing AI often produces when asked to "write a delay apology".

Before: We are so very sorry to inform you that, due to unforeseen circumstances beyond our control, we have been unable to complete your scheduled service. We understand how frustrating this must be and we truly value your patience and loyalty during this challenging time.

After: Rain has put us a day behind. Your lawn will be mown by the end of Thursday. Nothing you need to do. Questions: [number].

Notice what the "before" version leaves out: no day, no instruction, no number. It spends 44 words managing feelings and none telling the customer anything. Put "state the new day in the first sentence" into every delay prompt, and add "no more than one apology, and only in level 3".

Write a level [1, 2 or 3] delay notice for a lawn care customer, under
[30, 100 or 120] words. Use only the FACTS SHEET. Tone: [paste a tone line].
State the new day in the first sentence. Say what the customer must do, or
say "nothing you need to do". Describe billing using the sheet's weather rule.
Give the reason in one clause at most. One apology, and only at level 3.
Do not promise a time of day. Merge fields: [first name], [old day],
[new day], [number].

Tone settings you can reuse

Different customers want different voices. A retired neighbour on a fortnightly plan and a property manager with six sites should not receive the same letter. Rather than rewriting each time, keep four tone lines in the project and paste the right one into the prompt.

The same level 2 notice shows the difference. In the neighbourly setting: "Hi [first name], the wet spell has pushed us back, so your visit moves from [old day] to [new day]. Shout if that does not suit." In the formal setting: "Dear [first name], we are writing to confirm that the scheduled visit to [site address] will take place on [new day] instead of [old day]. Please contact [number] if an alternative date is required."

Both carry the same facts. If you use Gmail, check whether the "Help me write" feature on your plan can also match the tone of your earlier emails, which Google added in May 2026 for Workspace and Google AI plans; a project with a voice sample does a similar job in any chat tool.

Moving a customer to a different day

Route changes are the notice customers are most likely to read as "you are fitting me around yourselves", because that is partly what they are. New customers on the same street, a crew reshuffle or a tidier route can all move someone from Tuesday to Thursday. The letter should say plainly why it benefits the service, what stays exactly as it was, and how to ask for something different. Send it at least two weeks ahead if you can, and a text reminder the day before the first changed visit.

Subject: Your lawn day is moving to [new day]

Hi [first name], from [date] we are reorganising our routes so crews spend more time mowing and less time driving, and your visit moves from [old day] to [new day]. Your window stays [window]. Everything else is unchanged: [what does not change, from the facts sheet]. If [new day] does not suit you, reply by [date] and we will see what we can do. Thanks, [your name].

The line "what does not change" is deliberate. It makes the AI, and you, name the price, the crew or the standard of work out loud, and it stops the draft from implying changes you have not decided on. If one customer needs a particular day, such as someone who keeps a dog in on Tuesdays only, record it on their account so the next reshuffle does not undo it.

Autumn: thanking customers and asking them back

The season-end letter does two jobs that sit awkwardly together, so write them as two short paragraphs and let the customer read each on its own. The first thanks them and tells them when service stops. The second asks for a decision. The number of visits comes from your software, not from the AI, and one personal line from the crew lead keeps it from reading like a form.

Subject: Thanks for this season, [first name]

Hi [first name], our last scheduled visit this season is [date]. We made [number] visits to your lawn since [start date], and it has been a pleasure to look after. [One line from the crew lead, for example: "The back lawn has filled in nicely since June."]

Service restarts in [month or week], weather permitting. To keep your place on [crew day], reply "same again" by [date] and we will roll your booking forward. If you would rather pause or stop, tell us and we will close your account tidily. Thank you, [your name].

Three details do the work here. The reply is one phrase, so saying yes costs the customer ten seconds. The deadline is real: it is the date you need to plan next season's routes. And the crew lead's line is the only sentence the AI did not write, which is why it reads as human. If the new season brings a price change, do not bury it in this letter; send it separately, with notice, as set out in the price increase letter tutorial. For autumn extras, a separate offer works better than a paragraph here, and the aeration and overseeding offer scripts show how to word one without pressure. For the wider renewal picture, landscape maintenance renewals and visit notes goes further.

Customers who have not replied a week before the deadline get one reminder, and only one. Send it as a text to those who agreed to texts about renewals and offers, and as a short email to everyone else:

Hi [first name], a reminder from [company name]: to keep your [crew day] slot next season, reply "same again" by [date]. If you would rather not renew, reply "no thanks" and we will close your account. [your name]

Anyone still silent after the deadline is a decision for you, not for the software. A short call to a long-standing customer settles what a third message cannot, and it tells you whether the silence means a busy month or a quiet goodbye. Release the route slot only after that call, not on the deadline itself.

Email, text or paper: match the channel to the message

The same facts can travel three ways, and the wrong channel makes a good letter useless. A long email for a same-day delay arrives after the crew has already come. A text for a renewal decision gets lost under the next notification.

A printed card left at the first visit, with the crew day and your number, is a useful backup for customers who ignore email, but it should repeat the welcome letter, not replace it. One caution on texting: a delay notice about a booked visit is a service message, whereas a renewal offer or an autumn extra is promotion, and many texting rules treat the two differently. Record how each customer agreed to texts and keep offers out of delay messages.

Eight checks before a customer letter is sent

Run every draft through the same short list. It takes two minutes and catches nearly everything the AI gets wrong.

1. Every date, time, price and policy in the letter appears on the facts sheet.
2. No promise is bigger than the sheet allows ("first thing", "always", "guaranteed").
3. Merge fields are filled and point at the right customer, crew day and window.
4. The first sentence says what changed or what happens next.
5. The length suits the channel in the table above.
6. Any link opens on a phone, and the contact number is right.
7. Texts carry an opt-out line, and promotions are not mixed into service messages.
8. You would say every sentence to the customer's face.

For item 1, let the AI do a second pass as an auditor. Paste the letter and the facts sheet and ask it to list every promise, date and policy in a table with the supporting line from the sheet beside each.

Audit the letter below against the FACTS SHEET. List every promise, date,
price, policy or claim in a table: statement | supporting line from the
sheet | supported (yes/no). Do not rewrite the letter.

On the unedited welcome draft, an illustrative result flags three rows as unsupported: "rain or shine", "first thing Tuesday morning" and "premium, eco-friendly equipment". Those were the three lines cut earlier. The audit does not replace your read-through, because the AI can miss a promise it does not recognise as one, but it is a useful second pair of eyes. For a wider pre-send routine, the email QA checklist before you hit send is worth borrowing from.

What six letters save, in rough sums

Here are two sums with made-up inputs. Swap in your own numbers.

Welcome calls first. Suppose the company signs 60 new customers over the spring, and one in three phones in the first fortnight with a question the welcome letter would have answered. That is 20 calls, and at four minutes each, 80 minutes of office time in the weeks when the office has least to spare. A letter that halves the calls saves 40 minutes per spring intake, and ten households find their answer without waiting for someone to pick up. Small on its own, but it repeats every spring and costs nothing to resend.

Now a wet spell. If rain pushes back two days of visits, about 60 lawns for this company, and no notice goes out, perhaps 15 customers ring to ask where the crew is. At three minutes each that is 45 minutes on the phones during the hours the office most needs for rescheduling routes. A level 2 notice costs seconds per customer because the software sends it from a list, and most of those calls should never happen.

The time to build all this is the real cost: roughly an afternoon for the facts sheet, voice sample and six letters, then three minutes per letter afterwards. Revisit the facts sheet at the start of each season, because a stale policy line in a letter is worse than no letter. Count the calls for one spring before and after, and you will know whether the six letters earned their afternoon.

Practical questions about customer letters

How long should a welcome letter be?

One screen of text is plenty, roughly 150 to 200 words. Put the first visit, what the customer needs to do, what a visit covers, billing and your contact details in it, and move everything else into a link or a printed card. Customers read the first paragraph and skim the rest, so lead with the date.

Can I text a delay notice to every customer?

A message about a visit the customer has booked is a service message, but your texting platform may still expect a record of their agreement to texts, and promotions need separate permission. Keep delay texts factual with no offers in them, include a way to opt out, and ask a local adviser which rules apply to you.

Can AI write in my own voice?

Close enough to save time, if you give it samples. Paste three or four of your own best messages into the project as a voice sample and name the tone in each prompt. It will still drift towards polite filler, so keep the edit step: cut any line you would never say to a customer's face.

What if a customer replies to a letter with a complaint?

Treat the reply as a service issue rather than a letter problem. Answer within the working day, repeat back what went wrong, say what you will do and by when, and give one named contact. AI can draft the reply, but a person should read it, and any refund or credit stays your decision.

Further reads

• Lawn Care Invoicing Software: Autopay and Season-End Chasing With AI — Autopay and season-end chasing for invoices.
• AI Receptionist for Lawn Care: Handle the Spring Sign-Up Rush — Answer the calls the letters do not prevent.
• Lawn Care Leads: Answer Every Quote Request Fast With AI — Reply to new requests in minutes, before the welcome letter.
• How to Write a Customer Newsletter With AI in 30 Minutes — A monthly customer email written with AI.
• Landscaping Business AI: Review Requests Built From Job Photos — Ask happy customers for reviews using job photos.
• Eight Lawn Care Marketing Ideas for Spring, Written With AI — Fill the spring book from last year's customers.
• Garden Maintenance Contract: What Each Clause Is For, Drafted With AI — A clause-by-clause walk through a garden maintenance contract for a two-person business, with the reason for each clause and prompts to draft it in ChatGPT.
• How to Price Garden Maintenance: Visit Rates and Seasonal Extras With AI — A six-garden route shows what travel really costs, then builds visit rates, hedge and leaf-clearance extras and a monthly plan from your own times.
• Software for Lawn Care Automation: Which AI Features Are Worth Paying For — A payback sheet for a two-crew round ranks autopay, reminders, weather-delay texts, routing and AI agents, using plan details from vendor pages.
• How Can AI Help My Lawn Care Business? Five Jobs to Hand Over — Five lawn care jobs to hand to AI, quotes, invoices, reminders, replies and scheduling, with payback numbers for a solo operator and a three-crew firm.
• AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.

Sources: Google's Workspace announcement on Gmail Help me write matching your tone (May 2026); OpenAI and Anthropic help pages on ChatGPT and Claude projects. The letters, tone presets and sums are the author's own illustrations.