Team Alerts

Put the Right Person On-Call,
Automatically

Schedule who gets paged and when. Set escalation paths so critical alerts always reach someone — even at 3am on a holiday. Without the complexity or the PagerDuty bill.

✓ No credit card  ·  ✓ Team plan from $99/mo  ·  ✓ Works with existing NotiLens topics

Built for small teams and growing engineering orgs
Weekday / Weekend splits
Time-zone aware
Per-topic schedules
Escalation paths
ACK tracking
Slack-free

Everyone gets paged, or no one does

Without on-call scheduling, critical alerts either wake up the whole team or go unanswered because everyone assumed someone else would handle it.

Whole team gets paged at 3am

Without a schedule, a critical alert wakes everyone up. One person handles it. Seven people lose sleep. Team morale suffers every time there's an incident.

No one knows whose shift it is

Slack threads, spreadsheets, and calendar invites don't integrate with your alerts. The alert fires. The schedule is somewhere else. Time is wasted figuring out who's on.

Critical alerts go unacknowledged

If the primary person is asleep or away, the alert lands and no one ACKs it. Without an escalation path, a P0 incident can sit unnoticed for hours.

Set a schedule once. Alerts go to the right person automatically.

Assign on-call coverage per topic, per time window. NotiLens routes each alert to whoever is on shift — no manual forwarding, no Slack threads.

  • Weekday / weekend / time-of-day splits
  • Primary + secondary escalation chain per topic
  • If primary doesn't ACK in N minutes — secondary is paged
  • Per-topic schedules — payments team vs. infra team
  • iOS, Android & Web — wherever the on-call person is
On-Call Schedule · This Week
Mon – Wed
JD
Jamie D.
Primary
Thu – Fri
SR
Sam R.
Primary
Weekend
AL
Alex L.
Primary
Escalation path (if no ACK in 10 min)
Primary → Sam R. → Team Lead
Active

On-call coverage in under 10 minutes

No YAML files, no complex rotation configs. Just set who's on and when.

1

Invite your team

Add teammates to your NotiLens workspace. Each person installs the app on their phone — iOS, Android, or Web — and subscribes to the relevant topics.

2

Set the schedule

For each topic, define who is primary on-call and when. Set weekday vs. weekend coverage, time-of-day windows, and time zones per person.

3

Define the escalation path

If the primary doesn't ACK within your configured window, NotiLens automatically pages the secondary, then the tertiary. Set it and forget it.

Someone should always be on-call.
It just shouldn't always be you.

Distribute the burden. Route alerts to the right person. Sleep through the nights that aren't yours.

✓ Team plan · Up to 10 people per topic · Full escalation paths

PagerDuty-style coverage without the PagerDuty price

$99/mo

Team plan — up to 10 people per topic, full on-call scheduling and escalation paths included

10 min

to set up a full on-call rotation with escalation — no YAML, no complex config, no docs to read

0 alerts

go unanswered — escalation ensures someone ACKs every critical alert, even at 3am on a weekend

On-call scheduling — common questions

How many people can be in an on-call rotation? +
The Team plan ($99/mo) supports up to 10 people per topic. Each person can be assigned primary or secondary coverage for different time windows. For larger teams, contact us about the Enterprise plan.
What happens if the primary person doesn't acknowledge an alert? +
You configure an escalation window per topic — e.g. 10 minutes. If the primary on-call hasn't ACK'd within that window, NotiLens automatically pages the secondary. If the secondary doesn't respond either, it escalates to the tertiary (or team lead).
Can different topics have different on-call schedules? +
Yes. Each topic has its own on-call configuration. Your payments topic might route to the backend team on a tight escalation window, while your marketing analytics topic has a more relaxed schedule. Fully independent per topic.
Is this a replacement for PagerDuty? +
For small to mid-size teams, yes. NotiLens covers the core on-call scheduling, rotation, and escalation use cases at a fraction of the cost. If you need deep ITIL workflows, runbook integrations, or enterprise SSO, PagerDuty may be a better fit — but most teams don't need that complexity.

Set up on-call coverage in 10 minutes

Works with your existing NotiLens topics. No new tools to integrate.

Get Started Free