Wastehero
Part of WasteOS · request in, route out · you approve the slot

One-off jobs, captured, dispatched, and settled.

Bulky pickups, extra collections, and on-demand requests don’t have to live outside the system. Capture the job, slot it onto the next available route, and bill it, all on the same record as your recurring work.

See it on your own jobs See how a job gets matched Bring the request that never fits your rounds.
Thirteen seconds, request to invoice line: a job arrives, finds a route already going near it, and settles. Faithful recreation on demonstration data.
1Requestan odd job arrives
Bulky pickupvia portal
sofa + white goods · Parkvej 9
priced on the spotDKK 480
Phone, email, or portal · same queue
2Matchroutes already out today
V-01near capacitydetour 4.1 km
V-03has roomdetour 0.4 km
V-07has roomdetour 6.8 km
suggested · you approve 
3Doneon the plan, on the bill
slotted into today
customer got a time window
invoice line ready
V-03 · window 11:00 to 13:00
Measured, not promised: the platform’s own running totals
0
tickets handled on the platform
0
routes planned on the platform
0
crew hours run through the driver app
Platform totals across WasteHero operations, not projections. When your one-off jobs run on WasteHero, the numbers you see are your own.
The problem

Ad-hoc work is where the system breaks down

One-off and on-demand jobs arrive by phone, email, and portal, and they’re the requests most likely to be forgotten, done for free, or run as an inefficient special trip.

Requests arrive everywhere and stick nowhere

A bulky pickup booked over the phone lives on a sticky note, not on the plan, so it gets missed, or done twice.

Special trips wreck the day’s efficiency

Treated as one-offs, ad-hoc jobs become dedicated runs that ignore the routes already going near the address.

Extra work goes unbilled

On-demand collections are done as favours and never priced, so a real revenue stream quietly disappears into goodwill.

How WasteHero handles it

Capture it, route it, bill it

Turn every one-off request into a tracked, routed, and settled job on the same record as your rounds.

01
Request capture

Every request lands as a real job

Phone, email, or self-service requests become structured jobs with an address, a waste type, and a customer, so nothing lives on a sticky note or slips through the cracks.

Job queue · today
portalBulky pickup · Parkvej 9priced on the spot
phoneExtra lift · Harbour Road 41in the queue
emailGarden waste · Møllegade 3in the queue
02
Smart dispatch

Slot it onto a route that’s already going there

Ad-hoc jobs are dispatched onto the next suitable route instead of a dedicated special trip, so on-demand work rides along with the plan rather than fighting it.

Route N-4 · Thursday
08:10Nørrevang 12planned
11:20Harbour Road 41planned
11:40Parkvej 9 · ad hocsuggested · you approve
13:05Station Squareplanned
03
Settlement

Confirmed jobs become billed jobs

Once the driver confirms the collection, the job is priced and flows into billing like any other work, so on-demand service is a revenue stream, not a favour.

After the collection
Driver confirms the collectionfrom the cab
Job pricedfrom your price list
Invoice line createdready for billing
How it runs

From request to settled charge

The same four steps for every one-off job, however it arrives.

1

Capture the request

Log the address, waste type, and customer from any channel; the job enters the same queue as your planned work.

2

Slot it onto a route

Assign the job to the next suitable route rather than a dedicated trip, keeping the day efficient.

3

Collect and confirm

The driver sees the job in the cab and confirms the collection with any exceptions on the spot.

4

Price and settle

The confirmed job is priced and flows into billing, so the work is recorded and charged.

By design

What ad-hoc on WasteHero guarantees

No projected savings on this page. These are properties of how one-off work runs on the platform, and the outcome numbers that matter will be modelled on your own jobs in the demo.

0
Of captured requests land in one queue, whatever channel they arrived by
0
Record per job, from first request to invoice line
0
Re-keying: the confirmed job is priced and billed from the same record
Questions

Ad-hoc collection, answered

What operators ask us about on-demand work.

Where can requests come from? +
Phone, email, and a self-service portal all feed the same job queue, so however a request arrives it becomes a structured, trackable job rather than a note to remember.
Does an ad-hoc job mean a special trip? +
Not by default. Jobs are dispatched onto the next suitable route already serving the area, so on-demand work rides along with the plan instead of triggering a dedicated run.
How do we make sure ad-hoc work gets billed? +
A confirmed collection is priced and flows straight into billing like any other work, so on-demand jobs become a recorded, charged revenue stream instead of unbilled goodwill.
Can an ad-hoc job become a recurring one? +
Yes. When a one-off request turns into an ongoing need, it can be promoted into a recurring schedule or a contract without re-entering the customer’s details.
Can customers request collections themselves? +
A self-service channel lets customers and residents book on-demand collections directly, which cuts inbound calls and captures the job in a structured form from the start.

Stop running one-off jobs off the books.

Bring the on-demand requests that never quite fit your system. We’ll show how they’re captured, routed, and settled on WasteHero.

30 minutes · your own one-off jobs · no slides · no commitment.
Prefer email? hello@wastehero.io

Throw us your oddest job
Opens your email with everything pre-filled. Nothing is sent behind your back.
Ad-hoc collection · request in, settled out
30 minutes · your own one-off jobsBook a demo