# Automatic Ticket Tasks

https://docs.wisecp.com/es/automatic-ticket-tasks

Apply a delayed set of routing and communication actions whenever a ticket matches chosen departments, statuses and priorities.

## Reaching the Screen

Open **Support Settings** and choose **Auto Tasks**: `{admin}/tickets/settings?tab=tasks`

## What Is on the Screen

The list shows saved tasks and opens the same dialog for creation and editing. A task needs a name, at least one effective condition and at least one action.

## Fields

### Conditions

- **Existing Task**: Set automatically while editing so saving updates the selected rule.
- **Name**: A staff-facing label that explains the purpose of the rule.
- **Departments**: Matches selected departments. Leave empty to match all departments.
- **Statuses**: Matches standard or custom states. Leave empty to match all statuses.
- **Priorities**: Matches selected urgency levels. Leave empty to match all priorities.
- **Delay Time**: Minutes the ticket must remain in the matching situation before actions are applied.

### Actions

- **Department**: Moves the ticket to another department, or leaves it unchanged.
- **Status**: Changes the standard or custom state.
- **Priority**: Changes urgency.
- **Assign to**: Assigns the ticket to a staff member.
- **Mark Locked**: Stops further client replies after the rule runs.
- **Send Notification Template**: Dispatches a selected user-ticket or admin-ticket notification template.
- **Add Reply to Ticket**: Adds the language-specific reply text, with supported client variables expanded.
- **Repeat Action**: Lets the rule run again for the same ticket while the same conditions continue to match.

## Tasks

### Create an automatic task

1. Choose **Create Automatic Task** and give the rule a clear name.
2. Select the departments, statuses and priorities to match, then enter the delay.
3. Choose at least one action and enter any automatic reply in every required language.
4. Save. Matching tickets are processed after the configured delay.

### Control repeated actions

1. Edit the task and review whether its actions leave the ticket inside the same matching conditions.
2. Leave **Repeat Action** off for a one-time transition, or enable it only for an intentionally recurring reminder.
3. Save the task. The repeat behavior now applies on later automation runs.

## Things to Watch

> **Blank condition groups mean all**
> 
> Leaving Departments, Statuses or Priorities empty does not disable that part of the rule. It makes that group match every value.

> **Repeat can send more than one reply**
> 
> If the actions do not move the ticket out of the matching conditions, an enabled repeat action can add the reply or notification again on later runs.

## Privileges

**Ticket Operations** is required to create, edit or delete automatic tasks.

## Related Screens

- [Custom Ticket Statuses](%7Badmin%7D/tickets/settings?tab=statuses)
- [Departments](%7Badmin%7D/departments)