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.
The problem
Customer feedback is scattered across inboxes, tickets, calls and issue trackers. Leaders hear about problems late and wins never get shared.
Voice of the Customer
Version 1.0.0 · Last updated 2026-10-22 · Difficulty: Beginner · Setup time: 15–30 minutes
🧩 Based on the prebuilt skill
Voice-of-the-customer. You attach it; you don't have to write it.
Every morning your clone reads the last 24 hours of customer signal across your tools and sends one report: what hurt, what they asked for, what they loved, and what you owe them.
1. Overview and value
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.
2. Who it's for
Customer Success, Support, Leadership (a daily pulse on customers) and Marketing (quotes-worthy wins, recurring themes).
3. 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)4. What the clone does (and never does)
Does: reads sources, reports each as "No new signal from [source]" (connected, nothing new) or "[source] not connected" (can't check), includes Wins & Love every time. Never: invents quotes, includes personal contact details by default (company names and themes only), emails customers, or changes any record.
5. Setup walkthrough
- Give CLONE-INSTRUCTIONS.md to your clone: "Set this up. Show 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.
6. Placeholders to decide
| Placeholder | Meaning | Example |
|---|---|---|
{REPORT_RECIPIENT} | Who gets the email (default: you) | you@yourcompany.com |
{RUN_TIME} | Schedule and time zone | Weekdays 8 AM America/New_York |
{TRANSCRIPT_FOLDER} | Drive/OneDrive folder for transcripts | Call Transcripts |
{TEAM_CHANNEL} | Optional Slack/Teams channel | #customer-voice |
7. What to expect
An email with subject Voice of the Customer: {DATE} each scheduled day. Quiet days say so per source. Wins are always included.
8. Customizing
Add the channel post wording to the scheduled prompt, narrow to certain accounts or segments, change the lookback, or ask for a weekly version.
9. 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.
10. FAQ
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).
11. Troubleshooting
| Symptom | Likely cause | Fix |
|---|---|---|
| No email | Schedule missing or email not connected | Ask the clone to list scheduled tasks |
| "[source] not connected" | Connection missing or expired | Sign in again |
| Transcripts missing | Folder not consistent or not shared | Use one folder, share it |
| No channel post | Not requested | Add wording to the scheduled prompt |
Version: 1.0.0 · Last updated: 2026-10-22 · Part of the Clone Use Case Library.
Paste these instructions into clone chat
# Clone Instructions: Voice of the Customer
> **For the clone.** Your user has handed you this file. Follow it step by step.
> **Version 1.0.0 · Last updated 2026-10-22**
>
> 🧩 **Based on the prebuilt skill `Voice-of-the-customer`.** You attach it; you don't have to write it.
---
## 1. Role and goal
Set up the prebuilt skill **Voice-of-the-customer** so that on schedule you send the requesting user a daily HTML report of the trailing 24 hours of customer signal. This is setup only.
## 2. Safety rules
1. Show a numbered plan and wait for an explicit "yes" before attaching or creating anything.
2. Never ask for or handle passwords, API keys or tokens. The user connects via sign-in screens.
3. Never email customers or prospects during setup. Only a test report to the user, after approval.
4. Read-only for CRM, Linear, Drive and knowledge bases.
5. Use exact catalog names; they can differ slightly between orgs.
## 3. Discovery
Use the `platform` tool and `describeOperator`. Report:
| Item | Status (✅⚠️❌❓) | Exact name in catalog | Notes |
|---|---|---|---|
| Voice-of-the-customer | | | |
| Email (GoogleGmailOperator or Outlook) | | | Required |
| CRM (SalesforceCaseOperator or HubspotEngagementOperator) | | | Optional |
| Linear_Operator | | | Optional |
| Drive/OneDrive (GoogleDriveCoreOperator or Microsoft_OneDrive) | | | Transcript folder |
| meeting_archive / call_archive | | | Optional |
| search_knowledge | | | Optional |
| Scheduled task (platform) | | | Required |
| Slack or Teams | | | Only if channel posts wanted |
## 4. Collect placeholders
1. `{REPORT_RECIPIENT}` (default: the requesting user)
2. `{RUN_TIME}` (for example weekdays 8 AM, with time zone)
3. `{TRANSCRIPT_FOLDER}` (name of the Drive/OneDrive folder, if any)
4. `{TEAM_CHANNEL}` (optional; leave blank for email only)
Confirm in a table before the plan.
## 5. What you can do yourself after approval
- Attach **Voice-of-the-customer** via `platform`.
- Create the scheduled task (section 7).
If you can't attach it: settings → Skills → find **Voice-of-the-customer** → Add → tell me "added".
## 6. What the user must do
1. Connect email: settings → Connections → Google or Microsoft 365 → sign in.
2. Connect any of Salesforce or HubSpot, Linear, Drive/OneDrive the same way.
3. Move or share call transcripts in `{TRANSCRIPT_FOLDER}` with the clone.
4. For a channel post, make sure the clone is in `{TEAM_CHANNEL}`.
## 7. Prebuilt skill: configure and run
**What Voice-of-the-customer does, step by step:**
1. Check each source separately for the trailing 24 hours: email (customer-facing threads), CRM (Salesforce Cases created/updated, or HubSpot notes/engagements), Linear (customer-driven issues), transcripts (folder, `meeting_archive`, `call_archive`), knowledge notes (`search_knowledge`).
2. Normalize each finding: account, theme, category, sentiment, severity, source, summary, evidence, owner.
3. Dedupe, then group by theme, then account.
4. Build sections: TL;DR, Pain & Friction, Requests & Needs, Wins & Love (always), What We Owe Them, Themes & Trends, Recommended Actions.
5. Report "No new signal from [source]" when connected but empty, and "[source] not connected" when it can't be read.
6. Never invent quotes. Company names and themes only; no personal contact details by default.
7. Retry a failed call once, then mark the source unavailable and report it.
8. Send an HTML email to the requesting user with subject `Voice of the Customer: {DATE}`. Post to a channel only if the user asks explicitly or the scheduled prompt says so.
**Scheduled task prompt (paste exactly):**
```
Run Voice of the Customer
```
Optional channel wording (only if the user wants it):
```
Run Voice of the Customer and also post the TL;DR and Recommended Actions to {TEAM_CHANNEL}.
```
Other optional lines: `Focus on accounts in {SEGMENT}.` or `Look back 72 hours.`
## 8. Test plan
| Check | ☐ |
|---|---|
| Email arrived with subject "Voice of the Customer: {DATE}" | ☐ |
| All seven sections present, including Wins & Love | ☐ |
| Empty sources say "No new signal"; unconnected say "not connected" | ☐ |
| No invented quotes or personal contact details | ☐ |
| No channel post unless requested | ☐ |
| Scheduled task shows the right time zone | ☐ |
## 9. Final status checklist
- ✅ Done by me: skill attached, schedule created, test run
- ⏳ Waiting on you: source sign-ins, transcript folder, channel approval
- 💡 Optional next steps: channel post, segment focus, weekly variant
Reminder: this differs from Customer Pulse (per-account activity) and Weekly Customer Updates Recap (what you sent).
Requirements
Requirements: Voice of the Customer
Version 1.0.0 · Last updated 2026-10-22 · Estimated setup time: 15–30 minutes
🧩 Based on the prebuilt skill
Voice-of-the-customer. You attach it; you don't have to write it.
1. Required skills / operators
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 | GoogleGmailOperator 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).
2. Connections and minimum permissions
| Connection | Minimum permission |
|---|---|
| Gmail / Outlook | Read + Send (send to the requesting user) |
| Salesforce / HubSpot | Read cases / notes and engagements |
| Linear | Read issues |
| Drive / OneDrive | View the transcript folder |
| Slack / Teams | Post (only if you use channel posts) |
You sign in yourself. The clone never needs your password.
3. Optional add-ons and mapping
| Add-on | Adds | Operator |
|---|---|---|
| CRM | Support case or note signal | SalesforceCaseOperator / HubspotEngagementOperator |
| Linear | Customer-driven issues | Linear_Operator |
| Transcripts | Call and meeting signal | GoogleDriveCoreOperator / Microsoft_OneDrive, meeting_archive, call_archive |
| Knowledge | Internal notes | search_knowledge |
| Channel | Team post | Slack or Teams |
| Concept | Salesforce | HubSpot |
|---|---|---|
| Support item | Case | Note / engagement (HubspotEngagementOperator) |
| Customer org | Account | Company |
4. Data prerequisites
- Customer emails flow through the connected mailbox
- Transcripts saved in one consistent folder (or captured by
meeting_archive/call_archive) - Linear issues that come from customers are labeled or mention the account
- Decide the recipient (default: the requesting user)
5. Roles and permissions
| Role | Needs |
|---|---|
| Requesting user | Can connect own email and approve the plan |
| Admin | Can connect shared CRM or Linear if needed |
6. Estimated setup time
| Task | Time |
|---|---|
| Discovery and placeholders | 5–10 min |
| Connect sources | 5–15 min |
| Attach skill, schedule, test | 5 min |
| Total | 15–30 min |
7. Pre-flight checklist
- Email connected
- Other sources connected as available
- Transcript folder identified
- Run time decided
8. You're ready when…
- ✅ Voice-of-the-customer is attached
- ✅ Sources are connected (or reported "not connected")
- ✅ A weekday scheduled task exists
- ✅ A test report arrived with a Wins & Love section
Was this use case helpful?
Thanks!