Automated Endoscope Repair Tracking
Every morning, WebRun opens EndoManager, finds every endoscope currently out for repair, logs each scope's vendor, ship date, repair reason, and quoted return date to a Google Sheet, then posts a Slack summary of how many scopes are down and which have passed their promised turnaround.
How do I automatically track endoscopes out for repair and overdue returns?
WebRun tracks your scopes in repair every morning. It reads which endoscopes are out for repair in EndoManager, logs each vendor, ship date, and quoted return to a Google Sheet, marks anything past its promised turnaround as overdue, and posts a Slack summary of how many scopes are down, so gaps in the rotation surface early.
- The team always knows how many scopes are down and which type
- Overdue repairs get chased instead of sitting unnoticed at the vendor
- Scope shortages surface before they threaten the day's schedule
Built for endoscopy centers · GI charge nurses · biomedical equipment managers · ambulatory surgery centers
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
newcura.comin a real browser with your saved login - no setup, no API keys. -
1
EndoManager - find scopes flagged out for repair
newcura.com
WebRun opens EndoManager to find scopes out for repair. - Open EndoManager and list endoscopes marked out of service or sent for repair
- Capture each scope serial number, model, repair reason, and the date it left the center
- Note the repair vendor and any quoted return date on file
Done when Every scope currently out for repair is listed with its vendor and ship date.
-
2
Google Sheets - log vendor, ship date, and due back
docs.google.com
WebRun logs each repair to the Google Sheet. - Open the Scope Repair Tracker sheet
- Add or update a row per scope with vendor, ship date, repair reason, quoted return, and estimated cost
- Mark any scope past its quoted return date as overdue and calculate days down for each
Done when The tracker reflects every scope out for repair with days down and an overdue flag.
-
3
Slack - summarize scopes down and overdue
slack.com
WebRun posts the repair summary to Slack. - Post a Slack summary to the operations channel with the total number of scopes down and the count by type
- List any scope past its promised return date so someone can chase the vendor
- Link to the full Google Sheet for the detail
Done when The team has a Slack summary of scopes down, days out, and overdue repairs.
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 contact repair vendors or approve repair quotes?
No. WebRun builds the tracker and flags overdue scopes for someone to chase. Contacting the vendor, approving a quote, or authorizing a loaner stays with your team after they review the sheet.
How does it know a repair is overdue?
It compares each scope's quoted return date on file against today's date. Any scope past its promised turnaround is marked overdue, and days down is calculated from the ship date so long repairs stand out.
Can it help decide whether we have enough scopes for the schedule?
Yes indirectly. The Slack summary shows how many scopes of each type are down, so the charge nurse can see at a glance whether the remaining scopes cover the day's booked cases.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.