How we work: This guide uses current public documentation and does not claim hands-on testing unless stated. Some links may later become affiliate links, at no added cost to you. Rankings are independent of commissions.
Automate seasonal lawn customer reactivation with a reviewed, service-specific list and a stop check immediately before every message. A former mowing customer should enter because the correct service window is approaching, not merely because a year has passed. A booking, reply, opt-out, complaint, open estimate, or invalid contact should remove that customer before another message can send.
The practical first version is one useful email and, if the customer remains eligible, one reminder. Route every response to a named person. Add an always-on campaign only after synthetic records prove that entries, exits, suppression, and ownership work.
This is desk research, not a test of Jobber, Housecall Pro, or a messaging provider. The official product and regulatory documentation and independent landscape trade reporting cited below were opened and checked on September 9, 2026. The calendar and test records are proposed operating templates, not reported performance results or legal advice.
What should a seasonal reactivation automation do?
Use one controlled path:
service window → eligible segment → human review → message → recheck → route or stop
Reactivation is not the same as renewal. An active recurring client belongs in a contract or schedule-renewal process. Reactivation is for a former customer with relevant service history and no current work.
The National Association of Landscape Professionals (NALP) reports that lawn care companies use different schedules: examples in its win-back article include targeted spring and fall campaigns, year-round outreach, and a cool-down period for recent cancellations. That variation is the reason not to hard-code a national month or an unsupported “best” cadence.
Define the local operating inputs instead:
| Input | Required value | Why the automation needs it |
|---|---|---|
| Service | A normalized item such as weekly mowing, spring cleanup, aeration, or leaf cleanup | Prevents an irrelevant offer based only on a customer tag |
| Property | Service address and operating zone | Confirms the property remains inside the service area and a viable route |
| Target service window | Local start and end dates owned by operations | Anchors outreach to deliverable work rather than a generic anniversary |
| Capacity release date | Date operations approves selling this work | Prevents marketing work the crews cannot schedule |
| Prior service evidence | Completed job, line item, and completion date | Supports a truthful reference to the relationship |
| Relationship state | Former, active, lead, cancelled, or do not service | Keeps renewals, leads, and prohibited contacts out of reactivation |
| Contact permission | Channel, source, wording or scope, timestamp, and current state | Gives the sender evidence to evaluate before email or text |
| Cancellation context | Reason, date, unresolved issue, and owner | Routes sensitive cases to review instead of an automatic pitch |
| Current work state | Future job, open estimate, request, or manual follow-up date | Stops a campaign that the customer has already overtaken |
| Campaign history | Last message, reply, opt-out, bounce, and campaign ID | Enforces suppression and prevents overlapping sequences |
If service history is only free text, fix the records before automating. The solo landscaper CRM setup provides a minimal field and stage model. The CRM migration guide explains how to preserve property relationships and suppression fields when cleaning a spreadsheet.
Which reactivation method should a small lawn company use?
Rank the methods by control, not novelty.
| Rank | Method | Best use | Main control |
|---|---|---|---|
| 1 | Reviewed one-off email from a saved segment | First campaign for one service and one operating zone | Freeze and inspect the recipient list, then recheck suppressions before send |
| 2 | Rule-based CRM campaign | A repeated service window after the first campaign passes reconciliation | Dynamic entry plus immediate exits for bookings, replies, opt-outs, and exceptions |
| 3 | Reviewed, always-on text selection | A company with documented text permission and enough staff to handle daily replies | Inspect every proposed recipient and message before its deadline; preserve text opt-outs |
| 4 | Exported bulk list with no live CRM check | Do not use for an automated sequence | A copied list becomes stale when someone books, replies, or opts out |
Rank 1 creates the safest learning loop. It exposes bad service codes, out-of-area properties, unresolved complaints, and missing permissions before they become an always-on error.
What does Jobber currently document?
Jobber’s Campaigns help page, updated August 13, 2026, says Campaigns is part of its Marketing Suite on all plans except Lite. It documents one-off and automated email campaigns and a specific automated template to re-engage past clients.
Its one-off filters include client tags, client status, city, job completion
recency with no upcoming scheduled job, services used, recurring or one-off
work, and past or upcoming client states. Automated re-engagement can use time
since a job ended, line items, client tags, and job type. Multiple conditions
act as AND, and the interface previews the matching clients.
Those fields can implement a narrow seasonal segment:
past spring-cleanup line item AND north-zone tag AND former client AND no future job
The product documentation does not decide whether that segment is appropriate for a particular business, whether its records are accurate, or whether the chosen channel is permitted. A manager still needs to review the actual names, exceptions, message, reply address, and request or booking destination.
What does Housecall Pro currently document?
Housecall Pro’s automated-campaign article dated July 24, 2026 documents customer lists based on tags, location, lead source, lifetime value, creation date, last service date, customer type, and notification state. It says its default exclusions include customers who are opted out, marked do not service, missing valid contact information, or last serviced more than three years ago.
The same page documents early exits when a new job is scheduled, a new estimate is scheduled, or an estimate is won or lost. Those are useful product controls, but they are not a complete operating policy. A substantive reply, complaint, manual callback date, address outside the service area, or another campaign may still require a separate stop or review.
Housecall Pro also documents an Automated Texts feature that selects up to 10 past customers per business each day, holds each generated text for a three-day review window, and excludes opted-out, do-not-service, invalid-number, recently texted, or newly ineligible customers. The page says no customer receives more than one text from that feature within 90 days.
Those are the vendor’s current product rules, not a recommendation to turn on automated texts. The selection is always on and is based partly on service recency and customer value. A seasonal operator may need stricter service, zone, capacity, cancellation, and consent rules than the feature’s published description establishes.
How do you build the customer segments?
Make the hard exclusions global. Do not rebuild them differently for each campaign.
| Segment | Entry rule | Action |
|---|---|---|
| Former customer, good standing | Relevant completed service at this property; no active or future work; in service area | Eligible for reviewed reactivation |
| Active or auto-renewing customer | Current contract, recurring job, or future visit | Exclude; route to renewal or normal service communication |
| Open request or estimate | Current request, pending estimate, or agreed follow-up date | Exclude; keep in the active sales workflow |
| Recent cancellation | Inside the company’s defined cool-down period | Hold until review date; do not infer the reason is resolved |
| Service or relationship complaint | Unresolved issue, refund, dispute, or explicit dissatisfaction | Manual review by the relationship owner |
| Do not service | Safety, payment, behavior, scope, or other approved restriction | Hard exclude from sales outreach |
| No marketing contact | Email or text opt-out, revoked consent, or required evidence missing | Hard suppress on the affected channel |
| Invalid contact | Bounce, disconnected number, wrong person, or unknown owner | Suppress and create a data-correction task; do not switch channels automatically |
| Outside service area | Current property no longer matches an approved zone | Exclude unless operations changes the boundary |
| Campaign collision | Contact is active in another incompatible sales sequence | Choose one owner and one sequence before any send |
NALP’s win-back reporting supports recording why a customer cancelled and tailoring the response to that reason. It also includes a company example that delays recently cancelled clients rather than contacting them immediately. Use those as design considerations, not proof that every former customer is safe or profitable to pursue.
Create one reason code and keep the original note:
- moved or property sold;
- service no longer needed;
- price concern;
- quality concern;
- communication concern;
- route or timing mismatch;
- competitor or do-it-yourself;
- nonpayment or dispute;
- company-initiated cancellation; or
- unknown.
Never let an automation claim that a prior concern was fixed. A quality, communication, billing, or safety issue should create a review task for the person authorized to address it.
What calendar should the campaign follow?
Work backward from S, the first date operations can deliver the service. The
offsets below are a starting template, not a tested optimum:
| Relative date | Owner | Required evidence |
|---|---|---|
S − 6 weeks |
Operations | Service window, route zones, crew capacity, excluded work, and booking cutoff approved |
S − 5 weeks |
CRM owner | Service codes normalized; active work, complaints, and suppression sources reconciled |
S − 4 weeks |
Campaign owner | Recipient preview exported or frozen; exceptions resolved; test messages approved |
S − 4 weeks |
Sender | First useful email sent only to the final eligible set |
S − 3 weeks |
Sales or office owner | Replies, requests, bounces, and opt-outs reconciled; bookings checked against capacity |
S − 2 weeks |
Sender | One reminder sent only after every stop condition is re-evaluated |
S − 1 week |
Operations and campaign owner | Remaining responses routed; campaign closed if capacity or response ownership is constrained |
| After service | Accounting or analyst | Completed and paid work reconciled to the original campaign cohort |
Change the offsets for climate, service, route, sales cycle, and booking capacity. A leaf-cleanup window and a recurring mowing restart do not share the same operational lead time. Store the chosen dates with the campaign so next year’s team can see the decision rather than inherit unexplained automation.
If booking demand affects route feasibility, reconcile the accepted work with the recurring lawn route optimization workflow before promising a specific day.
What should the reactivation messages say?
Use facts already in the record, one decision, and one reply path.
First email template
Subject: Planning [service] for [season]
Hi [first name],
We completed [verified prior service] at [property street or approved property label] in [verified period]. We are planning [service] in [service window] and wanted to ask whether you would like an estimate or scheduling conversation for this season.
Reply to this email or use [request link]. We will confirm scope, timing, and price before scheduling anything.
If you do not want marketing email from us, use [unsubscribe method].
Omit any field that cannot be verified. Do not insert a service, date, property, result, price, discount, or capacity claim because a template has an empty variable.
Reminder template
Subject: Re: planning [service] for [season]
Hi [first name],
One follow-up on [service] for [property label]: would you like us to contact you about this season, or should we close this request?
Reply
contact me,not this season, or with a better time. You can also use [request link].If you do not want marketing email from us, use [unsubscribe method].
Do not write “last chance,” “only two spots,” or “your old price expires” unless current evidence supports the exact statement and a named owner controls it. Do not revive the campaign when a customer replies “later”; store the agreed date and route it to a person.
How should responses be routed?
Every reply needs one state, one owner, and one deadline set by the business.
| Response or event | Immediate system action | Owner |
|---|---|---|
| Wants service | Stop campaign; create request or estimate linked to the correct property | Sales or estimator |
| Asks a scope or timing question | Pause campaign; preserve the conversation | Service-qualified office owner |
| Not this season | Stop this seasonal campaign; record preference without inventing a permanent opt-out | Campaign owner |
| Contact later | Stop automation; create dated manual task with the customer’s wording | Named relationship owner |
| Stop, unsubscribe, or equivalent | Suppress the affected channel immediately and propagate the correction | Compliance or CRM owner |
| Complaint or disputed history | Stop campaign; open a restricted service-recovery task | Manager authorized to resolve it |
| Wrong person, moved, or sold property | Suppress the bad destination; create a property/contact correction task | CRM data owner |
| Bounce or failed text | Suppress that channel; do not automatically try another channel | CRM data owner |
| New job or estimate appears | Exit campaign and reconcile attribution | Sales operations |
| No response | Take no action after the approved final message | Campaign owner |
The estimate follow-up workflow begins only after an estimate is actually sent. Do not leave the customer in both sequences.
What consent and suppression checks are required?
Treat a reactivation message as marketing unless qualified counsel has confirmed otherwise for the actual content, channel, and jurisdiction.
The FTC says CAN-SPAM applies to commercial email, including a message to former customers announcing or promoting a service. Its guide requires accurate header information, a nondeceptive subject, clear identification as an advertisement, a valid postal address, a clear opt-out method, and honoring an opt-out within 10 business days. The opt-out method must remain available for at least 30 days after sending. Hiring a platform or agency does not transfer away the sender’s responsibility.
Automated marketing texts require a separate review. The FCC’s January 2026 order describes the TCPA rules for robocalls and robotexts when consent is required and says a reasonable revocation method ends permission for covered future calls or texts. The order extends until January 31, 2027 one limited requirement about treating an opt-out from one communication type as applying to unrelated types; it says the extension does not alter the other revocation rules.
This guide is not legal advice. Have qualified counsel review federal, state, and local requirements; the technology used to send; the exact consent language and evidence; identification and quiet-hour rules; opt-out handling; record retention; and the vendor’s configuration.
Operationally, use one controlled suppression record that:
- stores the channel, source, timestamp, disclosure, scope, and current permission state;
- records unsubscribe links, reply keywords, free-text requests, calls, staff notes, bounces, and provider events;
- is checked again immediately before each send;
- cannot be reset by a CSV import, stale integration, duplicate contact, or campaign restart;
- propagates corrections to every connected sender; and
- creates an exception when two systems disagree.
How do you test the automation before it sends?
Use synthetic names, properties, services, and addresses owned by the company. These are proposed tests, not results from either product.
| Synthetic record | Change before the next send | Expected result |
|---|---|---|
| Former mowing customer, eligible | None | Appears once in the preview with the correct property and service |
| Current recurring customer | None | Never enters reactivation |
| Former cleanup customer | Add future job after list creation | Removed before send |
| Former aeration customer | Create open estimate | Removed and left in the estimate workflow |
| Eligible customer | Reply with a question | Later messages stop; named owner receives the conversation |
| Eligible customer | Use email unsubscribe | Email suppression is immediate and survives list rebuild |
| Text-eligible customer | Revoke text permission in free text | Later covered texts stop; evidence and timestamp are retained |
| Recent cancellation | Remains inside cool-down period | Held for review, not automatically contacted |
| Prior complaint | Leave issue unresolved | Campaign stops and manager receives the case |
| Invalid email | Provider reports hard bounce | Email is suppressed; no automatic channel switch occurs |
| Multi-property customer | Prior service was at only one property | Message and request link use only the proven property |
| Duplicate contacts | Opt out on one duplicate | Suppression protects all records for that destination |
| Eligible customer | Books while a message is queued | Queued message is removed before send |
| Campaign collision | Add customer to another sales sequence | One owner selects one sequence; no duplicate contact |
Run the tests with sending disabled first. Then send only to controlled company inboxes and numbers. Verify rendered variables, links, sender identity, unsubscribe behavior, reply routing, timestamps, audit history, and every expected exclusion. Do not enroll live customers until all hard-stop cases pass.
The software stack audit template can document the systems and owners involved when the CRM, email sender, text provider, booking form, and accounting platform are separate.
How should reactivation results be measured?
Freeze the eligible cohort at the first send. Define each outcome before reporting it:
delivered rate = delivered messages ÷ attempted messages;reply rate = unique customer replies ÷ delivered messages;request rate = new attributable requests ÷ delivered messages;booking rate = customers with approved scheduled work ÷ delivered messages;completion rate = customers with completed work ÷ delivered messages; andcollected contribution = collected revenue − refunds − variable job cost − campaign cost.
Do not call an open, click, reply, estimate, booked job, completed job, and paid job the same conversion. Reconcile customer and property IDs from the campaign to the request, estimate, job, invoice, payment, refund, and cancellation. Keep unattributed work separate.
Compare service and zone cohorts only when their windows and capacity are meaningfully similar. Weather, route constraints, pricing, staffing, and prior service quality can all change the result. The goal of the first campaign is a controlled baseline from the company’s own records, not an industry benchmark copied from a vendor.
For this site’s desk-research and correction standards, read the editorial policy.
Frequently asked questions
When should a lawn care company contact former seasonal customers?
Work backward from the local service window and real crew capacity. The example calendar below starts list preparation six weeks before service, but it is a planning template to adjust, not a proven universal send date.
Who should be excluded from a lawn customer reactivation campaign?
Exclude or manually review opt-outs, do-not-service records, invalid contacts, unresolved complaints, recent cancellations, active clients, future jobs, open estimates, and anyone already in another incompatible campaign.
Should seasonal reactivation use email or text?
Start with a channel the customer is permitted and expects to receive. Email and automated marketing texts have different legal and consent requirements, so preserve channel-specific evidence and suppressions.
How many reactivation messages should a landscaper send?
There is no universal best number. Begin with one useful message and at most one reviewed reminder in the example workflow, then change the cadence only from the company's own measured results and complaint signals.
What should stop a customer reactivation automation?
Stop on a booking, new estimate, substantive reply, opt-out, delivery failure, complaint, do-not-service status, or a staff-set follow-up date. Recheck these conditions immediately before every send.
Sources checked
- Jobber Help Center: Campaigns and Marketing Tools
- Housecall Pro Help Center: Send Automated Campaigns
- Housecall Pro Help Center: Automated Texts
- National Association of Landscape Professionals: Strategic Win-Back Campaigns
- National Association of Landscape Professionals: Email Automation in the Sales Pipeline
- Federal Trade Commission: CAN-SPAM Act Compliance Guide for Business
- Federal Communications Commission: January 2026 TCPA Consent Revocation Order