The "Job Done" Text: Turning Completion Into the Next Job

The completion message most contractors never send — and the triple ask it carries: the review, the referral, and the maintenance plan. One text, three revenue motions, zero awkwardness.

System 8 from the Leveraged Owner Starter Pack

The tech packs up, shakes the customer's hand, and drives away. The job is done — and so is the relationship, as far as your systems are concerned. The invoice will go out, the customer will pay, and then… nothing. Until the next breakdown, when they Google around like they've never heard of you. The most valuable moment in the entire customer lifecycle — the completion high, when satisfaction peaks and goodwill is highest — passes without a single message capturing it.

The "job done" text closes that gap. Sent when the tech marks the job complete, it does three jobs in one message: confirms the work, asks for the review, and opens the door to the referral and the maintenance plan. It's System 8 (proactive communication) as a revenue tool — and the closing bookend of the full-and-calm-calendar appointment sequence.

The triple ask (and why one message can carry three)

Three asks in one text sounds like a lot. It works because of sequencing and framing — each ask is a single line, each feels like a natural next step, and none of them is a hard sell:

  1. The review ask — the primary goal. Satisfaction is at its peak; this is the moment reviews are born.
  2. The referral ask — the secondary goal. A happy customer at the completion high is at peak willingness to recommend.
  3. The maintenance plan mention — the softest goal. Not a pitch, just a door left open.

The template

Hi [First Name], [Tech Name] here from [Business Name] — your [service] is all done! Quick summary: [one-line summary of what was done, e.g., "replaced the capacitor and cleaned the coils — your AC is running like new"]. We'd love a quick Google review of the work: [review link]. Know anyone who could use a [trade] company they trust? We'd appreciate the introduction — and ask us about our maintenance plan if you'd like this kind of tune-up twice a year without having to think about it. Thanks for choosing us! Reply STOP to opt out.

Why this specific structure: it opens with the summary (proof of value — the customer sees what they paid for, in plain English), then the review ask rides the satisfaction peak, then the referral ask, then the maintenance mention as a soft close. The summary line is doing quiet heavy lifting — customers who can articulate what was done value it more and describe it better in reviews.

The timing variants

What each ask generates (the compounding)

Setting it up

  1. Trigger: job marked complete in your field-service software. The text fires automatically — the tech should never have to remember to send it.
  2. The summary line: this is the one manual input. Have the tech enter a one-line plain-English summary when closing the job ("replaced capacitor, cleaned coils") — it merges into the template. If your field-service software can't merge custom fields, use a strong generic summary per job type.
  3. Suppress when appropriate: no triple ask on warranty callbacks, complaint revisits, or jobs where anything went wrong. The completion text still goes (the summary and confirmation matter), but the asks wait until the customer is genuinely happy.
  4. Connect the downstream: review link → review tracking; referral mentions → the referral ledger; maintenance interest → the agreement pitch queue. The text generates the leads; the systems catch them.

The mistake to avoid

Compliance notes

The job-done text for multi-day jobs

On a three-day install, "job done" happens once — on day three. But the customer's anxiety happens on days one and two, watching strangers tear their house apart in silence. The fix is two different messages with two different jobs.

During the job, send progress updates, not asks. A short end-of-day text — what got done, what's next, whether you're on schedule — keeps multi-day customers calm. Save the triple ask (review, referral, rebook) for the final completion text only. Firing the review ask on day one trains the customer to treat it as noise; by day three, when it actually matters, they've already tuned it out.

The rule is simple: progress updates during, the triple ask once, at the end. Shops that blur the two — asking for reviews mid-install — get fewer reviews and more confused customers than shops that keep the line clean. One message per job phase, each doing exactly one job.

Related guides in this series

The "job done" text closes the loop opened by the appointment confirmation sequence — bookended communication, start to finish. For the review mechanics it triggers, see the automated review engine; for the referral follow-through, The Referral Request System; and for the maintenance conversion, HVAC Maintenance Agreements.

Get System 1 free: the complete Missed-Call Safety Net

The full setup guide, all four copy-paste scripts (including the owner notification), the "Your Numbers" missed-call worksheet, and the step-by-step setup guide — free, no catch. Fix your missed calls this week.

Want all 8 systems + 6 bonus modules in copy-paste form? The AI Automation Starter Pack is $27: https://leveragedowner.com/starter-pack/

The done-for-you version

This post is System 8 from the Leveraged Owner Starter Pack — the done-for-you version with the full completion-sequence setup guide, every script, the downstream checklists, and screen-by-screen setup instructions for all 8 systems.

No third-party research stats cited — all templates and frameworks are the author's own.

Keep building your systems

Related guides from the Leveraged Owner blog: