Take the incident on the phone without losing the plot

Northstar’s cold-chain monitor escalates while the responder is between depots. Polar Freight sees the same shape when a Starlink corridor drops. A flattened pager blurb forces a laptop hunt - or unsafe guesses from a title line alone.

Without Dataplicity

SMS or email with a vague summary. Ack lives in one tool; device context in another. Handoff loses the plot - and Northstar’s night NOC cannot tell whether the page is one sensor or a critical site.

With Dataplicity

Incident delivery reaches registered phones. When an incident is opened or escalated through on-call schedules - for example, from service, heartbeat, or user-impact incident automation - responders with the Dataplicity mobile app registered for the organisation receive native push (FCM / APNs). Email and chat cards can fire in parallel.
Tap opens the same incident. The notification carries the incident identity and labels. The app opens Incident detail - summary, state, severity - the same ops record as the web console.
Act from the phone. Acknowledge, escalate, or resolve without waiting for a laptop.
Pull richer context in-app as needed. Fleet presence and device detail load through the app’s APIs after open. The push itself is not a live fleet map, and it does not open straight into a terminal session.

Outcome

On-call acts on one ops record, not a dead-end notification - whether the altitude turns out to be a single freezer sensor or a Polar corridor event.

Take the incident on the phone without losing the plot ​

Without Dataplicity ​

With Dataplicity ​

Outcome ​

Next ​

Take the incident on the phone without losing the plot

Without Dataplicity

With Dataplicity

Outcome

Next