Catch generators due for an oil change before hours pile up
Every morning, WebRun opens FieldServio, checks each monitored unit's run hours and last oil change date, flags any generator within 25 hours or 30 days of its interval, logs the due list to Google Sheets, and alerts dispatch on Slack so the oil change gets scheduled before the engine runs past interval.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I track when a standby generator is due for an oil change based on run hours?
WebRun checks each monitored generator's run hours against its oil change interval in FieldServio every morning, flags any unit within 25 hours or 30 days of its limit, logs the due list to Google Sheets, and alerts dispatch in Slack with overdue units marked first. Oil changes get scheduled before an interval is crossed instead of after a technician notices on the next visit.
- Oil changes get scheduled before a run-hour or calendar interval is crossed
- Dispatch sees overdue units flagged first instead of scanning FieldServio manually
- Units that ran hard during an outage get caught between regular visits
Built for standby generator dealers · dispatch coordinators · generator service technicians · fleet and facilities managers
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 run hours against oil change interval
fieldservio.com How to Automate FieldServio
WebRun opens FieldServio to check run hours against oil change interval. - Open FieldServio and pull current run hours for each monitored unit
- Compare run hours since last oil change against the manufacturer's interval, typically 100 to 200 hours or annually, whichever comes first
- Flag any unit within 25 run hours or 30 days of its interval
- Capture customer, site, generator model, current hours, and interval limit for each flagged unit
Done when Every unit approaching its oil change interval is flagged with its current hours and limit.
-
2
Google Sheets - log the due list
google.com How to Automate Google Sheets
WebRun opens Google Sheets to log the due list. - Append each flagged unit to the oil change due sheet with customer, model, hours, and interval limit
- Sort by how close each unit is to its limit
Done when The oil change due sheet is updated with today's flagged units, closest to due first.
-
3
Slack - alert dispatch to schedule
slack.com How to Automate Slack
WebRun opens Slack to alert dispatch to schedule. - Post today's oil change due list to the dispatch channel
- Flag any unit that has already crossed its interval in red so it is scheduled first
Done when Dispatch has today's oil change due list in Slack, with overdue units flagged.
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 book the oil change appointment automatically?
No. WebRun only builds the due list and alerts dispatch in Slack. A person on your team schedules the actual visit, so nothing gets booked without your dispatcher deciding.
How does it track the interval if generators run on different schedules?
It compares each unit's live run hours in FieldServio against the manufacturer's interval, typically 100 to 200 hours or annually, whichever comes first, so a unit that ran hard during an outage gets flagged even between scheduled visits.
What happens if a unit has already gone past its interval?
It is flagged in red at the top of the Slack alert, so dispatch schedules the most overdue units first instead of working the list in order.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.