Win-back of dormant customers: segments and health score
Find customers who stopped booking, and bring them back.
Read the lesson
Goal: Find customers who have not booked in 12 months or more. Then bring some back with a short, consented offer.
You need: A Last service date custom field, Contacts saved views, CSV import with Smart Merge, and Workflows. Lesson 4 consent fields.
Why this matters
Every service business has a quiet list. These are customers who paid once or twice and then went silent. Some moved. Some found another company. Many simply forgot the name.
Winning back a past customer is often cheaper than finding a new one. They know the business. Their address and history are in the CRM. They need a reason and a nudge.
But win-back fails in two ways. The list is wrong, so active customers get a "we miss you" text. Or the list is right but the offer goes to people who never agreed to promo texts. This lesson fixes both.
The dormant rule
Dormant is a rule you set with the owner. Keep it fixed.
The SAU rule: no booking in 12 months or more.
Why a fixed rule? Because it lets you compare months. If the rule changes each month, the results mean nothing.
Some owners hear about churn risk scores and want one. ServiceAgent shows a contact Health Score under Customer Health. The bands run from Healthy (80 to 100) down to Critical (0 to 39). It is built from calls, tickets, surveys, invoices and recent activity.
The Health Score is not churn prediction. Treat it as a hint. It can help you word an offer. A customer with a low score and a past complaint needs an apology, not a coupon. But the score never sets the list. The 12-month rule does.
Health Score bands
Split the dormant list into segments. Each segment gets its own message.
| Segment | Who | Message angle |
|---|---|---|
| One-time repair | One job, 12+ months ago | "Time for a checkup?" |
| Former regular | 3+ jobs, then silence | "We miss you. Here is a returning customer offer." |
| Unhappy past customer | Low survey score or complaint | A call from the owner, not a text |
Which message a dormant customer gets
- No booking in 12 months or more
- Low survey score or a past complaint?YesOwner call task, no textEnds hereNoGo to the next check
- 3 or more past jobs?YesFormer regular: "We miss you" and the returning offerNoOne-time repair: "Time for a checkup?"
- Is there a marketing consent record?YesSend the textNoEmail if there is an address, or no messageEnds here
- One follow-up after 7 days, booked contacts removed first
What the owner decides
You build the list and the workflow. The owner makes four decisions before anything sends:
- The dormant rule. SAU recommends 12 months or more. The owner signs off on it once.
- The offer, if any. A discount, a free check or priority booking. In writing, with an end date.
- Who calls the unhappy segment. Usually the owner themselves.
- How often to send. Once a quarter is a good default.
Write the four answers in the client's notes. Next quarter, you run the same play without a new meeting. If the owner changes an answer, write the new one with the date. Then the next quarter's results still make sense, because you know what changed and when.
Writing the win-back messages
Each segment gets one short message. Keep it under 160 plain characters. Here are three examples for a plumbing client:
- One-time repair: "Hi Tom, it has been a year since we fixed your water heater. Want a free check while we are nearby? [link]"
- Former regular: "Hi Rosa, we miss you at Northside. Returning customers get priority booking this month. [link] Reply STOP to opt out."
- Unhappy past customer: no text. The owner calls.
A former regular comes back
- Northside Plumbing · 10:30 amHi Rosa, we miss you at Northside. Returning customers get priority booking this month. link Reply STOP to opt out.
- Customer · 11:05 amGood timing. The kitchen drain is slow again. Is Tuesday open?
- Northside Plumbing · 11:09 amTuesday at 9 works. You're booked.
- noteBooking tagged winback-2026q1
Any offer in the message must come from the owner. You never invent a discount or a deadline. "Free check while we are nearby" works only if the owner agrees to it in writing.
Send one message, then one follow-up after 7 days to those who did not book. Before the follow-up, remove anyone who already booked from the list. A campaign sends to everyone on its list with consent, so this check matters.
Reading the results
After 30 days, count three numbers for each segment:
- Sent.
- Booked jobs, tagged
winback-2026q1when booked. - Revenue from those jobs, from paid invoices.
Booked divided by sent is the win-back rate. Compare segments, not just the total. Former regulars often come back at a higher rate than one-time repair customers. If one segment books nothing for two quarters, change its message or stop sending to it.
Also count opt-outs. A STOP rate that climbs each quarter means the list is tired. Send less often.
Write the three numbers in the monthly report under Keep. The owner sees what the win-back brought in, next to what it cost in credits. That one line often decides if they keep paying for the Keep stage.
By business size
- Owner-operator. The list is small. A personal text from the owner's name works well.
- Fleet. The list is large. Send in two batches a few days apart so dispatch can handle the bookings.
- Multi-location. Run the rule per location tag. Each location reports its own win-back rate.
Build it in ServiceAgent
There is no date-field trigger and no "last booking" filter on Contacts today. So you build the date yourself, then tag from it.
Step 1. Add the field.
Settings→Contacts & Pipeline→Custom fields.- Add
Last service dateas aDatefield on Contact.
Step 2. Keep it current.
Workflows→Create→Build from scratch.Trigger Type:Event Trigger, eventAppointment Completed.- Add
Update Contactto setLast service date. Check in the account that the step can write the appointment date. Test, thenPublish.
Step 3. Fill the history once.
- Export the client's past jobs from the old system, or from the account.
- In a spreadsheet, find each customer's latest job date.
- Mark rows 12 months or older with the tag
dormant-12m, and a segment tag. - Import with
Simple ImportorSmart Merge. Smart Merge updates existing contacts. Test with about 20 rows first. The limit is 10MB and 10,000 rows.
Step 4. Save the views.
Contacts→Filter by Tags→dormant-12mand one segment tag.Saved Views→Save Current View. One view per segment.
Step 5. Send the offer.
- Use the Lesson 4 pattern:
Marketing→SMS Campaigns, one campaign per segment list. Do not use aManual Trigger; a manual run has no contact. - Contacts without marketing consent get an email if they have an address. Or no message.
- The unhappy segment gets a
Create CRM Taskfor the owner to call. - After 7 days, remove anyone who booked. Send the follow-up campaign to the rest.
Step 6. Refresh each quarter. Repeat the export and tag step every 3 months. Remove dormant-12m from anyone who booked.
Keeping the dormant list current
- 1Appointment CompletedEvent Trigger in a workflow
- 2Update ContactSets Last service date
- 3Quarterly export and tagdormant-12m plus a segment tag, then Smart Merge import
- 4Saved view per segmentReady for the next send
Worked example: Northside Plumbing
Northside Plumbing has 8 techs on Core. Owner Carol's average job is $380. These are example numbers for the list.
- Past customers: 2,400.
- Dormant 12+ months: 700.
- Dormant with a marketing consent record: 420.
The offer goes to 420 contacts as 1-segment texts.
- 420 texts x 2 credits = 840.
- A campaign has no workflow run.
- Total for the first send: 840 credits.
Credits for Northside's win-back send
Northside's Core plan includes 2,000 credits a month. Its AI calls also use credits. So this send may trigger a 500-credit Safe Pack for $20. Tell Carol before you send.
Say 4% of the 420 book a job. This is an example rate, not a promise.
- 420 x 4% = 16.8, so about 17 jobs.
- 17 x $380 = $6,460 of work.
Northside Plumbing win-back list
Measure the real rate after 30 days. Use it next quarter.
A campaign is not a workflow, so it does not use one of Core's 10 active automations. The Last service date workflow does use one.
Common mistakes
- Using a score to pick the list. The 12-month rule sets the list. A score is only a hint.
- Texting dormant customers with no consent. Dormant does not mean opted in. Email or skip them.
- One message for everyone. A former regular and an unhappy customer need different words.
- Never refreshing the tags. A customer who booked last week still gets "we miss you." Refresh each quarter.
- Promising a win-back rate. Use an example rate in planning. Report the real rate after.
Do this now
For a practice client, add Last service date and build the Appointment Completed workflow as a draft. Make a 20-row test CSV with two segment tags and import it. Save one segment view.
Practice the conversation
- Owner I read about AI that predicts which customers will leave. Can we use that?
- Operator You have a Health Score on each contact. It is a useful hint.
- Owner So let it pick who gets the offer.
- Operator I would rather use a fixed rule. No booking in 12 months. Then we can compare each quarter.
- Owner How many is that?
- Operator About 700. 420 agreed to promo texts.
- Owner And the others?
- Operator We email the ones with an address. The few who complained get a call from you, not a coupon.
- Owner What will it bring in?
- Operator If 4% book, about 17 jobs, or $6,460. That is an example. We will measure the real number.
Quick check
- An owner wants the win-back list picked by a churn risk score, not a fixed rule. What do you do?
- Keep the 12+ month rule, and treat any score as a hint
- Build the list from the score
- Send to every contact, then remove anyone who books
- Alternate the score and the rule each month
- 300 dormant contacts get a 1-segment campaign text. 40 book. After 7 days, the rest get a 1-segment follow-up. How many credits?
- 600
- 1,200
- 1,120
- 900
- A dormant customer once left a 1-star review about a late tech. What does they get?
- The standard coupon text
- Nothing, ever again
- A call task for the owner
- Two texts a week apart
ServiceAgent UniversityLearn to run a service business on autopilot. Free courses, Blueprints and certification for Service Operators.