SupportCandy Automatic Close Tickets
Antivirus scan
Powered by ClamAV
✅ Verified clean
This product file has passed our security filters.
Want to run a fresh ClamAV scan right now? Takes a few seconds and shows scanner version, signature DB and live result.
This can take 5 to 30 seconds.
Clean file Threat detected
No threats detected in this file.
- File
- Size
- Scanned
- ClamAV
- Signature database
⚡ Powered by ClamAV
Scan could not be completed
Report product
If you detected an issue (broken file, malware, inappropriate content, etc.) let us know and we'll review it ASAP.
Sign in to report
About SupportCandy Automatic Close Tickets
Tickets waiting for a customer who will not reply
A customer opens a ticket, your team answers, asks for a detail and the customer never comes back. The ticket sits in the inbox for weeks, mixed in with the ones that do need work. Over time nobody knows what is alive and what is just noise.
SupportCandy Automatic Close Tickets is an add-on that closes those tickets for you once the days of inactivity you have set go by.
What you decide in SupportCandy Automatic Close Tickets
The administrator defines the rule and the rest happens on its own:
- Days of inactivity: how many days without activity must pass before the ticket is closed.
- Statuses that are watched: you choose which statuses the rule applies to.
- Advance warnings: you can schedule several warning emails that the customer receives before the closing date.
Warnings before closing prevent complaints afterwards
Closing a ticket with no notice often ends in the classic "nobody answered me". With this add-on the customer receives one or more emails on the days you configure before closing. If they still do not reply, the ticket is closed when the inactivity period runs out.
Before going live, test it with a ticket of your own and check what happens if you reply after receiving a warning, to make sure the flow fits the way you work.
It only watches inactivity: you cover the rest
- Already solves: automatically closing tickets after the days of inactivity you specify.
- Already solves: limiting the rule to certain ticket statuses.
- Already solves: sending several warning emails to the customer before closing.
- You cover: having SupportCandy installed, because this is an add-on and does not work on its own.
- You cover: deciding how many days and how many warnings make sense for your kind of support.
- You cover: making sure the problem was really solved: the plugin closes because of silence, not because of a solution.
- You cover: any follow-up after closing, such as a satisfaction survey.
Frequently asked questions
Does it work without SupportCandy?
No. It is an extension for SupportCandy and needs that plugin as its base.
Can I warn the customer more than once?
Yes, several warning emails can be configured before closing.
Are all tickets without activity closed?
Not necessarily: you choose which statuses are taken into account.
What time frame should I set?
It depends on your support. If customers usually have to run tests or gather information, they need more room than with simple questions. The prudent approach is a generous period with the warnings spread across it.
Topics
Version history
-
v
3.1.2 Current 5 Sep 2026
-
v
3.1.1 24 Mar 2026
Customer reviews
Sign in to leave a review. Only people who have the product can review it.
No reviews for this product yet.
Frequently asked questions
-
GPL (General Public License) is the license under which WordPress and most premium plugins/themes are distributed. It grants you the right to use, modify and redistribute the software in as many projects as you want, with no domain restrictions.
-
Yes. With membership you get automatic updates via our GPLClub Updater plugin (installed on your WP, detects new versions and applies them). With individual purchase, you get one year of manual updates from your account.
-
Depends on the plan. Monthly: 3 domains. Semi-annual: 7. Annual and Lifetime: 15. Individual purchase: 1 domain.
-
GPLClub offers its own support for installation, configuration and compatibility. For direct support from the original author (feature requests, product-specific bugs), a license purchased from the author is required.
