Voice-of-Customer Action Routing
Turn daily customer conversations into owned product, marketing, and enablement actions
- Difficulty
- Moderate
- Time to result
- ~days to results
- Steps
- 7
- Confidence
- 99%
Voice-of-Customer Action Routing ingests customer and prospect transcripts, along with relevant emails, and refreshes a structured dashboard every day. It first identifies how the company is showing up, which messages or capabilities resonate, and what customers care about. It then adds the operational layer often missing from voice-of-customer reporting: what should be done and who should do it. Themes can generate product recommendations, enablement changes, marketing stories, testimonial requests, or channel-specific amplification. Users can drill into a section and launch follow-up work from the same evidence. The method converts qualitative conversation data into a shared decision surface, ensuring insights do not remain trapped in individual calls or end as an informational summary with no accountable next step.
Origin
Nate Folin presented Perplexity's daily voice-of-customer dashboard as the agent workflow he would most strongly recommend to other RevOps teams.
Core principles
- 01Refresh customer intelligence continuously
- 02Measure both company performance and customer priorities
- 03Move beyond summarization to prescribed action
- 04Route each insight to the team able to act on it
- 05Make every theme traceable to source conversations
How to run it
- 1
Collect customer evidence
Ingest recent transcripts and emails from approved customer and prospect interactions.
Pro tip Retain source links and dates so findings can be traced.
Watch out Apply consent, access, retention, and sensitive-data rules before model processing.
- 2
Extract recurring signals
Identify customer enthusiasm, objections, use cases, unmet needs, and repeated themes across the evidence.
Pro tip Distinguish isolated comments from patterns appearing across multiple accounts.
Watch out High emotional intensity from one customer does not establish prevalence.
- 3
Assess company performance
Determine how the company, product, and sales motion are appearing to customers and prospects.
Pro tip Separate customer language from internal interpretation.
Watch out Do not rewrite criticism into a more flattering but less accurate theme.
- 4
Prescribe responses
Translate each material theme into a concrete recommendation rather than merely reporting it.
Pro tip State the expected customer or business effect of each action.
Watch out Generic recommendations such as improve messaging are not operational.
- 5
Route ownership
Assign each action to the relevant product, enablement, marketing, sales, or RevOps owner.
Pro tip Give cross-functional findings one directly accountable owner.
Watch out Routing the same item to everyone often means nobody acts.
- 6
Launch follow-up work
Use dashboard sections as starting points for testimonials, customer stories, product investigations, or training updates.
Pro tip Include supporting quotes when requesting action from another team.
Watch out Verify permission before using customer statements publicly.
- 7
Refresh and track
Update the dashboard daily and monitor whether recommendations are accepted, completed, or disproven.
Pro tip Compare themes over time to identify acceleration or decline.
Watch out A continuously refreshed dashboard can become passive news unless action status is visible.
In the wild
The dashboard detects that several legal customers describe a valuable new efficiency use case. RevOps drills into the supporting calls, routes the opportunity to marketing, and proposes customer stories, testimonials, and LinkedIn amplification.
→ An emerging customer-discovered use case becomes evidence-backed marketing work.
Daily transcripts reveal what customers love and what they struggle with. The dashboard sends product implications to the product team and messaging gaps to enablement, each with supporting themes.
→ Customer evidence produces owned improvements instead of remaining an undifferentiated summary.
Common mistakes
Stopping at summarization
A digest of themes creates awareness but not the accountability required for improvement.
Losing source traceability
Teams cannot validate or contextualize a theme when it is detached from the underlying conversations.
Publishing without permission
A compelling customer quote or use case still requires appropriate authorization before external use.
Is it for you?
Best for
Organizations with frequent calls and emails that need a shared, current view of customer needs and emerging use cases.
Not ideal for
It is unreliable when conversation coverage is sparse, biased, or collected without appropriate privacy controls.
From the transcript
“what should we do about it?”
“And then what should our product team do about it? And then what should our enablement team do about it?”
“not only are we extracting things and kind of reading the news of what's happening and keeping a pulse, but we're suggesting things that I…”
From the episode
How 1 Human + AI Replaced a 15-Person RevOps Team