shadcn.io is not affiliated with official shadcn/ui
Urgent Page Acknowledgement Notification Block for React
An on-call paging panel with three urgent alerts that demand an answer: severity as a word, a glyph and a weight, a fixed escalation time, and an Acknowledge that stamps the time and takes the escalation line away.
Installation
Overview
Make an urgent alert impossible to scroll past with this high-priority notification panel for React with Base UI. It is the page list of Wakebell, an on-call paging service, in a narrow hairline frame with a plus mark on each corner: three alerts, each with its severity as a word in a Badge (Critical is solid and its title heavier, with a bar at its start), a glyph, what is wrong and since when, and the line that makes it urgent, "Escalates to on-call at 09:45 UTC". The first alert still waiting carries the one Shine Button, Acknowledge; the others are outline Buttons. Pressing it stamps "Acknowledged by you at 09:31 UTC" in the same place, removes the escalation line, keeps an Undo, and the band above ("2 need acknowledgement", with a Status dot while any remain) and the status line follow. One page was already taken by a teammate, so the receipt state is on the page from the start. Rules come from Guides, motion is CSS only, and nothing is timed. For incident tools, paging apps and any alert that must be answered.
FAQ
How do I fill it with my pages?
Edit PAGES. Each has an id, a level of critical or high, a title, a service, an ISO since, an escalates number (minutes after the page's "now") and, when a teammate already took it, takenBy and takenAt. AS_OF is the page's fixed "now" in UTC, so every time reads the same on the server and in every visitor's time zone. In your app replace it with the alert's own timestamps and your escalation policy.
What does Acknowledge do, and what stays local?
It marks the alert in this tab: a receipt with a time, the escalation line gone, an Undo, and a status message. The stamp is a demo clock (a minute after "now" for the first acknowledgement, two for the second), not a reading of your clock, and nothing is paged, sent or saved: a reload brings every alert back. In your app call your paging service from acknowledge, show the time it returns, and make Undo your service's own un-acknowledge.
Does the escalation count down?
No. The escalation time is fixed text worked out once from AS_OF and each alert's escalates, because a persistent alert should not hide behind a timer that can run out while you read it. If you want a live countdown, compute it on your server and pass the result in.
Why is only one Acknowledge coloured?
The panel has one primary action: the next alert that needs an answer. It sits on the first alert still waiting, so after you acknowledge the first, the button on the second becomes the Shine Button and the first shows its receipt. Everything else is outline or ghost.
How is severity shown without colour?
By a word, a glyph and a weight: Critical has a solid badge, a circle-alert glyph, a semibold title and a bar at the start of the row; High has an outline badge, a triangle glyph and a medium title. Only the critical glyph takes the destructive status colour, and the Status dot beside the count is a second, redundant mark next to the words.
Is it accessible?
Each Acknowledge button names its alert, so several rows can share the same visible word. After a press focus moves to that row's Undo, and after Undo back to Acknowledge. A single polite status message says what changed ("Acknowledged ... 1 needs acknowledgement"). Times are real time elements that keep their own direction inside right-to-left text.
Related
- Pro
Low-Priority Updates Bundle Notification
Quiet and digestsA quiet notification bundle: seven low-priority updates folded into one row that opens into the list, with a dismiss per row, Dismiss all with an Undo, and a switch that moves what remains to a digest at a time worked out from the page's now.
- 120Pro
System Alerts by Severity Notification
Incidents and alertsAn infrastructure monitor's alert panel: a count of open alerts by severity, and an accordion of three systems with their facts, an Acknowledge and a one-hour Mute that says when it ends.
- Pro
An outage notice with the facts of the incident in a quiet column (status, duration, start, regions as chips), an ordered list of updates in a frame, and a Subscribe to updates with Email and Push checkboxes that answers in the demo.
- Pro
Snooze Notification
Quiet and digestsA notification with a snooze popover: Later today, Tomorrow and Next week worked out from one fixed time, a custom hour, a Snoozed list with wake times and a Wake now that sends one back.
- Pro
Alert Banner Notification
Incidents and alertsAn operations console's banner bar over a sketch of its app: four notices queue by urgency and show one at a time, with Previous, Next, a link, Dismiss and Snooze all for an hour.
- Pro
Was This You Sign-In Alert Notification
Incidents and alertsA password manager asking whether a new sign-in was you: the device, browser, place, IP and time in hairline cells, one answer that marks it as yours, and one that opens a three-step checklist with an alert dialog before it signs the session out.