A quiet estimate is an unanswered question, not a diagnosis
A customer who has not replied may be comparing options, waiting for approval, unclear about the scope or no longer interested. A silence alone does not tell you which explanation is correct. Start with the estimate version, when it was delivered, the last real conversation and any date the customer asked you to respect.
Keep unsold work separate from estimates that expired, were declined or have already been approved. A reliable follow-up list gives each open estimate an owner and a next action. Without that separation, automation can ask an existing customer to accept a proposal they have already accepted or revive a price the business can no longer honor.
Different reasons require different follow-up
- Record state
- Delivered, no discussion yet
- Useful next step
- Confirm receipt and offer to clarify scope
- Avoid
- Assuming the customer rejected the price
- Record state
- A specific question is open
- Useful next step
- Answer that question or assign it to the right person
- Avoid
- Sending another generic reminder
- Record state
- Customer asked for a later date
- Useful next step
- Resume at the agreed time
- Avoid
- Repeated messages before that date
- Record state
- Declined, expired or approved
- Useful next step
- Close or move to the correct workflow
- Avoid
- Continuing the unsold-estimate sequence
| Record state | Useful next step | Avoid |
|---|---|---|
| Delivered, no discussion yet | Confirm receipt and offer to clarify scope | Assuming the customer rejected the price |
| A specific question is open | Answer that question or assign it to the right person | Sending another generic reminder |
| Customer asked for a later date | Resume at the agreed time | Repeated messages before that date |
| Declined, expired or approved | Close or move to the correct workflow | Continuing the unsold-estimate sequence |
Make each follow-up about the actual decision
A useful message references the work the customer is considering and offers one clear next step. It might clarify what is included, arrange a conversation or explain which information is still needed. It should read like a continuation of the existing discussion, with no false urgency or unsupported claim that a date is being held.
AI can summarize the conversation, identify an unresolved question and draft a response using the approved estimate. It should leave unknown facts blank for review. A message that sounds personal but contains the wrong scope, price or availability is worse than a simple accurate reminder.
A follow-up that resolves the unanswered question
Decide what the assistant can say and what needs approval
The approved estimate should remain the source for scope and price. Changes to discounts, payment terms, quantities or promised completion dates need the business’s agreed approval process. An assistant can assemble the request for a change without having authority to grant it.
Use a small set of explicit actions: prepare a draft, send an approved reminder, record a reply or assign a question. When a customer wants something outside those actions, create a visible handoff. Record which estimate version supported the message so the team can reconstruct the conversation later.
A good follow-up system knows when to stop
Stop the sequence when the customer declines, asks not to be contacted, approves the estimate or starts a conversation that needs a person. Pause when staff are already handling the request. A shared contact history helps prevent separate team members and automations from sending overlapping messages.
Choose the cadence from your buying process and customer expectations, not a universal rule about how many messages everyone needs. Review the content and timing of unanswered sequences. More activity can make the business less helpful if it ignores what the customer already said.
Measure completed decisions and the work needed to get them
Track the age of open estimates, time to the first relevant follow-up and whether the customer reached a clear decision. Separate approved estimates from completed work and collected payment. A proposal moving to “won” is not the same event as money reaching the business.
Use replies to learn why customers hesitate. Categorize questions about scope, timing and budget without inventing a reason for silence. Compare similar groups over complete time periods, and review opt-outs and complaints alongside approvals. A useful pilot improves clarity and follow-through without creating unnecessary contact.
Begin with drafts and a clean open-estimate list
Take a bounded group of current estimates and verify their status manually. Let the assistant prepare follow-up drafts for the owner to review before anything is sent. Include examples with conflicting prices, a recent customer reply and an estimate that has become stale.
Once the drafts consistently use the correct facts, consider automating only a narrow approved message type. Keep the process connected to live status changes so a reply or approval stops the reminder. The first project should improve a real follow-up queue, not create another disconnected sales dashboard.
Get the estimate list ready
A small, accurate queue is more useful than a large automatic message sequence.
- Separate current estimates from approved, declined and expired records.
- Keep the exact scope and price version with each opportunity.
- Identify the customer’s last question or agreed contact date.
- Review drafts before enabling automatic messages.
- Track clear decisions, opt-outs and completed work separately.
Hire TDAT to build your estimate follow-up.
Put TDAT in charge of connecting your estimates, customer replies and next actions. We handle the workflow design, implementation and testing so your team can follow up with accurate information and clear ownership.
Hire TDATOn the project call, we’ll discuss the problem, your existing tools and what TDAT should take off your hands. Then we can define the scope and next steps.
Or call (919) 289-1231
Common questions
Can AI offer a discount to close the sale?
Only if your business has explicitly authorized the relevant pricing rule. A safer starting point is to prepare the customer’s request for staff approval without changing the estimate.
How many follow-up messages should we send?
There is no universal number. Use the buying process, the customer’s stated timing and your contact rules, then stop or pause when the record requires it.
Is an approved estimate the same as revenue?
No. Approval, work completion, invoicing and payment are separate states. Report them separately so sales activity is not mistaken for collected income.
Should we buy a new customer management system first?
Not necessarily. Check whether your existing system can track estimate versions, replies and next actions. The improvement may be a connection and a review process rather than a replacement.