# Quote Follow-Up Playbook Without Pressure | 121 CRM > Follow up an issued estimate with useful context, clear ownership and respectful stop conditions. A fictional landscaping firm follows up Jo’s garden estimate before its stated validity date. This playbook turns that kind of situation into an owned sequence with explicit stop points, exceptions and measures. Use only channels, data and capabilities approved for your setup. ## Quote follow-up: the working sequence Illustrative playbook — names, organisations and activity are fictional. ## Capabilities explained ### Estimates Prepares an amount for customer review before it becomes an approved billing or document process. **How it works:** Uses configured products, merchant connections and checkout rules for an eligible payment or order journey. **Why a business would use it:** Provides a controlled step between a sales conversation and a formal charge. **Limitations:** Provider fees, tax treatment, disputes, settlement and feature eligibility remain separate responsibilities. **Human responsibility:** A responsible person must approve prices and terms and resolve refunds, disputes and fulfilment exceptions. ### Opportunities Represents a potential sale or deal linked to a contact, value, owner and pipeline position. **How it works:** Tracks a potential deal, stage, owner or task using configured pipeline and record rules. **Why a business would use it:** Shows which customer conversations are active commercial work rather than general contacts. **Limitations:** Pipeline position is only reliable when users and workflows update it consistently. **Human responsibility:** A responsible owner must qualify the deal, choose next actions and resolve stale or disputed status. ### Tasks Creates assigned, dated and optionally recurring actions against contacts or opportunities. **How it works:** Tracks a potential deal, stage, owner or task using configured pipeline and record rules. **Why a business would use it:** Turns the next step into owned work instead of leaving it inside notes or inboxes. **Limitations:** Pipeline position is only reliable when users and workflows update it consistently. **Human responsibility:** A responsible owner must qualify the deal, choose next actions and resolve stale or disputed status. ### Waits and timing Pauses a sequence until a duration, time, event or supported condition is reached. **How it works:** Runs an ordered sequence only after its configured trigger and conditions are met. **Why a business would use it:** Keeps communication paced around the customer rather than firing every step at once. **Limitations:** Automation follows its configuration; it cannot repair poor data, unclear rules or an unavailable external service. **Human responsibility:** A process owner must approve, test, monitor and pause or correct faulty automation. ### Goals and exits Moves or removes records when the configured outcome or stop condition has been met. **How it works:** Runs an ordered sequence only after its configured trigger and conditions are met. **Why a business would use it:** Helps avoid continuing follow-up after the customer has already acted. **Limitations:** Automation follows its configuration; it cannot repair poor data, unclear rules or an unavailable external service. **Human responsibility:** A process owner must approve, test, monitor and pause or correct faulty automation. ## Begin with a valid trigger, enough context and one owner An approved estimate is sent and the response remains open. Before any automated action, confirm that the event, customer record and communication basis are suitable for this playbook. ### Trigger An approved estimate is sent and the response remains open. ### Practical scenario A fictional landscaping firm follows up Jo’s garden estimate before its stated validity date. ### Accountable owner Name the person or queue that accepts the work, monitors exceptions and can stop the sequence. ## Run the quote follow-up playbook step by step Each step should leave evidence a colleague can understand. Timing and channels should follow the customer context rather than a generic high-pressure cadence. ### 1. Confirm the document Check that the right customer received the approved version with terms and exclusions. ### 2. Wait an appropriate interval Choose timing that reflects the value, urgency and decision complexity. ### 3. Offer useful help Ask whether the customer has questions rather than assuming silence means objection. ### 4. Record the outcome Capture accepted, declined, revised, delayed or no-decision status accurately. ### 5. Stop or continue deliberately End the sequence on response, expiry, opt-out or a human decision to pause. ## Stop the normal route when the facts change Exceptions are part of the process, not failures to be hidden. Route them to a person with the authority and context to decide what happens next. ### Pricing or scope query Route to someone authorised to explain or revise the estimate. ### Vulnerability or complaint Pause automated follow-up and move to the appropriate human process. ### Estimate superseded Stop messages tied to the obsolete version. ## Measure whether the work became safer and clearer Use measures that reveal ownership, service quality and control. Counts of messages, tasks or workflow runs are supporting signals, not proof of customer value. ### Open estimates with an owner Every live commercial document should have accountable follow-up. ### Age by decision status Separate genuinely pending work from stale records. ### Reasons for revision or loss Use structured reasons cautiously to improve the process. ## Frequently asked questions ### When should the quote follow-up playbook start? An approved estimate is sent and the response remains open. Confirm the record is eligible and that a named owner or monitored queue is available before allowing customer-facing action. ### Which channels should the quote follow-up playbook use? Use only configured channels that suit the purpose, customer preference and consent position. Give each channel a distinct role and check provider availability and usage charges before launch. ### When should quote follow-up automation stop? Stop when the purpose is complete, the customer responds or opts out, the data conflicts, or an exception needs judgement. In this playbook, pay particular attention to pricing or scope query, vulnerability or complaint, estimate superseded. ### How should we judge whether quote follow-up works? Review open estimates with an owner, age by decision status, reasons for revision or loss. Combine the numbers with sampled records and customer context; do not treat activity volume as a business outcome. ## Related CRM pages - [/crm/guides](https://121.direct/crm/guides) - [/crm/guides/customer-follow-up-automation](https://121.direct/crm/guides/customer-follow-up-automation) - [/crm/features/quotes-estimates](https://121.direct/crm/features/quotes-estimates) - [/crm/features/opportunity-management](https://121.direct/crm/features/opportunity-management) - [/crm/features/workflow-goals](https://121.direct/crm/features/workflow-goals) - [/crm/playbooks/appointment-confirmation](https://121.direct/crm/playbooks/appointment-confirmation) This Markdown alternative contains public product information only. It provides no access to CRM accounts, records, credentials or payment execution.