> ## 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.

# Classic AI

> Maintain legacy AI sources, guidance, response modes, and workflow triggers.

Classic AI is the legacy configuration area for sources, guidance, response modes, triggers, and workflow connections.

<Warning>
  Plan to fully move existing Classic AI automation to AI Agents, not only new work. Follow the [migration guide](/ai-agents/migrate-from-classic-ai) to replace one use case safely, then turn off overlapping Classic AI behavior once the replacement is proven. Start with [Getting started](/ai-agents/getting-started), and use the [Classic AI agent list](https://armin.cx/app/_/ai/agents) only during migration or for necessary maintenance.
</Warning>

## Maintain an existing setup

<CardGroup cols={2}>
  <Card title="AI sources" icon="brain" href="/ai/sources/intro">
    Maintain website, file, Q\&A, and guidance knowledge on one page.
  </Card>

  <Card title="Classic agent triggers" icon="play" href="/ai/agent-triggers">
    Decide when the classic AI agent should run on a ticket.
  </Card>

  <Card title="Workflows with AI" icon="bolt" href="/ai/using-workflows">
    Let Classic AI trigger approved workflows for legacy repeatable support tasks.
  </Card>

  <Card title="Take over from Classic AI" icon="hand" href="/troubleshooting/take-over-from-ai">
    Stop automatic replies when a human takes over a live ticket.
  </Card>
</CardGroup>

## Response settings

For an existing Classic AI agent, choose how it handles incoming messages per channel:

| Mode                     | Behavior                                                 | Use when                                                           |
| ------------------------ | -------------------------------------------------------- | ------------------------------------------------------------------ |
| Suggest Drafts (default) | AI drafts a reply for agents to review, edit, or send    | Most teams want AI speed with human control                        |
| Generate on Demand       | No automatic draft. Agent clicks Generate / Generate New | You want AI only when requested                                    |
| Auto-send                | AI generates and sends without review                    | An existing, well-tested setup already relies on automatic replies |

Keep existing Auto-send configurations narrow and tested. To stop Classic AI after a human steps in, see [Take over from Classic AI](/troubleshooting/take-over-from-ai).

## Routing with AI Agents

Ongoing work on the ticket continues first. A matching legacy AI-guided workflow may start before a new AI Agent. Once an AI Agent owns the conversation, Classic AI backs off.

See [Routing and ownership](/ai-agents/routing-and-ownership) for the canonical behavior.

<Note>
  Auto-tagging now lives with native tag settings. See [Auto-tagging](/inbox/auto-tagging).
</Note>