Most people read a mystery shopping report for the answers. Did the agent greet the shopper warmly? Ask for contact information? Offer a tour? Those answers matter, and we collect them in every shop. But some of the most useful information in a report isn't an answer to any question on the form. It's something that didn't happen.
The pattern no question asks about
Here's a scenario we see. A client asks us to shop a specific employee. Our shopper calls repeatedly, at different times of day. Every time, the same leasing agent picks up, and it's not the target. When the shopper walks in, they have to ask for the employee by name.
Each individual call went fine. But taken together, the pattern tells a client something they'd want to know.
What else shows up in the gaps
That's one example. These are others that never appear as a checkbox but should get a client's attention:
- The employee isn't on site when scheduled to work solo. The shopper arrives during a shift the employee is supposed to be covering alone, and they aren't there.
- Voicemails for a specific employee go unreturned, or a different leasing agent returns them.
- The shopper is told the employee doesn't give tours. Or they're handed off to a different leasing agent when they arrive on site.
Each of these is a missed chance at hospitality, professionalism, and an effective sale. A prospect who gets bounced around before seeing a unit is a prospect who may not come back.
How to read a report for patterns
One odd moment in one shop report is usually just that. Everyone, including leasing agents, has bad days, has to leave work for a family emergency, or gets backed up on projects and lets someone else take the incoming phone call. A pattern is what makes it worth acting on. When you're reading a report, or a stack of them, look past the individual answers and ask:
- Does the same thing happen across attempts? If the same agent answers every call, or the shopper is handed off again and again, that's a pattern. A single transfer isn't.
- Does it repeat across several shops? The same gap showing up across multiple shops over time carries far more weight than one report.
- What did the shopper have to do to get what they came for? Having to ask for someone by name, call back, or ask twice is information, even if every box got checked.
- Who was missing? When a report is about a specific employee, notice how much of the story involves someone else.
This is also the part of a report that doesn’t necessarily fit in a score, which is why we don't think of the score as the whole story.
The gaps tell you what to look into. You only find them if someone is reading the whole story, not just the answers.
Why a real person has to catch it
A checklist records the answers to the questions it asks. A gap, by definition, isn't written anywhere on the page. Seeing it means reading a report against everything around it: who the shop was supposed to target, what the shopper had to do to reach that person, and what happened across every attempt.
That's why every MarketStat report is fully edited by a human. We have the option to use AI in our editing process, and we decline it every time. A real editor reads the report the way a client would want it read. When something is off, a pattern or an absence that no question was built to catch, they notice it and relay the concern to the client directly.
What to do once you spot gaps
Before drawing conclusions about an employee, it helps to work through the likely explanations first:
- Check the schedule and coverage. Was the employee actually scheduled when the shopper called or visited? Who was covering, and was that coverage planned?
- Listen to voicemail handling. Where do messages left for a specific person go, and who is checking them? Does anything get returned, and by whom?
- Review lead routing. Are calls and visitors being directed to a particular person, or away from one? A workflow can send leads to the wrong place without anyone intending it.
- Then look at the individual. Once the system-level explanations are ruled out, a conversation with the employee is better informed and a lot fairer.
A pattern isn't a verdict
This matters enough to say plainly: none of this automatically means an employee is the problem. A pattern is a reason to ask a question, not an answer to it. Often the cause is a coverage gap, a scheduling issue, a phone system that rings one person's calls through to someone else, or a handoff habit that formed on the team long ago.
That's the point of surfacing it. A client can only ask the right question once someone has noticed the pattern, and can only find the right answer by looking at the whole picture rather than jumping to conclusions. We would rather give a client something they can investigate than hand them a conclusion we can't support from the outside.
We've written before about what automation can and can't notice in a leasing office. The same idea applies to our own reports. Tools are useful, but the details that matter most often come from a person paying attention.
Read the story around the score
If your mystery shopping reports only get a glance at the score, it's worth reading the story around it. What's missing can tell you more than what's there, and we make sure someone is looking for it.