← Voice of Customer (full guide)
Spoke · 5-block template · 7 min read
Voice of Customer template — free
Five copy-paste blocks: channel inventory, NPS/CSAT/CES tracker, weekly synthesis, action log, and loop-closure email. For Notion, Sheets, or whatever your team already uses.
Block 1: Channel inventory
List every channel where customer voice arrives — both passive and active. Most teams underestimate this: they remember surveys but forget support tickets, social mentions, sales call transcripts, churn reasons.
# VOC CHANNEL INVENTORY
Last reviewed: [YYYY-MM-DD]
Owner: [name]
| Channel | Type | Owner | Volume/week | Tagged? | Reviewed? |
|----------------------|--------------|-------|-------------|---------|-----------|
| NPS survey | Active | | | | |
| Support tickets | Passive | | | | |
| App store reviews | Passive | | | | |
| Reddit / X mentions | Passive | | | | |
| Sales call recordings| Passive | | | | |
| Churn survey | Active | | | | |
| User interviews | Active | | | | |
| Behavioral analytics | Passive | | | | |
## Channel hygiene rules
- Every channel has ONE owner (no shared accountability)
- Every channel has a tag taxonomy + review cadence
- Quarterly: prune channels nobody acts on
- New channel only added if existing channels can't capture the signal
Block 2: Metrics tracker
Best in Sheets/Excel. Track NPS, CSAT, CES over time. Look at trend, not absolute numbers — a falling CSAT is more important than a low one.
# VOC METRICS TRACKER
| Date | Metric | N (responses) | Score | Notes |
|-------|--------|---------------|-------|-------|
| Q1 24 | NPS | 142 | 32 | Promoters cited speed; detractors cited mobile UX |
| Q1 24 | CSAT | 480 tickets | 87% | Drop from 91% — investigate Q1 onboarding |
| Q1 24 | CES | 96 surveys | 5.2/7 | Slight improvement after onboarding redesign |
## Formulas
- NPS = % Promoters (9-10) − % Detractors (0-6)
=100*(COUNTIF(scores,">=9")/COUNT(scores) - COUNTIF(scores,"<=6")/COUNT(scores))
- CSAT = % rating 4 or 5 (out of 5)
=COUNTIF(ratings,">=4")/COUNT(ratings)*100
- CES = AVG of "How easy was it?" 1-7 score
=AVERAGE(ratings)
## What to watch
- Trend direction (week/month/quarter), not absolute number
- Gap between Promoters and Detractors widening = polarization
- CSAT < CES + 20 points = onboarding friction
- Sudden drops = investigate within 7 days, not "next quarter"
Block 3: Weekly synthesis
30-min weekly review. The output is decisions, not data. If you can\'t name 3 specific actions or non-actions after the review, the synthesis isn\'t working.
# WEEKLY VOC SYNTHESIS — Week of [date]
## Channels reviewed
☐ NPS responses (n=___)
☐ Support tickets (n=___)
☐ App store / G2 reviews (n=___)
☐ Social mentions (n=___)
☐ Customer interviews (n=___)
☐ Churn survey responses (n=___)
## Top 3 themes this week
1. [theme] — mentioned in [N] channels — quote: "..."
2. [theme] — mentioned in [N] channels — quote: "..."
3. [theme] — mentioned in [N] channels — quote: "..."
## What we're doing about it
- Theme 1 → Action: [specific] — Owner: [name] — Deadline: [date]
- Theme 2 → Already in roadmap (Q[X])
- Theme 3 → Conscious non-action — reason: [why]
## What changed from last week
- New theme that emerged: [...]
- Old theme that resolved: [...]
- Theme that's escalating: [...]
## Customers to follow up with personally
- [name @ company] — they raised [issue] — owner: [name]
Block 4: Action log
The most important block. Every piece of feedback that triggered an action gets one row. Without this, VoC is data collection without consequence.
# VOC ACTION LOG
| Date raised | Customer | Theme | Action | Owner | Deadline | Status | Date closed |
|-------------|----------|-------|--------|-------|----------|--------|-------------|
| 2026-04-12 | [name] | | | | | Open | |
## Status options
- Open: action accepted, not yet started
- In progress: actively being worked on
- Shipped: action completed
- Conscious non-action: explicitly decided not to do, reason logged
- Stalled: blocked, requires intervention
## Review cadence
- Weekly: every Open or In Progress action
- Monthly: every Stalled action — escalate or close
- Quarterly: every Conscious non-action — re-evaluate
## Stalled-action rule
If an action is stalled for 2+ weeks, owner must either:
1. Unblock it within 1 week
2. Reassign to someone who can
3. Move it to Conscious non-action with documented reason
"Stalled forever" is the failure mode that kills VoC programs.
Block 5: Loop-closure email
Sent to the customer who raised the issue when the action ships. This is what separates a VoC program customers respect from one they ignore.
Subject: You said it, we built it — [feature name]
Hi [name],
Back in [date], you mentioned [specific feedback they gave]. Quote
from your survey/email/interview:
> "[their words verbatim]"
We took that feedback seriously. Today we shipped [specific change]
that addresses what you raised:
- [change 1]
- [change 2]
You can see it in [where to find it / link].
If this hits the mark, would love to hear it. If it doesn't quite
solve what you were experiencing, even more important — reply here
and let me know what's still missing.
Thanks for taking the time to push us forward,
[your name]
---
WHY THIS WORKS:
- Verbatim quote shows you actually read their feedback
- "Today we shipped" is concrete, not "we're working on"
- Direct link to where the change appears (no hunting)
- Open invitation for follow-up — customers feel heard, not handled
- Personal sign-off (not "the [Company] Team") — it's a real person
Map your VoC starting point
Before filling Block 1 (channel inventory), you need to know which customer voice matters first. We built GoNoGo as the prep — a 30-min voice session that maps your customer hypothesis, runs synthetic personas, and tells you which segments are worth listening to before you spend time on tooling.
Map your VoC starting point free →30 min · No credit card
Frequently asked questions
Where should I use this template — Notion, Sheets, Confluence?+
The metrics tracker (Block 2) needs Sheets/Excel for formulas. The channel inventory + synthesis + action log work better in Notion (each row becomes a page with linked discussions). The loop-closure email pastes directly into Gmail/Outlook. Use whatever tool your team already lives in — VoC programs die when synthesis happens in a tool nobody opens.
How often should I update each block?+
Channel inventory (Block 1): once at setup, then quarterly review. Metrics tracker (Block 2): weekly. Synthesis (Block 3): every 2 weeks for active programs. Action log (Block 4): updated as actions move. Loop-closure email (Block 5): triggered when a customer-raised issue is shipped.
What's the most important block?+
Block 4 (action log). Most VoC programs collect feedback but never act on it — the action log is what separates a working program from a data graveyard. If your team can only adopt one block, adopt the action log: every piece of customer feedback gets an owner, a deadline, and a status.