In Grispi, closing multiple tickets at once is essential for archiving and keeping the interface clean. Tickets with Closed status are removed from view, become uneditable, and are more accurately represented in reports.
In this article, you’ll learn how to close tickets in bulk using two methods:
- Closing tickets in bulk via API
- Time-based closure using automation rules
🔌 Bulk Close Tickets Using API
Grispi’s API infrastructure allows you to programmatically manage a large number of tickets through external systems. Using APIs is ideal in the following scenarios:
- Closing hundreds or thousands of tickets based on specific filters
- Creating a closure schedule by timestamp, label, or brand (especially in systems with strict data retention policies)
With the Grispi API, you can:
- Update ticket status to Closed
- Perform batch operations using filters such as label, date, or brand
🧰 For more information, refer to the Grispi API documentation.
💡 If you’re not familiar with APIs, tools like Postman can help you send tickets to your Grispi account easily.
⏱️ Closing Tickets Using Automation
Grispi automations can automatically close tickets that remain inactive for a specified duration. This helps support teams clear forgotten or resolved tickets from the system.
To create an automation:
- Create a new automation
- Add a title (e.g., “Close tickets not updated for 30 days”)
- Set the following conditions:
- Ticket: Hours since last update > 720 (30 days = 720 hours)
- Ticket status < Closed
- Add the following action:
- Ticket status = Closed
- Save the automation
Note: If custom status categories are not enabled, you can directly use the condition and action: “Ticket Status = Closed”.
✅ Why Is This Important?
- Data Cleaning: Old tickets are archived, and clutter is removed
- Reporting Clarity: Only active tickets are included in analytics
- Performance Improvement: Interface runs faster and smoother
- Automation Efficiency: Eliminates repetitive manual work
🎯 Conclusion
Grispi provides robust automation and API capabilities for support teams aiming to streamline operations. Especially when managing a large number of tickets, these tools help ensure that:
- Time and effort are saved
- Old tickets are systematically archived
- A cleaner, more collaborative support environment is maintained
Whether you integrate with Grispi’s powerful API infrastructure or leverage time-based automations, you can elevate your support experience and improve operational efficiency.
For more information:
Automatic Ticket Closing in Grispi: Using Triggers and Macros
