A practical starting point

Following up on an unanswered estimate.

An estimate can be accepted, declined, postponed or simply waiting for a decision. A clear review process helps your team decide whether a follow-up is appropriate.

1. Start with the record you already keep

Choose one place where your team records estimates. Decide who keeps the status current and what information is actually needed, such as when the estimate was sent, what it covers and the customer’s preferred contact method.

2. Check the current situation

Before preparing a reminder, check whether the customer already replied, booked, declined or asked not to be contacted. A missing status is a question for a person to resolve, not proof that a customer is uninterested.

3. Set your own review rules

Your team can choose when an estimate is ready for review and what should prevent a message. The right timing and channel depend on the work and the customer’s preferences; there is no universal waiting period in this example.

4. Prepare a draft for a person

A template or assistant could assemble a short draft using only confirmed details. A team member should check the recipient, context and wording before deciding whether to send it.

Illustrative draft: “Hi, I’m checking whether you have any questions about the estimate we sent. If you’d like to discuss it, please let us know.” This is an example, not a message sent to a customer.

Check the tools you already use

Before buying something new, look for follow-up features in your existing software. For example, Jobber describes quote follow-up reminders. Check your own plan and settings, and decide which messages your team should review.

5. Test and measure the workflow

Try fictional examples first, including a reply already received, an incomplete record and a customer who asked not to be contacted. If the business later trials a change, agree on how to measure the work and review errors; a template alone does not prove time saved or more jobs won.

This is general guidance, not a claim about your current process. Any access, data handling, sending, costs and implementation need their own discussion and authorization.

Want a written look at one task?

Cooks Agents offers a free first review of one repetitive process. Start with a description or fictional example.

Contact Cooks Agents

See a fictional sample review