Automated FieldServio Fault Alert Triage
Every few minutes, WebRun opens FieldServio, checks monitored units for new fault codes, texts your on-call technician immediately for anything critical like low coolant, overcrank, or high engine temperature, and posts a running log of every fault to Slack for the team.
How do I get an immediate alert when a monitored standby generator throws a critical fault?
WebRun checks FieldServio every few minutes for new fault codes on monitored standby generators. When a fault is critical, like low coolant, overcrank, or high engine temperature, it immediately texts your on-call technician through Twilio with the unit and site details, and logs every fault, critical or not, to Slack, so a unit that cannot start on demand gets a fast response.
- Critical faults reach the on-call technician within minutes instead of at the next check-in
- Every fault is logged, so nothing gets lost between shifts
- Duplicate pages from a flapping sensor are filtered out automatically
Built for standby generator dealers · on-call generator technicians · generator service 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 - read new fault codes from monitored units
fieldservio.com
WebRun opens FieldServio to read new fault codes from monitored units. - Open FieldServio's monitoring feed and check for new fault codes since the last run
- Classify each fault as critical (low coolant, overcrank, high engine temperature, low fuel) or informational (battery voltage warning, maintenance due)
- Capture the unit, site, customer, and fault description for each
- Skip faults already alerted in the last 30 minutes to avoid duplicate pages
Done when Every new fault code is captured and classified as critical or informational.
-
2
Twilio - text the on-call technician
twilio.com
WebRun opens Twilio to text the on-call technician. - For each critical fault, send an SMS to the on-call technician with the unit, site address, and fault description
- Keep the message short enough to read at a glance
- Log the timestamp of each page sent
Done when The on-call technician has been texted for every critical fault from this run.
-
3
Slack - log every fault for the team
slack.com
WebRun opens Slack to log every fault for the team. - Post every fault from this run to the service channel, critical and informational alike
- Mark which ones were paged to the on-call technician
Done when The team has a complete log of this run's faults in Slack.
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 it text the customer when their generator faults?
No. The SMS only goes to your on-call technician's number. WebRun never contacts the customer directly. Any customer communication is a separate, human decision your team makes after the fault is triaged.
How does it decide which faults are urgent enough to page someone?
It classifies each fault code against a critical list, things like low coolant, overcrank, high engine temperature, and low fuel, that typically mean a standby system cannot start on demand. Everything else is logged but does not trigger a text.
Will I get paged twice for the same fault?
No. It checks for a fault already alerted in the last 30 minutes before sending another page, so a flapping sensor does not flood your on-call technician with texts.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.