A customer sees a cockroach.
They take a photo.
Before the manager has finished making a phone call, the review is live.
“This place is infested.”
Maybe it is. Maybe it isn’t.
Right now, nobody knows.
But the photo is already out there.
That’s the uncomfortable part of a pest sighting in a restaurant. Customers can share what they see immediately. Figuring out what actually happened takes longer.
Was it one pest or evidence of something bigger? Did it originate inside the restaurant? Come through a door? Arrive with a delivery? Is there a sanitation issue, a structural condition or something that changed?
A photo can document what someone saw.
It can’t answer all of those questions.
Before the photo
The best time to think about a pest sighting isn’t after someone posts one.
It’s every day before that.
Restaurants don’t sit still.
The delivery entrance that stayed closed all winter starts getting propped open in July. A beverage station gets relocated. Construction starts next door. A drain that wasn’t a problem six months ago suddenly is.
Things change.
And sometimes the small changes are the ones that matter.
A worn door sweep doesn’t look like much until you think about what can fit underneath it. A gap around a utility line becomes part of the building because everyone has walked past it a thousand times. A door gets propped open because the kitchen is hot and people are busy.
Sometimes the answer isn’t another treatment.
It’s fixing the door.
The same is true with sanitation. “Keep the restaurant clean” sounds good, but restaurants already clean. The harder question is what routine cleaning isn’t reaching.
Under equipment. Around beverage stations. Inside drains. Near waste areas. Places where moisture and organic material can collect without being obvious.
Sprague has documented conditions where frequent washdowns contributed to water and organic material moving beneath damaged flooring.
From the surface, the area was being cleaned.
Underneath was a different story.
Moisture has a way of doing that. A small leak, damaged grout, condensation or a wet area around equipment can change conditions long before anyone thinks of it as a pest issue.
Then there’s everything coming into the building.
Food. Packaging. Deliveries. Vendors. Employee belongings.
Restaurants aren’t closed systems. Neither are the buildings around them. A restaurant in a shopping center may share walls, common areas and pest pressure with businesses it doesn’t control.
Good pest programs don’t happen because somebody sprayed something.
They happen because people notice these things. Doors get fixed. Moisture problems get addressed. Employees report what they see. Recommendations actually get completed.
And that last part matters more than it sounds.
A recommendation to repair a door sweep doesn’t keep anything out if the door sweep never gets repaired.
What someone sees isn’t always the whole story
A customer doesn’t need to identify the species, determine the source or establish whether there’s an infestation.
They report what they experienced.
A photo can make that observation even more useful.
But the observation tells you where someone saw the pest.
The investigation determines why it was there.
One of the easiest mistakes to make is assuming the problem started where the pest was seen.
Sometimes it did.
Sometimes that’s just where somebody happened to notice it.
The source may be somewhere else entirely.
Then somebody sees something anyway
Even a strong pest management program can’t make a restaurant invisible to every pest.
A delivery comes in. A door gets left open. Something changes next door.
It happens.
The difference is that now you’re not starting from zero.
You have service history. Monitoring. Employee observations. Previous recommendations. You know what’s normal for the facility and, hopefully, what isn’t.
That gives the investigation somewhere to start.
What is it?
Where did it actually start?
What changed?
And what do we do next?
Those questions sound simple. They usually lead somewhere more useful than immediately assuming the worst, or immediately assuming it’s nothing.
Treatment might be part of the answer.
So might a plumber.
Meanwhile, the review is still live
This is where things get uncomfortable.
While you’re figuring out what happened, the customer has already told their version of the story.
And sometimes the public story and the eventual findings line up.
Sometimes they don’t.
In one 2026 California case, a customer posted photos alleging a cockroach had been served in a dish. A county investigation that same day resulted in a temporary closure for a major vermin violation.
In another case, a customer photographed a cockroach on a sandwich. An inspection later found pest-related violations, but public reporting didn’t establish how that particular insect reached the sandwich.
Another widely shared video showed what was described as a cockroach moving across a restaurant table. It reportedly received more than 151,000 views. The reporting didn’t include an inspection result establishing an infestation.
That’s the tricky part.
The customer observation can still be real.
What it means has to be investigated.
Don’t argue with what someone saw
If someone reports a pest, take it seriously.
Get the photo if there is one. Find out where they saw it and when. What was happening nearby? Had something changed?
And get that information to your pest management team while it’s still fresh.
An employee saying, “Someone saw a bug last Tuesday somewhere near the kitchen,” isn’t nearly as useful a week later.
This is also where the people working in the restaurant become part of the pest program.
Your pest management professional isn’t there all day.
Your employees are.
The server who notices flies appearing around the same area every afternoon knows something you need to know. So does the employee who starts seeing activity near receiving after deliveries.
Those observations are clues.
Use them.
What you do next becomes part of the story
There’s a public side to this, too.
In one reported case, a customer initially said she would never return after finding a cockroach on her food.
The restaurant apologized, temporarily closed for cleaning, contacted the health authority and cooperated with an inspection.
Later, the customer said she appreciated how the restaurant handled it and softened her initial reaction.
That doesn’t mean there’s a perfect response that makes a bad review disappear.
There isn’t.
But arguing with a customer before you know what happened isn’t much of a strategy either.
You can acknowledge what someone experienced without pretending you already know what caused it.
Then go find out.
Write it down
Sprague trains our teams to document service so someone who wasn’t there can understand what happened.
That’s a pretty good test.
Could the general manager who wasn’t working that night understand what happened?
Could the district manager?
Could an inspector six weeks later?
What did you see? What did you find? What did you do? What still needs to happen?
“Pest control came out” isn’t much of an answer.
And neither is a service report full of information nobody outside the pest industry understands.
The record should tell the story.
Because after a pest sighting, there may already be another version of that story sitting online.
You can’t control the first post
You can’t stop a customer from taking a photo.
You can’t decide what they write underneath it.
And you may not have every answer before they hit Post.
But you have a lot of influence over what happens before that moment.
The door that gets repaired.
The drain somebody finally investigates.
The employee who reports something unusual instead of ignoring it.
The recommendation that actually gets completed.
And if somebody sees a pest anyway, all of that work matters again.
It helps you get from what someone saw to what actually happened.
Because once the review is live, there are two things that matter.
What the customer saw.
And what you do next.
Pest management for restaurants
There’s a lot that happens before a pest ever becomes something a customer notices. Learn how Sprague helps restaurants manage pest risk, from prevention and monitoring to investigation and follow-through.