Automated Elevator Callback Digest
Every Monday, WebRun opens FIELDBOSS, reads the past ninety days of callback tickets, groups them by unit to find elevators with repeat trouble calls, logs the counts and common fault codes to a Google Sheet, and sends your service manager a Telegram digest of the worst repeat offenders.
How do I find elevators with repeat callback problems?
Every Monday, WebRun reads the last 90 days of callback tickets in FIELDBOSS, groups them by elevator to find repeat trouble calls, and logs the counts and common faults to a Google Sheet. It sends your service manager a Telegram digest of the worst repeat offenders, so chronic units get a root-cause fix instead of endless callbacks.
- Chronic units surface before they cause an entrapment
- Repeat-callback costs turn into root-cause fixes
- Modernization candidates are backed by real callback data
Built for elevator service contractors · service managers · operations leads · field-service teams
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
www.fieldboss.comin a real browser with your saved login - no setup, no API keys. -
1
FIELDBOSS - read recent callback tickets
fieldboss.com
WebRun opens FIELDBOSS to read recent callback tickets. - Open FIELDBOSS and pull callback and trouble-call tickets from the last 90 days
- Group them by elevator to count how many callbacks each unit had
- Note the recurring fault codes and the technicians who attended
Done when Every unit's callbacks over the last 90 days are grouped and counted with fault codes.
-
2
Google Sheets - count callbacks per unit
google.com
WebRun logs callback counts per unit to a Google Sheet. - Append a row per unit: site, callback count, and most common fault
- Sort so the units with the most callbacks sit at the top
- Track the trend week over week so a worsening unit stands out
Done when Callback counts per unit are logged and ranked by frequency.
-
3
Telegram - digest the repeat offenders
telegram.org
WebRun sends the service manager a repeat-offender digest in Telegram. - Send the service manager the top repeat-offender units with their callback counts
- Note the recurring fault so a root-cause fix or modernization can be considered
- Link the sheet for the full breakdown
Done when The service manager has this week's repeat-offender digest in Telegram.
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 change any tickets in FIELDBOSS?
No. WebRun only reads your closed and open callback tickets to count and group them. It never edits, closes, or reassigns a ticket. The digest is an internal read-only summary for your service manager.
How does it decide a unit is a repeat offender?
It counts callbacks per elevator over the last 90 days and ranks the units with the most, surfacing the recurring fault code so you can weigh a root-cause repair or modernization against endless callbacks.
Can it show whether a unit is getting worse?
Yes. It tracks each unit's callback count week over week in the sheet, so an elevator that is trending worse stands out before it becomes an emergency.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.