Told what matters. Never told who.
Content-minimal alerts reach agents and managers where they already work — browser push, mobile push, SMS, email, and channels like Microsoft Teams and Slack — and anything unacknowledged waits in an in-app recovery inbox.
Every channel. One rule.
Choose where each alert goes per location and per role. The content rule never changes: an alert names the work, not the contact.
Browser push
In-app and browser alerts for the agent on shift: a callback coming due, a lease about to expire, a workspace lock.
Mobile push and SMS
Managers on the floor get approvals and holds on their phone; SMS carries the same content-minimal line.
Digests and non-urgent items: the overnight batch is ready, a configuration revision awaits approval.
Microsoft Teams and Slack
Automated notifications into the channel your team already watches: queue health, SLA risk, reconciliation holds, batch reviews.
Recovery inbox
Anything unacknowledged stays in an in-app inbox until it is acted on; managers see the count.
Scoped delivery
Alerts respect location and role scope. A Northgate manager never receives Riverside’s approvals.
The alert is a pointer, not a record.
Notifications travel through third-party services. They carry a location, a time, and a work type; identity stays inside the workspace, behind scope.
No identity in transit.
A push says “Callback due · Northgate · 4:00 PM”, never a name, a number, or a message body. Opening it requires the workspace and the scope.
Every send is a ledger row.
Which alert, which channel, which role, and when it was acknowledged. Delivery failures are recorded, not retried blindly.
Versioned like everything else.
Notification policy is part of the location configuration: approved, activated, and rolled back as a revision.
See an alert arrive.
Bring the channels your team lives in; we’ll show you the policy table and the row it writes.