The bin's been full since Tuesday. Dispatch found out Friday.

No. He points his phone camera at the sticker and a web page opens. No app store, no download, no account creation, no password. This is the single most important design decision in the product — the moment you require an app, adoption on a construction site drops to nearly zero, because crews turn over constantly and nobody is installing your software to do you a favour.

You issue each customer a PIN — and optionally a separate PIN per site. The supervisor enters it after scanning. It exists because a bin sits in public where anyone can walk up to it, and you do not want the general public, a competitor, or an irritated neighbour generating dispatch traffic against your containers. The PIN keeps the intake open enough that your customer's whole crew can use it, and closed enough that nobody else can.

The report page holds the submission and sends it the moment the phone reconnects, with the original timestamp and GPS coordinates preserved from when the report was actually made. On rural or below-grade sites this matters — the supervisor still reports it standing at the bin, and you still get the accurate time and location, just delivered a few minutes later when he walks back toward the trailer.

No, and we'd advise against it. If you're running Roll-Off Amigo, Bin Boss, Trash Flow, CurbWaste, HaulerHero or anything similar, keep it. Those products handle routing, billing, and driver workflow properly and we don't compete with any of it. NotifyMeBins solves one thing: getting an accurate service request out of a person who doesn't work for you and into your system quickly. It hands off via webhook, email, or SMS and then gets out of the way.

It's the phone's own location, captured at the moment of the scan, so it's typically accurate to within a few metres outdoors — which is the relevant comparison, because the alternative is a verbal description of which corner of a forty-acre site the bin is in. The critical detail is that the pin comes from someone standing at the container, not from a civic address that may be a quarter mile away or may not exist at all.

Three things. The PIN limits reporting to your customer's people. The optional photo lets your dispatcher see the fill level before committing a truck. And every request is attributed and logged, so a customer who habitually calls bins early is visible in the data rather than invisible in a phone log. You can also configure per-customer rate limits if a particular site gets enthusiastic.

They're weatherproof outdoor-grade vinyl with UV-stable ink, specified for the environment roll-off containers actually live in — freeze-thaw, road salt, sun, and being dragged onto a truck deck. That said, containers take genuine abuse, and replacement stickers are cheap and included in the plan. Most operators place two per bin on opposite ends so a damaged one isn't a problem.

The sticker travels with the container, so the ID is always right. The GPS tells you where it is now. If a bin turns up at a site you didn't put it at, you find out on the first scan rather than on the next inventory count. Reassigning a container to a different customer and PIN takes about ten seconds in the dashboard.

An afternoon for a typical fleet. You get a sheet of numbered stickers mapped to your existing bin numbers, you put them on as containers cycle through the yard, you issue PINs to your customers, and you put your dispatcher on the notification list. There's no hardware, no installation, no vehicle downtime, and no onboarding project. Most operators start with a subset of containers at one or two customers to see how it lands.

Yes. Any container can be configured with a custom destination URL, and scans route there instead of to the NotifyMe report flow. Some operators want their own branded portal, or already have a work-order form they'd rather people land on. To be clear about the boundary: we route the scan to your URL, and whatever lives at the other end is your system to build and support. We don't touch it.

Pricing is per container per year, with dashboard access included, and it's structured to be recovered by avoiding a small number of dead runs annually. We're finalizing pricing with our first operator partners right now and would rather quote you against your actual container count and site mix than post a number that doesn't fit your operation. Book a demo and we'll give you a real figure in the conversation.

Your requests, your containers, your customers, your data. We don't sell it, share it, or aggregate it into anything sold to anyone else. We hold ourselves to strong privacy commitments across every market we serve. You can export the full request history at any time in a standard format, and if you leave, you take it with you.

That's the fair question, and it's the one we're actively testing rather than asserting. The argument is that scanning is genuinely less effort than calling — no number to find, no hold, no explaining which bin — and that people do the lower-effort thing. The counter-argument is that habits are stubborn. Which is why our early rollouts are structured as pilots with real measurement: we track scan rates against call volume at the same customer, and if it doesn't work at your operation, you'll know inside a month rather than a year.