Editorial and legal boundary: This guide follows up on a customer-requested estimate or existing service relationship. It is not a cold-lead campaign or a universal consent determination. This is operational research, not legal advice; country, state, province, channel, consent, and message purpose can change the applicable rules.
valid outstanding estimate → useful decision → clean workflow state
Automation earns a place only when the result is human-visible, reversible, measurable, and safely suppressible.
The status-aware sequence
Validate before send
Confirm the estimate was delivered, remains accurate, is still within its validity period, and belongs to a reachable customer with the required messaging basis.
Wait by job context
Use timing appropriate to emergency repair, routine service, replacement, project work, insurance, or commercial approval rather than one global delay.
Send the decision path
Link to the exact estimate and offer clear actions: approve, ask a question, request changes, decline, or schedule a conversation.
Route questions to a person
A customer reply should pause the sequence and create an owned task with the estimate, property, options, and message history.
Use a bounded second touch
If still eligible, send one later reminder with the same valid scope. Do not manufacture urgency or silently change terms.
Close the state
Stop on approval, rejection, request for change, expiration, replacement estimate, opt-out, dispute, lost job, or manual sales ownership.
Learn by segment
Measure conversion and complaints by trade, job type, estimate value band, channel, timing, and number of touches without attributing every win to automation.
Documented product controls to verify
| Platform | Documented behavior | Control question | Test case |
|---|---|---|---|
| Jobber | Can send up to two automated quote follow-ups on eligible plans and follows the original delivery method | Which statuses, contacts, and communication settings suppress the send? | Edit, approve, request change, and opt out before each touch |
| Housecall Pro Pipeline | Can resend estimates through staged follow-ups and update estimate status; messages follow the original contact channel | What is available on the purchased plan and how are quiet hours handled? | Pause, approve, reject, archive, and manual takeover |
| Manual control | Calendar or assigned tasks prompt a person instead of messaging automatically | Which estimates are too complex or sensitive for automation? | High-value project and unresolved technical question |
Controls that must exist before activation.
- Do not send an outdated scope, expired price, or superseded estimate.
- Pause all automation when the customer replies or a staff member takes ownership.
- Make approval, questions, changes, decline, and opt-out easy to express.
- Separate estimate reminders from unrelated marketing campaigns.
- Retain the estimate version and message that the customer actually received.
- Review consent, identification, quiet-hour, opt-out, and recordkeeping rules for every launch market.
Report outcomes, exclusions, and failure signals.
- Delivered estimates eligible for follow-up
- View and response rate
- Approval after each touch
- Change-request rate
- Human response time
- Expired-estimate send rate
- Opt-out and complaint rate
- Gross margin of converted work