A useful plumbing estimate follow-up SOP gives every open estimate one owner, one next action, and one stop condition. For a normal residential or light-commercial estimate, start by confirming delivery, then use a short seven-day sequence that makes it easy to ask a question, request a change, accept, decline, or choose a later date. Stop the sequence as soon as the customer responds.
The goal is not to chase people until they surrender. It is to remove uncertainty while protecting the customer relationship and the estimator's time. The cadence below is an original operating template, not a claimed industry benchmark. Adjust it for job size, sales cycle, customer preference, and applicable communication rules.
The seven-day plumbing estimate follow-up cadence
Original downloadable worksheet
Build your estimate follow-up plan
Enter the operating details once. The scripts and download update automatically. Check off each touch as your team completes it.
| Done | When | Channel | Owner action | Stop or route when |
|---|---|---|---|---|
| Day 0 | Send the estimate, summarize the next step, and record delivery status. | Bounce, wrong contact, or customer response. | ||
| Day 1 | Text, if approved | Confirm the estimate arrived. Invite one question. Do not restate the full proposal. | Opt-out, question, requested change, accept, or decline. | |
| Day 3 | Call | Make one brief call. Leave a short voicemail only if that matches company policy. | Live response or callback. Route technical, scope, and price questions. | |
| Day 5 | Offer three simple paths: proceed, ask for a change, or choose a later follow-up date. | Any choice or reply. | ||
| Day 7 | Customer's approved channel | Send a courteous close-the-loop note and move the estimate to the correct status. | Reply, opt-out, or final status recorded. |
Scripts that update with your operating details
Day 0 email
Subject: Your estimate from Your plumbing company
Hi [Customer first name], your estimate is ready. Reply here with any question or requested change. If anything about the scope or options needs clarification, I will route it to Estimator or service manager.
Thanks,
Office coordinator
Day 1 text
Hi [Customer first name], this is Office coordinator with Your plumbing company. I am checking that your estimate came through. Reply here with any question or requested change.
Day 3 call or voicemail
Hi [Customer first name], this is Office coordinator from Your plumbing company. I am calling to make sure you received the estimate and to see whether there is one question I can route for you. You can call or reply using the contact information on the estimate.
Day 5 email
Subject: What would be most useful next?
Hi [Customer first name], I am keeping your estimate open. You can reply with one of three next steps: ready to proceed, question or change needed, or follow up on a later date. I will record your choice and route anything that needs Estimator or service manager.
Day 7 close-the-loop note
Hi [Customer first name], I am closing the routine follow-up loop on this estimate so we do not crowd your inbox. If you want to proceed or revisit it later, reply here and we will confirm the current next step before making any commitment.
Assumptions: The customer requested or expects the estimate, the estimate has already been sent, contact details are accurate, and the company has confirmed that the chosen channel and message type are permitted. This cadence does not determine consent, create permission, or replace legal advice.
What must happen before day zero
A follow-up sequence cannot fix an estimate that was never delivered or a record nobody can interpret. Before the first touch, verify the customer name, contact details, estimate version, sent timestamp, delivery status, and the person authorized to answer questions. If the estimate depends on a pending technical, scope, availability, or pricing decision, resolve or label that exception before starting routine follow-up.
Choose a single system of record. The open estimate should not live only in an estimator's text thread or memory. ServiceTitan's current plumbing estimating page, for example, says its dashboard can use tags and filters to track customers who have not responded to estimates. That is one provider's documented feature, not a recommendation or a plumbing-wide standard. Review ServiceTitan's current estimating documentation.
Use one owner, not five senders
The follow-up owner should check the queue daily, send the approved touch, record the result, and route exceptions. The estimator or service manager should answer questions that require technical knowledge, a changed scope, a discount, an availability promise, or another decision outside the office role. Customers should not receive parallel calls from the technician, owner, CSR, and an automation because nobody knows who acted.
For a smaller shop, the owner may still be the decision-maker. That does not mean the owner must run the list. A coordinator or dedicated assistant can own approved estimate follow-up when the normal action, system, and escalation path are clear. The assistant should not change pricing, interpret technical questions, or promise field capacity without authority.
The CRM fields that make the SOP auditable
Use fields that answer what happened and what happens next. A compact record should include:
- Estimate ID and version: the exact proposal being discussed.
- Customer and preferred channel: plus the source and status of any permission your policy requires.
- Sent and delivered timestamps: including bounce or failed-message status.
- Follow-up owner: one named person or role.
- Last touch: date, channel, template version, and outcome.
- Next action and due time: never “follow up later.”
- Estimate status: awaiting response, question pending, revision requested, accepted, declined, later date, or closed.
- Decision owner and deadline: when a question leaves the routine lane.
- Stop or suppression status: the instruction that prevents another send.
A dashboard is useful only if these fields drive a daily work queue. Filter for open estimates with a due next action, exclude stopped records, and review exceptions separately. Automation can create the task or send an approved message. A person still needs to own failed delivery, ambiguous replies, stale pricing, and questions the template cannot answer.
Communication rules belong inside the workflow
Email and text rules depend on the message, technology, consent history, jurisdiction, and other facts. The FTC explains that CAN-SPAM treats commercial content differently from transactional or relationship content and requires an opt-out mechanism for covered commercial email. Read the FTC's current business guide. Do not assume that sending an estimate gives unlimited permission for later promotions.
For automated calls and texts, the FCC's 2024 consent order addresses reasonable ways to revoke consent and stopping covered communications after revocation. A January 2026 FCC order extended the effective date of part of the newer rule until January 31, 2027, while saying the waiver does not change other existing revocation rules or rulings. Read the 2024 FCC order and the 2026 extension order. Because the details are fact-specific and changing, have qualified counsel approve your calling and texting policy.
Your software settings should enforce that policy. Twilio's provider documentation says its long-code messaging handles several standard English opt-out keywords and can block future outgoing messages after an opt-out. That is a Twilio-specific control, not a complete compliance program. Check Twilio's current opt-out documentation or the equivalent documentation for your provider.
How to measure the process without inventing ROI
Start with process measures you can verify: estimates sent, delivered, awaiting response, touched on time, replied to, revised, accepted, declined, and closed with no response. Also track the time from customer question to a qualified answer. Do not label every acceptance after a reminder as revenue “recovered.” The customer may have accepted without the touch, and the estimate value is not the same as collected revenue or profit.
Review the queue weekly. Look for delivery failures, touches sent after a stop request, unresolved questions, estimates with no next action, and templates that produce confusion. Change one part of the cadence at a time and record the version. The practical win is a visible pipeline and a consistent customer experience, not a made-up conversion promise.