Clone Support
Use case

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.

The problem

Customer activity is spread across inboxes, meetings, CRM and issue tracker, so risks and momentum are noticed late.

Customer Pulse: Cross-Account Activity Briefing

Version 1.0.0 · Last updated 2026-10-22 · Difficulty: Beginner · Setup time: 20–40 minutes

🧩 Based on the prebuilt skill Customer-Pulse. You attach it; you don't have to write it.

Your clone reviews recent activity across all your customers and prospects and emails you one briefing: what happened, how it feels, what's open, and what to do next.


1. Overview and value

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.


2. 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.
  • RevOps teams checking CRM activity against what's really happening.

3. How it works

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

4. What the clone does (and never does)

Does: reads only connected sources; reports each source as checked with activity, checked with none, not connected, or failed; groups by account; recommends next steps.

Never: invents activity or sentiment; treats "not connected" as "no activity"; includes personal contact details beyond what's needed (names and roles only when relevant); emails customers; writes to the CRM, Linear or email.

5. Setup walkthrough

  1. Check requirements (5 min). See REQUIREMENTS.md.
  2. Hand CLONE-INSTRUCTIONS.md to your clone and say "Set this up. Show me a plan first."
  3. Review discovery (3 min).
  4. Attach Customer-Pulse (2 min). The clone does this via the platform.
  5. Connect sources (10–25 min). Email, calendar, CRM, Linear, knowledge bases. You sign in; no passwords to the clone.
  6. Answer placeholders (3 min) (section 6).
  7. Test (5 min): say "Run Customer Pulse for the past 24 hours".
  8. Optional schedule: for example weekdays at 7:30 AM (prompt in CLONE-INSTRUCTIONS.md).

6. Placeholders to decide

PlaceholderWhat it meansExample
{WINDOW}Time windowpast 24 hours, past 7 days, since Monday
{ACCOUNT_FILTER}Optional scope: owner, segment, customers vs prospectsmy accounts only; Enterprise segment; customers only
{BRIEFING_RECIPIENTS}Who gets the email (default: you)you@yourcompany.com
{DELIVERY_CHANNEL}Optional Slack/Teams channel#customer-pulse
{RUN_TIME}Schedule with time zone7:30 AM America/New_York, Mon–Fri

7. What to expect

  • A briefing email within a few minutes of the request.
  • Top: a source-status line and the cross-account summary. Below: one section per active account.
  • Accounts with no activity are not listed (just a count).
  • Quiet window: a short "no customer activity" note plus sources checked.

8. Customizing

Say things like: "Only my accounts", "Prospects only", "Past 7 days", "Since Monday", "Top 5 actions", "Skip Linear", or "Also post a short version to {DELIVERY_CHANNEL}".

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

10. FAQ

Does it change my CRM? No, read-only.

Prospects too? Yes, unless {ACCOUNT_FILTER} says customers only.

HubSpot support items? No ticket operator; it uses notes and tasks via HubspotEngagementOperator.

Can others receive it? Yes, name them in {BRIEFING_RECIPIENTS} or in the request.

11. Troubleshooting

SymptomLikely causeFix
No email receivedWrong recipient or schedule pausedCheck the task and recipient
An account is missingPersonal-domain emails or no CRM matchAdd the contact or domain in the CRM
"Email not connected"Sign-in expiredReconnect Gmail or Outlook
Window looks wrongVague wordingUse "past 7 days" or an explicit date
Too many accountsNo filterSet {ACCOUNT_FILTER}
No call or meeting dataClone wasn't in the meetingOnly meeting_archive and call_archive content is available

Version: 1.0.0 · Last updated: 2026-10-22 · Part of the Clone Use Case Library.

Paste these instructions into clone chat

# Clone Instructions: Customer Pulse (Cross-Account Activity Briefing)

> **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 `Customer-Pulse`.** You attach it; you don't have to write it.

---

## 1. Role and goal

You are setting up **Customer Pulse**. When done, the user can say **"Run Customer Pulse for the past 24 hours"** and you will email a briefing covering customer and prospect activity across email, meetings, CRM, Linear and knowledge notes, with per-account sections and a cross-account summary.

Your job now is **setup only**: discover, collect settings, plan, attach the skill, optionally schedule, test.

## 2. Safety rules

1. **Plan first.** Numbered plan, explicit "yes" before attaching, creating or changing anything.
2. **Never ask for, accept or handle passwords, API keys or tokens.** Users connect via sign-in (OAuth). If a secret is pasted, tell them to revoke it.
3. **Never email customers or prospects during setup.** Test briefings go only to the user.
4. **Read-only.** Never write to the CRM, Linear, email, calendar or knowledge bases.
5. **Don't guess names.** Use exact catalog names. Skill names can differ slightly between orgs; confirm them first.
6. **Fail closed.** "Not connected" is never reported as "no activity".
7. **Privacy.** Don't include personal contact details (phone, personal email, home address) beyond what's needed.

