> ## Documentation Index
> Fetch the complete documentation index at: https://docs.incident.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Snoozing escalations

> Temporarily snooze an escalation when you need more time before responding.

export const SlackPreview = ({snapshot, alt, maxWidth, caption}) => {
  const slug = snapshot.replace(/\.json$/, '').replace(/\//g, '--').replace(/[^a-zA-Z0-9-]/g, '-').replace(/-{2,}/g, '-').replace(/^-|-$/g, '').toLowerCase();
  const light = `/images/slack_generated_screenshots/${slug}-light.png`;
  const dark = `/images/slack_generated_screenshots/${slug}-dark.png`;
  return <>
<img src={light} alt={alt} className="block dark:hidden" style={maxWidth ? {
    maxWidth
  } : undefined} />
<img src={dark} alt={alt} className="hidden dark:block" style={maxWidth ? {
    maxWidth
  } : undefined} />
{caption && <p style={{
    fontSize: '14px',
    color: 'var(--content-tertiary)',
    marginTop: '8px',
    textAlign: 'center'
  }}>
{caption}
</p>}
</>;
};

<Frame>
  <SlackPreview snapshot="Message--Escalation notification--Direct message/For alert, with sent notification (snoozable).json" alt="Snoozing an escalation in Slack" />
</Frame>

Snoozing lets you temporarily pause an escalation when you've seen the alert but aren't ready to act on it yet. Instead of ignoring the page or acknowledging prematurely, snoozing gives you a defined window before the escalation resumes and notifies you again.

This is useful when you're paged about a known issue, need to finish something before investigating, or want to be reminded of an issue at a better time.

## How snoozing works

When you snooze an escalation:

1. The escalation moves to a **Snoozed** status and all notifications pause
2. After the snooze duration expires, the escalation returns to **Triggered** and resumes notifying as normal
3. The snooze is recorded in the escalation timeline, including who snoozed it and for how long

Snoozing is available from Slack, the dashboard, and the mobile app.

<Note>
  When you snooze an escalation, you'll be asked to provide a justification. This helps your team understand why the
  escalation was deferred.
</Note>

## What happens while snoozed

* **Notifications pause**: No further pages are sent while the escalation is snoozed. The escalation does not advance through further levels in the escalation path.
* **Escalation stays active**: Snoozed escalations still appear in your active escalation lists. They haven't been resolved — they're just paused.
* **Alert resolves**: If your alert route is configured to auto-resolve and the underlying alert resolves while the escalation is snoozed, the escalation resolves too — no page is sent when the snooze expires.
* **Timeline tracking**: Snooze and unsnooze events appear in the escalation timeline, so your team has a full audit trail.

## Snoozing and compliance (MTTA)

A snooze counts as an acknowledgement for MTTA (mean time to acknowledge). The responder has seen the escalation and made a deliberate decision to defer it, which is distinct from an escalation going unnoticed.

<Accordion title="Can I snooze an escalation that requires multiple acknowledgers?">
  No. Snoozing is not available for escalations that require multiple people to acknowledge. This is because a single
  responder snoozing would pause notifications for all required acknowledgers.
</Accordion>

<Accordion title="What happens if I snooze and the escalation path has more levels?">
  The escalation does not advance to the next level while snoozed. When the snooze expires, the escalation resumes from
  the same level in the path where it was snoozed.
</Accordion>

<Accordion title="Can anyone snooze an escalation, or just the person paged?">
  Anyone with permission to view and respond to escalations can snooze them. This follows the same permissions as
  acknowledging an escalation.
</Accordion>