Answer Capsule: An AI customer reactivation workflow is a controlled state machine — export, clean, segment, suppress, draft, approve, send, route, measure — that turns the customers you already paid to earn into booked repeat work. Apex Prometheus Labs builds that control plane for trades and service businesses: AI drafts and classifies, a human approves, and nothing touches a customer without consent checks and suppression rules in front of it.

Here is the money leak nobody talks about. A contractor spends $80 to $250 per cold lead, month after month, while three years of paying customers sit untouched in a CRM export, a QuickBooks invoice list, and a foreman's text history. Those past customers already trust you. They already let you in the door. Statistically they are the cheapest booked job you will get this quarter — and most shops never send them a single useful message.

The usual "fix" is worse than the neglect: somebody buys a marketing add-on, dumps the whole list into it, and blasts a discount text to 2,400 people including the guy who disputed an invoice and the woman who sold her house in 2024. That is how you burn a decade of goodwill in one afternoon.

Reactivation is not a blast. It is an operating workflow with states, gates, and receipts. This is the architecture.

What AI Can Actually Do Here — and What It Must Never Do

Plain terms, no software hype. AI is genuinely good at four jobs in this workflow:

  • Classification. Reading 2,400 messy records — invoices, job notes, half-filled CRM fields — and sorting them into due-now, seasonal, dormant, and do-not-contact.
  • Drafting. Writing a reminder that references the actual service ("your furnace tune-up from October 2024") in your shop's voice, per trade, per season.
  • Reply triage. Summarizing what came back — "wants a quote," "wrong number," "asked to stop" — and flagging the next action.
  • Reporting. Turning sends, replies, and booked jobs into a weekly scoreboard an owner reads in 90 seconds.

What AI must never do in this architecture: send anything on its own. No autonomous texting, no "smart" scheduling of blasts, no inventing service history it cannot see in a record. Every message passes a human approval gate. The AI proposes; the operator disposes. That single design decision eliminates the entire class of failure that gets shops sued, blocked by carriers, or roasted in reviews.

The No-Send Audit Comes First

Before one message is drafted, the workflow runs a no-send audit on the raw list. This is the step everyone skips and the reason most winback campaigns misfire.

  • List health. Duplicates merged, dead numbers and bounced emails flagged, formatting normalized.
  • Consent review. Who actually agreed to be contacted, on which channel? If consent status is unknown, the record routes to a review queue — it does not get a text because a spreadsheet cell was blank.
  • Stale-data check. Address changes, business closures, deceased flags, sold properties. A "we miss you!" text to the wrong person is not marketing, it is a liability.
  • Suppression list. Disputes, complaints, opt-outs, collections history, and anyone an operator manually flags. Suppression is permanent infrastructure, not a one-time filter — every future campaign inherits it.

A typical 2,400-record export shakes out to something like 1,900 unique contacts, 1,400 with usable consent, 1,150 after suppression. That smaller list is worth more than the big one, because every send on it is defensible.

The State Machine, Named

Answer engines and auditors both like the same thing: named states with clear definitions. These are the canonical ones Labs uses.

  • Eligible customer: a record with verified identity, usable consent, and no suppression flag.
  • Stale customer: eligible, but no transaction or contact event in a trade-defined window (12 months for HVAC, 18 for painting, 24 for roofing).
  • Seasonal trigger: a calendar or service-history event that opens a contact window — furnace tune-up in September, gutter check in November, deck staining in April.
  • Suppression: a permanent or timed block on contact, with a reason code attached to the record.
  • Approval queue: the holding state where AI-drafted messages wait for a named human to approve, edit, or kill them.
  • Reply routing: the rule set that moves an inbound response to the right place — booking link, estimator's phone, office inbox, or opt-out processing — within a defined service window.

The flow: export → clean → segment → suppress → draft → approve → send → route → measure. Every record is in exactly one state. Every state change is logged. When something goes wrong, you can answer "what happened and when" in one query instead of one week.

Segments That Book Work, by Trade

