AI suggests. You decide. It proves it.
Autopilot is the AI inside WasteOS that watches your ticket stream, learns which routine work is worth automating, and prices every proposal from your own history. Say yes once — and it keeps a ledger of promise next to measured outcome. Never an estimate dressed as a result.
One glance, every morning.
Pulse opens on four honest numbers: hours measurably given back, what needs your approval, what the AI is watching, and the top things still worth automating — each priced from your own history, not a benchmark.
3,127 completed tickets since March · 96% resolved the same way551.3 h/moBuild
940 completed tickets · uniform quick work165.0 h/moBuild
871 completed tickets · uniform quick work153.3 h/moBuild
It doesn’t guess. It mines.
Suggestions come from deterministic pattern mining over your completed tickets — routine volume, response-time outliers. The numbers are computed; the AI phrases the sentence, and the screen says which one wrote it.
See what it would have done. Then decide.
Before a flow touches anything, Autopilot replays it against your real recent history: which tickets it would have fired on, what each step would have changed, and what that was worth. A parked draft on the demonstration tenant priced out at 256 hours per 30 days — over 10,071 real events.
| Would have fired | Together with | Overlap | Verdict |
|---|---|---|---|
| 2,198 events | Bin delivery (live) | 2,198 shared | Collision |
| 2,198 events | Confirm extra pickup (live) | 0 shared | Clear |
| — | Escalate missed collection (draft) | different trigger | Not compared |
Ask in plain language. Get a backtest, not a vibe.
Type a what-if the way you’d say it in the morning meeting. Hero replays it against your real history and answers with what it would have done — fired-on counts, hours, collisions — then offers to arm it through the same reviewed builder path as everything else.
trigger matched · run started
executed · verified on the ticket afterwards
money step · run paused, waiting for a named human
resumed from the approved step · earlier steps never re-run
outcome re-read from the ticket — not assumed from the log
Live — with a leash.
Autopilot executes through the same domain code your team uses by hand, and treats “live” as a privilege it has to keep earning. AI suggests, you decide — and the system checks its own work.
The promise is frozen. So is the truth.
The moment a flow goes live, its promised saving is locked into the Impact Ledger. From then on the page shows the promise next to what was actually measured — and neither is ever edited. Misses show up as plainly as wins.
| Automation | Went live | Promised | Measured | Zero-touch |
|---|---|---|---|---|
| Auto-handle food-waste bags | Proven in simulation | 551.3 h/mo | 86.2 h | 1,034 |
| Confirm extra pickup | Manual override | no forecast on record | 12.4 h | 149 |
| Escalate missed collection | Proven in simulation | 31.0 h/mo | not measured yet | 0 |
| Rule | Runs today on | Convertibility | |
|---|---|---|---|
| Food waste bags → assign + close | Classic engine | Safe · 1:1 | Convert to draft |
| Extra collection → route + notify | Classic engine | Needs review | Preview |
| RFID block-until | Classic engine | Stays classic | honestly unsupported |
Your rules come along. Nothing fires twice.
Autopilot sits on top of the rules engine you already run — one product, one vocabulary. Every legacy rule is visible, with an honest label: converts faithfully, needs review, or stays on the classic engine.
What it can do today
Thirty-three registered actions — each executing through the same domain code your team uses by hand, each labelled honestly in the builder. If an action isn’t connected yet, the palette says “Not connected yet” instead of pretending.
Handle the ticket
Set status and priority, assign the right person or team, add the internal note, create the follow-up ticket, link related cases.
Talk to the citizen
Send the confirmation or the apology — templated or custom — through the same messaging pipeline your team already uses.
Fix it on the route
Re-dispatch a missed or extra emptying into the next available route, honouring your route schemes and areas.
Touch money — carefully
Waive a service fee on a grounded ticket. Always approval-gated, always audited, never an amount the AI computed itself.
For municipalities
The municipal waste-scheme world is the home turf: food-waste bags, extra collections, hazardous-waste boxes — the routine 80% handled the moment they arrive, the sensitive 20% paused for a named human. Fully bilingual: every screen ships in English and Danish.
For private operators
Same engine on your commercial estate: confirmation flows, missed-collection escalation, fee decisions with an approval trail your auditors will actually enjoy reading.
Honesty is the architecture, not the tagline.
Every number Autopilot shows traces to your own records: suggestions are priced from completed tickets, backtests replay real events, and the ledger only counts what it can prove. The AI phrases; the engine computes; the screen says which is which. Where the truth is “not measured yet” or “no history for this type”, that is exactly what it says.
Bring your noisiest ticket queue.
The one that eats your mornings. Watch Autopilot mine it, price what it finds, and show you — before anything goes live — exactly what it would have done last month.