Confirmation text message examples for contractors

A homeowner signs your water heater estimate at 9:15 on a Monday night and pays the deposit through the link. Nothing comes back except the card processor's receipt. On Tuesday morning they call the office: did you get it, when are you coming, do they need to be home? Your office manager is on the other line with someone asking whether their check cleared. By Wednesday a second homeowner who approved a quote last week has texted your personal cell twice and still doesn't know the start date.

Every one of those calls could have been a confirmation text message: a short note saying the thing they just did went through, and what happens next. Below are confirmation text message examples for each stage of a contracting job after the first booking: request received, estimate sent, quote approved, deposit in, start date set, parts in, crew on the way, job done and payment received. If you need the text that goes out right after someone books a visit, that one is in the appointment confirmation text post.

What a good confirmation text message does

A good one confirms a single thing and tells the customer what happens next and how to reach you.

• Put your business name in the first few words. Half your customers haven't saved your number.
• Name what you received or what you set: the signed quote, the deposit, the start date.
• Give the next step with a day or a window, even a rough one.
• On the first text you ever send a customer, add "Reply STOP to opt out."

Keep it to one message. A standard text holds 160 characters, and a single emoji cuts that to 70. Past the limit it splits into segments and can arrive out of order.

Confirmation text message examples for each stage of a job

Swap in your own details. Brackets mark the fields your office or your software fills in.

Request received

1. Web form or service request

Hi [Name], [Business] got your request about [issue]. We'll call by [time] to set up a visit. Reply here if it's urgent.

2. Photos received

Thanks, [Name]. [Business] got your photos of the [item]. We'll text a rough price or a visit time by [day].

Estimate sent

3. Estimate in their inbox

Hi [Name], your estimate from [Business] for [job] is in your email. Questions? Reply here and [Owner] will answer.

4. Estimate with options

Hi [Name], [Business] sent your estimate with [2] options. Reply with the one you want, or with questions.

Quote approved

5. Signed quote received

Thanks, [Name]. [Business] got your signed quote for [job]. We'll text a start date by [day].

6. Approved over the phone

Hi [Name], confirming you approved [job] at [price] with [Business]. Signed copy here: [Link]

I'd send text 6 every time. Two people can remember a verbal yes over the phone differently, and a written line with the price on it settles that before anyone orders parts.

Deposit received

7. Deposit in

Hi [Name], [Business] got your [$amount] deposit for [job]. Your start date comes next. Receipt: [Link]

Start date set

8. Single-day job

Hi [Name], [Business] starts [job] on [Day, Date] between [8] and [10] AM. Reply here with a gate code or pet info.

9. Multi-day job

Hi [Name], your [job] with [Business] runs [Mon, Date] to [Wed, Date]. Crew arrives by [7:30] AM each day. Reply with questions.

Parts or materials in

10. Waiting on parts

Hi [Name], the [part] for your [job] is ordered. [Business] will text when it's in to set your install date.

11. Parts arrived

Good news, [Name]. Your [part] is in. Can we install on [Day] or [Day]? Reply with the day that works.

Schedule change on your side

12. Moved because of you, not them

Hi [Name], [Business] needs to move your [job] to [Day, Date], same window. Sorry for the change. Reply if that doesn't work.

Crew on the way

13. On the way

Hi [Name], [Tech] from [Business] is on the way and should arrive around [time]. Reply here if anything changed.

Job complete

14. Work finished

Hi [Name], [Business] finished your [job] today. Questions about anything we did? Reply here. Invoice coming by email.

Payment received

15. Paid in full

Thanks, [Name]. [Business] received your payment of [$amount]. You're all set. Receipt: [Link]

If payment hasn't come in by the due date, that's a reminder rather than a confirmation. Those texts are in the payment reminder message post.

Quick reference

Most rows ask for nothing on purpose. If a confirmation doesn't need an answer, your office doesn't have to read any replies to it.

What it costs when these go out by hand

Every missing confirmation turns into an inbound call, and the call comes at the worst time: first thing in the morning, when the office is dispatching. A customer who signed a quote and heard nothing doesn't know whether to wait, so they call. If they don't call, some of them keep shopping, and a competitor who answers that night gets a job you had already won.

The other cost shows up in the field. When the start-date text never went out, nobody asked about the gate code or the dog, and a tech loses part of a morning standing in a driveway. When a verbal approval was never written down, the price argument happens after the work is done.

By hand, these texts depend on whoever is at the desk remembering nine different moments for every open job. They go out on slow days and get skipped on busy ones, and the busy days are when customers need them most.

What replacing it looks like

Every stage in that table already gets recorded somewhere. The estimate gets marked sent, the job moves to approved, the payment posts. A system that sends these on its own watches for those changes and sends the matching text.

1. List the job statuses you already use, in your field service software or even a shared spreadsheet.
2. Attach one text to each status, using the examples above as the starting draft.
3. Pull the fields (name, job, date, window, amount) from the job record so nobody types them.
4. Set quiet hours so a deposit that clears at 11 PM gets its text at 8 AM.
5. Route replies: a gate code gets saved to the job notes, "can we do Thursday?" goes to whoever schedules, and anything that sounds like a problem goes to the owner with the thread attached.
6. Log every text on the job, so the tech can see what the customer was told.

If you already pay for field service software, some of this may be built in. The work is usually wiring the stages it skips and routing the replies. More on what that looks like for a shop: automation for plumbing contractors. Builds start at $500 one-time, then a flat monthly from $99 after the included run-in period, and you can cancel.

What stays human

The texts can go out on their own, but the decisions around them still belong to a person. Someone still sets the start date when the schedule is tight, decides whether to squeeze in a customer whose parts arrived early, and calls when a job slips by more than a day, because a text isn't how bad news should arrive. When a customer replies to "job complete" with "the water heater is making a noise," that reply should reach a person right away instead of triggering another template. A good setup gets those replies in front of you fast with the full history attached, and leaves the answer to you.

If you'd like your customers to hear back at every stage without anyone at the desk remembering to send it, I can set that up around the software you already use. Start with the free 20 minute process audit.