AI Agent Operations

Who is on-call right now,
one URL the whole company can open

On-Call Roster is the public-facing live roster. Who is the primary on-call for each team right now? Who is next? When does the hand-off happen? Anyone in the org can open the page; nobody has to ask in Slack. Designed for the visitor with one question, not the operator configuring rotations.

Get Started Talk to Sales
app.novaaiops.com / on-call-roster
● LIVE
Live
who-is-on per team
4 weeks
lookahead
Org-wide
visible
Stable URL
safe for wiki embed
Right Now

Top of page, biggest type

The page is built for the visitor with one question: "who do I page?" Top of the page, biggest type: who is on-call right now per team, with their preferred channel (Slack, PagerDuty, phone). Below that: who is next, and when. Everything else is one scroll away.

  • Big type for now: today's on-call rendered at hero size; readable across the room
  • Preferred channel: each engineer publishes their preferred page channel, Slack, PagerDuty, phone
  • Hand-off countdown: shows when the current on-call ends so visitors know the question may have a fresh answer soon
app.novaaiops.com / on-call-roster · now
Coming Up

Next 4 weeks, scrollable

Below the right-now block, a 4-week lookahead grid shows every rotation. Hand-offs, quiet-hour overrides, vacation coverage. Useful for planning meetings ("who is on-call next week so we can avoid scheduling them in the all-hands?") and for engineers who want to see their own rotation.

  • 4-week lookahead: covers most planning horizons; scrollable to see further
  • Per-team rows: each team gets a row; weeks are columns; rotations color-coded by engineer
  • Override visibility: overrides shown distinctly so visitors see "marc is covering for sarah this week"
app.novaaiops.com / on-call-roster · coming-up
Org-Wide Visibility

Anyone can open the page

The roster is visible to anyone in the org, not just engineering. Customer support, sales, account management, everyone benefits from knowing who to escalate to without asking. The page does not expose private contact info; only the engineer's published preferred channel.

  • Org-wide read access: no role gate; anyone in the tenant can view the roster
  • Privacy-respecting: only the engineer's published preferred channel is shown; no phone numbers exposed
  • Wiki-embed friendly: stable URL; renders cleanly inside Notion / Confluence iframes
app.novaaiops.com / on-call-roster · access
Mobile View

Designed for the phone, too

The roster works on mobile. Open it from a phone, see who is on-call, tap the channel link to open Slack or your phone dialer directly. Critical for incident-side workflows where a non-engineering responder needs to reach engineering quickly.

  • Phone-native: designed mobile-first; no horizontal scroll, no tiny taps
  • Tap-to-page: tapping a preferred channel opens the right app (Slack, dialer, PagerDuty)
  • PWA-installable: roster can be saved to home screen for one-tap access
app.novaaiops.com / on-call-roster · mobile
Video walkthrough coming soon

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

A roster anyone can find

A pager system is only useful when reachable. The roster page is the contact directory.

Get Started Request a Demo