# Abandoned Form Follow-Up Playbook | 121 CRM > Handle incomplete forms carefully, using only data and permission that justify contact. A fictional workshop form saves an email before completion; the business contacts the person only where the notice and consent support it. 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. ## Abandoned-form follow-up: the working sequence Illustrative playbook — names, organisations and activity are fictional. ## Capabilities explained ### Forms Collects structured visitor details and maps supported responses into CRM records and workflows. **How it works:** Publishes or collects information through a configured visitor-facing page, form or content experience. **Why a business would use it:** Turns an enquiry into usable data instead of an unstructured email. **Limitations:** Generated or templated content is not automatically accurate, accessible, compliant or ready to publish. **Human responsibility:** A person must review content, test the journey and explicitly publish or change live assets. ### Contacts Stores a person or lead with contact details, activity, ownership and related records. **How it works:** Stores or organises supported business data under configured fields, permissions and record rules. **Why a business would use it:** Gives a team one place to understand who a customer is and what has happened. **Limitations:** The platform does not make imported, duplicated or incomplete data accurate without review. **Human responsibility:** A data owner must define the record model and resolve quality, ownership and access exceptions. ### Triggers Starts a workflow after configured contact, event, appointment, opportunity, course or other supported activity. **How it works:** Runs an ordered sequence only after its configured trigger and conditions are met. **Why a business would use it:** Lets follow-up begin from a business event instead of waiting for someone to remember. **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. ### 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. ## Begin with a valid trigger, enough context and one owner A person begins but does not complete an approved form and the configured system captures an eligible event. Before any automated action, confirm that the event, customer record and communication basis are suitable for this playbook. ### Trigger A person begins but does not complete an approved form and the configured system captures an eligible event. ### Practical scenario A fictional workshop form saves an email before completion; the business contacts the person only where the notice and consent support it. ### Accountable owner Name the person or queue that accepts the work, monitors exceptions and can stop the sequence. ## Run the abandoned-form 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 what was captured Know which fields, notice and consent state exist before considering follow-up. ### 2. Check eligibility Exclude tests, accidental starts, existing customers already helped and sensitive forms. ### 3. Choose a light response Offer a return link or help without pretending the form was submitted. ### 4. Limit attempts Use a short, documented cadence with clear opt-out. ### 5. Delete or retain appropriately Follow the approved retention rule for incomplete data. ## 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. ### No valid contact permission Do not follow up; apply the retention policy. ### Sensitive form Disable routine recovery and use the approved specialist design. ### Technical failure Fix the form and apologise where appropriate before encouraging completion. ## 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. ### Eligible recoveries versus raw starts Avoid inflating the addressable audience. ### Completion after useful assistance Review the customer journey, not pressure. ### Complaints or unexpected-contact reports Treat as a design failure signal. ## Frequently asked questions ### When should the abandoned-form follow-up playbook start? A person begins but does not complete an approved form and the configured system captures an eligible event. Confirm the record is eligible and that a named owner or monitored queue is available before allowing customer-facing action. ### Which channels should the abandoned-form 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 abandoned-form 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 no valid contact permission, sensitive form, technical failure. ### How should we judge whether abandoned-form follow-up works? Review eligible recoveries versus raw starts, completion after useful assistance, complaints or unexpected-contact reports. 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/forms-lead-capture](https://121.direct/crm/features/forms-lead-capture) - [/crm/features/funnels](https://121.direct/crm/features/funnels) - [/crm/features/workflow-triggers](https://121.direct/crm/features/workflow-triggers) - [/crm/playbooks/referral-follow-up](https://121.direct/crm/playbooks/referral-follow-up) This Markdown alternative contains public product information only. It provides no access to CRM accounts, records, credentials or payment execution.