Scheduled tickets

Scheduled tickets create themselves on a cadence — weekly server checks, monthly patch reviews, quarterly client health checks — so recurring work lands in the queue without anyone remembering to raise it.

Creating a schedule

1. Go to PSA → Workflows → Scheduled tickets and click New schedule.
2. Fill in the ticket to create: subject, description, client, type, priority and who it should be assigned to.
3. Set the cadence: daily, weekly (pick the weekday), monthly/quarterly/yearly (pick the day of month, 1–28), the local time and timezone.
4. Save. The list shows when each schedule will next run.

The ticket is created through the normal pipeline, so your ticket rules and notifications fire exactly as if someone had raised it by hand.

Behaviour worth knowing

• Every N: the interval multiplies the frequency — weekly with interval 2 is fortnightly.
• Missed runs create one ticket, not a backlog. If the platform was unavailable across several occurrences, the next sweep creates a single catch-up ticket and realigns the schedule.
• Pause instead of delete: deactivating a schedule keeps it configured but stops creating tickets.
• Day of month is capped at 28 so "monthly on the 30th" can never silently skip February.

Permissions

Schedules live on the automation surface and use the same permissions as ticket rules: view to see them, create/edit/delete to manage them.