How to Avoid SLA Reminders and Escalation Emails in BoldDesk
In BoldDesk, SLA reminders notify agents or groups before a response or resolution target is due, while escalation emails notify the configured recipients after an SLA target is breached.
If a ticket does not require active SLA tracking for a period, you can avoid reminders and escalation emails by:
- Moving the ticket to the On Hold status to pause the SLA timer.
- Applying a separate SLA policy with extended targets and disabled reminder and escalation notifications.
This article explains how to use both methods and when each method is appropriate.
Use the On Hold Status to Pause the SLA
Use the On Hold status when work on a ticket is temporarily paused, such as when your support team is waiting for information, approval, or an external action before continuing.
When a ticket is moved to the On Hold status, the SLA timer pauses. Because the applicable SLA due time is not reached while the timer is paused, the related escalation email is not sent.
To move a ticket to the On Hold status:
-
Sign in to the BoldDesk Agent Portal.
-
Open the required ticket.
-
Select On Hold from the Status field.
-
Save the ticket update.
Move the ticket from On Hold to the appropriate active status when work resumes. The SLA timer then continues according to the applicable SLA policy.
Apply a Separate SLA Without Reminders or Escalations
Use a separate SLA policy when specific tickets should remain active but require extended response and resolution targets without reminder or escalation emails.
For example, you can add a dedicated tag to selected tickets and configure an SLA policy that applies only to tickets containing that tag.
This method does not pause the SLA timer. It applies extended SLA targets and disables the related reminder and escalation notifications.
Add a Tag to the Ticket
Add a dedicated tag to identify tickets that should use the separate SLA policy.
To add the tag:
-
Open the required ticket in the Agent Portal.
-
Locate the ticket’s Tags field.
-
Add a dedicated tag, such as
my-tracking. -
Save the ticket update.
Use a unique and descriptive tag that is reserved for this SLA policy. This prevents the policy from being applied unintentionally to unrelated tickets.
Create a Separate SLA Policy
To create the SLA policy:
-
Go to Admin > Automation > SLA.
-
Click Add SLA.
-
Enter a clear name and description for the policy.
-
Select the required operational hours.
-
Configure when SLA evaluation should begin.
-
Add a condition that applies the policy to tickets containing the dedicated tag.
-
Proceed to the SLA target configuration.
Configure the SLA Targets
Configure the targets for each applicable ticket priority:
-
Set an extended target for Time to First Response.
-
Do not configure Time to Next Response if a next-response due time is not required.
-
Set an extended target for Time to Resolution.
-
Keep the Reminder option disabled.
-
Keep the Escalation option disabled.
-
Save the SLA policy.
With this configuration:
- The first-response and resolution due dates are calculated using the extended targets.
- Reminder emails are not sent because reminders are disabled.
- Escalation emails are not sent because escalations are disabled.
- A next-response due date is not calculated when Time to Next Response is not configured.
Extended SLA targets can make tickets appear compliant for a long period. Review tickets using this policy regularly so that unresolved issues are not overlooked.
Troubleshooting
The SLA Timer Continues After the Ticket Is Placed On Hold
Confirm that the selected ticket status is On Hold. Review the ticket status and applicable SLA configuration if the timer continues.
The Separate SLA Is Not Applied
Confirm that:
- The ticket contains the tag used in the SLA condition.
- The SLA policy is active.
- The configured condition matches the ticket.
- The policy is ordered correctly when multiple SLA policies can match the ticket.
Reminder Emails Are Still Being Sent
Confirm that the Reminder option is disabled for every configured SLA target and priority in the separate SLA policy.
Also, verify that the ticket is using the intended SLA policy rather than another matching policy.
Escalation Emails Are Still Being Sent
Confirm that the Escalation option is disabled for every configured target in the separate SLA policy.
Also, verify that the ticket is using the intended SLA policy rather than another matching policy.
A Next-Response Due Date Is Displayed
Review the separate SLA policy and confirm that Time to Next Response is not configured for the applicable ticket priority.
Frequently Asked Questions
-
Does the On Hold status pause the SLA timer?
Yes. Moving a ticket to On Hold pauses its SLA timer until the ticket is moved to an active status. -
Will an escalation email be sent while the ticket is On Hold?
The paused SLA timer does not advance toward its due time while the ticket remains On Hold. Therefore, the related escalation is not triggered during the paused period. -
Does creating a separate SLA pause the SLA timer?
No. A separate SLA applies different response and resolution targets. It does not pause SLA calculation. -
How can I prevent reminder and escalation emails for selected tickets?
Create a separate SLA policy for those tickets and keep the Reminder and Escalation options disabled. -
Can I use a tag to apply the separate SLA?
Yes. Add a dedicated tag to the required tickets and configure the SLA condition to match that tag. -
What happens when Time to Next Response is not configured?
BoldDesk does not calculate a next-response due date for that SLA target. -
Should I use On Hold or create a separate SLA?
Use On Hold when work is temporarily paused and the SLA timer should stop. Use a separate SLA when tickets should remain active with extended targets and no reminder or escalation emails.