How to Set Up Automated Follow-Up Emails After Service Calls

Here is the math that most field service owners do not run, but should. A plumber finishes a job. The customer pays, says thanks, the tech drives away. Six months later that same customer has a leaking water heater and could not remember the plumber's name if you offered them a hundred dollars. So they Google "plumber near me," click the first ad, and the original company never sees the second job.

That is not a customer service problem. It is a memory problem. And memory problems are exactly what automated follow-up sequences solve.

The operators I have seen run this well book somewhere between 15% and 30% more repeat service from their existing customer base after they ship a four-email follow-up sequence. Not because the emails are clever. Because the emails exist. The competitor's emails do not. When the water heater leaks, the customer's inbox already has six months of polite presence from one specific plumber, and they call that plumber.

This post is the full recipe. The four emails, what each one is for, the copy guidance, the suppression rules so you do not torch your sender reputation or annoy your commercial accounts, and the exact build in Deelo using Field Service, Automation, and Marketing.

There are only four emails. Resist the urge to add a fifth. Every additional touch past four cuts your unsubscribe-adjusted ROI because the customer's inbox tolerance is finite. The four are: the immediately-after-close thank-you, the three-day follow-up, the thirty-day satisfaction check, and the six-month service reminder. Each does one job.

This is the easiest one and the one most field service businesses still get wrong. The mistake is sending a templated, branded receipt-style email that looks like it came from an accounts payable department. Nobody opens those. Nobody remembers them.

The email that works is short, signed by the tech who actually did the job, and reads like a thoughtful human typed it. Five sentences maximum. The structure: thank the customer by name, name the specific thing you did ("replaced the kitchen disposal"), set the expectation for warranty or follow-up ("24-month warranty on the unit, 90 days on the labor"), invite them to reply if anything is off, sign off with the tech's name and direct number. No marketing CTA. No "book your next service" button. The point of this email is to make the customer feel like they hired a person, not a brand.

The technical detail that matters: the email needs to fire fast. If you send it 24 hours after the job, the moment is gone. The customer should hear the truck door close, look at their phone, and see the thank-you within the hour. In Deelo, the trigger is the Field Service "job completed" event, which fires the instant the tech marks the work order as complete in the mobile app.

Three days is the sweet spot. Long enough that any installation issue would have surfaced. Short enough that the customer still remembers exactly which company you are. The job of this email is operational: catch the small problems before they become bad reviews.

The copy is one paragraph. "Hey {{firstName}}, it's been a couple of days since {{tech}} {{jobShortDescription}}. Wanted to check in — is everything working the way you expected? If anything is off, even something minor, just reply to this email and I'll get a tech back out today." Sign it from the office manager or the owner, not the tech. The signal you are trying to send is: this company is run by someone who cares about quality. Replying must go to a monitored inbox, and replies must be answered within 90 minutes during business hours, or the whole exercise is theater.

This email also captures your second-most-valuable signal after the review (which we cover in the dedicated review post): private negative feedback. A customer who is mildly unhappy will not call to complain, but they will reply to a soft, low-friction email asking how things are going. Catching that reply is worth more than the next ten upsell campaigns combined.

By day 30, the job is settled in. The disposal works or it does not. The HVAC unit has run through enough cycles that a slow leak would have shown up. This email serves two purposes: a second pass at catching any lingering issues, and a soft introduction of the maintenance program or service plan if you have one.

The copy is slightly longer than the three-day. Two paragraphs. First paragraph: still checking in, hope everything is holding up, here is the warranty refresher. Second paragraph (optional, only if you actually have a maintenance plan worth promoting): "A lot of homeowners on this system find that a yearly tune-up keeps the warranty intact and catches small issues before they become expensive. If that's something you'd like, here's how it works." Link to a real plan page on your site, not a generic "contact us."

Do not stack offers. Do not include a coupon. The single CTA principle is doing real work here: every additional ask cuts conversion on every other ask. If you have a maintenance plan, this email is the maintenance plan email. If you do not, it is just a check-in.

