Voice of the Customer
A daily digest of what customers said across email, support cases, Linear, calls and notes: pain, requests, wins and what you owe them.
A prebuilt skill combs the trailing 24 hours of customer signal from email, CRM support cases (Salesforce Cases or HubSpot notes), customer-driven Linear issues, call and meeting transcripts and knowledge base notes. It normalizes, dedupes and groups findings, then emails an HTML report with TL;DR, Pain & Friction, Requests & Needs, Wins & Love, What We Owe Them, Themes & Trends and Recommended Actions.
At a glance
- Difficulty
- Beginner
- Setup time
- 15–30 min
- Built for
- Customer Success, Leadership, Marketing, Support
Version 1.0.0 · updated 2026-10-22
Overview
Customer feedback is scattered across inboxes, tickets, calls and issue trackers. Leaders hear about problems late and wins never get shared.
Each day the clone combs:
| Source | Where it looks |
|---|---|
| Customer-facing threads (Gmail or Outlook) | |
| CRM support items | Salesforce Cases created or updated; HubSpot notes and engagements |
| Linear | Customer-driven issues |
| Calls and meetings | A Drive or OneDrive transcript folder, Meeting Archive, Call Archive |
| Knowledge base | Notes via Search Knowledge |
It normalizes every finding (account, theme, category, sentiment, severity, source, summary, evidence, owner), removes duplicates, and groups by theme, then account.
Report sections: TL;DR · Pain & Friction · Requests & Needs · Wins & Love (always included) · What We Owe Them · Themes & Trends · Recommended Actions.
Who it’s for
Customer Success, Support, Leadership (a daily pulse on customers) and Marketing (quotes-worthy wins, recurring themes).
How it works
Weekdays 8 AM ("Run Voice of the Customer")
│
▼
Email · CRM cases/notes · Linear · transcripts · knowledge notes
│ (trailing 24 hours; each source checked separately)
▼
Normalize ► Dedupe ► Group by theme, then account
│
▼
HTML email to the requesting user
(channel post ONLY if asked or configured in the scheduled prompt)Setup, step by step
- Give CLONE-INSTRUCTIONS.md to your clone: "Set this upShow me a plan first."
- Review the discovery table
- Answer the few placeholder questions
- Approve the plan: the clone attaches Voice Of The Customer via the platform
- Connect your sources (sign-in screens)More sources means a better report
- The clone creates the scheduled task with "Run Voice of the Customer"
- Run it once on demand and review
The full walkthrough is in the README. The Clone Instructions file tells your clone exactly what to do.
What you’ll need
Skill names can differ slightly between orgs. Confirm the exact names in your skill catalog before saving the skill.
| # | Skill / operator (exact name) | Used for |
|---|---|---|
| 1 | Voice Of The Customer (prebuilt skill) | Report logic |
| 2 | Google Gmail Operator or the Outlook email operator | Read customer threads; send the report |
| 3 | Scheduled task (platform) | Daily run |
At least one source is needed; more is better (section 3).
Known gotchas
- Connect as many sources as possible. Unconnected sources are reported, but gaps limit insight.
- Keep transcripts in one consistent folder.
- Different tools: this is not Customer Pulse (per-account activity) or Weekly Customer Updates Recap (what you sent).
- Channel posts are opt-in.
Questions
Who gets the email?
The requesting user by default.
Does it need a CRM?
No, but cases and notes add a lot.
Does it include contact names?
Not by default.
Will it make up quotes?
No. Evidence is taken from sources only.
HubSpot?
Supported via notes and engagements (no ticket operator).