Mystery Shopping Survey Template
Deploy this mystery shopping survey to capture consistent, comparable observations across locations and channels. Use pass/fail compliance checks plus 1-5 ratings to produce coaching-ready scorecards, spot critical fails fast, and benchmark trends over time.
Trusted by 5000+ Brands
Mystery shopping questions to audit the full customer journey (with channel branching)
"Which visit scenario did you complete today?"
Why it matters: Use this section to score the same journey steps the same way in every location, then branch only where the channel changes what your shopper can observe.
- Set this first: Scenario (choose 2-4 standard scenarios)
- Set this first: Channel (in-store vs phone vs curbside)
- Set this first: Scoring rules (critical Pass/Fail + 1-5 anchors)
When to use: Include in every run. Keep the scenario list stable so your program stays apples-to-apples over time (consistency is a common issue in mystery shop scoring; see Finn and Kayande's psychometric assessment at Unmasking a phantom: A psychometric assessment of mystery shopping).
Next step in the template: Add 2-4 scenario options (ex: "First-time buyer," "Return/exchange," "Ask for a recommendation," "Order pickup") and make this question required.
"Which channel did you use for this shop?"
Why it matters: Channel branching keeps your core audit consistent while letting you ask only what the shopper can actually see/hear in that channel.
When to use: Use for mixed programs (stores + phone + curbside). Turn on branching so phone shops skip "store cleanliness" and store shops skip "hold time."
"What time did you arrive (or start the call)?"
Why it matters: Timestamped shops let you compare weekday vs weekend and peak vs off-peak without guessing.
When to use: Include in every run. Use the time field to validate you hit your timing windows.
"Within your standard greeting window (e.g., 30 seconds), did any employee acknowledge you (eye contact, greeting, or offer of help)?"
Why it matters: This forces an observable fact (seen/heard) instead of an interpretation like "they seemed attentive."
When to use: Use as a core Pass/Fail service standard. Set the time window in your rubric (many teams start with 30 seconds) and keep it fixed across locations; adjust only after you baseline results.
"What exactly did the employee say when they greeted you? (Write the closest wording you can remember.)"
Why it matters: Verbatim snippets help you coach to a script without relying on a shopper's opinion.
When to use: Add after any greeting/compliance item. Keep wording simple and specific so shoppers answer consistently (see question wording guidance in Internet, Phone, Mail, and Mixed-Mode Surveys: The Tailored Design Method).
"Did the employee ask at least one question to understand your need (size, use case, budget, timeline)?"
Why it matters: Needs discovery is a behavior you can observe and coach. It also explains why a recommendation did or did not happen.
When to use: Use in retail, banking, telecom, pharmacy, and any consultative sale. Keep it in the core set for comparability.
"Rate the employee's product/service knowledge."
Why it matters: A 1-5 rating captures quality when Pass/Fail feels too blunt, but you still need clear anchors to avoid score drift.
When to use: Use for coaching and training priorities. Add 1/3/5 anchors in the question text (ex: 1 = gave incorrect info, 3 = answered basics, 5 = explained options and confirmed fit).
"How long did you wait before service began?"
Why it matters: Time-to-service is a measurable operational constraint. It often drives ratings down even when staff behavior is strong.
When to use: Use for queues, host stands, curbside handoffs, and phone hold time (with channel branching). Capture minutes/seconds, not "long/short."
"Was pricing (or key fees) clearly communicated before you agreed to purchase?"
Why it matters: This is a common trust breaker. It also maps cleanly to a non-negotiable compliance step in many industries.
When to use: Use as Pass/Fail when policy requires disclosure. If not applicable, allow N/A but require a short note.
"During checkout, did the employee offer any relevant add-on (warranty, accessory, side, loyalty sign-up) without being pushy?"
Why it matters: This separates "asked" (behavior) from "quality" (rating). You can coach to the behavior first, then improve delivery.
When to use: Use for standardized sales steps. Pair with a 1-5 rating on professionalism if you want quality scoring.
"Before you left (or the call ended), did the employee thank you and invite you to return?"
Why it matters: Closings are easy to standardize and coach. They also provide a consistent end-of-journey checkpoint across scenarios.
When to use: Keep in the core set across all store formats (mall vs standalone) so your trend line stays stable.
"Optional module: If you used the restroom/fitting room, was it clean and stocked?"
Why it matters: Optional modules keep your audit-ready checklist available without bloating every shop. You get depth when it matters and comparability when it doesn't.
When to use: Turn on only for formats where the facility exists or when you run a targeted cleanliness sprint.
Next step in the template: Keep a stable core (arrival, staff interaction, checkout, closing), then add optional modules (restrooms, fitting rooms, issue handling) as separate, clearly labeled sections so your location benchmarks stay comparable.
How to run a mystery shopping program with consistent, comparable results
- Lock your visit scenarios and timing windows
Use this section to make your shops repeatable so location-to-location differences reflect operations, not random visit conditions.
- Set this first: Scenario (2-4 standard scenarios)
- Set this first: Channel (in-store/phone/curbside)
- Set this first: Scoring rules (Pass/Fail + 1-5 anchors)
Copy-paste shopper preface: "Complete this survey immediately after the visit. Write what you saw/heard (quotes, counts, timestamps). If you make an assumption, label it as an assumption."
Next step in the template: Add a required "scenario" question and a required "arrival/call time" field so you can enforce timing windows.
- Build a simple rotation plan (and stick to it)
Choose a cadence you can sustain. For many multi-location teams, start monthly per location, then add targeted retests after fixes.
Define a basic sampling plan: rotate weekday/weekend and opening/peak/close across the month, and rotate shoppers across locations to reduce recognition risk.
- Freeze the rubric before you field
Set this once: define what counts as a critical fail, what counts as N/A, and what evidence is required for a fail (example: quote + timestamp).
Coach shoppers to separate observation from opinion to reduce response bias. Tell them to avoid labels like "rude" and instead record what happened (ex: "Employee sighed and said, 'I can't help with that'").
- Brief shoppers with clear do/don't guardrails
- Do: use role-based notes ("cashier," "shift lead") instead of employee names unless your policy allows names.
- Do not: record audio/video without consent. Follow local laws and your internal policy.
- Do not: collect customer faces, payment details, or other sensitive data; follow your security and privacy policy.
If you work with an agency, document these rules as part of your program governance. ISO's service requirements for market research operations provide a useful baseline for documentation and quality control (see ISO 20252:2019 vocabulary and service requirements).
- Schedule retests using the same scenario
When a location fixes an issue, retest with the same scenario and timing window so you can see if behavior changed, not just conditions.
Next step in the template: Add a "retest?" flag and a "previous shop ID" field so your dashboard can pair the before/after results.
Scoring options: compliance checks vs experience ratings vs weighted scorecard
| Scoring layer | What you score (examples) | When to use it | Set it up so scores stay comparable |
|---|---|---|---|
| Start here (set-up checklist) | Outcome: Use this section to score every location the same way, even when you run multiple channels. |
| Copy-paste prompt: "If a question is N/A, choose N/A and write one sentence explaining why." Next step in the template: Add an N/A option only where it is truly possible. |
| A) Pass/Fail compliance | ID checked when required; safety steps followed; policy disclosure made; greeting within 30 seconds. | Use for non-negotiables where a miss requires action, not debate. | Define a critical fail list (ex: any safety/legal miss) and decide if one critical fail caps the overall score. Require a short evidence note (quote, count, timestamp). |
| B) 1-5 experience ratings | Friendliness; professionalism; product knowledge; problem handling. | Use when quality matters and you need a coaching gradient (not just Pass/Fail). | Use a Likert scale with explicit anchors in the question text. Do this: define 1/3/5 for each rating (to prevent score inflation and "everyone gets a 4"). |
| C) Weighted composite score | One executive rollup score across sections (example weights: Arrival 15%, Staff 40%, Process 25%, Environment 20%). | Use when leaders need a single benchmark plus drill-down section scores. | Lock weights for a full quarter (or longer) so trends stay meaningful. Keep the same question set behind each section score. Research shows mystery shop scores can relate to outcomes, but results depend on instrument quality and consistent implementation (see Do Mystery Shoppers Really Predict Customer Satisfaction and Sales Performance?). |
| N/A rule (applies to all layers) | Not observed because the scenario did not trigger it (ex: no line, so wait time is N/A). | Use to avoid penalizing a location for a step that did not occur. | Allow N/A only when the shopper could not reasonably observe the step. Require a one-sentence reason so you can audit misuse. |
Next step in the template: Decide which layer is your primary KPI (compliance %, section ratings, or composite), then align your dashboard to show that metric plus the top 3 misses that drive it down.
Turn mystery shop responses into coaching, retests, and operational accountability
- Build a scorecard that a manager can act on in 5 minutes: Use this section to turn raw answers into a repeatable coaching loop (score, coach, retest).
- Set this first: Scenario (so retests match)
- Set this first: Channel (so benchmarks compare like-for-like)
- Set this first: Scoring rules (critical Pass/Fail + 1-5 anchors)
Copy-paste manager prompt: "Pick the top 3 misses, assign an owner and due date, and schedule a retest using the same scenario."Next step in the template: Add fields for "owner" and "due date" (even if you store them outside the survey) so every shop produces an action list. - Report three headline metrics every time: Overall score, compliance % (with critical fails highlighted), and section scores (Arrival, Environment, Staff, Process, Checkout). Keep the section names stable so leaders can compare month over month.
- Cut results in ways that drive fixes: Compare location vs region, weekday vs weekend, time-of-day, and scenario type. Then pick one cut to prioritize this week (example: "weekend peak checkout compliance").
- Coach to the exact question that failed: Use the evidence note (quote/count/timestamp) to keep feedback specific. Audit-and-feedback paired with coaching can improve service behaviors when feedback is specific and repeatable (see Mystery shopping and coaching as a form of audit and feedback).
- Retest with the same conditions: Schedule the retest shop using the same scenario, channel, and timing window. Track "before" vs "after" as a pair, not as unrelated single shops.
- Keep monitoring lightweight but continuous: Publish a simple monthly summary, then use the same core measures for trending. ISO's guidance on monitoring customer satisfaction reinforces the value of consistent measurement and review cycles (see ISO 10004:2018 guidelines for monitoring and measuring).
Next step in the template: Create a "critical fails" tag and a "top 3 coaching priorities" section in your report view so every shop produces the same action format.
Frequently Asked Questions
How many mystery shops do I need per location to trust the results?
Set a consistent cadence first (often monthly per location), then increase frequency for high-variance locations, new managers, or after training. Rotate timing windows (weekday/weekend; opening/peak/close) and keep scenarios consistent so you reduce noise. Avoid strong conclusions from a single shop unless it is a critical fail.
Should mystery shopping be anonymous or confidential?
Keep shoppers anonymous to staff during the visit so behavior stays natural. Keep results confidential inside your company based on role, and write notes using role labels ("cashier," "shift lead") instead of employee names unless your policy explicitly allows names. Do not record audio/video without consent, and follow local laws and your internal rules.
How do I keep scores comparable across stores, regions, and time?
Lock the rubric before you field: the same scenario definitions, scoring anchors, critical-fail rules, and timing windows for every location. Use a stable core question set for every shop, and add optional modules (restrooms, fitting rooms, issue handling) as separate sections so they do not change the main trend line.
Can employees or managers do the mystery shops instead of a third party?
Yes, and it can reduce cost, but it increases the risk of bias and recognition. If you use internal shoppers, rotate auditors, limit repeat visits to the same site, and rely on observable prompts (quotes, counts, timestamps) so scoring stays consistent.
Can I ask shoppers to upload photos or receipts as evidence?
You can add an optional receipt reference field or photo upload when your policy and local law allow it, especially for physical conditions (signage, displays, cleanliness). Keep evidence narrowly scoped: avoid customer faces, payment details, and employee personal data, and follow your security and privacy policy. If evidence is not essential, make it optional so you do not slow down completion.
How do I connect mystery shopping scores to business outcomes?
Track correlations and trends rather than assuming causation. Compare recurring standards failures with changes in complaints/returns, conversion proxies, and likelihood-to-return items in your shop survey, then validate improvements with retests after coaching. Use repeated measures (same scenarios over time) so you can see whether fixes move the score in the expected direction.
Related Survey Templates
FREE TO START -- NO CREDIT CARD REQUIRED