Route maintenance requests to the right crew instantly
Every few minutes, WebRun opens StarRez, checks for newly submitted maintenance requests, reads the category and description to route each one to the right Zendesk queue, plumbing, electrical, HVAC, or general, and texts the on-call tech through Twilio the moment a request is marked urgent.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I automatically route student housing maintenance requests to the right crew?
WebRun checks StarRez every few minutes for new maintenance requests, reads the category and description, and opens a routed ticket in the right Zendesk crew queue, plumbing, electrical, HVAC, or general. When a request is flagged urgent, such as no heat or flooding, it also texts the on-call tech through Twilio immediately, so urgent issues get a response in minutes, not hours.
- Every request lands in the right crew queue within minutes
- Urgent issues text the on-call tech instantly instead of waiting in a queue
- Residents are never messaged directly, all updates route through your team
Built for facilities and maintenance teams · residence life operations · university housing offices · on-call maintenance staff
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.starrez.comin a real browser with your saved login - no setup, no API keys. -
1
StarRez - find new maintenance requests
WebRun opens StarRez to find new maintenance requests. - Open StarRez and check for maintenance requests submitted since the last run
- Read the category, hall, room, and description for each request
- Flag requests marked urgent, such as no heat, flooding, or a lock failure
Done when Every new request is categorized and its urgency is set.
-
2
Zendesk - route the ticket to the right crew
WebRun opens Zendesk to route the ticket to the right crew. - Create a ticket for each request in the matching crew queue: plumbing, electrical, HVAC, or general
- Attach the hall, room, and resident-provided description to the ticket
Done when A routed ticket exists in the right queue for every new request.
-
3
Twilio - text the on-call tech for urgent requests
WebRun opens Twilio to text the on-call tech for urgent requests. - For requests flagged urgent, text the on-call tech the hall, room, and issue
- Skip texting for standard, non-urgent requests, they wait for the normal ticket queue
Done when The on-call tech has been texted for every urgent request.
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 text residents about their request?
No. WebRun only texts your on-call maintenance tech through Twilio for urgent requests. Residents are never messaged directly, updates to them stay with your team.
How does it decide what's urgent?
It reads the request category and description for signs of an urgent issue, like no heat, flooding, or a lock failure, and only those trigger an immediate text to the on-call tech.
What happens to non-urgent requests?
They're still routed to the right crew queue in Zendesk right away, they just don't trigger a text. Your crew works them through the normal ticket queue.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.