Triage new maintenance requests into the right technician's queue
Throughout the day, WebRun reads new maintenance request emails in Gmail, opens UpKeep to create the matching work order with a category and priority, assigns it to the right technician by location, and pings them in Slack so nothing waits in an inbox.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I automatically triage and assign new maintenance requests?
WebRun reads new maintenance request emails as they land in Gmail, opens UpKeep, and creates a work order with a category, priority, and the right technician assigned by location. It pings that technician in Slack and flags anything it cannot confidently categorize for a supervisor, so requests move into a queue within minutes instead of sitting in an inbox.
- New requests become a triaged, assigned work order within 15 minutes of arriving
- Safety issues get flagged as high priority automatically, not left for review
- Nothing sits unread in the facilities inbox overnight
Built for facilities managers · maintenance supervisors · in-house maintenance teams · property and campus operations
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
mail.google.comin a real browser with your saved login - no setup, no API keys. -
1
Gmail - read new maintenance requests
gmail.com How to Automate Gmail
WebRun opens Gmail to read new maintenance request emails. - Search the facilities inbox for unread maintenance request emails
- Open each one and read the location, description, and reported issue
- Mark each processed email as read
Done when Every new maintenance request email is read and its details captured.
-
2
UpKeep - create and triage the work order
upkeep.com How to Automate UpKeep
WebRun creates and triages the work order in UpKeep. - Open UpKeep and create a work order for each request
- Set the category and priority based on the reported issue, and mark safety issues as high priority
- Assign the work order to the technician who covers that location
Done when A categorized, prioritized, and assigned work order exists for every new request.
-
3
Slack - notify the assigned technician
slack.com How to Automate Slack
WebRun notifies the assigned technician in Slack. - Message the assigned technician with the work order, location, and priority
- Post a running count of new requests triaged to the maintenance channel
- Flag any request WebRun could not confidently categorize for a supervisor to review
Done when The assigned technician has been notified for every new work order created.
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
How does WebRun decide who gets assigned?
It matches the request's location to the technician who covers that site in UpKeep. Update technician coverage in UpKeep and future requests route accordingly.
What happens to requests it cannot categorize confidently?
It still creates the work order, but flags it in Slack for a supervisor to set the category and priority by hand instead of guessing.
Does it reply to the person who submitted the request?
No. WebRun only creates and assigns the internal work order. It does not email or message the requester back on its own.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.