AI Agent Operations

On-call rotations as a settings page,
not as a Slack thread anyone could lose

On-Call Manager is the configuration page for everything pager-related. Rotations, escalation chains, quiet hours, hand-off times, override windows. Changes are versioned, reviewed, and visible in audit. The on-call paying you at 3am has the right schema behind it.

Get Started Talk to Sales
app.novaaiops.com / on-call-manager
● LIVE
Versioned
every change
3-tier
escalation
Quiet
hours per person
Live
who-is-on display
Rotation Patterns

Weekly, daily, follow-the-sun

Three rotation patterns built in. Weekly: one person per week, hand-off Monday morning. Daily: one person per day. Follow-the-sun: rotation across regions so the person on-call is always in business hours. Custom patterns supported via cron expressions for the rare cases that do not fit the templates.

  • ✓
    Weekly · most common: simple, predictable; default for small teams
  • ✓
    Daily · spread the load: works for teams with many engineers; reduces individual fatigue
  • ✓
    Follow-the-sun: 3 regions, 8h shifts each; nobody pages overnight
app.novaaiops.com / on-call-manager · patterns
Escalation Chains

Three tiers, time-boxed

Each rotation has a 3-tier escalation chain by default: primary, secondary, tertiary. A page that is not acknowledged in the configured window escalates to the next tier. Default: 5 minutes for tier-1 escalation, 10 minutes for tier-2. Tunable per service tier; sub-1-minute escalations are supported for tier-0 services.

  • ✓
    Primary, secondary, tertiary: standard 3-tier chain; rarely needs more depth in practice
  • ✓
    Time-boxed escalation: 5/10 min defaults; tunable per service tier and per severity
  • ✓
    Tier-0 fast escalate: critical services can configure sub-minute escalation for sev-1 alerts
app.novaaiops.com / on-call-manager · escalation
Quiet Hours & Overrides

Per-person, per-week

Quiet hours let an engineer mark windows where they cannot take pages (a planned event, vacation, parental leave). Overrides automatically cover them. Overrides are visible in advance so coverage is never a surprise. Overrides are a first-class object in the rotation, not a hack.

  • ✓
    Per-person quiet hours: engineer sets them; system picks an alternate for the window
  • ✓
    Auto-coverage: system finds an available teammate; if none, escalates to team lead before the window starts
  • ✓
    Visible in advance: next 4 weeks of who-is-on display reflects all upcoming overrides
app.novaaiops.com / on-call-manager · quiet
Audit

Every change, every page, every ack

On-Call Manager logs every config change (who, what, when), every page (which alert, which on-call, which severity), and every acknowledgment (timestamp, response time). The data feeds Timeline Analytics directly, and the audit log is part of SOC2 export. No more "I think I was on-call that week."

  • ✓
    Config audit: every rotation change, escalation change, override has a timestamp and an author
  • ✓
    Page audit: every page recorded with severity, target, ack window, ack time
  • ✓
    SOC2 export: the on-call audit is part of the standard compliance bundle
app.novaaiops.com / on-call-manager · audit
Video walkthrough coming soon

Subscribe to Nova AI Ops on YouTube for demos, tutorials, and feature deep-dives.

On-call as a system, not a memory

Every change tracked, every page logged. Disputes about "who was on" stop happening when the page tells you.

Get Started Request a Demo