To follow up on an estimate reliably, record every sent estimate in one shared list, assign one owner, set a next-action date, contact the customer through an appropriate channel, and update the record when the customer responds. No single waiting period fits every service business, so the timing should reflect the job, customer expectations, and previous conversation.
The goal is not to contact every customer as often as possible. It is to prevent estimates from being forgotten, avoid duplicate messages, and give every open quote a clear next step or final outcome.
The estimate follow-up workflow at a glance
- Move the estimate into a sent or awaiting-response state. It should no longer appear as an unfinished draft.
- Assign an owner. One person is responsible for reviewing the estimate and taking the next action.
- Set a next-action date. Base it on the job context and what was discussed with the customer.
- Create an internal reminder or supported automation. Follow-up should not depend on memory or an inbox flag.
- Record every response. Update the status when the customer asks a question, requests a change, approves, declines, or pauses the decision.
- End active follow-up deliberately. Stop reminders and mark the estimate approved, declined, paused, won, or archived as appropriate.
Keep the workflow compact enough that employees will maintain it. A short, consistently used process is more useful than an elaborate pipeline with outdated fields.
What to track for every sent estimate
The tracker can live in field service software, a shared spreadsheet, or a basic team list. Whatever tool you use, each row or record should answer three questions: What is happening now, who owns it, and what happens next?
- Customer and job reference: Enough information to identify the customer and proposed service.
- Estimate value: The quoted amount shown on the estimate.
- Date sent: When the estimate was delivered to the customer.
- Current status: For example, awaiting response, change requested, approved, declined, paused, or archived.
- Owner: The person accountable for the next action.
- Last contact: The date, channel, and a short summary of the latest interaction.
- Next action and due date: What needs to happen next and when it should be reviewed.
- Final outcome: Approved, won or booked, declined, paused, or archived.
A fictional tracker might look like this:
| Customer | Date sent | Status | Owner | Last contact | Next action |
|---|---|---|---|---|---|
| Sample Customer A | 8 July | Awaiting response | Office | Email sent 8 July | Review 11 July |
| Sample Customer B | 9 July | Change requested | Estimator | Phone call 10 July | Revise scope 11 July |
| Sample Customer C | 10 July | Paused | Owner | Customer reply 10 July | Review in agreed period |
Create a saved view or filtered list for estimates with overdue next actions, missing owners, or an awaiting-response status. That gives the team a practical work queue instead of requiring someone to search through email and message threads.
Assign follow-up ownership by team size
For a solo operator
Use one consolidated reminder list for all open estimates. A calendar reminder, spreadsheet due date, or software task can work, but avoid splitting follow-ups across inbox flags, paper notes, and memory. Record the result immediately after a call, email, or text so field work does not erase the context.
For an office-managed team
Assign the next action to a named role or employee, such as the estimator, CSR, office manager, or business owner. Keep one current owner even when several people can view the estimate. This reduces the risk of two employees contacting the same customer with conflicting information.
Define a simple handoff when a field employee creates the estimate but office staff manage follow-up. For example, the field employee completes and sends the estimate, then the office becomes the owner once its status changes to awaiting response. If the customer requests a technical or scope change, ownership can return to the estimator until the revision is ready.
Choose manual reminders or automated follow-ups
Manual reminders and customer-facing automations solve different problems. An internal reminder tells an employee to review the estimate and decide what to do. An automation sends a predefined message when stated conditions are met.
Use an internal reminder when context matters
- The proposed work is complex or has several options.
- The customer has already raised questions.
- An employee should review job notes before making contact.
- The appropriate channel or message depends on the previous conversation.
- A scope or price change may be required before another message is sent.
Use automation for repeatable follow-ups
Automation can fit a consistent acknowledgement or check-in, but it should verify that the estimate is still eligible before sending. An approved, declined, changed, paused, or archived estimate should not continue receiving stale reminders.
Current official examples illustrate the distinction. Jobber’s quote approval documentation describes quote reminders and follow-up methods, with manual reminders available across plans and automated follow-ups dependent on plan availability. Workiz estimate automation documentation describes add-on automations tied to estimate states and says conditions are checked again before an automation fires, allowing an action to be cancelled when the estimate no longer qualifies.
These are examples rather than a product comparison. Before implementing automation, confirm the current plan or add-on requirement, available channels, trigger conditions, and country or regional availability for the product you use. Email, text, approval, and automation options are not identical across platforms or accounts.
How to follow up on an estimate without a fixed schedule
Set the first next-action date when the estimate is sent. Use any expectation already established with the customer, such as when they plan to make a decision or whether they need a revised option. If there is no agreed timeline, choose an internal review date appropriate to the job rather than treating an arbitrary number of days as a universal rule.
A useful follow-up message should identify the estimate, invite questions or changes, and provide one clear way to respond:
Hello [customer name], I am following up on the estimate for [service or job reference] sent on [date]. Please let us know if you have questions, would like a change, or are ready to confirm the next step. You can reply to this message or contact [team member or office].
Adapt the wording to the customer and prior conversation. Avoid implying artificial urgency or repeatedly contacting someone who has declined, paused the decision, or asked for no further follow-up.
Choose and document the channel
- Email: Useful when the customer may need to review detailed information or reply with questions.
- Text: Suitable when supported by the software and consistent with the established customer conversation.
- Phone: Useful when a direct discussion is appropriate, but record the call outcome and next action in the same tracker.
Do not leave the record as awaiting response after the customer has answered. Enter a summary, change the status if needed, and set the next action while the conversation is still fresh.
Process approvals, declines, and change requests
Each response should move the estimate into a defined operational outcome instead of leaving it indefinitely open.
Approved
Stop estimate follow-up and hand the record into the business’s booking process. Customer approval and an internally won or booked job may be separate steps, so do not assume that approval automatically schedules work in every system.
For one current product example, Housecall Pro’s estimate documentation describes sending estimates by email or text and recording customer approval or decline in the account. Other platforms may use different terminology or processes.
Declined or lost
Record the response, stop active reminders, and close the quote using the most appropriate available status. A declined estimate should not remain in the same queue as customers who still need a response.
Change requested
Assign the estimate to the person responsible for revising it. Record what needs attention, set a due date, and pause generic follow-up messages until the revised estimate has been reviewed and sent. Keep this operational; questions about contractual meaning or pricing decisions require separate business review.
Paused
Use a paused state when the customer has not declined but active contact is intentionally on hold. Record why it is paused and, if appropriate, when the team should review it again.
Some systems let customers review or approve quotes through a self-service area. Readers evaluating that adjacent feature can consult our comparison of field service software with customer portals.
Review open estimates and close stale records
Review the open-estimate list on a routine that fits the volume of quotes your business sends. The review should focus on exceptions rather than rereading every record.
- Find estimates with overdue next actions.
- Assign records that have no owner.
- Check awaiting-response estimates with no recent contact.
- Move customer replies into approved, declined, change-requested, or paused states.
- Confirm that reminders and automations have stopped for records that no longer qualify.
- Archive estimates that no longer require active follow-up while retaining their operational history.
There is no universal point when every unanswered estimate should be archived. Make an intentional decision based on the job context, customer response, and your own operating process. Once active follow-up ends, record the outcome and remove any outstanding next action so the record no longer appears as unfinished work.
A reliable estimate follow-up process ultimately depends on four controls: a visible status, one owner, a dated next action, and a deliberate closing outcome. If you are moving from workflow design to evaluating two named platforms, the separate Jobber and Housecall Pro comparison examines their broader fit without changing the workflow described here.
Frequently asked questions
How long should I wait before following up on an estimate?
There is no universal waiting period. Set a next-action date based on the type of job, any decision timeline the customer provided, and the previous conversation. Treat timing as an editable workflow choice rather than a guaranteed best practice.
What should I say when following up on a quote?
Identify the estimate and date sent, ask whether the customer has questions or needs a change, and give one clear response path. Keep the message concise and avoid artificial urgency or aggressive language.
Should estimate follow-ups be manual or automated?
Use an internal reminder when an employee should review context before contacting the customer. Automation can suit repeatable messages when the system checks current estimate status before sending. Availability, channels, conditions, plans, add-ons, and regions vary by platform.
How do I keep sent estimates from being forgotten?
Maintain one open-estimate list with the customer, date sent, current status, owner, last contact, and next-action date. Review overdue actions and missing owners routinely rather than relying on email flags or memory.
When should an unanswered estimate be archived?
Archive it when the business has intentionally ended active follow-up. Record the outcome, remove the next action, and confirm that no reminder or automation remains active. The appropriate cutoff depends on the job and customer context.