How to schedule recurring support tickets in WordPress

Write down how often the ticket should be created, when the first ticket should appear, who should receive it, and whether the schedule has an end date. Decide whether each occurrence should be a new ticket or a reply on an existing ticket.

Also choose a duplicate rule. A useful rule is one ticket per scheduled occurrence, identified by the schedule ID and due date. Without this, a delayed cron run or duplicated event can create the same ticket twice.

Open the documentation for your existing helpdesk plugin and confirm that it can create tickets programmatically or provides its own recurring-ticket feature. Do not guess a function name or hook: ticket creation is specific to the plugin.

If the plugin has neither a recurring-ticket setting nor a documented creation method, WordPress alone cannot complete the job. You will need custom integration or a ticket plugin with scheduling support.

Create a small custom plugin or site-specific plugin that schedules a recurring WordPress event with wp_schedule_event(). Use wp_next_scheduled() before scheduling so the event is not added repeatedly, then attach the event to code that creates the ticket through your helpdesk plugin's documented method. WordPress supports hourly, twice-daily, daily and weekly intervals by default; custom intervals can be added through the cron_schedules filter.

This route is flexible but is not a quick dashboard setting. You must handle ticket fields, assignment, notifications, duplicate protection, schedule changes and cleanup. Unschedule the event when the custom plugin is deactivated or the recurring rule is removed.

Remember that WP-Cron is triggered by site requests rather than running continuously. On a low-traffic site, a ticket scheduled for a particular time may be created late because no request triggered the event.

For deadlines that matter, configure your hosting provider's system cron or another monitor to request wp-cron.php at a regular interval. If you replace visitor-triggered cron with a server task, disable automatic WP-Cron requests in wp-config.php to avoid duplicate processing.

Run the scheduled event manually or use WP-CLI to inspect and run due cron events. Confirm that one ticket is created, the correct agent is assigned, email notifications arrive, and the next occurrence remains scheduled. WP-CLI includes commands for listing, running, scheduling and deleting cron events.

Test a missed run, a failed email, a daylight-saving-time change and deactivation of the custom code. The common Friday problem is a schedule that still exists after its source code has been removed, or a low-traffic site that leaves overdue tickets waiting until the next visit.

For the fast route, install and activate SupportCandy Schedule Tickets, then configure the recurring ticket's interval, first run, ticket content, assignment and notification settings in its scheduling controls. This avoids writing and maintaining the WP-Cron-to-ticket integration yourself.

Run one short test schedule before creating a daily or monthly rule. Check the generated ticket, email delivery and next scheduled occurrence, then remove the test rule and create the production schedule.