If an SLA is not activated in ticket events, it could be due to several reasons, such as incorrect SLA policy settings or conditions not being met. Ensure that your SLA policies are correctly configured and that the ticket meets all the conditions for the SLA to apply.
Reviewing the SLA policy settings and the specific conditions required for activation can help identify why an SLA might not be triggering as expected.
Once an SLA target is missed, it remains breached even if you change the ticket's priority. For example, if a ticket misses the 1-hour first reply SLA for high priority, downgrading it to low priority with a 24-hour target will not retroactively…
Yes, a proactive ticket created by an agent can trigger an SLA. SLAs are applied based on the conditions set in your SLA policies, which can include tickets created proactively by agents. It's important to ensure that your SLA policies are…
SLAs are typically not applied to tickets in a resolved status. SLAs are designed to measure the time taken to respond to or resolve tickets, so once a ticket is marked as resolved, the SLA is no longer applicable. If you need to track metrics on…