Customer Pulse: Cross-Account Activity Briefing
One briefing on what happened across all your customers and prospects, with sentiment, open asks, risks and next steps.
Your clone reviews a window (default past 24 hours, or "past 7 days", "since Monday") of email threads, meetings and transcripts, Salesforce or HubSpot changes, customer-linked Linear issues and knowledge notes. For each account it reports what happened, sentiment, open asks, deal movement, risks and a recommended next step, then adds a cross-account summary with the top 3 actions. Delivered as an HTML email, optionally to Slack or Teams.
At a glance
- Difficulty
- Beginner
- Setup time
- 20–40 min
- Built for
- Leadership, Customer Success, Sales, RevOps
Version 1.0.0 · updated 2026-10-22
Overview
Customer activity is spread across inboxes, meetings, CRM and issue tracker, so risks and momentum are noticed late.
Customer activity is scattered across email threads, meetings, CRM changes and Linear issues. Nobody reads all of it, so risks and momentum get noticed late.
Customer Pulse looks at a window (default past 24 hours, or what you ask for, like "past 7 days" or "since Monday") and builds a briefing.
Per account:
- what happened (emails, meetings, CRM changes, issues),
- sentiment,
- open asks and what we owe,
- deal movement,
- risks,
- a recommended next step.
Then a cross-account summary: accounts needing attention, momentum list, at-risk list, and the top 3 actions.
Who it’s for
- Leadership wanting a daily or weekly read on customers.
- Customer Success managers covering many accounts.
- Sales reps and managers tracking deals and prospects.
- Rev Ops teams checking CRM activity against what's really happening.
How it works
"Run Customer Pulse for the past 24 hours" (or scheduled)
│
▼
┌─────────────────────────────────────────────────────────┐
│ Customer-Pulse │
│ 1. Set the window ({WINDOW}) and filters │
│ 2. Collect, per source (fail-closed status): │
│ Email · Calendar + meeting_archive + call_archive │
│ · CRM changes · Linear · knowledge notes │
│ 3. Match activity to accounts (by domain / CRM record) │
│ 4. Per account: what happened, sentiment, open asks, │
│ deal movement, risks, next step │
│ 5. Cross-account summary + top 3 actions │
│ 6. Build HTML email │
└───────────────────────────┬─────────────────────────────┘
▼
Email to the requesting user (+ Slack/Teams if stated)Setup, step by step
- Check requirements (5 min)See REQUIREMENTS.md.
- Hand CLONE-INSTRUCTIONS.md to your clone and say "Set this up. Show me a plan first."
- Review discovery (3 min)
- Attach Customer Pulse (2 min)The clone does this via the platform.
- Connect sources (10–25 min)Email, calendar, CRM, Linear, knowledge bases. You sign in; no passwords to the clone.
- Answer placeholders (3 min)(section 6).
- Test (5 min) say "Run Customer Pulse for the past 24 hours".
- Optional schedule for example weekdays at 7:30 AM (prompt in CLONE-INSTRUCTIONS.md).
The full walkthrough is in the README. The Clone Instructions file tells your clone exactly what to do.
What you’ll need
| # | Skill / operator (exact name) | Used for | Required? |
|---|---|---|---|
| 1 | Customer Pulse (prebuilt skill) | The briefing | Required |
| 2 | Google Gmail Operator or the Outlook email operator | Customer threads; sends the briefing | Required |
| 3 | Google Calendar Operator or the Outlook calendar operator | Meetings in the window | Recommended |
| 4 | Meeting Archive, Call Archive | Transcripts of meetings and phone calls | Optional |
| 5 | Salesforce operators (Salesforce Account Operator, Salesforce Opportunity Operator, Salesforce Case Operator, Salesforce Activity Operator) or HubSpot operators (HubSpot Company Operator, HubSpot Deal Operator, HubSpot Engagement Operator) | Account list and CRM changes | Strongly recommended |
| 6 | Linear Operator | Customer-linked issues | Optional |
| 7 | Search Knowledge | Knowledge base notes | Optional |
| 8 | platform | Attach the skill, schedule | Required |
Skill names can differ slightly between orgs. Confirm the exact names in your skill catalog before saving the skill.
Known gotchas
- Only knows connected sources. Missing sources are reported as not connected, not as quiet.
- Personal-domain emails (gmail.com and similar) don't map to accounts unless the contact is in the CRM.
- Window wording matters. "Past 24 hours" and "since yesterday" are different. Be specific.
- Not the same as other cards: Voice of the Customer finds themes across feedback; Account Health is a weekly grading written to the CRM. Pulse is a read-only activity briefing.
- Slack/Teams can't be read. Delivery only.
Questions
Does it change my CRM?
No, read-only.
Prospects too?
Yes, unless {ACCOUNTFILTER} says customers only.
HubSpot support items?
No ticket operator; it uses notes and tasks via HubSpot Engagement Operator.
Can others receive it?
Yes, name them in {BRIEFINGRECIPIENTS} or in the request.