Skip to main content
PortaPro
Routing and dispatch

Proof of service: the stamped photo, the completion text and the page the customer can open

The complaint is never 'you did a bad job'. It is 'you never came'. A photo with the time and location stamped on it, sent when the stop is done, ends that conversation before it starts.

November 4, 20263 min read

Ask a dispatcher what the worst phone call is and it is not a complaint about a dirty unit. It is a customer insisting nobody came, when the driver was there, did the work and drove off. There is no way to win that call without evidence, and the evidence has to exist before the call, created at the stop by the person who did it.

The photo, and what makes it proof

Drivers take photos. The question is what the photo can prove. A picture of a clean unit proves a clean unit existed at some point. A picture with the date, time and location written onto the image at the moment it was taken proves the driver stood there then. The stamp has to be on the pixels, not in a database field that a screenshot drops.

Be honest about what you do not know. If the phone had no GPS fix, the stamp should say "Location unavailable", not borrow a stale fix from ten minutes ago. If the driver picked the photo from the library instead of the camera, it should say "Added from photo library" and carry no location at all. The stamp is only evidence if it never claims more than it knows.

The notice, when the stop completes

Proof nobody sees is not proof. When the stop is completed, the customer who wants to hear about it should get an email or a text: serviced today at 10:42, here is the photo, here is the page. Two rules keep this from becoming spam. It goes to the service contact on the account, not the billing contact; the person who cares that the unit was cleaned is the site superintendent, not accounts payable. And a customer with twenty units gets one end-of-day summary, not twenty texts. Offer both, per customer, and let the office turn it on for the accounts that have asked.

A notice should never go out for a stop completed a week late by someone catching up in the office. If the completion is more than a day after the scheduled date, skip the notice; it would read as a lie.

The proof page

The link in the notice opens one page for one visit: the site, the driver's first name, the time, the photos, the checklist items and the signature if there was one. No login. Nothing about other customers, no prices, no account details. A superintendent forwards that link to his project manager and the conversation is over.

The same page should attach to the invoice. An invoice line that says "4 services" next to a link that shows four stamped visits is an invoice that gets paid without a question.

The service report is the long form

For septic and grease, the proof is a report: gallons pumped, tank condition, the disposal site, the manifest. The same photos and signature belong at the end of that PDF under a "Proof of service" heading, with every time printed in the company's time zone, not the server's. A report that says the pump-out finished at 19:14 UTC is technically true and will be read as a typo.

What this does to complaints

It does not eliminate them. It changes them from "you never came" to "the unit was dirty again by Friday", which is a conversation about frequency and pricing, not about trust. The complaints post covers the rest of that conversation. And on the days a stop genuinely was not done, the missed-stop report is how you know first.

Questions this post answers

Is a photo from a phone's camera roll proof?

Not on its own. A photo taken on site and stamped at that moment with the time and GPS location is. A photo picked from the library should say so and carry no location, because nothing can verify where it was taken.

Will customers get too many texts?

A customer with twenty units does not want twenty texts a day. Offer a daily summary per customer instead of a message per stop, and let them choose.

Should the proof page need a login?

No. It is one visit, linked from the notice, with nothing on it but that visit's facts. Making the customer log in to see it defeats the purpose.

More on routing and dispatch.

Every routing and dispatch post
How to reduce customer complaints in your portable toilet business

March 18, 2026 · 3 min read

Complaints in this business come in four kinds, and three of them are operational. What each one is really about, how to find the cause in your own records, and the changes that make the phone ring less.

Read the post
What to do about missed stops: the end-of-day report, rescheduling and when to auto-move

November 4, 2026 · 3 min read

A missed stop is not a driver problem until it is a dispatch problem that nobody saw. How to find out at five, not next Tuesday, and the one rule that makes automatic rescheduling safe.

Read the post
Give customers a portal and the phone stops ringing: what a portable sanitation portal should do

November 4, 2026 · 3 min read

Most calls to the office are a customer asking something they could look up: when is the next service, what do I owe, can I get another unit. A portal that answers those and takes the request is the cheapest hire you will make.

Read the post

See it on your own book.

Book a walkthrough with your own sites, units and billing cycle, or start a free trial and import your customer list tonight.

Start free trial

14-day free trial (card required, no charge today). Or a guided 30 to 60 day trial with no card.

Kygo, PortaPro's support assistant