- Start only after the estimate is actually sent
- Space follow-up instead of sending everything at once
- Use the approved channels for that customer
- Stop when the opportunity changes or the customer responds
- Move true no-response leads into longer-term nurture
A practical estimate-follow-up sequence starts when the estimate reaches an approved Estimate Sent state, waits before the first reminder, follows up at gradually wider intervals, and exits as soon as the customer no longer belongs in the sequence. The biggest mistake is treating “entered the workflow” as the goal. The workflow exists to support the sales process. A customer who replies should be handed back to a person; one who accepts should move forward; one who declines should stop receiving sales-chase messages; one who remains unresponsive may eventually belong in long-term nurture.
A real Enciu Consulting estimate-follow-up sequence
The Carmil Car Audio build uses a 42-day email and SMS sequence: follow-up fires at 2, 7, 14, 21, 28, and 42 days after the estimate is sent, and unresolved opportunities are then moved into long-term nurture rather than left in the same sequence indefinitely. See the full case study →
Start with a reliable trigger
The workflow should begin from an event that actually means the estimate is ready for follow-up, such as a pipeline stage change or an estimate-status event. HighLevel currently supports both a Pipeline Stage Changed trigger and an Estimates trigger that can react to an estimate being sent, accepted, or declined.
The stop rules matter more than the number of messages
A sequence that cannot recognize a reply, an acceptance, a decline, or a booking is a bigger risk than one with too few follow-up touches. Design the exit conditions before deciding how many reminders to send.