Ticket SLAs
Use ticket SLAs to enforce both first response time and ticket resolution time.
Last updated
Was this helpful?
Use ticket SLAs to enforce both first response time and ticket resolution time.
SLAs can be as short as 15 minutes or as long as 10 working days (two weeks). Time spent outside of workspace-level working hours will not count against your SLAs, nor will time spent in the On Hold status.

Once an SLA has been breached, Wrangle will at-mention your inbox agents and inbox admins in the ticket thread.

Sometimes agents may forget to place a ticket On Hold or update the status of a ticket. With the Waiting for Reply automation, a ticket's status will automatically be updated to "Waiting for Reply" every time the assigned agent posts a message in the ticket thread, and will automatically go back to "In Progress" when the requester replies.
By default, both Agents and Inbox Admins in an inbox receive SLA reminder notifications when tickets are late.
If a ticket is assigned, only the assigned agent(s) receive pings.
If a ticket is unassigned, Wrangle pings all Agents and Admins in the inbox (by default).
A toggle in Inbox Settings → Ticket SLAs controls this:

"Include inbox admins in SLA reminders"
On (default): Both Agents and Admins receive SLA pings for unassigned late tickets.
Off: Only Agents receive SLA pings. Inbox Admins are excluded from SLA notifications entirely.
What about account admins? Account (workspace-level) admins have access to all non-confidential inboxes but are not inbox members. Because they are not added as inbox members, they never receive SLA pings — regardless of inbox SLA settings.
Last updated
Was this helpful?
Was this helpful?