Automation

How Plumbing Contractors Automate Follow-Ups and Invoices

A text fires when a call gets missed, a quote checks in on its own, and an invoice nudges itself until it's paid — no one has to remember.

A plumber sits in his service van checking his phone, with tools and a water heater visible behind him.

You finish a water heater swap at 4:30, write the invoice on your phone in the truck, and mean to send it that night. Thursday you remember. By then two voicemails are sitting unanswered, and the quote you gave Mrs. Alvarez on Monday has gone quiet.

Office work falls apart when it depends on a person who is also under a sink. That's all this is.

The way plumbing contractors automate their follow-ups and invoices is less dramatic than it sounds. A text fires when a call gets missed. A quote checks in with the customer on its own. An unpaid invoice nudges itself at day three, day seven, day fourteen.

By the end of this page you'll know which of those to set up first, and whether to build it yourself or have it built.

Where plumbing follow-ups and invoices actually fall apart

Three places, every week, in almost every shop we've worked with.

The phone during a job. A technician is on his back with a wrench in one hand. The phone rings. Maybe it goes to voicemail, maybe it just rings out. Either way the customer is already dialing the next plumber on the list, because a clogged main doesn't wait. That call is gone before anyone in the office knows it happened.

The quote nobody touches again. You walk the job, price the repipe, send the number that evening. The customer says they'll talk it over with their spouse. Then nothing. No second ask, no check-in, no "still want to get on the schedule?" Most of the time, silence is what loses the quote. The customer never heard back from anyone.

The invoice with one ask. Invoicing usually happens once. You send it, the customer means to pay it, life gets in the way, and the invoice sits there until the bookkeeper flags it a month later. Meanwhile you're floating the parts.

The pattern is the same in all three. Something needs a follow-up, and the only person who can give it is on a roof or under a house. Owners care about follow-up. It gets skipped because it lands in the exact hour nobody's free.

What automating follow-ups and invoicing actually means

An automation is a rule. Something happens, and a message goes out without anyone deciding to send it.

That's the whole idea. You pick a trigger — a call comes in and nobody picks up, a quote gets sent, an invoice hits its due date — and you write the SMS or email that should follow. From then on it goes out on its own, at the same time, in the same words, whether you're under a sink or asleep.

No new habits required. The follow-up you already meant to do just stops depending on you remembering.

Two of these carry most of the weight for a plumbing shop.

The first is missed-call text back. A call goes unanswered, and within seconds the caller gets a text saying you're on a job and will call back, usually with a question that keeps them talking. Text messages work here because people read them. A voicemail sits.

The second is automatic invoice reminders. Invoicing stops being a one-shot send. The invoice goes out, and if it isn't paid, the customer hears from you again on a schedule you set, politely, without you checking a list.

Quote follow-up sits in the middle of those two and runs the same way. All three are covered below, with the trigger and the timing spelled out.

Missed-call text back: the first automation worth setting up

A homeowner with water coming through the ceiling skips the voicemail. They hang up and dial the next plumber on the list.

The mechanic is simple. Your phone system or software watches for a call that rings out, and the second it does, it sends an SMS to that number. No one in the office has to notice. It fires while the caller still has your name on the screen.

What the text says matters less than how fast it goes. Something like: "Sorry we missed you — this is Dave at Miller Plumbing. We're on a job. What's going on and what's the address?" That's it. Name, reason, question. The question is the important part, because a reply gives you something to work with before you ever call back.

A few things worth doing when you set it up:

  • Send from the same number people dialed, so the reply lands where you'll see it.
  • Keep it under two lines. Long text messages read like a form letter.
  • Route replies to whoever runs dispatch, not to a shared inbox nobody checks.

Then decide what happens next. A reply should show up somewhere a person acts on it — a phone that buzzes, a board that updates. You can automate the first message all day, but somebody still has to book the job.

Emergency calls, in our experience, are where this automation pays for itself first.

Quote follow-up sequences that turn quotes into signed jobs

Most quotes that sit for five days die of silence. The customer didn't pick a cheaper plumber. Nobody called them back, and the water heater kept working well enough that the whole thing slid down their list.

So the cadence matters more than the wording. Here's a sequence that works for repair and replacement quotes:

  • Day 1, a few hours after the quote goes out. Short text: "Sent your quote over for the water heater swap. Any questions on it?" People read a text the same day. They rarely open a PDF the same day.
  • **Day 3. A call from the technician or owner who priced the job, with a voicemail if they don't pick up. This is the one that closes work. Everything else is a nudge toward this call.
  • Day 7. One last text that gives them an easy out. "Still want to go ahead with this, or should I close it out?" That question gets a straight answer either way, and a no is useful.

