Framework
Automate routine steps only after the manual process is clear. Define what starts the workflow, what state it records, who owns replies, and what stops the next message.
Start with states, not messages
Map the estimate from sent to viewed, accepted, declined, paused, or needing a human response. Each state should have one clear next action. This prevents several tools from sending overlapping reminders.
Design the trigger and stop conditions
A trigger can be an estimate status or a defined delay. Stop or reroute when the customer replies, books, declines, opts out, or needs a revision. Human judgment belongs in exceptions, urgency, and scope decisions.
Keep the system observable
Review whether messages fire at the right time, whether ownership is visible, and whether exceptions are handled. A small, auditable workflow is more useful than a complicated sequence no one can maintain.
For the practical sequence—timing, SMS versus email, and implementation steps—read How to Automatically Follow Up on Estimates.