Monday morning: everything your customers heard last week
Your clone gathers every customer email, campaign and support update from last week into one recap for your team.
Each Monday your clone reads the past week of outbound customer messages from your CRM, marketing email, sent folders and support inbox. It removes duplicates, sums up each item in a line with opens and clicks, points out gaps, and posts a single recap to Slack or Teams.
What your clone does
Marketing, success and support all email customers, and nobody can say what customers actually heard last week. Your clone keeps the record.
Customer communication comes from many places: HubSpot sends newsletters, CSMs send update emails, support sends announcements from a shared inbox, and the CRM logs some of it (but rarely all). By Monday, nobody on the team can say for sure what customers received last week. People repeat updates customers already got, or miss the chance to follow up on a great one.
The Weekly Customer Updates Recap fixes that. Every Monday at {RUN_TIME} your clone:
- reads the last 7 days of outbound customer communications from every source you've connected,
- combines and de-duplicates them (one line per piece of content, no matter how many places it showed up),
- groups them by type (videos, blog posts, tips, features, announcements and more),
- adds open/click totals where HubSpot marketing shares them,
- points out gaps (days with no send, items missing from the CRM log, sources that didn't respond),
- posts one recap to
{TEAM_CHANNEL}.
It only reads. The single thing it writes is the channel post.
What you get:
| Benefit | What it looks like |
|---|---|
| One shared picture | Sales, CS, support and leadership all see the same list every Monday |
| Better conversations | "Did you see our video on X last week?" instead of repeating it |
| Fewer duplicate sends | Teams see what already went out before sending their own update |
| Program health at a glance | Totals, top email and gaps tell you if your cadence is slipping |
| Cleaner CRM logging | Items missing from the CRM log are flagged every week |
This is not "voice of the customer". Voice of the customer is about inbound feedback (what customers say to you: surveys, tickets, call notes). This recap is about outbound communications (what you said to customers). The two pair well, but this use case never summarizes customer replies or feedback.
Who it helps
- Customer Success teams who want to reference recent updates in check-ins and avoid repeating them.
- Marketing teams who want a weekly, human-readable log of what actually went out and how it performed.
- Support teams who need to know which announcements customers received (so they can answer "I got an email about…").
- Leadership who want a quick Monday pulse on customer communication volume and consistency.
It works especially well alongside the Automated Customer Email Program use case, which logs each send in your CRM with a consistent subject line. It also works fine on its own.
How it runs
┌───────────────────────────────────────────────────────────────────┐
│ Every Monday at {RUN_TIME} (scheduled task) │
└───────────────────────────────┬───────────────────────────────────┘
│
▼
┌───────────────────────────────────────────────────────────────────┐
│ "Weekly Updates Recap" skill (read-only) │
│ │
│ 1. Set the window ──► last 7 days in {RECAP_TIME_ZONE} │
│ 2. Read each source (skip what isn't connected): │
│ a. CRM: "[Customer Email]" tasks + synced email activity │
│ b. HubSpot marketing: sent emails + open/click totals │
│ c. Inbox: Sent items labeled {SEND_LABEL} + │
│ copies received at {SEED_ADDRESS} │
│ d. Shared support inbox {SUPPORT_INBOX} (optional) │
│ 3. Filter out internal and non-customer mail │
│ 4. Combine + de-duplicate by content title │
│ (earliest date wins, record which sources found it) │
│ 5. Group by type, add stats, find top email and gaps │
│ 6. Post ONE recap ──► {TEAM_CHANNEL} (Slack or Teams) │
└───────────────────────────────┬───────────────────────────────────┘
│
▼
┌───────────────────────────────────────────────────────────────────┐
│ Team reads the recap → uses it in customer conversations │
│ If every source failed: a failure notice is posted instead │
└───────────────────────────────────────────────────────────────────┘Where the data comes from
| Source | What the clone looks for | Required? |
|---|---|---|
| Salesforce or HubSpot | Completed tasks/activities with subject [Customer Email] {Type} – {Title} (the logging convention from the Automated Customer Email Program), plus marketing email activity synced into the CRM | Recommended |
| HubSpot marketing (HubSpot Marketing Operator) | Emails sent in the window, with list/audience and open/click totals | Optional |
| Your inbox | Messages in Sent with the label/category {SEND_LABEL}, plus marketing emails received at {SEED_ADDRESS} (an address subscribed to your customer lists) | Required (at least one of the two) |
| Shared support inbox | Customer announcements sent from {SUPPORT_INBOX} | Optional |
The clone uses whatever is connected and tells you in every post which sources worked.
Set it up, step by step
- Check requirements (5 min)Open REQUIREMENTS.md and run through the pre-flight checklist. You need at least an email connection, a Slack or Teams connection that can post to {TEAMCHANNEL}, and the ability to create a scheduled task. A Salesforce or HubSpot operator is strongly recommended.
- Hand the instructions to your clone (2 min)Paste or upload CLONE-INSTRUCTIONS.md into a chat with your clone and say: "Please set up this use case for me. Show me a plan before changing anything."
- Review the discovery table (3 min)The clone reports which skills/operators and connections it already has and which are missing.
- Answer the placeholder questions (5 min)See the table in section 6.
- Approve the plan (2 min)The clone lists exactly what it will attach, create and schedule. Say "yes" only when it looks right.
- Do your part (10–15 min)Things only you can do: - Complete sign-in (OAuth) for email, chat, Salesforce or HubSpot, and HubSpot marketing connections. - Add the clone to {TEAMCHANNEL} (Slack: /invite the clone's app; Teams: add it to the team/channel). - Subscribe {SEEDADDRESS} to your customer email lists in HubSpot (if you use a seed address). - Give the clone access to {SUPPORTINBOX} (if used). - Start labeling customer emails with {SENDLABEL} (if you send updates by hand).
- Save the Weekly Updates Recap skill (5 min)If the clone can't create custom skills directly, it gives you the full skill text in a copy-paste block with exact steps. Read it before you save it.
- Run the test (10 min)The clone does a test run that posts to a test channel first (or sends you the draft in chat), so you can check it before your team sees it.
- Let it runFrom next Monday, the recap appears in {TEAMCHANNEL} at {RUNTIME}.
The README has the full walkthrough. The Clone Instructions tell your clone exactly what to do.
Before you start
Your clone matches these to the exact skill names in your workspace. Confirm them in your skill catalog before saving the skill. Your clone will report the exact names it finds.
Skill names can differ slightly between orgs. Confirm the exact names in your skill catalog before saving the skill.
| # | Skill / operator (exact name) | What it's used for | Notes |
|---|---|---|---|
| 1 | Google Gmail Operator (Google) or the Outlook email operator (Microsoft 365) | Read Sent items with {SEND_LABEL}, copies at {SEED_ADDRESS}, and {SUPPORT_INBOX} if used | Read-only is enough |
| 2 | Slack or Microsoft Teams (the clone's messaging integration) | Post the weekly recap (and thread replies) to {TEAM_CHANNEL} | Delivery only; chat is never read as a source |
| 3 | Scheduled task (via the platform tool) | Run Weekly Updates Recap every Monday at {RUN_TIME} | Platform feature; the clone may be able to create it |
Good to know
- The clone must be in the channel. Slack: in the channel, type
/invite @{CLONE_NAME}(or the name of the clone's Slack app). Teams: add the clone/app to the team and channel. Private channels always need this step. Without it, the post fails. - The seed address must really be subscribed. If
{SEED_ADDRESS}isn't on your customer lists (or got unsubscribed or suppressed by HubSpot after a bounce), marketing emails won't show up there. Check it once a quarter. - The clone can only read what it can see. It can't read a coworker's Sent folder or a shared inbox unless that mailbox is connected or delegated to it.
- De-duplication isn't perfect. The same email can appear as "Bulk edit is here!" in HubSpot marketing and "[Customer Email] Feature – Bulk Edit Is Here" in the CRM. The skill normalizes titles (ignores case, punctuation, emoji and prefixes like "Fwd:" or "[Customer Email] Type –"), but very different subjects may still show as two lines. Fix by using the same title everywhere.
- Time zone of the window. "Last 7 days" depends on the time zone. An email sent Sunday 11 PM in New York is Monday in London. Set
{RECAP_TIME_ZONE}to the zone your team works in. - HubSpot marketing read permissions. HubSpot can split "read campaigns" from "read reports/stats". If stats show "n/a" but sends appear, the connection probably lacks reporting access. If the read tools fail entirely, the clone skips the source and notes "send data unavailable".
- Failure is not an empty week. If every source fails, the clone posts a failure notice, never "nothing was sent". If one source fails, the recap still posts with that source marked unavailable.
- Stats change over time. Open/click totals are a snapshot at run time. Emails sent Friday will have fewer opens than emails sent Monday. Also, privacy features in some mail apps inflate opens, so treat clicks as the more reliable number.
- Message length limits. Slack and Teams cut off or reject very long messages. The skill keeps the main post short and moves long groups into thread replies.
- Use exact skill/operator names as they appear in your skill catalog. Names can differ slightly between orgs; the clone checks them during discovery.
- Read every instruction before saving it into a skill. You're responsible for what your clone does.
Questions, answered
Which CRMs and marketing tools work?
Salesforce and HubSpot for the CRM log (see the Salesforce to HubSpot mapping in REQUIREMENTS.md). For marketing send data and stats, HubSpot (HubSpot Marketing Operator) only. Other marketing tools aren't supported, but the seed address and labeled Sent items still catch their sends.
Do I need the Automated Customer Email Program use case?
No. It helps, because it logs every send in the CRM with a consistent subject. Without it, the clone relies on HubSpot marketing, your labeled Sent items and the seed inbox.
Do I need a HubSpot marketing connection?
No. Without it you lose open/click stats and the HubSpot send list, but the seed address still catches marketing emails.
Will the clone email anyone?
No. It only posts once a week to {TEAMCHANNEL}.
Will customer names or email addresses appear in the post?
No. The post describes audiences by list or segment name (e.g. "All customers", "Admins segment") and never lists recipients.
Will it change anything in my CRM or inbox?
No. It's read-only everywhere except the single channel post.
Is this the same as a voice-of-the-customer report?
No. Voice of the customer summarizes what customers say to you. This recap summarizes what you sent to customers.
What if we sent nothing last week?
If the sources were read successfully and found nothing, the post says so clearly and lists the sources it checked. If the sources couldn't be read, it posts a failure notice instead.
Ready when you are. So is your clone.
Build your clone, paste in the Weekly Customer Updates Recap instructions, and approve the plan it shows you.