Difference between revisions of "Support Ticket Escalations"
| (18 intermediate revisions by 6 users not shown) | |||
| Line 1: | Line 1: | ||
| − | + | Ticket escalation rules allow you to specify actions to take automatically if a [[Support Tickets|support ticket]] is in a specified state for a set period of time. | |
| − | You can | + | You can access this feature at '''Configuration (<i class="fa fa-wrench" aria-hidden="true"></i>) > System Settings > Escalation Rules''' or, prior to WHMCS 8.0, '''Setup > Support > Escalation Rules'''. |
| − | + | == Configuring Escalation Rules == | |
| − | + | You can select the departments, statuses, and priorities that an escalation rule applies to. For example, in the example below, low and medium priority tickets will change to high priority, an automatic response will go to the client, and members of the relevant support department will receive an email after four hours with no response. | |
| − | + | The following merge fields are in the '''Add Reply''' box: | |
| − | + | [NAME] - Ticket Submitter Name | |
| + | [FIRSTNAME] - First Name | ||
| + | [EMAIL] - Ticket Submitter Email | ||
| − | === | + | [[Image:Ticketescalations.png|650px]] |
| − | Escalation rules only apply to tickets submitted after the escalation rule. | + | |
| + | ===Setup=== | ||
| + | |||
| + | WHMCS 7.0 and earlier require a dedicated cron task entry for escalations: | ||
| + | |||
| + | <div class="source-cli">php -q \path\to\home\public_html\whmcspath\crons\cron.php do_escalations</div> | ||
| + | |||
| + | Note the space between <tt>cron.php</tt> and <tt>do_escalations</tt>. The command will only run the escalations task for the cron job. Configure this to run once every few minutes (we recommend every 3–5 minutes). | ||
| + | |||
| + | <div class="docs-alert-warning"> | ||
| + | If you are running WHMCS 7.1 or later, this is NOT necessary. | ||
| + | </div> | ||
| + | |||
| + | ===Escalation Behavior=== | ||
| + | |||
| + | Escalation rules only apply to tickets that customers submitted after the escalation rule's creation. Existing tickets will not escalate automatically. | ||
| + | |||
| + | Escalation rules apply to every ticket that meets the specified conditions. If nothing happens to ensure that the ticket doesn't meet the conditions, the escalation rule will continue to affect the ticket. It will only stop affecting the ticket when it no longer matches the escalation rule conditions. | ||
Latest revision as of 20:48, 11 May 2022
Ticket escalation rules allow you to specify actions to take automatically if a support ticket is in a specified state for a set period of time.
You can access this feature at Configuration () > System Settings > Escalation Rules or, prior to WHMCS 8.0, Setup > Support > Escalation Rules.
Configuring Escalation Rules
You can select the departments, statuses, and priorities that an escalation rule applies to. For example, in the example below, low and medium priority tickets will change to high priority, an automatic response will go to the client, and members of the relevant support department will receive an email after four hours with no response.
The following merge fields are in the Add Reply box:
[NAME] - Ticket Submitter Name [FIRSTNAME] - First Name [EMAIL] - Ticket Submitter Email
Setup
WHMCS 7.0 and earlier require a dedicated cron task entry for escalations:
Note the space between cron.php and do_escalations. The command will only run the escalations task for the cron job. Configure this to run once every few minutes (we recommend every 3–5 minutes).
If you are running WHMCS 7.1 or later, this is NOT necessary.
Escalation Behavior
Escalation rules only apply to tickets that customers submitted after the escalation rule's creation. Existing tickets will not escalate automatically.
Escalation rules apply to every ticket that meets the specified conditions. If nothing happens to ensure that the ticket doesn't meet the conditions, the escalation rule will continue to affect the ticket. It will only stop affecting the ticket when it no longer matches the escalation rule conditions.