You can automate the day 1 and day 7 messages entirely. The day 3 call belongs on someone's list, and that list should come from the same place the quote came from, so nothing depends on memory. A CRM or field service app that tracks quote status will generate it for you.

Set the follow-up to stop the moment a quote is accepted. Nothing sours a signed job like a text asking if they're still thinking it over.

Automatic invoice reminders that get you paid faster

Most unpaid invoices aren't arguments about the bill. The customer meant to pay, put the email in a pile, and moved on with their week. Nobody is avoiding you.

That's good news, because forgetting is easy to fix. A dispute needs a phone call and a conversation. A forgotten invoice needs one text message on a Tuesday morning.

So the office stops chasing and starts sending payment reminders on a schedule. Same wording every time, same days after the invoice went out, no decision required from anyone. The first reminder catches most of what's outstanding. The later ones catch the slow payers, and what's left after that is a short enough list that the office manager can actually work it by phone.

You automate this part of your invoicing to stop letting money sit out there because a Thursday got busy. Aggression has nothing to do with it. Two things make the difference: when the reminders go out, and how easy you make it to pay.

Set the triggers and delay timing

The trigger is the invoice going out, not the work order being closed. Those are two different moments in most shops, and if you tie reminders to the job being finished, you'll text somebody about a bill they haven't seen yet.

A schedule that works for most plumbing invoicing:

  • Due date. A short, friendly text. "Hi Dana, your invoice for the water heater install is due today. Here's the link to pay."
  • 7 days past due. Same information, slightly firmer. Name the amount and the job.
  • 14 days past due. Direct. State the balance, state that it's two weeks past due, and ask them to call the office if there's a problem.

The tone climbs, the frequency doesn't. Three payment reminders across two weeks reads as organized. Six reads as harassment, and people stop opening your texts.

Set one more rule this week: any payment, partial or full, stops the sequence immediately. Nothing burns goodwill faster than a reminder that arrives the morning after a customer paid you.

Handle deposits, partial payments, and how customers pay

A deposit changes the math on every reminder that follows. If a customer paid half up front on a repipe, the payment reminders that go out after the job have to name the remaining balance, not the full invoice total. Getting that wrong makes the office look sloppy and gives the customer a reason to call and argue instead of pay.

So build the sequence around balance due, not invoice status. Any payment posts, the balance drops, the next text quotes the new number. Zero balance, sequence ends.

Payment method matters too. Card payments cost you a percentage of every job, and on a big install that comes straight out of your margin. ACH usually costs a flat fee instead. Put both links in the invoice and the reminder, with ACH listed first.

One step for this week: pull your recent big-ticket invoices — the ones well above a normal service call for your shop — and check how each one was paid. If most came in on a card, your invoicing is quietly pushing people there.

Partial payments should reset the clock, not the tone. Someone paying in pieces is paying.

Build it yourself with QuickBooks and Zapier

If you're one truck and a phone, you can automate most of this yourself in an afternoon. It'll look rough, and it'll work.

Start with the invoice side. In Zapier, create a Zap with QuickBooks Online as the trigger and "New Invoice" as the event. Connect the account, pull a sample invoice, and check that the customer's email and mobile number actually come through in the test data. If the phone field is blank, your invoicing setup is the problem, not Zapier. Fix the customer records first.

Then add a Delay After Queue or Delay For step. Set it to run a few days out. After the delay, add a Filter: only continue if the invoice balance is still greater than zero. Zapier can re-look-up the invoice with a QuickBooks "Find Invoice" step before the filter, so it checks the current balance instead of the old one. Last step: send the text through your texting provider, or send an email, with the payment link pulled from the invoice record.

Copy that Zap twice and change the delay lengths. Now you have a reminder sequence that runs without you.

The missed-call piece needs a phone system that fires a webhook or has a Zapier app. Most VoIP providers do. Trigger on a call that ends with no answer, filter out your own technicians' numbers and any repeat triggers from the same caller, then send a text back with your name and a question. Log the call as a task or a draft work order so it doesn't vanish.

What this setup won't do is handle exceptions. Deposits, disputed balances, a customer who replies STOP. You'll be watching it for the first few weeks, and that's the real cost of building it yourself.

Texting customers automatically without breaking the law

The moment you automate text messages, you stop being one person sending a note and start being a system sending at scale. That's the line the TCPA cares about.

The short version: you need consent before you send marketing texts. A customer who called you and left a voicemail has given you a reason to call back, and a reply to their own inbound call is a different thing from a promotion. A customer who hasn't contacted you in two years and gets a "spring special" SMS is a different thing again. Transactional messages tied to a job the customer asked for — appointment confirmation, invoice reminder, a text back after a missed call — sit on much safer ground than blasts.