This one is conditional. Send it only if the job type is one that has a recurring service rhythm: HVAC tune-ups, pest control quarterly applications, septic pumping, lawn-treatment programs, sprinkler winterization, water heater flushes, IT MSP quarterly health checks. Do not send it after a one-time emergency call like a clogged drain or a stuck garage door, because the customer has nothing they need from you on a six-month cadence and the email will read as needy.

The copy for the six-month reminder is the most direct of the four. The customer has been on your list for half a year. They know who you are. The job is to make booking effortless. Three sentences plus a button. "Hey {{firstName}}, {{lastJobDate}} was about six months ago. Time to think about {{nextRecommendedService}}. Want to grab a slot?" The button goes to your online booking page, pre-filled with the customer's address and last service if your booking system supports it.

This is the email that closes the loop on the math from the intro. The reason 15-30% of follow-up sequences convert to a repeat booking is that this email arrives exactly when the customer's brain has started to vaguely register that something needs attention, and it removes every barrier between intent and a scheduled visit.

Cadence without suppression is a complaint factory. Three rules.

Open the Automation app, create a new workflow, name it "Post-Service Follow-Up." The structure is one trigger, four scheduled action branches, and a global suppression gate.

Trigger: `field_service.job.completed`. This event fires when a tech marks a work order as complete from the Field Service mobile app or when the admin closes a job from the web. The payload includes `customerId`, `jobId`, `serviceLine`, `techName`, `jobDescription`, and `completedAt`.

Add a filter immediately after the trigger: only proceed if `customer.consent.marketingEmail === true` and `customer.tags` does not include `do-not-followup`. This prunes the workflow at the door instead of hitting suppression on each individual send.

Each of the four emails is a `marketing.email.send` action. Use a separate Marketing template for each, named clearly: `post-job-1-thank-you`, `post-job-2-three-day`, `post-job-3-thirty-day`, `post-job-4-six-month-reminder`. The template variables (`{{firstName}}`, `{{tech}}`, `{{jobDescription}}`, etc.) are populated from the trigger payload. Use a `delay` step between each send: 1 hour, 3 days, 30 days, 180 days respectively.

For the six-month reminder, wrap it in a conditional that checks `serviceLine` against an allowlist: HVAC, pest, septic, lawn, sprinkler, water-heater, msp-quarterly. If the service line is not on the list, end the workflow after the 30-day send.

Before each delayed send (not just the trigger), call a CRM lookup: `crm.contact.get` with `contactId`. Check whether the contact has been tagged `plan-member-active` or has been added to another active drip campaign in the time between sends. If yes, skip the send and exit the branch. This catches the case where a customer signs up for the maintenance plan three weeks after the original job — they should not get the 30-day check-in, because the plan onboarding email is doing that work better.

Create a test customer in Field Service with your own email address. Create and immediately complete a fake work order. Verify the thank-you arrives within the hour. Then use Deelo's workflow simulator to fast-forward through the delays — the simulator preserves the conditional logic so you can confirm the 6-month reminder fires for an HVAC job and gets suppressed for an emergency drain job. Only after the simulator passes should you flip the workflow's status from `draft` to `active`.

Monitor the workflow's run history for the first two weeks. The numbers you want to see: 95%+ send success on the thank-you, 30-50% open rate on the three-day, 1-3% reply rate on the three-day (those replies are gold — every one is a chance to fix something before it becomes a bad review). If your three-day reply rate is zero, the email is too marketing-flavored. Rewrite it.

If you do 800 jobs a year at an average ticket of $475, and the four-email sequence drives 20% of those customers to book one additional job within 12 months, that is 160 incremental jobs and roughly $76,000 in incremental revenue. The cost is whatever you pay for your marketing app per month plus about three hours of one-time setup time. There is no other system I know of in field service operations where the ratio of effort to recurring revenue is this absurd. It exists because the competition is not running these emails. Yet.

Get the four emails written this week. Wire the workflow on Saturday morning. By the time the first thank-you fires Sunday afternoon, the math starts compounding.