# CRM Workflow Exception Handling Playbook | 121 CRM > Make failed, paused and unexpected automation visible, owned and safe to resolve. A fictional invoice reminder fails because the contact has no eligible channel and creates an accounts task. 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. ## Workflow exception handling: the working sequence Illustrative playbook — names, organisations and activity are fictional. ## Capabilities explained ### Testing and execution logs Supports test runs and operational evidence used to diagnose why a record did or did not follow a path. **How it works:** Runs an ordered sequence only after its configured trigger and conditions are met. **Why a business would use it:** Gives a human a way to verify automation and investigate exceptions. **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. ### Conditions and branches Routes a record through different configured steps when relevant data or events differ. **How it works:** Runs an ordered sequence only after its configured trigger and conditions are met. **Why a business would use it:** Lets one process handle common variations without pretending every customer is the same. **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. ### 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. ## Begin with a valid trigger, enough context and one owner A workflow log, customer response or monitoring rule identifies an exception. Before any automated action, confirm that the event, customer record and communication basis are suitable for this playbook. ### Trigger A workflow log, customer response or monitoring rule identifies an exception. ### Practical scenario A fictional invoice reminder fails because the contact has no eligible channel and creates an accounts task. ### Accountable owner Name the person or queue that accepts the work, monitors exceptions and can stop the sequence. ## Run the workflow exception handling 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. Contain the effect Stop repeat or conflicting actions where the exception could harm the customer. ### 2. Capture the evidence Record workflow, record, step, time and safe diagnostic context without exposing credentials. ### 3. Assign an owner Route technical, data or customer exceptions to the right accountable person. ### 4. Resolve the customer need Complete the required action manually where appropriate. ### 5. Correct and retest Fix the rule or data, test representative paths and document restart decisions. ## 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. ### Large or repeated failure Pause the affected workflow and escalate before processing more records. ### Customer already affected Communicate honestly and correct the relationship impact. ### Cause unknown Keep the record stopped; do not repeatedly rerun an unexplained action. ## 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. ### Exceptions with named owners Measure queue coverage. ### Time to contain customer impact Separate containment from final technical fix. ### Repeated root causes Prioritise removal and regression tests. ## Frequently asked questions ### When should the workflow exception handling playbook start? A workflow log, customer response or monitoring rule identifies an exception. Confirm the record is eligible and that a named owner or monitored queue is available before allowing customer-facing action. ### Which channels should the workflow exception handling 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 workflow exception handling 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 large or repeated failure, customer already affected, cause unknown. ### How should we judge whether workflow exception handling works? Review exceptions with named owners, time to contain customer impact, repeated root causes. 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/workflow-triggers](https://121.direct/crm/features/workflow-triggers) - [/crm/features/workflow-goals](https://121.direct/crm/features/workflow-goals) - [/crm/features/automation](https://121.direct/crm/features/automation) - [/crm/playbooks/new-lead-response](https://121.direct/crm/playbooks/new-lead-response) This Markdown alternative contains public product information only. It provides no access to CRM accounts, records, credentials or payment execution.