All templates

Automated Conservice Submeter Offline Alerts

Every hour, WebRun opens Conservice, checks every submeter's last reported read time against its expected reporting interval, flags any meter that's gone quiet for more than a set number of hours, and posts the current offline list to Slack ranked by how long each has been silent, so a technician can be dispatched before the gap affects billing.

Deploy this workflow Browse all templates
Runs on WebRun · Strict Lockdown policy
Every hour WebRunorchestrates each step
1 Conservice check each submeter's last read
2 Slack alert the team to dispatch
In short

How do I catch offline submeters before they create a billing gap?

Every hour, WebRun checks each submeter's last reported read time in Conservice against its expected reporting interval and flags any meter silent for more than 24 hours. It posts the ranked offline list to Slack with how long each has been silent, so a technician can be dispatched before the gap turns into a missing charge on next cycle's bill.

  • Offline meters get caught within the hour instead of at billing close
  • Technicians get a ranked dispatch list instead of scanning every meter
  • Billing gaps get prevented before a missing read reaches the resident's bill

Built for multifamily maintenance teams · submetering operations · utility billing teams · property managers

Step by step

What does WebRun do on every run?

The exact actions WebRun takes, in order - in plain language, so you can adjust anything.

  1. WebRun signs in and gets to work

    Opens www.conservice.com in a real browser with your saved login - no setup, no API keys.

  2. 1
    Conservice - check each submeter's last read
    conservice.com
    WebRun in Conservice: check each submeter's last read
    WebRun opens Conservice to check each submeter's last read.
    • Open Conservice and pull the last reported read time for every submeter
    • Compare it against each meter's expected reporting interval
    • Flag any meter with no new read for more than 24 hours, and note how long it's been silent

    Done when Every submeter's last read time has been checked and any meter overdue is flagged with its offline duration.

  3. 2
    Slack - alert the team to dispatch
    slack.com
    WebRun in Slack: alert the team to dispatch
    WebRun opens Slack to alert the team to dispatch.
    • Post the current offline meter list to the maintenance channel
    • Put the longest offline meters first so the oldest gaps get dispatched first
    • Note which units are approaching the billing cutoff with no read on file

    Done when Maintenance has the current offline meter list in Slack, with the most urgent gaps at the top.

Run settings

How is each run configured?

Starting pageWhere Chrome opens at the start of each run
www.conservice.com
ScheduleRuns automatically on this cadence
Every hour
DeliveryHow each run's result reaches you
Offline meter list · Slack
OutputWhat each run produces - A ranked list of submeters that have stopped reporting reads, with how long each has been offline, posted each hour.
Text
Setup & safety

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.

Your credentials stay in your own private environment - WebRun never stores your passwords.
Strict Lockdown

Every action is checked against this policy before it runs.

Domains ALLOWLIST
Typed input ALLOW
Shell command BLOCK
File uploads BLOCK
Runs in a contained environment More on policies
Good to know

Questions, answered

Will it dispatch a technician automatically?

No. WebRun only flags and logs offline meters. Deciding who to send and when is a decision your maintenance team makes.

How long does a meter have to be silent before it's flagged?

More than 24 hours past its expected reporting interval by default. You can set this shorter for meters on a tighter reporting schedule.

Does it warn me before an offline meter causes a billing gap?

Yes. It notes which offline units are approaching the billing cutoff with no new read on file, so the team can prioritize those first.

Keep going

Related templates

Automated Conservice Billback Dispute Follow-Ups
When a resident disputes a utility billback charge, WebRun pulls the unit's meter read history and allocation math from Conservice, drafts a response in Gmail that walks through exactly how the charge was calculated, and leaves it unsent for your property manager to review before it goes to the resident.
Conservice›Gmail
Automated Conservice Cost Recovery Ratio Report
After each billing cycle closes, WebRun pulls total provider utility cost and total resident billback from Conservice for every property, calculates the cost recovery ratio for each, and posts a ranked Slack report so you can see which properties are under target before the next cycle.
Conservice›Google Sheets›Slack
Automated Conservice High Consumption Leak Alerts
Every morning, WebRun compares each occupied unit's latest submeter read in Conservice against its own trailing average, flags any unit running well above its normal consumption, and posts the list to Slack so maintenance can check for a leak before it shows up on next cycle's bill.
Conservice›Slack

Put this on autopilot.

Turn it on in minutes - or have our team set it up for you.

Deploy this workflow Talk to us