Auto Close

Automatically close old, stale and abandoned tickets

Do you need a way to manage tickets that have been abandoned by users?  How many times have you had to go through your ticket list to manually close out tickets that a user has not bothered to respond to?

This plugin can help.  It allows you to automatically create and send warning emails as well as automatically close tickets – all based on sophisticated rules centered around the age and status of a ticket.

Send Warning Emails Based On The Status Of A ticket

The most common condition is an in-process ticket where the agent has replied but the user has not bother to respond back.  However, you can also send warning emails based on the custom statuses created by our custom status add-on – for example, an agent can set a status to automatically close out a ticket after 24 hours.  Or maybe a warning email can be sent if an email has been placed on hold for too long.

as-atc-addnewwarningmessage01

Send A Series Of Warning Emails

You can create a series of warning emails.  For example, you can send one email after 48 hours, another after 5 days and another after 7 days.

Automatically Close Tickets

Any warning email that is sent can also automatically close a ticket.  For example, if you have a series of warning emails that are sent after 2 days, 5 days and 7 days – you can configure the 7-day email to close the ticket.

Different Sequences For Different Statuses

You can create different sequences for different statuses.  For example, you can create a 1-2 day sequence for a status called “Completed” where the agent is reasonably sure that there is no reason to keep the ticket open but still wants to give the user an opportunity to respond.  You can then have a completely different sequence for “in-process” tickets where the user has not responded at all.

Control How Often Abandoned Tickets Are Checked

Usually you would only want to check tickets every 24 hours or so but for operations with an extremely large volume of tickets you can check as often as 5 minutes.

as-atc-cron01

Unlimited Sequences, Unlimited Emails

While not necessarily practical, you do have the ability to set up sequences of dozens or even hundreds of warning emails that cover dozens of different custom statuses.

Purchase options

  • Billed yearly until cancelled

  • Billed yearly until cancelled

  • Billed yearly until cancelled

Add to Cart

Cart

  • Your cart is empty.

Basic System Requirements

  • WordPress Version 4.4 or later
  • Awesome Support Version 5.8.0 or later
  • PHP 5.6, (7.1 or later recommended)

Additional Requirements

There are no additional requirements for this item.

Documentation

Purchase options

  • Billed yearly until cancelled

  • Billed yearly until cancelled

  • Billed yearly until cancelled

Add to Cart

RELATED ITEMS

The items below are great complements to this product!


 

Recurring Subscription Notification

The pricing for this (and most other add-ons) is set as a subscription by default. However, you are free to cancel the recurring subscription at any time – you will still be entitled to the one year of free updates and support from the time of your last payment. The software will generally continue to work without additional payments. However, you should be aware that, as with all software, a future update of any of WordPress / Awesome Support Free Core could include a breaking change. At that time, if you are not on a subscription plan, you will need to purchase a new license to obtain the compatibility updates necessary for the product to continue to work.

To cancel your subscription:

  • Credit card or stripe users- just go to your MY ACCOUNT page on our website.
  • Paypal users - cancel from directly inside your Paypal account.

This notice does not apply to service products such as custom programming or to free plugins.

Changelog

Version 1.0.7

  • Fix: Cron Schedules array needed an is_array check before attempting to use it as an array

Version 1.0.6

  • Fix: An array of notifications was not including the proper array configuration which meant that emails were being sent to numbers instead of email addresses

Version 1.0.5

  • Tweak: Use AS core logging function instead of proprietary logging
  • Tweak: Make sure that auto-close system user includes an email address when its being created

Version 1.0.4

  • Fix: Minor fix to deactivation code to remove a PHP notice.
  • Fix: Use gmt dates for both sides of a key time based calculation.
  • Tweak: Now requires AS version 4.1.0 as the minimum version
  • Tweak: Now requires PHP 5.6 as the minimum version since that is what AS 4.x requires
  • Tweak: Email receipients to match changes made in notifications api for 4.0.6
  • Tweak: Updated warning message custom field internal definition to use new 4.1.0 attributes to prevent display on the front end.
  • Tweak: Grammar changes
  • Tweak: Update language catalog file
  • Tweak: Option to control how many messages per sequence is sent out on each cron cycle. Now defaults to 1 instead of All
  • Tweak: Option to clear and restart the sequence of messages for any tickets where the full message cycle is not yet complete.

Version 1.0.3 - November 3rd, 2016

- Update: Clean up translation catalog, textdomains and add to poeditor.com.
- Fix: Force use of HTTPS when FORCE_SSL_ADMIN is set to true

Version 1.0.2 - October 26th, 2016

- Added: Show the last date the ticket was evaluated for auto-close in the AutoClose metabox.
- Fix: Additional fixes for potential duplicate emails

Version 1.0.1 - October 20th, 2016

- Changes to handle re-opening of tickets (clear processed flag)
- Fix: warning emails were being duplicated under certain circumstances.

Version 1.0.0 - October 14th, 2016

- First Release

Version 0.9.0 - September 26, 2016

- Initial: First Public Beta

Version 0.0.1 - September 20, 2016

- initial: Initial Alpha-Only Release