The right person, every time

Auto-rotation, multi-step escalation, override requests, voice paging, and TTA metrics that prove your rotation actually works.

Pool mode + auto-rotation

Rotate through your team automatically. Include everyone or set per-user exclusions for vacations and travel.

Multi-step escalation + auto-unack

Define escalation chains with delays. Auto-unacknowledge after a configurable timeout so silenced pages don't stop escalation.

Swaps + override requests

Trade shifts with teammates. Request coverage with one click. They accept by clicking a link in email or SMS.

Schedule management

Build on-call schedules that fit how your team actually works. Daily rotations, weekly shifts, custom intervals. With a visual calendar so everyone knows when they're on.

  • Daily, weekly, or custom rotation intervals to match your team's rhythm
  • Manual or automatic mode. Full control when you need it, hands-off when you don't
  • Pool mode with exclusions so you can keep certain people off certain rotations
  • On-call preview calendar so responders always know what's ahead
  • Layered schedules. Primary on-call rolls up to secondary if no one acks
  • iCal feed per schedule for Google Calendar / Apple Calendar / Outlook sync
Currently On-Call
AK
Alice Kim
Until Mon, 9:00 AM
This week
MTWTFSS
Alice
Bob
Carol
Escalation
1
After 5 min → notify Alice
2
After 15 min → notify team

Escalation policies + auto-unack

When the first responder doesn't pick up, the incident shouldn't just sit there. Define exactly who gets paged next and when. And make sure 'silenced' is never the same as 'handled'.

  • Multi-step escalation with configurable delays between each step
  • Notify via any channel. Slack, SMS, voice call, PagerDuty, email, webhook
  • Auto-unacknowledge after N minutes (configurable per policy). Silenced pages re-escalate
  • Target specific users or 'current on-call' from a schedule (resolves dynamically)
  • Repeat the chain with a max-repeat cap to avoid infinite loops

Escalation Policy

0m Page primary on-call
5m Page secondary on-call
15m Page entire team
Auto-unack after 30 min. Escalation continues

Override requests

The 'cover-me-Friday' workflow. Request coverage from any teammate with one click. They accept or decline by clicking a link in email or SMS, no need to log in.

  • Request override for a single day or a date range
  • Recipient gets email + SMS with one-click accept/decline links
  • Token-signed responses so links expire safely after use
  • Pending override requests appear in the recipient's Inbox
  • Originating user notified the moment coverage is accepted

Override request · pending

@daniel needs coverage Fri, Jun 14

"Doctor's appointment in the afternoon. Anyone available?"

Accept Decline

Voice + SMS paging

Sometimes Slack and email aren't loud enough. Voice paging makes a real phone call. The kind that wakes someone up. Available on Business; SMS available on Pro.

  • SMS paging with reply-to-ack support (text 'Y' to acknowledge)
  • Voice paging makes a real phone call with IVR. Press 1 to acknowledge
  • Per-user opt-in for both SMS and voice so users control when they want loud paging
  • Voice paging is a Business-tier feature; SMS is Pro+
  • Delivery handled by Signalog, no third-party setup required

Incoming call · Business

Signalog · Page

"Acknowledge incident: payment processing degradation. Press 1…"

Press 1 · Ack Press 2 · Escalate
SMS · Pro 2 min ago

Signalog: Incident #4218 — Auth service down. Reply Y to ack.

You replied: Y

On-call performance metrics

If you can't measure it, you can't improve it. Signalog tracks exactly how your rotation performs. Time-to-acknowledge percentiles, unacked rate, and per-user ack leaderboards.

  • Time-to-acknowledge p50, p90, p95 across the team
  • Unacknowledged rate. % of pages that auto-unacked or escalated
  • Per-user ack leaderboard. Who picked up the most pages last month
  • Severity breakdown. Fast acks on P1s vs P3s
  • Weekly trend lines. Is your team getting faster, or slower
  • Configurable period. Last 7, 30, or 90 days

On-call performance · last 30 days

TTA p50

2m 14s

TTA p95

11m 42s

Unacked rate

3.2%

Total pages

47

Top responders

1. @sarah (18) · 2. @daniel (14) · 3. @priya (9)

Wired into your incident workflow

When an incident is created, your on-call schedule determines who gets paged first. If they don't acknowledge. Or if their ack expires via auto-unack. The escalation policy kicks in automatically.

Monitor alertIncident createdOn-call pagedAuto-unack timerEscalation policy

Start monitoring in 60 seconds

Free forever for small projects. No credit card required.

Start free