The Customer Reactivation SOP

Purpose

To recover revenue from customers who have stopped calling, on a fixed schedule, without relying on anyone remembering to do it, and without burning the list in the process.

Reactivation fails in most shops for one of two reasons: it never gets scheduled, or it gets run once in a panic against a list nobody has cleaned. This procedure fixes both by making the cycle a standing calendar event with a defined owner, a defined list definition, and a required disposition on every record touched.

Scope

In scope. Customers with at least one completed job whose silence has crossed the shop's dormancy threshold, and who have not requested no contact.

Out of scope, handled elsewhere:

• First-time customers who never returned. These belong to the first-visit follow-up sequence, not to reactivation. Running them through this procedure wastes the window when they are still recoverable cheaply.
• Customers with an open complaint, dispute, or unpaid balance. These route to the complaint or collections process first. A reactivation message to somebody in a billing dispute is the worst message you will send all year.
• Named accounts with a contracted service frequency. A missed cycle there is a contract-performance issue raised the month it happens, not a lifecycle case reviewed quarterly.
• Customers recorded as lost with a reason. They are excluded until the reason expires, if it ever does.

Roles and responsibilities

The cycle owner is a named person, not a department. A cycle with two owners has none.

Definitions

• Dormant. Months since the last completed job exceed the shop's dormancy rule. Use the multiple-of-personal-interval definition rather than a flat duration; the derivation belongs to a separate reference and should not be re-argued each cycle.
• Suppressed. A record that must not be contacted: a standing no-contact request, a confirmed deceased customer, or an address confirmed sold or vacated.
• Reason. One specific, checkable fact about that customer's property or equipment, pulled from service history, used to open the contact.
• Disposition. The recorded outcome of the contact. Every contacted record gets exactly one.

Procedure

1. Schedule the cycle

Run four cycles a year on fixed dates set at the start of the year, positioned in the shoulder weeks before your busy seasons rather than during them. Put all four on the calendar in January. A cycle scheduled quarter by quarter gets postponed once and then never rescheduled.

2. Pull the list

Cycle owner pulls every customer meeting the dormancy definition as of the cycle start date. Export or write out: customer name, address, last job date, months since last job, total completed jobs, and the last job type.

Do not filter by ticket size at this stage. Ranking comes later and needs the whole list visible.

3. Clean the list

Remove, and record why:

• Standing no-contact requests.
• Confirmed moves, sales, and deceased customers.
• Records with no working contact method. These go to a separate list for address correction, not to the trash.
• Duplicates, which are common where one property has been entered under two spellings.

Cleaning before ranking, not after, because a dirty list makes every downstream number wrong and the opt-out risk sits almost entirely in the rows you should have removed.

4. Qualify and rank

For each remaining record, the service manager checks whether service history yields a usable reason. Sort the list into two groups:

• Group A, reason found. Gets the personal treatment.
• Group B, no reason found. Gets a shorter general message or waits for the next cycle. Do not manufacture a reason to move a record into group A.

Within group A, rank by total completed jobs descending, then by recency. The customer with six jobs who went quiet last year is worth more attention than the customer with one job who went quiet four years ago, and they should be contacted first while the cycle owner still has energy.

5. Batch

Split into batches of 20 to 40 names, sized so that all replies from one batch can be answered within one business day. Send the next batch only when the previous batch's replies are cleared.

Batching is not an efficiency measure, it is a quality control. It caps the damage of a message that reads wrong and it guarantees the reply speed the message implicitly promises.

6. Prepare the reasons

Service manager writes one sentence per group A record, in plain language, naming the specific item or condition. Budget about four minutes per record. This is the most expensive step in the procedure and the one that determines whether it works.

7. Run touch 1

Sent from a named person with a working reply path. Structure: the specific fact, why it matters now, what you would do, one question with an easy no in it. No discount, no urgency, no apology for the silence.

8. Answer every reply within one business day

Replies route to whoever can actually answer them. A technical reply goes to the service manager. A reply describing a past problem goes to the owner or service manager, never to a template.

Slow replies here undo the entire campaign. The message asked the customer to give the shop another look, and a three-day silence is the shop answering the question for them.

9. Run touch 2 at day 10

