Voice of customer examples: what customers said and what changed

How to read these

These voice of customer examples are illustrative scenarios, not case studies of named companies. Each follows the same shape: what customers said, the pattern it revealed, the decision taken and how it was checked.

1. Retail: "nobody to help"

• Pattern: staff-availability complaints concentrated on weekend afternoons at mall stores.
• Decision: weekend floor staff, with tills covered by a separate rota.
• Check: weekend staff-availability complaints fell over two months at changed stores, not at others.

2. Jewellery: "charges not explained"

• Pattern: pricing-clarity complaints across many stores, rising after a pricing format change.
• Decision: an itemised price breakdown shown before billing.
• Check: pricing-clarity complaints fell network-wide over the following quarter.

3. Restaurant: "delivery always late on Fridays"

• Pattern: delivery-time complaints peaking on Friday and Saturday nights at three kitchens.
• Decision: delivery radius reduced at peak hours at those kitchens.
• Check: weekend lateness complaints fell; order volume held.

4. Hotel: "pool closed, nobody told us"

• Pattern: facility-closure complaints at several properties, all about surprises.
• Decision: closures included in booking confirmations and pre-arrival messages.
• Check: closure complaints fell even though closures continued.

5. App: "can't find the return option"

• Pattern: steady usability complaints about returns in app reviews.
• Decision: return option moved to the order summary.
• Check: return-usability complaints on the next version fell sharply.

What the examples share

• One comment is an anecdote; a pattern across stores, times or versions is evidence.
• The decision addressed a cause, not the individual customer.
• Several fixes were about communication, not policy.
• Each was checked against comparison stores, periods or versions.

Common questions

When the voice is small

Not every useful voice of customer example involves hundreds of comments. A dozen reviews that all describe the same unclear exchange rule, at one store, after one change, can be enough to act on, especially if the fix is cheap. The rule of thumb: the more expensive or risky the change, the more evidence you want; the cheaper and more reversible, the less.

A positive example

• Pattern: praise for proactive explanations concentrated at a handful of stores.
• Decision: those stores' practice turned into a short checklist for all stores.
• Check: positive share for explanations rose at the other stores over the next quarter.

VoC is as useful for spreading what works as for fixing what does not.

Doing this with Falcon

Falcon adds the review-based measures to your CX metrics: for every theme and store, the volume of mentions, negative share, its change month to month and the number of reviews behind it, from Google Maps reviews of your stores and Google Play reviews of your app. Every number opens the reviews that explain it, which survey scores alone cannot do.