Pickup requests
Request an extra or standing pickup for any site, choose a window and add a note for the driver.
An office manager who needs a certificate of destruction for an audit should not have to dig through an email from last spring. A customer app for document shredding companies lets clients book bin pickups, request a locked console and download proof of destruction from a phone.
A typical request starts with a phone call or an email. The office manager asks for a bin, the dispatcher adds the stop to a route sheet, and the driver collects the locked console on the scheduled day. The bin count goes on a paper ticket that gets scanned later, and certificates are produced in batches at the end of the month. Many clients only learn about a missed pickup when a bin overflows in a hallway.
The breaks are familiar. A console fills before its next pickup because nobody asked for an extra one. A certificate is needed in a hurry for an audit, but the batch has not been produced yet. The customer asks which bin held a set of records, and the answer sits on a paper ticket in a box at the depot.
A facilities manager at a dental practice opens the app from a link in a text message and sees the next scheduled pickup, the console's last fill level and the latest certificate. She opens a locked console request, picks the Thursday window and adds a note that the back-office console is full.
The dispatcher sees the request and the driver receives the stop on the route. That afternoon the pickup completes, and the app shows the collection time and a link to the signed pickup record. A certificate for the completed batch appears in the library once the depot processes it.
Two months later an auditor asks for proof covering a set of records. The facilities manager searches her pickup history, filters by site and date, and runs a certificate of destruction download for the matching batch. She forwards it to the auditor without calling the office.
Most shredders run a route or dispatch tool, keep customer accounts in an accounting package such as QuickBooks Online, and track bins with barcodes or paper tags. Some keep certificates in a spreadsheet. The customer app should read schedules, bin records and invoices from those sources, and write pickup requests back as new stops. The most useful check is whether the pickup history matches the bin list a client expects.
Bin barcodes are useful only when the scan reaches the record. Where the route tool has an export, the app can match each pickup to its bins and weights automatically. Where it does not, a daily file keeps the two aligned. We confirm the connections during the free scoping call.
Request an extra or standing pickup for any site, choose a window and add a note for the driver.
Each console shows its last collection and the fill level the driver recorded, so a full bin prompts a request early.
Every certificate of destruction sits in one library, searchable by site, date and bin, with a one-tap download.
A pickup history log shows each collection with its time, bin count and the signed record behind it.
Statements and invoices for each site sit beside the pickups they cover, with payment status shown.
The build needs a list of customer sites with addresses, access hours, key holder details and building rules. It also needs bin records for each console, bin pickup scheduling rules for each site and the price per bin or per pound. Existing certificates of destruction should be loaded so that past proof is searchable.
Access for the project matters too. Give the team a sandbox copy of the route tool, a sample of certificate templates and read access to a few past pickups. A short list of the questions customers ask most often will shape the first screens better than any template.
The starting point for a mobile build is $4,500, and the written scope sets the final figure. The biggest drivers are the number of route integrations, whether certificates are generated in the app or stored from the depot, and how many customer roles the app supports. Each one is priced as its own line. Dates depend on the number of route tools in use, which is why we ask about them first.
Dates follow the same drivers. A date comes out of the scoping call, once the route tool and the certificate process are clear, and it is confirmed in writing. Keep the first release to pickup requests, certificates and invoices, and move anything else into a second document.
Start with a small group of accounts that already ask for certificates often. The account manager walks them through a request and a certificate download on the phone, and those first customers show which screens cause a second call. Keep the list of pilot accounts short, so the account manager can follow up on each one.
Drivers need the app only where it touches their route. Keep the driver view to the stop list and the collection record, and leave customer messages out of it. Review the first month of requests with the depot, then decide which features to widen.
It can hold the proof customers ask for, including certificates, pickup records and the bin list for each site. It does not replace your compliance process. Legal and retention questions go to the client's own advisers, and the app keeps the records they ask for.
Yes, if past certificates are loaded into the library. We agree the import method during the scoping call, and older records become searchable by site and date once they are in. Records that are missing stay missing until they are found.
That depends on your route and your cut-off time. The app shows only windows the dispatcher can actually serve, so a customer never books a slot that will not happen. Urgent requests can still be routed to a person.
A mobile build starts at $4,500, and the final figure follows the written scope. Route connections, certificate handling and customer roles are priced separately, so you can decide which to include first.
Book a free scoping call and get the scope and price in writing for your route and records.