Only to non-responders from touch 1. Shorter than touch 1, references it, and this is the only place an incentive is permitted, framed as removing risk rather than cutting price.

Then stop. No third touch this cycle. Non-responders return to the dormant list and are eligible again next cycle with a new reason.

10. Disposition every contacted record

Same day the outcome is known, using the codes below. A record contacted with no disposition is the single most common defect in this procedure, and it is what causes a customer who told you they moved to get called again next quarter.

11. Close the cycle and report

Cycle owner produces a one-page report within a week of the last batch: counts by disposition, the six metrics below, and a verbatim list of every reason recorded under DECLINED.

12. Feed the findings back

Owner reads the DECLINED reasons at the next management meeting. This is the step that converts reactivation from a revenue tactic into a diagnostic. Customers who left rarely tell you at the time; a reactivation cycle is the one moment in the year when a meaningful number of them do, and those reasons describe a problem that is still happening to customers who have not left yet.

Cycle metrics

Targets are starting points; tune them after two cycles against your own history rather than against another shop's.

Records to keep

Per cycle, retained for at least three years: the pulled list with the dormancy definition used, the suppression removals with reasons, the message text for both touches, the disposition on every record, and the closing report. Retaining the definition alongside the results is what makes cycle-over-cycle comparison meaningful; without it you are comparing two different lists.

Worked example: one full cycle

A shop with 480 customer records runs its spring cycle.

Pull. The dormancy rule returns 58 names.

Clean. Six removed: 2 standing no-contact, 3 confirmed moved, 1 deceased. Workable list is 52.

Qualify. The service manager finds a usable reason on 34 records. The other 18 have thin history and go to the general message. Preparing 34 reasons at about four minutes each takes just over two hours.

Batch. Three batches: 20, 20, and 12.

Touch 1. All 52 contacted. 17 replies, about 33 percent of the 52 contacted. 8 of those 17 book.

Touch 2, day 10. Sent to the 35 who did not reply. 6 replies, 3 of which book.

Totals. 23 replies across both touches, about 44 percent of the 52 contacted. 11 booked, about 21 percent of the 52 contacted.

Dispositions: 11 BOOKED, 7 DECLINED, 3 NOT RELEVANT, 2 OPT OUT, 29 NO RESPONSE. Those add to 52.

Against the targets: contact completion 100 percent, reply rate 44 percent against a 25 percent target, booking rate 21 percent against a 10 percent target. Five of six metrics clear.

The one that fails is opt-out. Two opt-outs on 52 contacted is about 3.8 per 100, above the target of 2 or fewer. That is a small absolute number and easy to wave off, and waving it off is the mistake. Both opt-outs came from the 18-record group that got the general message, none from the 34 with a specific reason. That is not proof, because the group with no usable service history is also the group with the weakest relationship, so the two variables are tangled. But it points the next cycle's test in an obvious direction: hold the group B message next cycle, contact only group A, and see whether opt-outs go to zero. If they do, group B is a list to repair rather than a list to mail.

Cost. About two hours of reason preparation, roughly two hours of sending, and roughly four hours handling 23 replies, so about eight hours of office time across the cycle, producing 11 booked jobs. That is about 0.7 hours of office time per job booked, before any tech time. Compare that against what a lead costs you through advertising channels before deciding this is expensive.

The finding that mattered more than the jobs. Of the 7 DECLINED reasons recorded, 5 named the same thing: a stretch the prior year when the shop could not get out to people for over a week and stopped returning calls promptly. Nobody complained at the time. They simply stopped calling, and the shop learned about it four cycles later from a list of people who had already left. Eleven booked jobs is the visible result of this cycle. The five matching reasons are the valuable one, because the condition that produced them was still in place.

References

• U.S. Small Business Administration (SBA), customer retention and small business marketing guidance
• Federal Trade Commission (FTC), CAN-SPAM Act requirements for commercial email, including opt-out handling and honoring requests promptly
• Trade-standard practice for service recall, maintenance recontact, and customer record retention
• See related: The Dormant Customer Definition Worth Setting, How to Run a Win-Back Campaign That Does Not Feel Desperate, Reactivating Dormant Customers, How to Segment a Customer List by Lifecycle Stage