## 3. Discovery

Use the `platform` tool and `describeOperator`.

| Need | Required? | Look for |
|---|---|---|
| Prebuilt skill | Required | Customer-Pulse |
| Email | Required | GoogleGmailOperator or Outlook email operator |
| Calendar | Recommended | GoogleCalendarOperator or Outlook calendar operator |
| Transcripts | Optional | meeting_archive, call_archive |
| CRM | Strongly recommended | Salesforce operators (Account, Opportunity, Case, Activity) or HubSpot operators (Company, Deal, Engagement) |
| Linear | Optional | Linear_Operator |
| Knowledge | Optional | search_knowledge |
| Scheduled tasks | Optional | platform |
| Slack/Teams delivery | Optional | Messaging integration |

| Item | Status | Exact name in catalog | Notes |
|---|---|---|---|
| Customer-Pulse | ✅ ⚠️ ❌ ❓ | … | … |
| Email | … | … | … |
| Calendar | … | … | … |
| meeting_archive / call_archive | … | … | … |
| CRM | … | … | … |
| Linear | … | … | … |
| Knowledge base | … | … | … |
| Slack/Teams | … | … | … |

Mark unknowns "❓ Couldn't check" with a reason. For unsupported tools, say they aren't supported.

## 4. Collect placeholders

> 1. **Window** (`{WINDOW}`): default past 24 hours. Or "past 7 days", "since Monday".
> 2. **Account filter** (`{ACCOUNT_FILTER}`): optional. Owner, segment, customers only vs prospects.
> 3. **Recipients** (`{BRIEFING_RECIPIENTS}`): default the requesting user.
> 4. **Delivery channel** (`{DELIVERY_CHANNEL}`): optional Slack/Teams channel.
> 5. **Schedule** (`{RUN_TIME}`): none, or e.g. weekdays 7:30 AM with time zone.

Confirm in a table.

## 5. What you can do yourself (after approval)

> **Proposed plan (nothing changes until you say yes):**
> 1. Attach **Customer-Pulse** and any missing operators.
> 2. Run a test for the past 24 hours; email it to you only.
> 3. (Optional) Create a scheduled task at `{RUN_TIME}`.
>
> **You'll need to:** sign in to the connections in section 6. Reply **yes** to proceed.

After "yes":

1. **Attach Customer-Pulse** via the platform tool, confirm with `describeOperator`. If you can't: tell the user to open settings → Skills → find **Customer-Pulse** → Add/Enable, then say "attached".
2. **Attach missing operators** the user approved.
3. **Create the scheduled task (optional).** Paste exactly, filling the braces:

```
Run Customer Pulse for {WINDOW}. Account filter: {ACCOUNT_FILTER}. Email the HTML briefing to {BRIEFING_RECIPIENTS}. If a delivery channel is given ({DELIVERY_CHANNEL}), also post a short version there. Report each source as checked with activity, checked with no activity, not connected, or failed. Do not invent activity. Do not email customers or prospects. Do not change any records.
```

Schedule: `{RUN_TIME}` (for example weekdays 7:30 AM).

**Optional customization lines:** "Only my accounts." / "Prospects only." / "Past 7 days." / "Since Monday." / "Show top 5 actions." / "Skip Linear."

## 6. What the user must do

1. **Connect email** (Gmail or Outlook): settings → Connections → provider → sign in → approve read and send.
2. **Connect calendar** the same way.
3. **Connect CRM** (Salesforce or HubSpot) with read access. A CRM admin may need to grant it.
4. **Connect Linear** (read) if used.
5. **Share knowledge bases** with the clone if used.
6. **Allow Slack/Teams posting** if delivery there is wanted.
7. Tell me "done". I never need your password.

## 7. What the prebuilt skill does (Customer-Pulse)

1. **Sets the window** from `{WINDOW}` (default past 24 hours; accepts "past 7 days", "since Monday") using the real current time, and applies `{ACCOUNT_FILTER}`.
2. **Collects, per connected source:** email threads (Gmail/Outlook); meetings (calendar plus `meeting_archive` transcripts and `call_archive`); CRM changes (Salesforce: accounts, opportunities, cases, activities; HubSpot: companies, deals, engagements); Linear issues tied to customers; knowledge base notes via `search_knowledge`.
3. **Maps activity to accounts** by email domain and CRM records. Personal-domain emails map only if the contact is in the CRM.
4. **Per account:** what happened, sentiment, open asks and what we owe, deal movement, risks, recommended next step.
5. **Cross-account summary:** accounts needing attention, momentum list, at-risk list, top 3 actions.
6. **Fail-closed source status:** each source is checked with activity, checked with none, not connected, or failed. A failed call is retried once, then marked unavailable.
7. **Delivers** an HTML email to the requesting user (or `{BRIEFING_RECIPIENTS}`), and a short Slack/Teams post only if stated.
8. **Privacy:** no personal contact details beyond what's needed.

