Ticket automations
How Core uses due dates, reminders, and recurring tickets to reduce manual follow-ups
Due dates & "due soon" reminders
When a ticket has a due date, Core can generate “due soon” notifications as it approaches the deadline. This works best when:
- Due dates are set intentionally
- Tickets are assigned to the right owner
- Status is kept current (so completed tickets don’t keep showing up in active queues)
Waiting customer reminders (and auto-close)
When a ticket is in Waiting Customer, Core can send reminders to prompt a response. If there’s still no response after repeated reminders, Core can automatically close the ticket to keep queues clean.
Use this workflow when you’re truly blocked on customer input, and include a clear “next step” in your last message (what you need and how they can provide it).
Recurring tickets
For scheduled work (maintenance, periodic reviews, recurring requests), Core supports recurring tickets so you don’t have to recreate the same work every month.
Recommended pattern:
- Write a clear template description
- Use consistent tags/categories for reporting
- Assign ownership up front (or route to a queue via “Waiting for Technician”)