Catch possible leaks before the water bill does
Every morning, WebRun opens Conservice, pulls the latest submeter read for every occupied unit, compares it to that unit's own trailing 3 month average, flags any unit running well above its normal consumption, and posts the list to Slack with the percent above baseline so maintenance can check for a leak before it turns into a large bill.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I catch a possible leak before it shows up on the utility bill?
Every morning, WebRun compares each occupied unit's latest submeter read in Conservice against that unit's own trailing 3 month average. Any unit running well above its normal consumption gets flagged and posted to Slack with the percent over baseline, ranked so the largest spikes are checked first, catching a likely leak before it shows up on the next bill.
- Likely leaks get flagged the same morning instead of next month's bill
- Each unit is judged against its own baseline, not a property average
- Maintenance opens Slack to a ranked list instead of scanning every meter
Built for multifamily maintenance teams · property managers · utility billing teams · facilities managers
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.conservice.comin a real browser with your saved login - no setup, no API keys. -
1
Conservice - compare consumption to baseline
conservice.com How to Automate Conservice
WebRun opens Conservice to compare consumption to baseline. - Open Conservice and pull the latest submeter read for every occupied unit
- Compare each unit's read to its own trailing 3 month average for that utility
- Flag any unit running more than 50 percent above its normal consumption
Done when Every occupied unit's latest read has been compared to its own baseline and any spike is flagged.
-
2
Slack - alert maintenance to check the unit
slack.com How to Automate Slack
WebRun opens Slack to alert maintenance to check the unit. - Post the day's high consumption list to the maintenance channel
- Include the unit, the utility type, and the percent above baseline for each
- Put the largest spikes first so the most likely leaks get checked first
Done when Maintenance has today's high consumption list in Slack, ranked by how far above baseline each unit is.
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 schedule a maintenance visit automatically?
No. WebRun only flags the unit and posts it to Slack. Your team decides whether to dispatch maintenance and schedules the visit.
How is a unit's normal consumption defined?
Its own trailing 3 month average for that utility, not a property wide number. That way a naturally heavy user doesn't get flagged just for being above the property average.
Does it check vacant units too?
This flow checks occupied units. Vacant units are covered by a separate check, since a vacant unit's normal baseline should be close to zero rather than a trailing average.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.