## 8. Test plan

Use your own mailbox as the only recipient.

| ☐ | Check | Expected |
|---|---|---|
| ☐ | Run "Run Customer Pulse for the past 24 hours" | Window stated with real dates |
| ☐ | Source status | Accurate for each source |
| ☐ | Account sections | Each has what happened, sentiment, open asks, deal movement, risks, next step |
| ☐ | Cross-account summary | Attention, momentum, at-risk, top 3 actions |
| ☐ | Disconnect a source (or use one not connected) | Reported "not connected", not "no activity" |
| ☐ | Window wording | "since Monday" resolves to the right date |
| ☐ | Email arrives to the user only | HTML renders |
| ☐ | No customer emailed, no records changed | Confirmed |

## 9. Final status checklist

**✅ Done by me:** *(skill attached, operators attached, schedule created, test sent)*

**⏳ Waiting on you:** *(sign-ins, CRM access, sharing, review of the test)*

**💡 Optional next steps:** add a Slack/Teams channel post, a weekly "past 7 days" run, owner-specific filters, and pair with Voice of the Customer or Weekly-Account-Health-Update.

Requirements

Requirements: Customer Pulse

Version 1.0.0 · Last updated 2026-10-22 · Estimated setup time: 20–40 minutes

🧩 Based on the prebuilt skill Customer-Pulse. You attach it; you don't have to write it.


1. Required skills / operators

#Skill / operator (exact name)Used forRequired?
1Customer-Pulse (prebuilt skill)The briefingRequired
2GoogleGmailOperator or the Outlook email operatorCustomer threads; sends the briefingRequired
3GoogleCalendarOperator or the Outlook calendar operatorMeetings in the windowRecommended
4meeting_archive, call_archiveTranscripts of meetings and phone callsOptional
5Salesforce operators (SalesforceAccountOperator, SalesforceOpportunityOperator, SalesforceCaseOperator, SalesforceActivityOperator) or HubSpot operators (HubspotCompanyOperator, HubspotDealOperator, HubspotEngagementOperator)Account list and CRM changesStrongly recommended
6Linear_OperatorCustomer-linked issuesOptional
7search_knowledgeKnowledge base notesOptional
8platformAttach the skill, scheduleRequired

Skill names can differ slightly between orgs. Confirm the exact names in your skill catalog before saving the skill.

2. Connections and minimum permissions

ConnectionMinimum permissionWhy
EmailRead + SendRead threads; send the briefing
CalendarReadMeetings in the window
Salesforce or HubSpotReadAccount, deal, case/engagement, activity changes
LinearReadCustomer-tagged issues
Knowledge basesView (shared with the clone)Account notes
Slack or Teams (optional)Post to the channelDelivery

All connections are made by you through sign-in (OAuth). Your clone never needs your password.

3. Optional add-ons and CRM mapping

Add-onAdds
meeting_archive, call_archiveWhat was said and promised
LinearBugs and requests tied to customers
Knowledge baseInternal account notes
Slack or TeamsA short channel version
ConceptSalesforceHubSpot
AccountAccount (SalesforceAccountOperator)Company (HubspotCompanyOperator)
DealOpportunity (SalesforceOpportunityOperator)Deal (HubspotDealOperator)
Support itemCase (SalesforceCaseOperator)Notes/tasks via HubspotEngagementOperator (no ticket operator)
ActivitySalesforceActivityOperatorHubspotEngagementOperator

4. Data prerequisites

  • CRM accounts or companies have a website or email domain.
  • Contacts have email addresses so threads can be matched.
  • You know how customers and prospects are told apart (stage, type, lifecycle).
  • Linear issues mention or link the customer (optional).
  • Knowledge base shared with the clone (optional).

5. Roles and permissions

WhoNeeds to
Clone adminAttach the skill, approve the plan, create the schedule
Connection ownerSign in to email, calendar, CRM, Linear
CRM adminGrant a read-only user if required

6. Estimated setup time

StepTime
Pre-flight5 min
Discovery and plan5–10 min
Sign-ins10–20 min
Test run5 min
Total20–40 min

7. Pre-flight checklist

  • I'm the clone admin (or have one)
  • Customer-Pulse is in my catalog
  • Email (Gmail or Outlook) can be connected
  • CRM (Salesforce or HubSpot) can be connected with read access
  • (Optional) Calendar, Linear, meeting_archive, call_archive, knowledge base
  • I've chosen {WINDOW}, {ACCOUNT_FILTER}, {BRIEFING_RECIPIENTS}

8. You're ready when…

  • ✅ Customer-Pulse is attached.
  • ✅ Email and a CRM are connected.
  • ✅ A test run produced a briefing with a correct source-status line.
  • ✅ (Optional) A scheduled task is created.

Then download CLONE-INSTRUCTIONS.md and give it to your clone.

Was this use case helpful?