Lesson 15 of 15 · 6 min

Seasonal promotions to past customers

Send seasonal promotions to past customers.

Read the lesson

Goal: Send a seasonal offer to the right past customers, with consent, and book the work from it.

You need: Tags, saved views, SMS registration done, a seasonal service in Service Catalog, and the booking page.

Why this matters

Cleaning and landscaping follow the calendar. Spring brings cleanups and deep cleans. Fall brings leaf removal and gutter work. Customers who bought a seasonal service last year are likely to want it again. Many forget to call until the leaves are already on the lawn.

A seasonal promotion reaches them first. It is the easiest revenue in the business. These customers know the company, liked the work, and need the same service again.

The danger is the shortcut. The owner says, "Text everybody." That wastes credits on people who never bought the service. It annoys them. Worse, it texts people who never agreed to texts. Texting without consent breaks carrier rules and can get the number blocked.

The right list is small and precise. It holds customers who bought this season's service last year and gave SMS consent. That list books well and costs little.

Size changes the setup:

  • Owner-operator. A list of 50 customers can fill the first two weeks of the season.
  • Fleet (Green Acre Lawn and Landscape, 5 crews). Hundreds of customers. Send in waves, so the calendar fills in order.
  • Multi-location. Each location sends to its own customers, on its own season dates.

The right list, the right message, the right time

Build the list from facts, not guesses.

FilterWhy
Bought this service last seasonThey need it again
Gave SMS consentOnly consented contacts get texts
Not already booked this seasonNo offers to people who already said yes

Tag last year's buyers with a clear tag, such as leaf-cleanup-2025. Next year, add leaf-cleanup-2026. The tag names the service and the year, so the list builds itself.

The message is short and honest. It names the service, the owner's real price or offer, and the booking link. It stays under 160 plain characters. Emoji cut a segment to 70 characters and can double the cost.

Fig 1

The fall offer and its reminder

  1. Green Acre · Oct 2, 10:00 amHi Pat, it's Green Acre. Fall leaf cleanup is open for booking at [PRICE]. Pick your day here: [link]
  2. note7 days later, not booked yet
  3. Green Acre · Oct 9, 10:00 amStill want a fall leaf cleanup this year? Book any open day here: [link]
  4. Customer · Oct 9, 6:40 pmBooked Tuesday. Added gutters too.
Short and honest: the service, the owner's price and the booking link. No fake deadline.

The timing matters. Send before the season peaks, so customers book early slots. A second text a week later reaches people who missed the first. A Condition before the second text skips anyone who already booked.

Fig 2

The seasonal workflow

  1. Send tag added: one run per contact
  2. Did the contact give SMS consent?YesSend SMS: offer and booking linkNoStop. No textEnds here
  3. Delay 7 days
  4. Already booked this season?YesSkip the reminderNoSend the reminder text
A Condition before each text. Adding the send tag starts one run per contact.

Quiet Hours default to 9 PM to 8 AM. Texts stay inside the day. STOP replies are always honored.

The booking page does the selling. Turn on Service Add-Ons, so a leaf cleanup customer can add gutter clearing. If the owner offers a code, use Promo Codes.

Build it in ServiceAgent

  1. Open Settings → Service Catalog → Services. Check the seasonal service has the right duration and price.
  2. Open the booking page Features. Turn on Service Add-Ons. Turn on Promo Codes if the owner offers one.
  3. Open Contacts. Filter by last season's tag and the consent tag. Click Save Current View.
  4. Open Workflows → Build from scratch. Choose Event Trigger → Contact Updated, the tag method from lesson 6. Do not use a Manual Trigger. A manual run has no contact picker and runs once, with no contact. A saved view cannot feed a workflow either.
  5. Add a Condition: tags contain fall-offer-2026. Add a second Condition: tags do not contain fall-offer-sent. Then add Update Contact with the tag fall-offer-sent, so a later edit cannot start a repeat.
  6. Add a Condition for SMS consent, then Send SMS with the offer and the booking link.
  7. Add a Delay of 7 days.
  8. Add a Condition that skips anyone already booked. Then send the reminder text.
  9. Click Test, then Publish.
  10. Open the saved view. Add fall-offer-2026 to each contact, one wave at a time. Each tag starts one run for that contact.
  11. Tag each new booking with this season's tag, such as leaf-cleanup-2026.

Check it works: Add fall-offer-2026 to a dummy contact with your own number. Book from the link. Confirm the reminder text is skipped.

