Follow up on installation quotes without making more work
Give every quote an owner, a next action and a way to stop. Check the tools before adding automation.
Give the quote an owner first
A quotation can be sent correctly and still become hard to manage. A customer asks a question by phone. Someone records acceptance while a reminder waits elsewhere. The only person who knows the next action is away.
Start with an accountable person and a small set of meaningful states. Automation can support that process once the team knows what should happen. These are proposed operating rules, not results from a client campaign.
Use states that tell the team what to do
| State | Next action |
|---|---|
| Prepared | Check the quotation before issuing it. |
| Sent | Record the owner and next review date. |
| Question received | Pause ordinary reminders and assign a response. |
| Accepted | Stop sales reminders and move to the agreed booking or payment process. |
| Declined | Stop reminders and record the reason where appropriate. |
| No response | Review or close the quote under the business’s policy. |
| Contact restricted | Stop customer messages and review the record. |
Define “sent” and “accepted” in the system you use. An email leaving the outbox is not evidence that the customer read it. Opening a document is not acceptance of the quotation.
Keep the quote reference, contact route, owner, current status and next action in the appropriate customer record. Avoid copying every attachment into an additional tool.
Look at what the existing software can do
Request forms, tasks and quote reminders are already available in many field-service products. Check the current account and subscription before adding another application.
Jobber documents built-in quotation approval and follow-up tools. That is an example of a native option to inspect, not a promise that every account or process supports the same connection. Jobber quote approval documentation.
If the tools cannot reliably detect a reply or a changed status, create an internal reminder and let a person decide what to send. A simple routine the team trusts can be more useful than an unattended message sequence.
Agree timing and write a useful message
A planned installation, an urgent repair and a commercial estimate have different decision cycles. Do not give them the same automatic sequence.
As an illustrative starting point, a team might review an unanswered installation quote after three business days, then decide whether a follow-up is appropriate. A second internal review could happen after seven business days or at the quote’s actual expiry. These intervals are examples, not an industry benchmark.
An approved message should refer to the real quote and make replying easy:
I am following up on the installation quotation we sent. If you would like us to explain an item or check the proposed scope, reply to this email. If your plans have changed, let us know and we will update the record.
Add the correct quote reference and business identity. Do not invent a reserved appointment, limited stock or an expiry date. Check the purpose and permissions for the actual communication; service correspondence does not give unlimited permission for later promotions.
Check the current status before sending
The status may change while a reminder waits. Check it again at the sending point. Has the customer replied, accepted or declined? Was the quotation changed? Has someone paused the process or asked for contact to stop?
A check made when the workflow first starts cannot answer those questions several days later. The team needs a dependable override and a clear way to remove queued actions.
Confirm how replies are detected. If a phone conversation is not recorded in the system, an automatic rule may not know it happened. Document the part a person still needs to do.
Make failure visible, then test it
A failed connection needs a responsible person, the affected reference and a practical recovery instruction. Retrying should not create repeated messages or competing quote records.
Test with separated sample records before sending anything to customers:
- A normal quotation with no reply.
- A reply, acceptance or decline while a reminder waits.
- A changed quotation or missing contact detail.
- A repeated event or connection failure.
- A staff pause and a request to stop contact.
Check the receiving system as well as the workflow’s success label. An execution can complete while assigning the wrong person or creating an unhelpful task.
The Still Air enquiry demo illustrates assignment, duplicate handling and recovery using sample data. It does not implement this entire quotation process.
Measure the process before extending it
Track the active quote count, overdue actions, exceptions and maintenance effort. Record accepted jobs separately from email opens or reminder counts.
Only add the next routine when the first is useful and reliable. Booking handover or maintenance reminders introduce their own states, permissions and support work.
A complete quotation process may exceed a small fixed-scope integration. Ask for the applications, actions, stop rules and support in writing. Our follow-up automation service starts with one agreed process. The pricing page sets out its limits and separate costs.
Need a second look?
A first fit conversation is free. If a written priority list would help, the Website & enquiry review has a separate price and scope.
See the review and project prices