An SLA (Service Level Agreement) defines how quickly a team commits to responding to or resolving work (for example, “P0 issues must be triaged within 1 hour”).
With SLA Alerts enabled, Shortcut helps support and product teams maintain response-time commitments for high-priority or customer-impacting work.
What SLA Alerts do
When SLA Alerts are enabled, Shortcut will:
- Automatically apply an SLA to qualifying Stories
- Display a clear time-based indicator on the Story
- Send a single warning before the SLA breaches
- Send a breach notification if the SLA is not satisfied
- Display “SLA Met” on the Story once it moves to a completed state
How SLA Alerts work
Trigger
An SLA applies to a Story when the Story meets the criteria set in Settings (for example, Severity = Sev 0). That can happen when the Story is created, or later when someone sets the field.

When the SLA applies:
- The SLA clock starts. It counts from when the SLA applied, not from when the Story was created.
- The Story displays an SLA indicator on the card and in Kanban/Table view on the Stories page
If the field changes to a value with a different SLA, the Story drops its old SLA and the new SLA starts its own clock.
Satisfying the SLA
Each SLA has a Completed State. The SLA is satisfied when the Story moves into a workflow state it covers:
- Any completed state is the default for new SLAs. Any Done state satisfies the SLA, including Done states you add later.
- Specific states lets you choose one or more Done states. Hover over a state, or move to it with Tab, and choose Only to select just that state.
When satisfied:
- The Story displays “SLA Met” with the time it was completed
- No breach notification is sent
When you change an SLA’s Completed State, open SLAs whose Story is already in a newly covered state are satisfied right away. This can’t be undone.
Warning (At-Risk) & Breach Notifications
When a Story is at risk or has breached its SLA, Shortcut emails the Story’s owners. If the Story has no owners, its requester and followers get the email instead. If a Slack channel is linked in Settings, Shortcut also posts in that channel.
- Warning is sent halfway through the SLA’s time limit, counted from when the SLA applied and rounded down to the whole hour. For a 1-hour SLA that rounds down to zero, so the warning is sent as soon as the SLA applies.
- Breach is sent if the Story hasn’t moved to a completed state by the end of the SLA’s time limit.
Each Story gets at most one warning and one breach per SLA. Shortcut checks SLAs every 15 minutes, so a notification can arrive up to 15 minutes after its time.