Alert Delivery

The Right Person, and Proof They Got It

An alert nobody reads is worse than no alert at all. Threatwhere filters before it sends, escalates when nobody answers, and keeps a record of every attempt — so duty of care is something you can evidence, not just assert.

CHANNELS

Three ways in, chosen per person

Every user picks the channels that suit how they work. Turn one off and the others carry on — you can never end up with none.

In-app

The notification centre in Overwatch. Everything that fired, in order, with the event behind it one click away.

Email

For the alert that has to survive a closed laptop. Written to be read on a phone screen, with a direct link back into the platform.

Push

Straight to the phone — Operator in the field, and the browser at the desk. Reserved for the things that genuinely cannot wait.

PRECISION

Filtered before it is sent

The reason teams stop reading alerts is that too many of them did not matter. Threatwhere decides that before anything leaves — against the scores our pipeline has already put on every event.

  • Event type and sub-type — conflict, terrorism, cyber, civil unrest and the rest
  • Threat, urgency and severity scored above the floor you set
  • Countries, regions and geographic scope you actually care about
  • Event status, damage level and how well corroborated the reporting is
  • Breaking only, when you want nothing but the first report

Quiet hours

Nights and weekends stay quiet unless the threshold says otherwise. Set once, in your own timezone.

Digest windows

Everything below the waking-someone-up line batched into one message, on your schedule rather than the world’s.

Per-person rules

The regional lead, the travel manager and the duty officer are not watching for the same thing. They do not have to.

WHEN IT MATTERS MOST

Nobody answered. Now what?

A missed check-in and an SOS are not notifications. They are the start of a procedure — and the platform runs it.

Escalation chains

Build the ladder yourself — who is raised, how long after, and on which channel. Step by step, until somebody responds.

Every device, once

An SOS reaches every device the responder carries — and exactly once per device, however many routes it travelled to get there.

The delivery log

Sent, failed, bounced, skipped — every attempt on the record. Where we tried and cannot confirm the outcome, it says unconfirmed, rather than claiming a delivery nobody proved.

Take the record with you

Your audit trail, messaging audit and check-in history export to CSV whenever an insurer, a regulator or your own board asks what happened and when.

Set it up for how your team actually works

Talk to us about the thresholds, the rotas and the escalation ladder your duty-of-care obligations require — and we will help you configure them.