SLA Management
Set first-response and resolution targets per priority, get warned before they slip, and see whether each ticket met them
SLA management, called Response targets on the dashboard, gives every ticket two timers: one for the first staff reply and one for resolution. Targets depend on the ticket's priority, and follow it when the priority changes.
As a timer approaches its target the bot warns your team in a notification channel, and when it passes the target the breach is recorded on the ticket and announced, and the ticket is escalated. It is built for teams that promise response times and need to know when they are about to miss one.
SLA management is an Enterprise feature. On lower plans the Response targets block shows an Enterprise badge instead of its settings, and the bot does not start SLA timers unless the bot owner's plan is Enterprise. Upgrade your plan to use it.
Setting up
Open the Response targets settings
Go to Staff → Response targets. The settings are one card titled Response targets.
Turn SLA tracking on
Enable the card's main switch. Nothing is tracked until this is on, and only tickets created after you save get timers.
Set targets by priority
Under Targets by priority, enter First reply within (the first-response target) and Solved within (the resolution target) in minutes for Low priority, Medium priority, High priority, and Critical priority. Targets are whole minutes. The resolution target must be at least as long as the first-response target: if you enter them the other way round, the other value of the pair is changed to match the one you typed when you leave the field.
Choose the SLA notification channel
Post warnings in shows where every warning, breach, escalation alert, and target-met message goes: your logs channel until you pick another. To change it, go to General → Where the bot posts and pick a channel for Late ticket warnings, for example a staff-only #sla-logs. Save the response targets once first: the picker is available after they are set up.
Choose who gets mentioned
Under Who gets pinged, decide whether alerts mention the Staff roles (all configured staff roles) and Whoever claimed the ticket.
Tune the advanced rules
Under Warnings and escalation and When to alert, keep the defaults unless you have a reason to change them. The sections below explain each option.
Save
Click Save changes on the bar at the bottom of the page (or press Ctrl/Cmd + S). New tickets pick up the new settings immediately; tickets that already have timers keep the targets they started with.
Settings
| Setting | Allowed values | Default |
|---|---|---|
| Response targets (main switch) | on or off | off |
| Pause outside business hours | on or off | on |
| Move late tickets to the top | on or off | off |
| Also report targets that are met | on or off | off |
| First reply within (per priority) | 1 to 1,440 minutes | Low 240, Medium 120, High 60, Critical 15 |
| Solved within (per priority) | 1 to 10,080 minutes, at least the first-reply target | Low 2,880, Medium 1,440, High 480, Critical 120 |
| Post warnings in (changed under Late ticket warnings in General → Where the bot posts) | any text channel the bot can post in | Same as logs: the logs channel |
| Who gets pinged → Staff roles | on or off | on |
| Who gets pinged → Whoever claimed the ticket | on or off | off |
| Early warning | on or off | on |
| Include ticket details | on or off | on |
| Include member info | on or off | on |
| Include recent performance | on or off | off |
| Escalate automatically | on or off | on |
| Maximum escalations | 1 to 10 | 3 |
| Wait between escalations | 5 to 1,440 minutes | 30 |
| Warning alert threshold | 50% to 99%, below the critical value | 75% |
| Critical alert threshold | 51% to 99%, above the warning value | 90% |
Worked example: a three-person team
A small team that promises "we reply within the hour to anything urgent, within the day to everything else" could choose the targets below. These are one example team's own values, not TicketCord's defaults: the defaults are in the Settings table above (first reply Low 240, Medium 120, High 60, Critical 15 minutes).
| Example team's own targets (defaults are in Settings) | Example first response | Example resolution |
|---|---|---|
| Low | 480 min (8 h) | 4,320 min (3 days) |
| Medium | 240 min (4 h) | 1,440 min (24 h) |
| High | 60 min | 480 min (8 h) |
| Critical | 30 min | 240 min (4 h) |
With these example targets, Pause outside business hours on and a Monday to Friday 09:00 to 18:00 schedule in Business Hours, a High ticket opened at 17:30 on Friday has 30 minutes of its first-response budget left when Monday morning starts. This team keeps Warning alert at 75% and Critical alert at 90% (the defaults), sets Wait between escalations to 60 (the default is 30), and sets Late ticket warnings under General → Where the bot posts to a private #sla-alerts channel that only the three of them can see.
What happens
-
Timers start when the ticket is created. The ticket's priority at that moment selects the targets:
low,medium, andhighuse those targets,urgentuses the Critical priority targets, and a ticket with no priority is tracked as Medium. -
Targets follow the priority. When the ticket's priority changes, whether staff use
/priority, change it on the dashboard or through an AI tool, or Atlas sets it automatically, every timer still running switches to the new priority's targets, counted from when the timer started. A shorter target can therefore be missed straight away. A timer already met or missed keeps its result. A role listed under Priority support can give its members' tickets a tighter first-response target. The ticket then uses the shorter of the two, also after its priority changes. -
First response is met by the first staff message in the ticket. Claiming alone does not stop the timer; a staff member has to write something.
-
Resolution is met when the ticket is closed, whether by
/close, the dashboard, a close request, or a scheduled or automatic close. Deleting an open ticket ends its timers the same way. -
Warnings are posted to the notification channel when a timer reaches 75% and again at 90% of its target, as long as Early warning is on. The message reads "Ticket 42 is approaching SLA deadline (first_response at 75%)" and includes the ticket link, priority, and server, plus the targets when Include ticket details is on, the customer's name and ID when Include member info is on, and workload context when Include recent performance is on.
-
Escalation alerts fire when a timer crosses the Warning alert and Critical alert percentages, as long as Escalate automatically is on. Each is posted to the notification channel once per percentage for each timer, so an alert does not repeat while a ticket sits untouched, and it does not ping the people under Who gets pinged. Wait between escalations is the shortest gap between two alerts on a ticket, and Maximum escalations caps how many one ticket can get.
-
Move late tickets to the top does two things when the first warning fires: it moves the ticket channel to the top of its category and appends
-🆘to the channel name so it stands out in the channel list. -
Breach happens when a timer passes 100%. For each missed target, the bot:
- posts the Response target missed alert in the notification channel, reading "[CRITICAL] SLA Breach: Ticket 42 resolution target missed by 12.0 minutes" and mentioning the people chosen under Who gets pinged;
- posts an SLA breached log entry in your logs channel, without a ping, when a logs channel is set;
- sets the ticket's SLA status and sends an
sla.breachwebhook.
The first missed target also escalates the ticket, unless it is already escalated: an escalation with reason Reply target missed appears on the dashboard's Escalations page, a Ticket escalated log entry is posted in your logs channel without a ping, and Atlas stops answering in the ticket for the time set in When Atlas can't help, as after any escalation (see Escalations). Missing the other target later adds no second escalation, and a target found missed as the ticket closes adds none, because the ticket is no longer open. Nothing is posted in the ticket itself.
-
Target met posts a green confirmation for each timer that finishes within target, only if Also report targets that are met is on.
Mentions in warnings, missed-target alerts and target-met messages follow Who gets pinged: the staff roles when Staff roles is on, and the user who currently has the ticket claimed when Whoever claimed the ticket is on. If neither is on the message is posted without a ping. The log entries in your logs channel never ping anyone. With Late ticket warnings at Same as logs, the alerts and the log entries all land in your logs channel.
SLA statuses
Each ticket's SLA tracking ends with one of these overall results. Stats reports each target on its own, so these combined results are not shown there.
| Status | Meaning |
|---|---|
| Active | The ticket is open and at least one timer is still running |
| Met | Both the first-response and resolution targets were met |
| Partial breach | The resolution target was met but the first-response target was not: it was missed, or the ticket closed with no staff reply |
| Breached | The resolution target was missed |
Business hours and pausing
With Pause outside business hours on (the default), SLA timers pause whenever your Business Hours schedule says you are closed, including holidays, and resume when you reopen. The paused time is subtracted from the elapsed time, so a ticket opened Friday evening does not breach over the weekend.
This only works when business hours is configured and enabled for the server; with no schedule, timers run around the clock even if the switch is on. There is no manual pause.
Open tickets follow their own server's current schedule and pause switch, including after a bot restart. Turning Pause outside business hours off resumes timers paused by that schedule on the next check; it does not end a server-restore pause.
Where to see the results
- Ticket page: the Conversation tab of the ticket on Tickets logs the moment the first-response target was met as a First response event.
- Stats: when open tickets have used 80% or more of a target, not counting paused time, a banner at the top counts them, broken down by priority. Under More stats, Reply and close targets shows the share of tickets that met each target, by priority and over time. The Late first replies card, and the Late replies column on the Your team page (See team), count each staff member's late first replies.
- Escalations: the first target a ticket misses creates one escalation with reason Reply target missed, unless the ticket is already escalated; missing the other target adds no second one. It stays Pending until the ticket is closed or deleted, then is resolved automatically.
- Webhooks:
sla.warningandsla.breachevents carry the ticket, priority, timer type, target and elapsed minutes, and percentage used. See Webhooks.
Limits and gotchas
With Late ticket warnings left at Same as logs, every SLA message goes to your logs channel. Pick a separate channel under General → Where the bot posts if they crowd the logs.
- SLA priorities are Low, Medium, High, and Critical. The
/prioritycommand and priority detection call the top levelurgent; anurgentticket uses your Critical priority targets. A ticket set tononeis tracked as Medium. - The 75% and 90% warning points are fixed. The Warning alert and Critical alert fields change when escalation alerts fire, not when the plain warnings are posted.
- Changing the targets in the settings affects new tickets only. An open ticket keeps the targets it has until its priority changes; then it takes that priority's current targets.
- Reopening a ticket does not restart its timers. The result recorded when it closed stands, and the reopened ticket is not tracked again.
- Move late tickets to the top only works for text and announcement channels inside a category; it does nothing for thread tickets.
- Channel renames are rate limited by Discord, so the
-🆘suffix can lag by a few minutes on a busy server. - If the notification channel is deleted or the bot loses permission to post in it, SLA notifications for that channel stop until you pick a working channel.
Troubleshooting
| Symptom | Cause | Fix |
|---|---|---|
| No SLA alerts at all | SLA tracking is off, or the bot cannot post in the Late ticket warnings channel (or the logs channel, when it is Same as logs) | Confirm the Response targets switch is on and save, then check the channel under General → Where the bot posts |
| Alerts arrive but nobody is pinged | Both switches under Who gets pinged are off, or no staff role is configured in Staff → Staff roles | Turn on Staff roles or Whoever claimed the ticket |
| An urgent ticket is using the Critical targets | urgent maps to Critical priority | Expected. Use /priority level:high for tickets that should follow your High targets |
| Timers do not pause overnight | Pause outside business hours is on but business hours is not configured or enabled | Set up a schedule in General → Business hours |
| Timers never pause even with a schedule | Pause outside business hours is off | Turn it on; it is the only way to pause a timer |
| A ticket breached even though staff replied quickly | The reply came from someone who is not staff, or was a claim without a message | Only messages from members with a staff role count as a first response |
The -🆘 suffix stays after the ticket is handled | Discord rename rate limits delay the change, and the suffix is not removed automatically | Rename the channel with /rename if it bothers you; closing the ticket removes the channel anyway |
| Changing targets did not affect an open ticket | An open ticket keeps its targets until its priority changes | Only new tickets, and tickets whose priority changes afterwards, use the new targets |
| A ticket breached right after its priority went up | Its timers switched to the shorter targets of the new priority, counted from when they started | Expected. Reply sooner on tickets you raise to a higher priority |
Common questions
Does claiming a ticket stop the first-response timer? No. The first-response timer stops at the first message from a staff member in the ticket. Claim and then reply.
Where do SLA warnings appear? In the Late ticket warnings channel under General → Where the bot posts, which is your logs channel while it is Same as logs. Post warnings in on Staff → Response targets shows which one. Nothing is posted inside the ticket itself, so users never see SLA chatter.
Where is a missed target posted, and who is mentioned? Each missed target posts two messages. The Response target missed alert ("[CRITICAL] SLA Breach: Ticket 42 resolution target missed by 12.0 minutes") goes to the Late ticket warnings channel and mentions the people chosen under Who gets pinged. An SLA breached log entry goes to your logs channel without a ping. The first missed target also escalates the ticket, which adds a Ticket escalated log entry in the logs channel, again without a ping. While Late ticket warnings is Same as logs, all of them are in your logs channel. See the Message Reference for each message.
A ticket missed both targets. How many escalations does it get? One. The first missed target creates the Reply target missed escalation, and the second adds none, although both are still announced. If the AI or Talk to Staff had already escalated the ticket, the breach adds no escalation. It stays Pending until the ticket is closed.
Which targets does an urgent ticket get?
The Critical priority ones. SLA priorities are Low, Medium, High, and Critical, and urgent (the top level of /priority and priority detection) counts as Critical.
What happens to the timers when I change a ticket's priority?
Timers still running switch to the new priority's targets, counted from when they started, so raising a ticket from Low to High can make it late at once. Timers already met or missed keep their result. This applies however the priority changes: /priority, the dashboard, an AI tool, or Atlas.
Can I pause the SLA on one ticket while I wait for the customer? No. The only pause is Pause outside business hours, which pauses every timer outside your schedule. There is no per-ticket pause.
What counts as resolved?
Closing the ticket by any method: /close, the dashboard, an accepted close request, a scheduled close, or auto-close.
How many escalation alerts will I get for one ticket? One for each alert percentage on each timer, and never more than Maximum escalations (default 3) on one ticket. They are spaced by Wait between escalations (default 30 minutes), as long as Escalate automatically is on and the ticket stays open.
Do SLA timers respect holidays? Yes, when Pause outside business hours is on. Holidays in the General → Business hours settings count as closed days and pause the timers for the whole day.
Is the SLA status visible to the user who opened the ticket? No. SLA alerts go to your Late ticket warnings channel and SLA results appear only on Stats; nothing is posted inside the ticket. The only thing the member may notice is that Atlas stops answering in the ticket after a missed target, because the breach escalates it.
Join our Discord server for support
Was this page helpful?
Last updated on