Automated Conservice Vacant Unit Cost Alerts
Every night, WebRun opens Conservice, pulls the vacant unit list for each property, checks each vacant unit's latest submeter read against a near zero baseline, and logs any unit still posting real consumption to a Google Sheet with the likely cause, so maintenance can check it before the cost keeps accruing.
How do I catch utility costs still running on units marked vacant?
Every night, WebRun checks Conservice for units marked vacant and compares each one's submeter read against a near zero baseline for water, electric, and gas. Any vacant unit still posting real consumption is logged to Google Sheets with a likely cause, so maintenance can check for a running fixture or unauthorized use before the cost adds up.
- Utility costs on vacant units get caught the same night, not next cycle
- Leaks and meter faults surface before they show up as a loss
- Repeat cases are tracked instead of blending into a long unit list
Built for multifamily property managers · maintenance supervisors · utility billing teams · asset 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 - check vacant unit consumption
conservice.com
WebRun opens Conservice to check vacant unit consumption. - Open Conservice and pull the current vacant unit list for each property
- Read each vacant unit's latest submeter consumption for water, electric, and gas
- Compare it against a near zero baseline for an unoccupied unit
Done when Every vacant unit's consumption has been checked against the baseline.
-
2
Google Sheets - log units still consuming
google.com
WebRun opens Google Sheets to log units still consuming. - Log any vacant unit whose consumption is above the baseline, with the utility type and the amount
- Note the likely cause: a running fixture, a miswired meter, or possible unauthorized use
- Carry forward units flagged on a prior night so repeat cases stand out
Done when Every vacant unit still consuming above baseline is logged with a likely cause for maintenance to check.
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 dispatch maintenance on its own?
No. WebRun only logs the vacant units still consuming above baseline. A human on your team decides whether to send maintenance to check it.
How does it tell a real leak from normal vacant unit usage?
It compares each vacant unit's read against a near zero baseline for an unoccupied unit, so any real consumption of water, electric, or gas stands out immediately.
Does it flag the same unit every night if it's not fixed?
Yes. A unit flagged on a prior night is carried forward and marked as a repeat case, so it doesn't quietly drop off the list.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.