ACK & Escalate

Every Critical Alert Gets Answered.
Or It Escalates.

Mark an alert actionable and NotiLens keeps paging until someone ACKs it. If the primary person doesn't respond, it automatically escalates to the next in line. No alert falls through the cracks.

✓ No credit card  ·  ✓ Configurable ACK window  ·  ✓ Multi-level escalation

For every event that can't be ignored
Payment failures
Server down
Deployment errors
Data pipeline halted
Security events
SLA breaches

A notification is not the same as a guarantee

Sending an alert fires and forgets. For critical events, you need to know it was received, acknowledged, and acted on — not just delivered.

Notifications get swiped away

A push notification fires. The on-call person is in a meeting, asleep, or driving. They see it, swipe it away, and forget. The incident sits unhandled.

No ACK means no accountability

If your alerting system doesn't track who acknowledged what and when, you have no audit trail. Incidents get dropped. Post-mortems have gaps. The same failure repeats.

Escalation paths live in someone's head

"If Jamie doesn't respond, call Sam" — stored in a Notion doc or a Slack pinned message that nobody finds at 2am. Escalation needs to be automated, not manual.

Set it actionable. It repeats until someone owns it.

When you send an alert with is_actionable: true, NotiLens tracks it as open until it's ACK'd. If the window passes, the escalation chain fires.

  • ACK from the lock screen — no app open required
  • Remind Me Later — re-pings you at your chosen interval
  • Configurable escalation window per topic (5 min – 2 hrs)
  • Full ACK audit trail with timestamp and who responded
  • Escalation stops the moment anyone ACKs
Actionable Alert
Stripe charge failed — $1,299
payments · 2 min ago
Urgent
Customer: Acme Corp. · Card declined · Retry #3 failed
Escalation path (if no ACK in 10 min)
1
You — paged now
Sam R. — paged in 10 min if no ACK
Team Lead — paged in 20 min if still unacknowledged

Three steps to zero unacknowledged alerts

1

Mark alerts as actionable

In your API call, add is_actionable: true. NotiLens tracks this alert as open until it's explicitly ACK'd.

2

Configure the ACK window

Set how long NotiLens waits for an ACK before escalating — from 5 minutes for P0 payment failures to 2 hours for low-priority system alerts.

3

Define the escalation chain

Add teammates as secondary and tertiary escalation targets. When the window expires unacknowledged, NotiLens automatically pages the next person.

An alert without an ACK
is just noise with consequences.

Know that every critical event was seen, owned, and resolved — with a full audit trail to prove it.

✓ is_actionable: true — that's all it takes

Accountability built into every critical alert

1 flag

is_actionable: true — one field in your API call turns any alert into a tracked, escalating event

0 gaps

in coverage — the escalation chain ensures every actionable alert reaches someone, no matter the time of day

Full log

of who ACK'd what and when — every acknowledged alert has a timestamp and owner for post-incident review

Alert escalation — common questions

How do I make an alert actionable? +
Add is_actionable: true to your JSON body when posting to the NotiLens webhook URL. For SDK users, pass is_actionable=True (Python) or { isActionable: true } (Node.js) in the options. NotiLens then tracks the alert as open until it's ACK'd.
What does "Remind Me Later" do? +
Remind Me Later lets you snooze an actionable alert without closing it. You choose the interval (15 min, 1 hr, etc.) and NotiLens re-pings you at that time. The alert stays open and escalation is paused while you're snoozed — it resumes if you don't ACK before the remind fires.
Does escalation stop if someone ACKs partway through? +
Yes. The moment any person in the escalation chain ACKs the alert, all further escalation stops. The alert is marked resolved with the ACK timestamp and the name of who responded. Everyone in the chain can see it was handled.
How many levels of escalation are supported? +
Up to 3 escalation levels on the Team plan (primary → secondary → tertiary). Enterprise plans support deeper chains. Each level can have a different ACK window — e.g. 10 minutes for the primary, 15 for secondary, 30 for the team lead.

Make every critical alert accountable

One field. Full escalation. No alert falls through the cracks.

Get Started Free