Automated FieldServio Offline Unit Alerts
Every hour, WebRun opens FieldServio, checks monitored units for a lost communication signal, texts the on-call technician for any unit offline more than 2 hours so a possible connectivity or system issue gets checked, and logs every offline event to Google Sheets with duration so recurring problem units stand out.
How do I get alerted when a monitored standby generator stops reporting or goes offline?
WebRun checks FieldServio every hour for monitored generators that have stopped reporting, texts the on-call technician through Twilio for any unit offline more than 2 hours, and logs every offline event to Google Sheets with its duration. Connectivity gaps get checked quickly, and units that repeatedly drop signal show up as a pattern instead of a string of one-off alerts.
- Offline units get checked within the hour instead of at the next scheduled visit
- Recurring connectivity problems show up as a pattern in the log, not scattered one-off alerts
- On-call technicians are not paged twice for the same ongoing gap
Built for standby generator dealers · on-call generator technicians · generator monitoring coordinators · commercial facilities with backup power
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.fieldservio.comin a real browser with your saved login - no setup, no API keys. -
1
FieldServio - check for units with no recent signal
fieldservio.com
WebRun opens FieldServio to check for units with no recent signal. - Open FieldServio's monitoring dashboard and check each unit's last-reported timestamp
- Flag any unit with no signal for more than 2 hours
- Capture the unit, customer, site address, and hours since last signal
Done when Every unit offline more than 2 hours is listed with its last-signal time.
-
2
Twilio - text the on-call technician
twilio.com
WebRun opens Twilio to text the on-call technician. - For each newly flagged unit, send an SMS to the on-call technician with the unit, site address, and hours offline
- Skip units already texted about in the last 4 hours to avoid repeat pages for the same gap
Done when The on-call technician has been texted for every newly offline unit.
-
3
Google Sheets - log the offline event
google.com
WebRun opens Google Sheets to log the offline event. - Append each offline event to the monitoring log with unit, customer, start time, and duration once it is resolved
- Leave the row open until the unit reports back online
Done when The monitoring log reflects every offline event this run, open or resolved.
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
Does an offline alert mean the generator itself failed?
Not necessarily. It usually means the monitoring unit lost cellular or network signal, not that the generator failed. That is exactly why it gets checked, so a real problem is not mistaken for a connectivity blip, or the other way around.
Does it contact the customer when their unit goes offline?
No. The SMS only goes to your on-call technician. WebRun never messages the customer directly, your team decides if and when the customer needs to know.
How does the log help beyond a single alert?
Because every offline event is logged with its duration, a unit that keeps dropping signal shows up as a pattern in Google Sheets, which usually points to a connectivity issue worth fixing at the site rather than a one-off glitch.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.