Automated Vacation Rental Maintenance Issue Routing
When a maintenance issue is reported in Guesty, WebRun reads the property, categorizes the issue type (plumbing, HVAC, electrical, appliance, or general), posts a routed work order to the right Slack channel with the vendor's contact info, and logs the ticket in Google Sheets so nothing falls through the cracks.
How can I automatically route vacation rental maintenance issues to the right vendor?
When a maintenance issue lands in Guesty, WebRun reads the property and issue description, categorizes the problem, and posts a routed work order to the matching Slack channel with the relevant vendor's contact details. Every issue is logged in Google Sheets with its routing and resolution status so nothing slips through.
- Every maintenance report is routed to a vendor within minutes, not the next morning
- No issue is lost in a text thread or email inbox
- A running Sheets log shows open vs. resolved issues across all properties
Built for vacation rental managers · short-term rental property managers · property management companies · Airbnb co-hosts managing multiple properties
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.guesty.comin a real browser with your saved login - no setup, no API keys. -
1
Guesty - detect incoming maintenance report
guesty.com
WebRun opens Guesty to detect incoming maintenance report. - Open Guesty and detect the newly submitted maintenance request
- Read the property name, issue description, and severity level
- Categorize the issue as plumbing, HVAC, electrical, appliance, or general maintenance
Done when The maintenance issue is read, categorized, and the correct vendor type is identified.
-
2
Slack - post routed work order to the right channel
slack.com
WebRun opens Slack to post routed work order to the right channel. - Post a structured work order to the appropriate Slack channel for the issue category
- Include property name, issue description, severity, and the vendor's contact information
- Tag the property manager on urgent or high-severity issues
Done when The routed work order is live in the correct Slack channel with vendor contact details.
-
3
Google Sheets - log issue, routing, and resolution status
google.com
WebRun opens Google Sheets to log issue, routing, and resolution status. - Append a row to the maintenance log with property, issue type, severity, vendor routed, and timestamp
- Leave a resolution column blank to mark when the issue is fixed
Done when The maintenance issue is logged in Google Sheets with routing details and open status.
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 know which vendor to route the issue to?
It uses the vendor categories and contact info you configure at setup. Each property can have its own preferred plumber, HVAC tech, and handyman, and WebRun routes by issue category and property.
What happens if the issue is urgent, like a water leak or no heat?
High-severity issues are tagged in Slack and the property manager is @-mentioned directly so urgent situations are not buried in a channel feed.
Does it contact the vendor directly to book the repair?
No. WebRun posts the work order details and vendor contact information in Slack for your team to action. Your team makes the final call on when and how to engage the vendor.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.