Recurring tickets overview

SummitPSA's recurring-ticket engine creates tickets for you on a schedule or in response to changing data, so routine maintenance and follow-ups never get forgotten. Two distinct mechanisms live side by side under Admin → Ticket Templates.

Scheduled templates

A recurring ticket template fires on a calendar schedule (every N days, weekly, monthly, quarterly, or annually). Each run creates one ticket for every company in the template's scope — all companies, internal companies, companies on a given contract type, or a hand-picked list. An internal_single scope produces exactly one ticket not tied to any company.

Automated rules

An automated ticket rule watches your data and raises a ticket when a condition is met — for example a contract or asset warranty nearing expiry, or an invoice left unpaid past a cut-off.

When it runs

Scheduled templates are evaluated hourly: a template fires when its next run date has arrived and the current server-local hour matches the template's configured creation hour. Automated rules are evaluated hourly too — both run in the same hourly job — but per-company duplicate protection limits each rule to at most one ticket per company per day. You can also trigger any template manually with Run now.

Generated tickets are logged. Each template keeps a run history with the number of tickets created, companies in scope, and any errors, viewable from its History page.