Automated FieldServio Load Bank Test Scheduling
Every Monday, WebRun opens FieldServio, finds units that have gone 12 months or more without a load bank test, drafts a scheduling email in Outlook for each customer explaining why the test matters, and posts the team a ranked Slack list of who is furthest overdue.
How do I find and schedule standby generators that are overdue for their annual load bank test?
WebRun checks FieldServio every Monday for standby generators that have gone 12 months or more without an annual load bank test, drafts a scheduling email in Outlook for each customer with proposed visit windows, and posts a ranked overdue list to Slack. The scheduling team works down the list in order, so no unit drifts further out of compliance.
- Overdue units get booked before they drift further out of compliance
- Coordinators see a ranked overdue list every Monday instead of searching FieldServio by hand
- Customers get a clear, on-brand explanation of why the test matters
Built for standby generator dealers · generator service coordinators · generator technicians · commercial generator service companies
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 - find units overdue for a load bank test
fieldservio.com
WebRun opens FieldServio to find units overdue for a load bank test. - Open FieldServio and filter service history by test type to Load Bank Test
- Find units whose last load bank test was 12 or more months ago
- Capture customer name, site contact, generator kW rating, and last test date
- Exclude units that already have a load bank test scheduled
Done when Every unit overdue for a load bank test is listed with its last test date.
-
2
Outlook - draft the scheduling email
microsoft.com
WebRun opens Outlook to draft the scheduling email. - Draft a scheduling email for each overdue customer explaining that annual load bank testing keeps the standby system compliant and ready
- Reference the generator's kW rating and the last test date
- Propose two to three available service windows for the technician
- Save each email as a draft in Outlook for the team to review
- Never send a scheduling email automatically
Done when A load bank test scheduling draft is ready in Outlook for every overdue customer.
-
3
Slack - post the week's overdue list
slack.com
WebRun opens Slack to post the week's overdue list. - Post the week's overdue load bank test list to the scheduling channel
- Sort by months overdue so the longest overdue units are booked first
Done when The scheduling team has this week's ranked load bank test list 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
Will it schedule the load bank test without asking the customer?
No. WebRun only drafts the scheduling email in Outlook. Your team reviews it, proposes final times, and sends it, so no visit gets booked without a person confirming it.
Why does load bank testing need its own reminder, separate from PM service?
Because it is tracked and required on its own cycle. WebRun filters FieldServio's service history specifically by test type, so a unit that had its oil changed recently but never had a load bank test still gets flagged.
How is the Slack list prioritized?
It ranks units by how many months overdue they are, so the ones furthest from compliance show up first for the scheduling team to book.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.