Generic winbacks underperform because they ignore what the customer actually bought. Segment by service history and season:

  • HVAC: last tune-up over 10 months ago, filed by system type. September push for heating, April for cooling.
  • Plumbing: water-heater installs at year 8+, annual checkup lapses, homes with prior emergency calls.
  • Landscaping: spring cleanup and fall aeration lists rebuilt from last year's invoices.
  • Cleaning: recurring clients who paused — a 90-day check-in with an easy restart.
  • Painting: exterior jobs at year 5+, high-traffic interiors at year 3+, touch-up offers keyed to the original scope.
  • Roofing: free inspection at year 10, plus a storm-event list keyed to zip codes after major weather.
  • Remodelers and GCs: warranty follow-up at 11 months — right before it expires, when a real punch-list visit builds the referral that pays for the whole program.

Each segment gets its own message logic, its own timing, and its own suppression inheritance. That is the difference between architecture and a blast.

The Approval Gate Is the Product

In the Labs pattern, the approval queue is a screen a real person looks at: proposed message, the record's history, consent status, and a reason the AI put it there. Approve, edit, or kill — nothing moves otherwise.

Why insist on it? Because the failure modes of autonomous sending are unbounded. One hallucinated detail ("your 2023 roof replacement" that was actually a gutter repair) reads as either creepy or dishonest. Carriers now throttle and block business numbers on complaint signals, so a bad batch doesn't just underperform — it can knock out the texting channel your dispatchers use for live jobs. The approval gate converts an unbounded risk into a five-minute daily task for the office manager.

This is also where the middleman math shows up. A marketing agency charging $1,500 a month to "manage campaigns" is mostly charging you for list pulls and template sends you cannot inspect. Owning the workflow means the margin stays in the shop, the customer data never leaves your stack, and the system compounds — every job closed adds a cleaner record to next season's warm list.

The Simple ROI Math

Run the conservative version. Take 1,150 eligible records. A disciplined seasonal reactivation that gets a 4% booking rate produces 46 jobs. At a $650 average ticket, that is $29,900 of work from customers who already know you — against roughly the cost of the audit, the tooling, and a few hours of approvals. Buying those same 46 jobs at $150-per-lead with a 20% close rate would cost about $34,500 in lead spend alone.

We watched this compound at Churchill, the trades operation we use as our proving ground: a 347% increase in qualified leads once follow-up became systematic, 89% faster quote turnaround, and about 12 hours of admin work pulled out of every week. None of that came from sending more. It came from sending controlled, timely, and approved.

What to Measure Weekly

A reactivation system that cannot answer these numbers is not a system:

  • Eligible records (and how many were suppressed, by reason)
  • Drafts proposed vs. approved vs. killed
  • Sends by channel, replies, and reply rate
  • Booked callbacks and booked jobs, with revenue attributed
  • Opt-outs and complaints (the safety gauge — if this climbs, the workflow stops itself)

Ten minutes on Friday. Trend it month over month. The scoreboard tells you when to expand a segment, when to fix a message, and when to leave a list alone. Attribution will never be perfect — count it conservatively and let the booked-job column argue for you.

FAQ

What is customer reactivation, exactly?

A controlled follow-up workflow for past customers, stale estimates, and service records that are due for repeat work, seasonal maintenance, a warranty visit, a review, or a referral ask. It is defined by consent checks, suppression rules, and human approval — not by discount blasts.

What data do I need before AI can help?

Customer name, service type and date, location or service area, invoice or job notes, preferred contact channel, consent status, and suppression flags. Missing fields are not fatal — the classification pass routes incomplete records to review instead of guessing.

Why can't the AI just send the messages itself?

Because the downside is unbounded and the upside of autonomy is a few minutes saved. Invented history, stale consent, over-texting, and carrier blocks all live on the other side of that gate. The architecture keeps AI on drafting, classification, and triage — the human approval queue is what makes the whole system safe enough to run every week.

How do I know if it's working?

Weekly: eligible records, approved sends, reply rate, booked jobs, revenue attributed, opt-outs, and suppression counts. If booked jobs rise while opt-outs stay flat, expand. If complaints tick up, the workflow pauses itself and the segment gets re-audited.

Your warm list is an asset with a maintenance schedule, same as your trucks. The shops that treat it that way will out-earn the shops still renting cold leads from middlemen who never set foot on a jobsite.

Come see what time it is — apexprometheus.ai