Skip to content
DevOps AI ToolKit
Newsletter
All prompts
AI for Slack Difficulty: Intermediate ClaudeChatGPT

Slack Quiet-Hours and Timezone-Aware Paging Prompt

Design notification routing that respects each on-call engineer's local quiet hours and timezone — pages only for high severity after hours, defers low-priority noise to working hours, and never silently drops a real page.

Target user
Platform engineers tuning on-call notification routing in Slack
Difficulty
Intermediate
Tools
Claude, ChatGPT

The prompt

You are a senior platform engineer who has tuned on-call routing so engineers sleep through noise but never miss a real incident. Design timezone-aware, quiet-hours-respecting paging through Slack.

I will provide:
- On-call roster with each person's timezone and working hours
- Severity tiers and which currently page vs notify
- The routing layer (Alertmanager/PagerDuty + a Slack webhook proxy)
- Pain points (after-hours noise, missed pages, follow-the-sun gaps)

Your job:

1. **Routing matrix** — define, per severity, the channel and method by time of day in the recipient's local timezone: Sev1/Sev2 always page; Sev3 pings the channel during working hours and defers (digests) after hours; Sev4 always goes to a digest.

2. **Timezone resolution** — resolve the current on-call's local time at evaluation time (not server time). Show how to read the timezone from the roster or Slack user profile and compute whether it's quiet hours for them right now.

3. **Deferral mechanics** — for deferred alerts, hold and batch into a working-hours digest; show the queue, the flush trigger, and how a deferred alert escalates to a page if its severity is later raised.

4. **Override & safety valve** — never let quiet hours suppress a Sev1; provide a documented override and a "storm" condition where many deferred low-sevs together imply a real problem and escalate.

5. **Follow-the-sun** — when the rotation hands off across regions, ensure an alert at a handoff boundary reaches the incoming on-call, not the one going to sleep.

6. **Validation** — track after-hours page count, deferred-then-escalated count, and any alert that was deferred but should have paged, to tune the matrix.

Output as: (a) the severity × time-of-day routing matrix, (b) the timezone/quiet-hours evaluation logic, (c) the deferral queue + working-hours flush design, (d) the safety overrides and storm-escalation rule, (e) the metrics to review.

Bias toward: high-severity always pages regardless of hour, conservative deferral that errs toward notifying, and timezone computed for the actual recipient.

Related prompts

Newsletter

Free: the DevOps AI Incident-Triage Cheat Sheet

Subscribe and we’ll send you the one-page cheat sheet — plus weekly AI prompts, automation ideas, and tool reviews for infrastructure engineers. One email a week. No spam, unsubscribe anytime.

  • AI Incident-Triage Cheat Sheet (PDF)
  • Access to 2,104 DevOps AI prompts
  • One practical workflow email per week