Flag submeter reading exceptions for you
Each time a new batch of submeter readings is uploaded to ManageAmerica, WebRun compares every reading against that resident's trailing usage history, flags anything that spikes, drops, or reads as a negative or zero consumption, logs the exceptions to a sheet, and posts your billing team a Slack alert before utility bills go out.
- No credit card
- Under $0.01 per run
- Cancel anytime
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.manageamerica.comin a real browser with your saved login - no setup, no API keys. -
1
ManageAmerica - compare readings to usage history
manageamerica.com How to Automate ManageAmerica
WebRun opens ManageAmerica to compare readings to usage history. - Open ManageAmerica and pull the newly uploaded submeter reading batch
- Compare each reading against that resident's trailing 6 month usage average
- Flag any reading more than 3 times the average, any drop to near zero, and any negative reading
Done when Every reading in the batch has been compared and any outlier is flagged.
-
2
Google Sheets - log the exceptions
google.com How to Automate Google Sheets
WebRun opens Google Sheets to log the exceptions. - Open the Submeter Exception Log sheet
- Log each flagged reading with the resident, lot, current reading, and trailing average
- Mark the likely cause: possible leak, possible meter fault, or vacancy
Done when The exception log reflects every flagged reading from this batch.
-
3
Slack - alert the billing team
slack.com How to Automate Slack
WebRun opens Slack to alert the billing team. - Post an alert to the billing channel listing this batch's exceptions before invoices generate
- Recommend holding the flagged accounts from this billing run until checked
- Link to the full exception log
Done when Your billing team has been alerted to every exception before bills go out.
How do I catch submeter reading errors before they become resident bills?
WebRun compares every submeter reading in a newly uploaded ManageAmerica batch against that resident's trailing usage average, flagging any reading that spikes, drops near zero, or reads negative. It logs each exception with a likely cause to a sheet and alerts your billing team in Slack before that batch generates invoices, so a bad reading never becomes a bad bill.
- Meter errors are caught before invoices generate instead of after residents complain
- Possible leaks get flagged with a likely cause instead of a bare number
- Billing team holds only the flagged accounts, not the whole batch
Built for manufactured housing billing teams · MHC utility administrators · mobile home park operators · community billing offices
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 change a resident's bill because of a flagged reading?
No. WebRun only flags the outlier and logs it. Your billing team decides whether to hold, re-read, or bill the account, and makes any change in ManageAmerica directly.
What counts as an exception?
By default, a reading more than 3 times the resident's trailing 6 month average, a drop to near zero, or a negative reading. These thresholds can be adjusted in your run settings.
Can a reading be a real spike and not a meter error?
Yes, which is why it is flagged for a human check rather than corrected automatically. A guest stay or a leak can look identical to a meter fault on paper.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.