Opt-out handling is where automated systems get owners in trouble. If someone replies STOP, every future message has to stop, across every sequence. Not just the one they replied to. Check that your texting tool honors STOP globally and that it writes the opt-out back to the customer record, so a review request doesn't fire a week later.

Our rule of thumb: text about the job in front of you, keep a record of how you got the number, and honor STOP the first time. Anything that reads like an ad needs real consent.

We build software, not legal advice. Run your setup past an attorney before you send at volume.

Full platform or simple automation: what fits a one- or two-truck shop

A one-truck shop with a whiteboard that works needs the follow-up and the invoice chase to happen without anyone remembering. The whiteboard can stay. That's a lightweight setup: a texting tool, QuickBooks, and a handful of automations wired between them.

The math that matters is hours. Count the time your office spends chasing money and calling back quotes in a normal week. Then count the time it would take to build and maintain a Zapier setup, because that second number is never zero. Zaps break when a vendor changes a field name. Somebody has to notice and fix it.

Three things push a shop toward a full field service app, whether that's ours, Jobber or Housecall Pro:

  • Call volume. Once the phone rings more than one person can answer, scheduling by text and memory starts costing you jobs.
  • Dispatch. Two trucks can be juggled in a group chat. Four or five with same-day changes can't. When you're calling techs to ask where they are, you've outgrown the whiteboard.
  • Recurring jobs. Maintenance agreements, quarterly drain cleanings, annual backflow tests. These need to fire on their own or they quietly disappear. A spreadsheet won't chase them for you.

If scheduling and dispatch are genuinely solved and the crew is small, don't buy a platform to fix an invoicing problem. Bolt automations onto what you have.

If job history lives in three places and nobody can pull up what you quoted a customer two years ago, you have a CRM problem, and stitching that together with automations gets expensive in maintenance time fast. A single system holding customers, jobs, quotes and invoices is what the automations are supposed to run on.

How First-Rate Tech Corp builds this for you

We start by watching how the shop already runs. Who answers the phone, what happens when nobody does, how a quote gets written, when invoicing actually happens. Then we build the automation around that, instead of asking your office manager to learn a new set of habits on top of a full day.

Missed-call text back is usually first. The caller gets a text within seconds, and your phone shows you the reply, so a call that would have gone to the next plumber on the list turns into a booked job. Quote follow-up runs on the same idea: the reminder goes out on schedule, in plain language, and stops the moment the customer answers. Invoice reminders chase the balance so you don't have to bring it up in person.

Our field service app carries scheduling, dispatch, quotes, invoices and job notes for a small crew. You own it. No per-user fee that climbs every time you hire an apprentice, and no charge for the SMS automations sitting on top of it.

If you want to see what this would look like with your own call volume and your own invoice list in front of us, book a New Project Consultation. We'll walk through what falls through the cracks now and what we'd automate first.

Common questions about automating plumbing follow-ups and invoices

What is the 135 rule in plumbing?

That's a code question, and it lands in the same searches as billing software often enough to be worth a straight answer. Definitions vary by jurisdiction, and the version your inspector goes by is the only one that matters. Look up the fitting and venting language in the plumbing code your jurisdiction has actually adopted, and call the inspector's office to confirm how they read it before you rough anything in.

What makes billing software "best" for a plumbing shop?

Whether it fits the way your office already bills. A few things we'd hold out for: you can send the invoice from the truck before you pull out of the driveway, the customer can pay from the text without calling the office, it syncs to your bookkeeping instead of making you type everything twice, and payment reminders go out on their own. Price matters too. Watch for per-user fees that climb every time you put another apprentice on the schedule.

How do you automate the invoicing process, step by step?

  1. Pick one place invoices live. One. Not a folder, a notebook and an app.
  2. Invoice at the job, not at the kitchen table on Sunday.
  3. Put a pay link on every invoice so the customer can settle it from their phone.
  4. Write three short reminder messages in plain words. Polite, then direct.
  5. Set when each one goes out, and set the rule that stops all of them the moment the balance hits zero.
  6. Send yourself a copy of the first week's messages so you can hear how they sound.
  7. Check the unpaid list after two weeks and adjust the timing.

The office work you automate first should be the work that's costing you money right now, usually unanswered calls and unpaid invoices. If you'd like a second set of eyes on which one that is for your shop, book a New Project Consultation.

More onplumbinginvoice remindersmissed-call text backquote follow-upfield service software

Chris Hobbick

The Person Who Wrote This

Chris Hobbick

I build websites, stores, and automations for small businesses. I watch where the work gets stuck, calculate what it costs, and give you a fixed price to remove it.

Meet Chris →

The Newsletter

One useful idea. Once a week.

No trend reports. No recycled marketing advice. One practical breakdown of a problem that costs a small business time or money.

No daily noise. Unsubscribe whenever you want.