Customer Success · Built on Voice Of The Customer

What your customers said yesterday, in one email

Your clone collects the pain, requests, wins and promises from every channel into a daily digest.

Every day your clone reviews the last 24 hours of email, support cases, customer-linked issues, call transcripts and notes. It groups what it finds and emails a report with a quick summary, pain points, requests, wins, what you owe customers, trends and recommended actions.

What your clone does

Why it matters

Customer feedback is scattered across tools, so problems surface late and good news never gets shared. Your clone gathers it every morning.

Each day the clone combs:

SourceWhere it looks
EmailCustomer-facing threads (Gmail or Outlook)
CRM support itemsSalesforce Cases created or updated; HubSpot notes and engagements
LinearCustomer-driven issues
Calls and meetingsA Drive or OneDrive transcript folder, Meeting Archive, Call Archive
Knowledge baseNotes 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 helps

Customer SuccessLeadershipMarketingSupport

Customer Success, Support, Leadership (a daily pulse on customers) and Marketing (quotes-worthy wins, recurring themes).

How it runs

code
 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)

Set it up, step by step

  1. Give CLONE-INSTRUCTIONS.md to your clone: "Set this upShow me a plan first."
  2. Review the discovery table
  3. Answer the few placeholder questions
  4. Approve the plan: the clone attaches Voice Of The Customer via the platform
  5. Connect your sources (sign-in screens)More sources means a better report
  6. The clone creates the scheduled task with "Run Voice of the Customer"
  7. Run it once on demand and review

The README has the full walkthrough. The Clone Instructions tell your clone exactly what to do.

Before you start

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
1Voice Of The Customer (prebuilt skill)Report logic
2Google Gmail Operator or the Outlook email operatorRead customer threads; send the report
3Scheduled task (platform)Daily run

At least one source is needed; more is better (section 3).

Good to know

  • 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, answered

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).

Ready when you are. So is your clone.

Build your clone, paste in the Voice of the Customer instructions, and approve the plan it shows you.

Download