UpKeep Automated Critical Asset Downtime Alerts
Every few minutes, WebRun checks UpKeep for critical assets whose status changes to down or out of service, pages the on-call technician on Telegram with the asset and location, and posts a summary to the ops channel in Slack so critical downtime gets a fast response.
How do I get notified the moment a critical asset goes down?
WebRun checks UpKeep every few minutes for critical assets whose status changes to down or out of service. It pages the on-call technician on Telegram with the asset, location, and any open work order, then posts the same alert to your ops channel in Slack, so critical downtime gets a human response within minutes instead of hours.
- On-call technicians are paged within 5 minutes of a critical asset going down
- The ops channel has live visibility into every asset currently down
- Downtime response starts before a shift supervisor even opens UpKeep
Built for facilities managers · maintenance supervisors · on-call technicians · manufacturing operations
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
app.onupkeep.comin a real browser with your saved login - no setup, no API keys. -
1
UpKeep - check critical assets for downtime
WebRun opens UpKeep to check critical assets for downtime. - Open UpKeep and check the status of assets marked critical priority
- Compare the current status against the last check to catch any newly marked down or out of service
- Capture the asset, location, and any open work order tied to it
Done when Every critical asset that changed to down since the last check is identified.
-
2
Telegram - page the on-call technician
WebRun pages the on-call technician on Telegram the moment a critical asset goes down. - Send the on-call technician a Telegram message naming the asset, location, and time it went down
- Include a link to the open work order in UpKeep if one exists
- Send within minutes of the status change being detected
Done when The on-call technician has been paged for every newly down critical asset.
-
3
Slack - post to the ops channel
WebRun posts the downtime alert to the ops channel in Slack. - Post the same downtime alert to the operations channel for visibility
- Include how long the asset has been down since it was first detected
- Update the Slack thread when the asset's status returns to up
Done when The ops channel has visibility into every critical asset currently down.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
How fast does the on-call tech get paged?
Within minutes of the asset's status changing to down in UpKeep, since WebRun checks every few minutes around the clock.
Which assets does it watch?
Only assets you have marked critical priority in UpKeep. Change an asset's priority in UpKeep and WebRun's watch list updates on the next check.
Does it try to fix or restart anything itself?
No. WebRun only detects the status change and pages people. Diagnosing and resolving the downtime stays with your technician.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.