voice-of-customer

Featured

Builds the loop from what customers say to what gets changed — collecting feedback, distinguishing signal from noise, routing it to owners, and closing the loop back to the customer. Use this to set up a feedback program, design or interpret CSAT/NPS, decide what customer feedback deserves action, get product to act on recurring issues, or diagnose why feedback is collected but nothing changes.

AI & Automation 1,356 stars 209 forks Updated 1 weeks ago MIT

Install

View on GitHub

Quality Score: 91/100

Stars 20%
100
Recency 20%
90
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Voice of customer Most feedback programs collect diligently and change nothing. The collection is the easy half; the loop is the whole value. ## Sources, weighted honestly - **Support contacts** — the highest-volume and least *prompted* source, and the most under-used. People contacting you have a real problem nobody asked them about. But the sample is strongly self-selected: it excludes everyone who silently churned, worked around the problem, or would never contact you. Treat it as operational evidence to be normalized per active account and triangulated against churn and behavioral data — never as representative of the customer base. - **Churn and loss reasons** — the most valuable and most under-sampled. People leaving have no reason to be polite. - **Interviews** — depth, small n, best for understanding *why* something in the data is happening. - **Surveys** — breadth, and only meaningful once you know what to ask. - **Public reviews and forums** — biased toward extremes, useful for what people say when you are not in the room. Anything a customer built a workaround for outranks anything they merely said in a survey. ## On CSAT and NPS Both are useful as trends and misleading as targets. The moment a team is measured on a score, the score improves faster than the experience does — asking at the favorable moment, coaching for the rating, excluding difficult segments. Treat the score as a prompt for the free-text answer, which is where the information ...

Details

Author
cbrock84
Repository
cbrock84/headcount
Created
1 weeks ago
Last Updated
1 weeks ago
Language
Markdown
License
MIT

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

voice-of-customer

When the user wants to know what customers are actually telling them — turning NPS, CSAT, CES, support tickets, call transcripts, churn reasons, feature requests and sales-loss notes into ranked themes with ARR attached and an owner on each. Also use when the user mentions 'across surveys and tickets', 'nps feedback', 'into themes', 'what are customers telling us', 'VoC readout', 'our NPS came back', 'NPS dropped', 'analyse our survey results', 'top complaints', 'customer feedback summary', 'feature request themes', 'why are customers unhappy', 'churn reasons', 'exit interview', 'win/loss themes', or 'quarterly feedback review'. Use this whenever someone is holding customer feedback and asking what to do with it, even if they never say 'voice of customer' — including when they paste raw verbatims, survey exports, or a ticket dump. For one account's risk read, see churn-risk. For the exit-timeline reconstruction of a single loss, see churn-postmortem. For the customer-facing deck, see qbr-builder.

1 Updated 2 weeks ago
gaintrace
AI & Automation Listed

voice-of-customer

Voice of Customer program - multi-source signal collection, theming and prioritization, evidence-to-action routing, and product / CS / marketing feedback loop closure. Use when: voice of customer, VoC program, customer feedback, NPS / CSAT / CES, qualitative theming, feedback synthesis, product feedback loop, customer insight engine.

6 Updated 1 months ago
varunk130
AI & Automation Listed

customer-research

Mines reviews, interviews, support tickets and forum threads for voice-of-customer insight — verbatim pains, desires, objections and triggers, clustered into themes with JTBD statements and a message-market map. Use when the user says "analyze these reviews", "what do customers actually want", "synthesize this feedback", or before writing any positioning or copy.

15 Updated 2 days ago
alebgl77