Automated Maintenance SLA Breach Alerts
Every hour, WebRun opens Propertyware, reviews open work orders, finds any past its target response or completion time, logs each breaching job with its unit, age, and assigned vendor into a Google Sheet, and alerts your team in Slack so the slowest jobs get attention before they turn into tenant complaints.
How do I get alerts when maintenance breaches SLA?
Every hour, WebRun opens Propertyware and reviews open work orders, finding any past their target response or completion time. It logs each breaching job with its unit, age, and assigned vendor to a Google Sheet and alerts your team in Slack, so slow maintenance gets pushed within the hour instead of becoming a tenant complaint.
- SLA breaches surface within the hour, not at week's end
- The worst-overdue, highest-priority jobs are pushed first
- Slow vendors get chased before tenants escalate
Built for property managers · maintenance coordinators · residential property teams · landlords
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.propertyware.comin a real browser with your saved login - no setup, no API keys. -
1
Propertyware - review open work orders
WebRun opens Propertyware to review open work orders. - Open the Maintenance module in Propertyware and list open work orders
- Capture each job's status, age, assigned vendor, and priority
- Flag any job open past its target response or completion time
Done when Every open work order has been checked against its SLA target.
-
2
Google Sheets - log breaches and age
WebRun logs each SLA breach into a ranked sheet. - Log each breaching job with its unit, age, vendor, and how far past target it is
- Sort so the worst breaches and highest priorities sit at the top
- Keep a running view so jobs closed in the last hour drop off
Done when Every SLA breach is logged and ranked in the sheet.
-
3
Slack - alert on overdue jobs
WebRun alerts the team to overdue maintenance jobs. - Post an alert listing work orders past their SLA target
- Name the unit, the assigned vendor, and how overdue each job is
- Leave it for your team to chase the vendor. Never reassign or close jobs automatically
Done when Your team is alerted to every job breaching SLA in Slack.
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
Will it reassign or close work orders on its own?
No. WebRun only reads the Propertyware work orders and alerts your team. Reassigning a vendor, escalating, or closing a job stays a human decision inside Propertyware.
How does it know a job has breached SLA?
It reads each open work order's age and status in Propertyware and compares it to your target response and completion times, flagging anything past target and ranking it by how overdue it is.
How often does it check?
Every hour during business hours, so a job slipping past its target surfaces within the hour rather than at the end of the week when a tenant has already complained.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.