> ## Documentation Index
> Fetch the complete documentation index at: https://docs.armin.cx/llms.txt
> Use this file to discover all available pages before exploring further.

# Legacy auto-resolve workflow

> Maintain workflow-builder auto-resolve flows for existing setups.

This page is for existing workflow-builder auto-resolve flows.

<Warning>
  Replace existing auto-resolve workflows over time. Native [Auto-resolve](/inbox/auto-solve) uses substring matching, so use it only for narrow phrases, senders, or subjects that always need no action. Use an [AI Agent example](/ai-agents/examples) whenever the surrounding conversation can change the decision. Follow the [migration guide](/ai-agents/migrate-from-classic-ai), then turn off the overlapping workflow once the replacement is proven. [Create an AI Agent](/ai-agents/getting-started), and open [Workflows](https://armin.cx/app/_/workflows) only during migration or for necessary maintenance.
</Warning>

## When to keep the workflow during migration

Keep the workflow active while you prove its replacement when:

* it already resolves the right tickets
* the conditions are fixed and easy to audit
* the flow does not need semantic matching
* the replacement is still being tested in a controlled scope

If the flow needs to understand message meaning, branch by topic, or explain why it resolved a ticket, move it to an [AI Agent](/ai-agents/getting-started). Once the replacement is proven, turn off the workflow for the same tickets before expanding the rollout.

## Maintenance checklist

<Steps>
  <Step title="Review the trigger">
    Confirm the trigger event still matches the tickets the flow should evaluate.
  </Step>

  <Step title="Check filters">
    Keep filters exact and narrow. Avoid using workflow branches to approximate customer intent.
  </Step>

  <Step title="Review actions">
    Confirm the flow adds the expected tag or note before resolving the ticket.
  </Step>

  <Step title="Test before changing">
    Use realistic tickets that should and should not be resolved.
  </Step>
</Steps>

## Watch the walkthrough

[Watch the legacy auto-resolve workflow guide](https://www.loom.com/share/6db1e7277bc94723b78d84c9876e8dd8?sid=f15dba6e-c1c9-4b34-b17a-23ec5abb7363)