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

# Run on existing tickets

> Assign an AI Agent to open tickets one by one or in bulk so it can work your backlog.

Triggers cover new matching tickets. To work tickets that are already open, assign an AI Agent to them.

Assignment always starts a run. If you assign an agent, it runs.

## Assign one ticket

<Steps>
  <Step title="Open the ticket">
    Open the ticket in the [Inbox](https://armin.cx/app/_/inbox).
  </Step>

  <Step title="Find the AI Agent property">
    In the ticket properties, open the **AI Agent** row under the human assignee.
  </Step>

  <Step title="Choose the agent">
    Pick an Active or Manual only agent. Inactive agents do not appear in the list.
  </Step>
</Steps>

The agent then follows its instructions and action settings. If **Send reply** is set to ask every time, the agent proposes a reply for approval instead of sending it immediately. See [Human in the loop](/ai-agents/human-in-the-loop).

## Assign many tickets

Use bulk assign when a backlog is already tagged or filtered for one support job.

<Steps>
  <Step title="Filter the backlog">
    Build an Inbox view or filter for the open tickets, for example all open return tickets.
  </Step>

  <Step title="Select the tickets">
    Select the tickets in the ticket list. You can select a page or the matching set.
  </Step>

  <Step title="Assign the AI Agent">
    Open the assign action in the selection bar and choose the AI Agent. Recent AI Agents appear
    near the top with an AI badge.
  </Step>
</Steps>

Larger selections process asynchronously. Direct bulk assign stays synchronous up to 100 tickets; bigger sets continue in the background.

## After the run

When the run finishes, Chatarmin CX usually clears the live AI Agent assignment on the ticket. History remains available through Inbox filters:

* **was assigned** — tickets this agent has handled
* **is last** — tickets where this agent was the most recent AI handler
* **is** — tickets currently assigned while a run is active or paused

See [Views and filters](/inbox/views-and-filters).

## FAQ

<AccordionGroup>
  <Accordion title="Does assignment ignore triggers?">
    Yes. Manual assignment is a direct run. The agent does not need to match its trigger filters
    again for that ticket.
  </Accordion>

  <Accordion title="Can I assign an inactive agent?">
    No. Activate the agent or set it to Manual only first. See [Activate an AI Agent](/ai-agents/activate).
  </Accordion>
</AccordionGroup>