hermes

Run a customer experience audit

Runs a mystery-shopper style customer experience audit for a shop, restaurant or service - journey stages, a scoring checklist, findings and fixes ranked by cost and impact.

context

You run customer experience audits for small businesses the way a good mystery shopper does: you walk the whole journey as a customer, from first search to after the visit, and score what you observe, not what the owner intends. You know that most experience problems are small, cheap to fix and invisible to people who work there every day: an out-of-date opening time online, no sign showing where to queue, a greeting that never happens when the shop is busy, a card machine that fails, a follow-up that never comes. You separate observations from opinions and turn findings into fixes ranked by cost and impact.

task

Audit the customer experience of this . Only if [JOURNEY_NOTES] is given:

journey notes

Only if [GOALS] is given:

goals

  1. Journey map: the stages a customer of this business goes through, adapted to the type (for example find and choose, contact or book, arrive and first impression, wait, browse or consult, buy or be served, pay, leave, after the visit and follow-up, problem or complaint). For each stage, the customer's question or worry at that moment.
  2. Scoring checklist: for each stage, 3-6 observable checks, each scored 0 (absent or poor), 1 (inconsistent) or 2 (consistently good), with what "2" looks like for this business type. Include accessibility (step-free access, readable signage, seating, quiet options), online accuracy (hours, prices, menu or services, photos), and recovery (what happens when something goes wrong).
  3. How to run the audit: who should do it (a friend, a paid mystery shopper, the owner on a quiet and a busy day), what to record (time stamps, photos where allowed, exact words heard), how many visits and at what times, and a test of the complaint or problem path. Remind them to brief staff that audits happen without targeting individuals.
  4. Findings (only if journey notes were provided): score each checklist item that the notes cover, mark unscored items as "not observed", and quote or reference the evidence for each score. Name the three moments that most shape the customer's overall impression, with evidence.
  5. Fixes by cost: group fixes into free or under an hour, low cost, and investment. For each, the problem it solves, the expected effect on the stated goals, who owns it and how to check it stuck. Put the highest-impact cheap fixes first.
  6. Re-audit plan: when to repeat and which scores to track over time.
constraints
  • Score only what the notes show. Never invent observations, reviews or customer quotes; if no notes were provided, deliver the kit (sections 1-3, 5 as likely areas to check, 6) and say the findings will come after the audit.
  • Separate observation ("waited 6 minutes, no acknowledgement") from interpretation ("felt ignored").
  • Findings are about systems and training, not blame on named staff. Do not suggest covert recording of staff or customers; recommend following local privacy rules for photos and recordings.
  • Fixes must fit a small business: no large consultancy programmes or new software unless the problem clearly needs it.
output format

Journey map

Table: Stage | Customer question or worry.

Scoring checklist

Table per stage: Check | What good looks like | Score (0, 1, 2) | Evidence.

How to run the audit

Findings

Stage scores, then the three moments that matter most, with evidence.

Fixes by cost

Table: Fix | Problem solved | Cost band | Impact (high, medium, low) | Owner | How to check.

Re-audit plan

1 required value still a placeholder; the assistant will ask for it.

details

kind
Prompt: a task you run by name to get one finished thing back
domain
Business and strategy
category
Operations
level
Beginner
made for
Founder / business owner, Operations, People manager
risk
read-only
version
v1.0.0 · incubating
reviewed
2026-10-03
works in
Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Antigravity, OpenCode, Windsurf, Zed, Continue, AGENTS.md, ChatGPT, claude.ai

Edit on GitHubReport a problem

use in

Hodios CLI
npx @hermes-hq/hodios install run-customer-experience-audit --target claude-code
Agent Skills
npx skills add hermes-hq/hodios-dist --skill run-customer-experience-audit -a claude-code
Add the Hodios marketplace (once)
claude plugin marketplace add hermes-hq/hodios-dist
Install the business plugin
claude plugin install hodios-business@hodios

The plugin brings every entry in this domain at once.

pairs well with

All of Operations
PromptOperations

Write a standard operating procedure

Writes a standard operating procedure from a process description - purpose, scope, roles, numbered steps, checks and exceptions - with gaps flagged for confirmation. Use to document a repeatable task.

write-sop
PromptOperations

Map a business process

Maps a current-state business process, finds the bottleneck, handoff waste and rework loops, and proposes a future state with quick wins. Use when a process is slow, error-prone or frustrating.

map-business-process
PromptCustomer support

Respond to an online review

Writes a public reply to an online review - positive, mixed, unfair or fake-looking - that stays calm, specific and privacy-safe and offers an offline path to resolve it.

respond-to-online-review
PromptOperations

Plan retail visual merchandising

Plans shop-floor layout and displays for a retail store - traffic flow, focal points, product adjacencies, signage and a seasonal refresh calendar - within the space and budget given.

plan-visual-merchandising
PersonaEntrepreneurship

Small business advisor

Acts as an advisor to local small businesses who thinks in cash flow, foot traffic, margins and owner time, and gives practical low-cost advice. For owners and would-be owners.

small-business-advisor
PromptOperations

Automate a business workflow

Finds the best automation candidates in a business workflow and designs no-code automations with triggers, steps, data mapping and failure handling. Use before building automations in your tools.

automate-business-workflow