For one text with no reminder, Marketing → SMS Campaigns is simpler. Choose the list, and it sends only to contacts with SMS consent. A campaign has no workflow run, so it cannot skip people who booked after the first text.

Worked example: Green Acre Lawn and Landscape

In early October, Green Acre builds the fall leaf cleanup list. These are example inputs.

  • 240 customers bought a fall leaf cleanup last year.
  • 200 of them gave SMS consent.

Credits:

  • 2 texts each at 2 credits: 4 credits.
  • 1 workflow run each: 1 credit.
  • 200 × 5 = 1,000 credits.

Growth includes 6,000 plan credits a month. The campaign uses about one sixth.

Results, as an example: say 35% book. 200 × 35% = 70 cleanups. At Green Acre's example $300 cleanup job, 70 × $300 = $21,000.

Fig 3Example numbers

Green Acre's fall leaf list

240Bought leaf cleanup last year
200With SMS consent
70, worth $21,000Example bookings at 35%
A small, precise list books the season's first slots.

Compare the shortcut. Texting all 1,500 contacts in the CRM, at 5 credits each, would use 7,500 credits. That is more than the whole month's plan credits. It would also text people with no consent.

Fig 4Example numbers

Right list vs everyone

Right list
  • 200 contacts
  • 1,000 credits
  • All gave SMS consent
Everyone in the CRM
  • 1,500 contacts
  • 7,500 credits
  • Many never gave consent
The shortcut costs more credits than the whole month's plan, and breaks texting rules.

Report the real result after the season. Replace each example number with the client's own. Count bookings from the list, revenue, and STOP replies. A high STOP count means the message or the list needs work. A low booking count often means the send came too late, or the offer was unclear.

Spring and cleaning versions

The same method works for every seasonal service. Fresh Start Cleaning can send a spring deep clean offer in March. Its list is last spring's deep clean buyers with SMS consent. Green Acre can send a spring cleanup offer the same way.

Recurring customers need a different message. They are already on the schedule. Offer the seasonal service as an add-on to a visit they already have. That saves a trip and fills the visit.

Now the calendar. 70 cleanups at 3 hours each is 210 crew hours. Green Acre sends in two waves a week apart. Bookings then spread across the season, not into one week.

Fig 5

A seasonal campaign

  1. Late SeptemberBuild the list: last year's buyers with consent
  2. Early OctoberWave 1: first text
  3. A week laterWave 2, plus reminders to those not booked
  4. All seasonTag every booking leaf-cleanup-2026
Send before the peak, in waves. Then tag for next year.

Common mistakes

  • Texting everyone with a mobile number. Fix: only last season's buyers who gave SMS consent.
  • No skip for people who booked. Fix: a Condition before the reminder.
  • Long texts with emoji. Fix: under 160 plain characters, with the booking link.
  • Sending at the peak. Fix: send before the season, so early slots fill first.
  • No tag on new bookings. Fix: tag every booking with this season's tag, so next year's list is ready.

Do this now

Build next season's list for one client. Count last season's buyers and how many gave consent. Write the offer text in under 160 characters. Then build the workflow in a draft and test it on two dummy contacts.

Practice the conversation

  1. Owner Let us text everybody about fall cleanups.
  2. Operator I would text the people who bought it last year and agreed to texts.
  3. Owner Why not everyone? More people, more jobs.
  4. Operator Your full list would use 7,500 credits. The right list uses 1,000.
  5. Owner That is a big difference.
  6. Operator And people without consent should not get texts at all. That can get your number blocked.
  7. Owner How many would we reach?
  8. Operator About 200 people. If a third book, that is around 70 cleanups.
  9. Owner Do it. Can they add gutters?
  10. Operator Yes. I will turn on add-ons on the booking page.

Quick check

  1. In early October, you build the fall leaf cleanup list for a landscaping client on Growth. Which contacts go on it?
    • Every contact with a mobile number
    • Customers who bought a fall leaf cleanup last year and gave SMS consent
    • Customers who bought any service last year, with or without consent
    • Only dormant customers with no booking in 12 months
  2. A list has 150 consented contacts. Each gets 2 texts and 1 workflow run. How many credits does the campaign use?
    • 300
    • 450
    • 600
    • 750
  3. Why add a `Condition` before the reminder text?
    • To stop texts during `Quiet Hours`
    • To skip customers who already booked
    • To double the number of texts sent
    • To switch the message to email

ServiceAgent UniversityLearn to run a service business on autopilot. Free courses, Blueprints and certification for Service Operators.

Learn

Get certified

Community