Automated Waste Overage and Contamination Charge Alerts
Every morning, WebRun opens Routeware and AMCS to find any stops flagged for overage weight or contamination from the previous day's routes, logs each incident to a Google Sheet with the account and details, and posts an alert to your billing team's Slack channel so charges can be verified before the next invoice cycle.
How can I automatically flag overage and contamination charges before invoicing waste service customers?
WebRun checks Routeware and AMCS every morning for overage weight and contamination flags from the previous day's routes, logs every incident to Google Sheets with account details, and posts a billing team alert in Slack. Charges are reviewed by your team before reaching any customer invoice.
- Every overage and contamination flag reviewed before it reaches a customer invoice
- Incident history logged in Google Sheets for compliance and trend analysis
- Repeat contamination offenders identifiable from the running account log
Built for waste hauling billing teams · operations managers · recycling compliance teams · commercial waste contractors
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.routeware.comin a real browser with your saved login - no setup, no API keys. -
1
Routeware - find overage and contamination flags from yesterday
routeware.com
WebRun opens Routeware to find overage and contamination flags from yesterday. - Open Routeware and navigate to the route exception or service note report for yesterday
- Filter to stops with overage weight, contamination, or similar exception flags
- Capture the customer name, service address, route, exception type, and driver note for each flagged stop
Done when Every overage or contamination flag from yesterday's routes is captured from Routeware.
-
2
AMCS - check asset-level exception notes
amcsgroup.com
WebRun opens AMCS to check asset-level exception notes. - Open AMCS and check for container-level or service-level exception notes from the same period
- Look for weight overages, rejected loads, or contamination rejections logged against specific containers or accounts
- Merge any additional flags with the Routeware list, deduplicating by account and date
Done when All overage and contamination exceptions from both systems are combined into one list.
-
3
Google Sheets - log incidents with account and detail
google.com
WebRun opens Google Sheets to log incidents with account and detail. - Open the overage and contamination incidents Google Sheet
- Append each flagged incident with the date, customer, address, route, exception type, and source system
- Update the summary count of incidents flagged this week and this month
Done when All incidents are logged in Google Sheets with the full incident detail.
-
4
Slack - alert billing team for review
slack.com
WebRun opens Slack to alert billing team for review. - Post an overage and contamination alert to the billing team channel in Slack
- List each incident with the customer, address, and exception type
- Note the total count flagged since last Monday and link to the Google Sheet for the full log
Done when Billing team has a full list of yesterday's overage and contamination flags 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
Does this automatically add overage charges to a customer invoice?
No. WebRun flags and logs the incidents for your billing team to review. Charges are only added to invoices after your team verifies each flag. Nothing is billed without human approval.
Can it track recurring contamination offenders across multiple incidents?
Yes. Because every incident is logged to the same Google Sheet with the customer and address, your team can spot repeat offenders by reviewing the account history in the Sheet.
What if a flag was recorded in error by the driver?
All flags are surfaced for review, not billed automatically. Your billing team reviews each incident in Slack and the Google Sheet before any charge is applied, so errors can be removed.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.