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

# Snooze

> Snooze tickets to hide them from views temporarily and have them automatically return at a chosen time so you can focus on immediate priorities.

Snooze tickets to temporarily hide them until you're ready to work on them. Snoozed tickets disappear from default views and automatically return when their snooze period expires. Use snoozing for tickets that depend on other work, need follow-up after a specific date, or when you want to focus on immediate priorities.

## Mental model

Snooze is a time-based visibility filter on a ticket. When a ticket is snoozed, it is hidden from default views until the snooze expiration time. The ticket still exists and is fully accessible via direct link or filtered views. Snooze does not change the ticket's status, priority, assignee, or any other property.

Think of snooze as "remind me later." It is not a status change, not a workflow action, and not an assignment change. It is purely a display filter tied to a timestamp.

***

## Snooze vs other deferral mechanisms

| Mechanism                         | What it does                                          | When to use                                                            |
| --------------------------------- | ----------------------------------------------------- | ---------------------------------------------------------------------- |
| **Snooze**                        | Hides ticket from default views until a specific time | Ticket needs follow-up later but no status change is needed            |
| **Status change** (e.g., Waiting) | Changes ticket status, visible in all views           | Ticket is blocked on external input and the status should reflect that |
| **Due date**                      | Sets a deadline, does not hide the ticket             | Ticket has a completion deadline but should remain visible             |
| **Assignee change**               | Transfers responsibility                              | Someone else should handle the ticket now                              |

Use snooze when the ticket does not need attention right now but should resurface automatically. Use status changes when the ticket's state has genuinely changed.

***

## Snooze behavior

* Snoozed tickets are excluded from default ticket views but can be found using the "Snoozed = True" filter.
* When the snooze period expires, the ticket reappears in default views automatically.
* Snoozing does not suppress notifications. If the ticket receives new messages or updates while snoozed, normal notification rules still apply.
* Snoozing a ticket sends a notification to team members if granular notifications are enabled for the channel.
* Snooze can be removed early, making the ticket active in default views immediately.

***

## Constraints and gotchas

* Snooze is a per-ticket operation. There is no bulk snooze.
* Snooze does not pause SLA timers or due date tracking. A snoozed ticket can become overdue while hidden.
* Snooze is not a workflow action. You cannot snooze tickets via workflow automation. It is a manual user action only.
* Quick snooze options (1 day, 3 days, end of week, next week) use 9 AM as the default return time. Custom dates allow specific time selection.
* "End of Week" targets Friday at 9 AM, or the following Friday if used on Friday afternoon. "Next Week" targets Monday at 9 AM, or the following Monday if used on Monday afternoon.