Weekly Customer Updates Recap
Every Monday your clone posts one clear recap of everything your company sent to customers last week.
The problem
Customer updates go out from marketing, CS and support, but nobody can say for sure what customers heard last week. Teams repeat updates, miss follow-up chances and can't spot gaps in their send cadence.
Weekly Customer Updates Recap
Version 1.1.0 · Last updated 2026-10-22 · Difficulty: Beginner · Setup time: 30–45 minutes
Every Monday morning your clone sums up everything your company sent to customers in the last 7 days and posts one clear recap to your team channel in Slack or Microsoft Teams. Everyone knows what customers just heard from you, before they talk to them.
1. Overview and value
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.
2. Who it's for
- 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.
3. How it works
┌───────────────────────────────────────────────────────────────────┐
│ 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 (HubspotMarketingOperator) | 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.
4. What the clone does each week
- Sets the window: the 7 full days before the run, in
{RECAP_TIME_ZONE}. - Reads every connected source and keeps only messages that went to customers.
- Drops internal briefings, messages only to
{YOUR_COMPANY_DOMAINS}, vendor mail, personal one-to-one replies and anything it can't tell is customer-facing. - Merges duplicates: the same newsletter found in the CRM, HubSpot marketing and the seed inbox becomes one line, dated by the earliest copy, with the sources noted.
- Writes a one-line, customer-facing summary for each item (what the customer was told, in plain words).
- Groups items by type with emoji headers, then adds totals, the top email (if open/click data exists) and gaps.
- Posts once to
{TEAM_CHANNEL}. If the post is long, it continues in thread replies.
What it never does:
- Never emails customers or anyone else. The channel post is its only output.
- Never creates, edits or deletes anything in Salesforce, HubSpot or inboxes (no labels, no archiving, no "mark as read" on purpose).
- Never includes recipient names, email addresses or other personal details in the post. Audiences are described by list or segment name only.
- Never posts "nothing was sent this week" when it simply couldn't read the sources. If every source fails, it posts a failure notice.
- Never summarizes customer replies or feedback (that's voice of the customer, a different use case).
Example post
📬 Customer Updates Recap: Oct 13 – Oct 19 (America/New_York)
🎬 Videos
• Oct 14 · "Setting up approvals in 3 minutes": short walkthrough of the new approval flow · All customers · <link> · 1,240 opens / 212 clicks
📝 Blog
• Oct 15 · "5 ways teams cut reporting time": practical tips with examples from the dashboard · Newsletter list · <link> · 980 opens / 143 clicks
💡 Tips
• Oct 16 · "Tip: save filters as views": how to reuse filters across reports · Admins segment · <link> · stats n/a
✨ Features
• Oct 17 · "Bulk edit is here": customers can now update many records at once · All customers · <link> · 1,410 opens / 305 clicks
📣 Announcements
• Oct 13 · "Scheduled maintenance on Oct 18": 30-minute window, no action needed · All customers (support inbox) · <link> · stats n/a
📈 Totals: 5 items · 4 emails with stats · 4,630 opens · 660 clicks
🏆 Top email: "Bulk edit is here" (305 clicks)
⚠️ Gaps:
• No customer send on: none this week (Mon–Fri all covered)
• Missing from CRM log: "Scheduled maintenance on Oct 18"
• Sources: CRM ✅ · HubSpot marketing ✅ · Inbox (label + seed) ✅ · Support inbox ✅(Your real post uses your own types, lists and links. Stats show "n/a" when no source provides them.)
5. Setup walkthrough
The quickest path: download CLONE-INSTRUCTIONS.md and give it to your clone. It will check what's already connected, ask you for the placeholder values, show you a plan, and set up what it can after you approve. The steps below are what happens, so you know what to expect.
Step 1: 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 {TEAM_CHANNEL}, and the ability to create a scheduled task. A Salesforce or HubSpot operator is strongly recommended.
Step 2: 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."
Step 3: Review the discovery table (3 min) The clone reports which skills/operators and connections it already has and which are missing.
Step 4: Answer the placeholder questions (5 min) See the table in section 6.
Step 5: Approve the plan (2 min) The clone lists exactly what it will attach, create and schedule. Say "yes" only when it looks right.
Step 6: 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
{TEAM_CHANNEL}(Slack:/invitethe clone's app; Teams: add it to the team/channel). - Subscribe
{SEED_ADDRESS}to your customer email lists in HubSpot (if you use a seed address). - Give the clone access to
{SUPPORT_INBOX}(if used). - Start labeling customer emails with
{SEND_LABEL}(if you send updates by hand).
Step 7: 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.
Step 8: 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.
Step 9: Let it run From next Monday, the recap appears in {TEAM_CHANNEL} at {RUN_TIME}.
6. Placeholders to decide
| Placeholder | What it means | Example |
|---|---|---|
{CLONE_NAME} | Your clone's display name | "Ava" |
{CLONE_INBOX} | The inbox the clone reads (its own, or a delegated one) | ava@yourcompany.com |
{YOUR_COMPANY_DOMAINS} | Your company's email domains (mail only to these = internal) | yourcompany.com, yourcompany.io |
{TEAM_CHANNEL} | The Slack or Teams channel for the recap | #customer-updates (Slack) or "Customer Success › Updates" (Teams) |
{TEST_CHANNEL} | A private channel for the test run | #clone-test |
{RUN_TIME} | When the weekly run happens (with time zone) | Monday 8:00 AM America/New_York |
{RECAP_TIME_ZONE} | Time zone that defines the 7-day window | America/New_York |
{SEND_LABEL} | Label/category on customer emails sent by hand from the inbox | "Customer Update" |
{SEED_ADDRESS} | An inbox subscribed to your customer lists, so marketing copies arrive there | updates-seed@yourcompany.com |
{SUPPORT_INBOX} | Shared support inbox that sends customer announcements (optional) | support@yourcompany.com |
{CONTENT_TYPES} | The types to group by, with emoji headers | 🎬 Videos, 📝 Blog, 💡 Tips, ✨ Features, 📊 Industry/Comparison, 📣 Announcements, 🔁 Other |
{SEND_DAYS} | Days you expect at least one customer send (for gap checks) | Mon–Fri |
Tip: set {RUN_TIME} early enough that the recap is there before your Monday team meeting.
7. What to expect day to day
- Every Monday at {RUN_TIME}: the run starts. It usually takes a few minutes.
- Shortly after: one post appears in
{TEAM_CHANNEL}, with long sections continued in thread replies. - Each post ends with source status, so you know if any source was skipped (for example "HubSpot marketing: send data unavailable").
- Rest of the week: nothing. The clone does not post again until next Monday unless you ask: "Run the Weekly Updates Recap for the last 7 days now."
- Your only regular task: keep labeling hand-sent customer emails with
{SEND_LABEL}and keep logging sends in Salesforce or HubSpot.
8. Customizing
Content types. Rename, add or remove groups (e.g. add 🎓 Webinars or 🛠️ Release notes). Items that don't fit go to 🔁 Other.
Window and schedule. Change to a Friday afternoon recap, a two-week window, or business days only.
Audience detail. Show list/segment names, or hide them and just show counts.
Stats. Show opens and clicks, clicks only, or no stats at all.
Sources. Add or remove sources at any time. The skill uses whatever is connected and reports what worked or failed.
Multiple channels. Post a short version to a leadership channel and the full version to the CS channel (ask the clone to add a second post step).
9. Known gotchas
- 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.
10. FAQ
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 (HubspotMarketingOperator) 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 {TEAM_CHANNEL}.
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.
11. Troubleshooting
| Symptom | Likely cause | Fix |
|---|---|---|
| No post on Monday | Scheduled task missing, paused, or wrong time zone | Ask the clone to list its scheduled tasks; check {RUN_TIME} |
| "Couldn't post to channel" | Clone not added to {TEAM_CHANNEL}, or chat connection expired | Slack: /invite the clone; Teams: add it to the channel; re-run sign-in |
| Marketing emails missing | Seed address not subscribed, or HubSpot marketing not connected | Subscribe {SEED_ADDRESS} to customer lists; check it isn't suppressed |
| Same email listed twice | Different titles in different sources | Use the same title everywhere, or ask the clone to add a title alias |
| Stats show "n/a" | HubSpot marketing not connected, or it lacks reporting permission | Reconnect HubSpot with reporting/read stats access |
| "Send data unavailable" | HubspotMarketingOperator read tools failed twice | Re-run sign-in; confirm read access to campaigns and reports |
| Internal emails appear | Internal domain not in {YOUR_COMPANY_DOMAINS}, or internal list on seed address | Add the domain; unsubscribe the seed address from internal lists |
| Hand-sent updates missing | {SEND_LABEL} not applied, or sent from a mailbox the clone can't read | Apply the label; connect or delegate that mailbox |
| Items flagged "missing from CRM log" every week | Sends not logged in the CRM | Log them with the [Customer Email] subject format, or turn off that gap check |
| Post cut off | Message too long for Slack/Teams | Ask the clone to shorten summaries or move more groups to thread replies |
| Failure notice posted | Every source failed (often expired sign-ins) | Re-run sign-in for each connection, then ask the clone to run the recap again |
Version: 1.1.0 · Last updated: 2026-10-22 · Part of the Clone Use Case Library.
Paste these instructions into clone chat
# Clone Instructions: Weekly Customer Updates Recap
> **For the clone.** Your user has handed you this file. Follow it step by step.
> **Version 1.1.0 · Last updated 2026-10-22**
---
## 1. Role and goal
You are setting up the **Weekly Customer Updates Recap** use case for your user.
When setup is done, every Monday at `{RUN_TIME}` you will run a skill called **Weekly Updates Recap** that:
1. sets a 7-day window in `{RECAP_TIME_ZONE}`,
2. reads outbound customer communications from every connected source (Salesforce or HubSpot, HubSpot marketing, inbox, seed address, shared support inbox),
3. filters out internal and non-customer mail,
4. combines and de-duplicates items by content title,
5. groups them by type with a one-line customer-facing summary each,
6. adds totals, the top email and gaps,
7. posts one recap to `{TEAM_CHANNEL}` in Slack or Microsoft Teams.
This is about **outbound** communications (what the company sent to customers). It is not a voice-of-the-customer report: never summarize customer replies or feedback.
Your job right now is **setup only**: discover what's available, collect the user's settings, propose a plan, do the parts you're able to do after approval, and clearly hand over the parts only the user can do.
Be honest about your limits. If a tool isn't available to you or a step fails, say so plainly and give the user the exact manual steps instead.
## 2. Safety rules (read before doing anything)
- **Plan first, then act.** Before you attach, create, schedule, post or change anything, show the user a numbered plan and wait for an explicit "yes". No yes = no changes.
- **Approval is per plan.** If the plan changes, show the new plan and ask again.
- **Never ask for, accept or handle passwords, API keys or tokens.** All connections are made by the user through the platform's own sign-in (OAuth) screens. If the user pastes a secret into chat, tell them not to and don't use it.
- **Never email customers or prospects.** Not during setup, not in the weekly run. This use case sends no email at all.
- **Read-only everywhere except one channel post.** Never create, edit or delete records in Salesforce, HubSpot or HubSpot marketing. Never label, move, archive or delete email. The only thing you write is the recap post (and during setup, a test post to `{TEST_CHANNEL}` after approval).
- **No personal details in posts.** Never include recipient names, email addresses or other personal data. Describe audiences by list or segment name.
- **Don't guess names.** Use exact skill/operator names as they appear in the user's skill catalog. Skill names can differ slightly between orgs, so confirm them before saving the skill.
## 3. Discovery
Check what you already have. Use the platform tool to list your attached skills/operators and connections, and use `describeOperator` on each relevant operator to confirm what it can do (especially: can it read sent items, read labels/categories, read campaigns and reports, post to a channel) and whether its connection is active.
Look for:
| Need | Required? | Examples of what to look for |
|---|---|---|
| Email | **Required** | GoogleGmailOperator or the Outlook email operator (read, including Sent and labels/categories) |
| Chat delivery | **Required** | Slack or Microsoft Teams messaging integration (post to a channel, post thread replies) |
| Scheduled task | **Required** | `platform` tool: create a recurring scheduled task |
| Salesforce or HubSpot | Optional (strongly recommended) | SalesforceActivityOperator, SalesforceAccountOperator; or HubspotEngagementOperator, HubspotCompanyOperator |
| HubSpot marketing | Optional | HubspotMarketingOperator (read marketing emails + reports) |
| Seed address inbox | Optional | `{SEED_ADDRESS}`, readable by you (your own inbox, a delegated one, or a forward into yours) |
| Shared support inbox | Optional | `{SUPPORT_INBOX}`, connected or delegated to you |
**Report the results to the user in a table like this:**
| Item | Status | Exact name in catalog | Notes |
|---|---|---|---|
| Email | ✅ Connected / ⚠️ Attached, not signed in / ❌ Missing | … | … |
| Chat (Slack / Teams) | … | … | … |
| Scheduled task | … | … | … |
| CRM (Salesforce or HubSpot) | … | … | … |
| HubSpot marketing | … | … | … |
| Seed address inbox | … | … | … |
| Shared support inbox | … | … | … |
If you can't check something (for example, there's no way to list connections, or you can't tell whether you're in a channel until you try to post), mark it "❓ Couldn't check" and say why.
## 4. Collect placeholder values
Ask the user **once**, in a single short list. Offer the examples. Don't proceed with the plan until you have answers (the user may say "use the default" where a default is given, or "skip" for optional items).
> To set this up I need a few details:
>
> 1. **Team channel** (`{TEAM_CHANNEL}`): which Slack or Teams channel should get the recap? e.g. `#customer-updates`, or "Customer Success › Updates" in Teams.
> 2. **Test channel** (`{TEST_CHANNEL}`): a private channel for my test post. *(default: I'll send you the draft in this chat instead)*
> 3. **Run time** (`{RUN_TIME}`): when should I post, with time zone? *(default: Monday 8:00 AM your time zone)*
> 4. **Window time zone** (`{RECAP_TIME_ZONE}`): which time zone defines "the last 7 days"? *(default: same as run time)*
> 5. **Your company domains** (`{YOUR_COMPANY_DOMAINS}`): e.g. `yourcompany.com, yourcompany.io`. Mail only to these is internal and excluded.
> 6. **Send label** (`{SEND_LABEL}`): the label/category you put on customer emails sent by hand. e.g. "Customer Update". *(or "skip")*
> 7. **Seed address** (`{SEED_ADDRESS}`): an inbox subscribed to your customer lists that I can read. e.g. `updates-seed@yourcompany.com`. *(or "skip")*
> 8. **Support inbox** (`{SUPPORT_INBOX}`): a shared inbox that sends customer announcements. *(optional, or "skip")*
> 9. **Content types** (`{CONTENT_TYPES}`): *(default: 🎬 Videos, 📝 Blog, 💡 Tips, ✨ Features, 📊 Industry/Comparison, 📣 Announcements, 🔁 Other)*
> 10. **Send days** (`{SEND_DAYS}`): days you expect at least one customer send, for gap checks. *(default: Mon–Fri)*
Also fill `{CLONE_NAME}` and `{CLONE_INBOX}` from what you can see, and confirm them.
Repeat the answers back in a table and ask the user to confirm.
## 5. What you can do yourself (after approval)
Present a plan like this, filled in with real names from discovery:
> **Proposed plan (nothing changes until you say yes):**
> 1. Attach these missing skills/operators from the catalog: *[list exact names]*.
> 2. Create the **Weekly Updates Recap** skill using the text in section 7, with your values filled in.
> 3. Create a scheduled task "Monday Customer Updates Recap" that runs Weekly Updates Recap every Monday at `{RUN_TIME}`.
> 4. Do one test run and post the result to `{TEST_CHANNEL}` (or show it to you here in chat). Nothing goes to `{TEAM_CHANNEL}` until you approve.
>
> **You'll need to do:** *[list from section 6]*.
>
> Reply **yes** to proceed, or tell me what to change.
After a clear "yes":
1. **Attach skills/operators.** Use the platform tool to search the catalog and attach each required/optional item the user approved. Confirm each with `describeOperator`. If an item needs a sign-in, tell the user (it goes on their list).
2. **Create the Weekly Updates Recap skill.** Fill the placeholders with the confirmed values and save it. Remove source steps the user skipped, or leave them in (the skill skips sources that aren't connected).
- **If you can't create a custom skill directly**, give the user the complete skill markdown in one copy-paste block, plus exact steps:
1. Open your clone's settings → **Skills** (or **Custom skills**).
2. Click **New skill** / **Add skill**.
3. Name it exactly **Weekly Updates Recap**.
4. Paste the full block into the skill instructions field.
5. Read it through, then **Save**.
6. Tell me "saved" so I can verify it's attached.
(Menu names may differ slightly in your workspace.)
3. **Create the scheduled task.** Name: "Monday Customer Updates Recap". Schedule: every Monday at `{RUN_TIME}`. Action: "Run the Weekly Updates Recap skill for the last 7 days and post to {TEAM_CHANNEL}." If you can't create scheduled tasks, give the user these exact values and steps to create it manually.
4. **Report back** what succeeded and what failed, honestly.
## 6. What the user must do
Give the user this list, with the how-to steps, and track which ones are done.
1. **Sign in to connections (OAuth).** For each connection marked ⚠️ or ❌ (email, Slack/Teams, Salesforce or HubSpot, HubSpot marketing): open the clone's **Connections** / **Integrations** page → choose the app → **Connect** / **Sign in** → approve the requested permissions. Minimum permissions: email read (including Sent and labels), chat post to channel, CRM read, HubSpot marketing read emails + reports. *I can't do this for you and I never need your password.*
2. **Add me to the channel.**
- *Slack:* open `{TEAM_CHANNEL}` (and `{TEST_CHANNEL}`), type `/invite @{CLONE_NAME}` (or the name of my Slack app) and press Enter. Required for private channels; recommended for public ones.
- *Microsoft Teams:* add me (or my app) to the team, then make sure I can post in the channel. In Teams, apps may need an admin to allow them first.
3. **Subscribe the seed address** (if used). Add `{SEED_ADDRESS}` to every customer list/audience in HubSpot, and make sure it isn't suppressed or unsubscribed. Then connect or delegate that inbox to me, or set it to forward to `{CLONE_INBOX}`.
4. **Give me access to the support inbox** (if used). Connect `{SUPPORT_INBOX}` to me, or delegate read access (Google Workspace: mail delegation or a Google Group I can read; Microsoft 365: shared mailbox with Read permission).
5. **Label hand-sent customer emails.** When you or your team send a customer update by hand, apply `{SEND_LABEL}` (Gmail: label; Outlook: category). I can only read the Sent folder of mailboxes connected to me.
6. **Keep logging sends in Salesforce or HubSpot.** Log each send as a completed task/activity (Salesforce Task, or a HubSpot task/note) with subject `[Customer Email] {Type} – {Title}` (the Automated Customer Email Program use case does this automatically).
## 7. The Weekly Updates Recap skill (save this in full)
Fill in the placeholders, then save as a skill named **Weekly Updates Recap**. Don't shorten it.
~~~~markdown
# Weekly Updates Recap
## Purpose
Every Monday, summarize everything the company sent to customers in the last 7 days
and post one recap to {TEAM_CHANNEL}. This covers OUTBOUND communications only
(what we sent). It is not a voice-of-the-customer report: never summarize customer
replies or feedback.
## Settings
- Clone name: {CLONE_NAME}
- Clone inbox: {CLONE_INBOX}
- Company domains (internal): {YOUR_COMPANY_DOMAINS}
- Team channel: {TEAM_CHANNEL}
- Run time: {RUN_TIME}
- Window time zone: {RECAP_TIME_ZONE}
- Send label: {SEND_LABEL}
- Seed address: {SEED_ADDRESS}
- Support inbox (optional): {SUPPORT_INBOX}
- Content types: {CONTENT_TYPES}
- Expected send days: {SEND_DAYS}
## Tools
Use the exact names from my skill catalog (names can differ slightly between orgs). Use whatever is connected; skip what isn't.
| Purpose | Tool (exact catalog name) | Required | Access |
|---|---|---|---|
| Sent items with {SEND_LABEL}; copies at {SEED_ADDRESS}; {SUPPORT_INBOX} | GoogleGmailOperator or Outlook email operator | Yes | Read-only |
| Post the recap and thread replies | Slack or Microsoft Teams messaging integration | Yes | Post to {TEAM_CHANNEL} only |
| "[Customer Email]" tasks/activities and synced email activity | Salesforce: SalesforceActivityOperator, SalesforceAccountOperator. HubSpot: HubspotEngagementOperator, HubspotCompanyOperator | Optional | Read-only |
| Sent emails, lists/audiences, open/click totals | HubspotMarketingOperator | Optional | Read-only |
## Guardrails
- READ-ONLY: never create, update or delete anything in Salesforce, HubSpot or any inbox. Never label, move, archive or delete email.
- The ONLY write action is posting to {TEAM_CHANNEL} (main post plus thread replies). Never post anywhere else. Never send email.
- No personal details in the post: no recipient names, email addresses, phone numbers or individual customer names. Describe audiences by list or segment name ("All customers", "Admins segment", "1:1 CSM emails").
- Customer-facing content only. Exclude internal briefings, mail only to {YOUR_COMPANY_DOMAINS}, vendor/partner mail, sales prospecting, and personal one-to-one replies.
- Only state facts found in a source. If a stat is missing, write "n/a"; never estimate.
- Retry rule: if a tool call fails, retry ONCE. If it fails again, mark that source "unavailable" for this run, continue without it, and report it in the post.
- Failure is not an empty week: if EVERY source is unavailable, post the failure notice in Step 8. Never post "nothing was sent" unless at least one source was read successfully.
- Never ask for or handle passwords or tokens.
## Step 1: Set the window
- Window = the 7 full days before today, 00:00 to 23:59 in {RECAP_TIME_ZONE} (for a Monday run: last Monday through Sunday).
- Convert all source timestamps to {RECAP_TIME_ZONE} before comparing.
## Step 2: Read each source
For each source, record: worked / no data / unavailable (after retry) / not connected.
a. CRM (Salesforce or HubSpot)
- Completed tasks/activities in the window whose subject starts with "[Customer Email]".
Parse the subject "[Customer Email] {Type} – {Title}" into type and title.
- Email activity synced from HubSpot marketing into the CRM in the window (marketing email engagements / campaign activity). Use the email name or subject as the title.
- Note the list/audience if recorded. Do not collect contact names or addresses.
b. HubSpot marketing (optional, HubspotMarketingOperator)
- Emails/campaigns with a send date in the window: name, subject, send date, list/audience, link to the web version if available, total opens and clicks.
- If the read tools fail twice or aren't permitted, skip and note "HubSpot marketing: send data unavailable".
c. Inbox (Gmail or Outlook)
- Sent items in the window with the label/category {SEND_LABEL}. Keep only messages with at least one recipient outside {YOUR_COMPANY_DOMAINS}.
- Messages received at {SEED_ADDRESS} in the window that come from HubSpot marketing or company domains (these are copies of list sends). Ignore anything else in the seed inbox.
d. Shared support inbox (optional)
- Messages sent from {SUPPORT_INBOX} in the window that are announcements to customers (same message to many customers, or sent to a customer list). Exclude individual ticket replies.
## Step 3: Filter
Drop anything that is:
- internal (all recipients in {YOUR_COMPANY_DOMAINS}), an internal briefing, or a test send,
- to vendors, partners or prospects only,
- a personal one-to-one reply or a support ticket reply,
- a customer reply or feedback (that's inbound, not part of this recap).
If unsure whether an item is customer-facing, leave it out and count it under "Excluded (unclear)".
## Step 4: Combine and de-duplicate
- Normalize each title: lowercase; remove emoji, punctuation, extra spaces; remove prefixes like "Fwd:", "Re:", "[Customer Email] {Type} –", and list/brand tags in brackets.
- Items with the same normalized title (or one clearly contained in the other) are ONE item.
- For each merged item keep: the earliest date, the best title (the customer-facing subject), the type, the list/audience, a link (prefer the public/web version), stats (from HubSpot marketing if present), and the list of sources that found it (CRM, Marketing, Label, Seed, Support).
- Don't merge items that only share generic words (e.g. two different "Monthly newsletter" editions on different dates: keep both, with dates).
## Step 5: Classify and summarize
- Assign each item one type from {CONTENT_TYPES}. Use the CRM type if present; otherwise decide from the content. If nothing fits, use 🔁 Other.
- Write a one-line, customer-facing summary: what the customer was told, in plain words, max ~20 words. No internal jargon.
## Step 6: Totals, top email and gaps
- Totals: number of items, number with stats, total opens, total clicks (only from items with stats).
- Top email: highest clicks (or opens if no click data). If no stats exist, write "Top email: n/a (no stats available)".
- Gaps:
- Days in {SEND_DAYS} with no customer send.
- Items found in other sources but not in the CRM "[Customer Email]" log ("Missing from CRM log"). Skip this check if the CRM wasn't connected.
- Sources that were unavailable or not connected.
- Count of "Excluded (unclear)" items, if any.
## Step 7: Post the recap to {TEAM_CHANNEL}
Main post format:
📬 Customer Updates Recap: {start date} – {end date} ({RECAP_TIME_ZONE})
{emoji} {Type}
• {date} · "{title}": {one-line summary} · {list/audience} · {link} · {opens} opens / {clicks} clicks (or "stats n/a")
(one bullet per item, oldest first; only show types that have items)
📈 Totals: {N} items · {N} with stats · {opens} opens · {clicks} clicks
🏆 Top email: "{title}" ({clicks} clicks)
⚠️ Gaps:
• No customer send on: {days} (or "none")
• Missing from CRM log: {titles} (or "none")
• Sources: CRM {status} · HubSpot marketing {status} · Inbox label {status} · Seed {status} · Support inbox {status}
If sources were read successfully and found nothing, post:
"📬 Customer Updates Recap: {dates}. No customer sends found. Sources checked: {list with status}."
Formatting:
- Slack (mrkdwn): bold = *text*, italic = _text_, links = <url|title>, bullets as "•". Keep the main post under ~3,000 characters.
- Microsoft Teams (markdown): bold = **text**, italic = _text_, links = [title](url), bullets as "- ". Teams rejects messages over about 28 KB (less with links and formatting), so aim for the same ~3,000 characters.
- If the recap is long (more than ~15 items or over the limit): post the header, totals, top email and gaps as the main post, then post each type group as a thread reply under it.
## Step 8: Failure notice
If EVERY source is unavailable or not connected, post instead:
"⚠️ Customer Updates Recap for {dates} could not be built: no source could be read.
CRM: {status} · HubSpot marketing: {status} · Inbox: {status} · Seed: {status} · Support inbox: {status}.
This does NOT mean nothing was sent. Please check the connections and ask {CLONE_NAME} to run the recap again."
If posting to {TEAM_CHANNEL} itself fails twice, report the failure to my owner in chat with the reason (e.g. "not a member of the channel").
~~~~
## 8. Test plan
Run this before relying on the weekly schedule. Ask the user to approve the test first. Use safe test data only: never send anything to real customers or prospects for a test.
1. **Prepare safe test data** (the user does this, or confirms existing data is fine to read):
- Option A: use last week's real sends as they are. Reading is safe; the test post goes only to `{TEST_CHANNEL}` or this chat.
- Option B: the user sends one test email from their inbox to an address they control outside `{YOUR_COMPANY_DOMAINS}` (not a customer), with `{SEND_LABEL}` applied and subject "Test update: recap check".
- Optionally, the user also sends one internal-only email with `{SEND_LABEL}` so we can check it gets excluded.
2. **Run Weekly Updates Recap manually** with the post target set to `{TEST_CHANNEL}` (or "show me the draft here").
3. **Verify the checklist together:**
| Check | Pass? |
|---|---|
| Window dates and time zone are correct | ☐ |
| Each connected source shows worked / no data / unavailable | ☐ |
| Known sends from last week appear once each (duplicates merged, sources listed) | ☐ |
| Internal-only email was excluded | ☐ |
| Items are grouped under the right type headers with one-line summaries | ☐ |
| Stats appear where available, "n/a" where not | ☐ |
| Totals, top email and gaps are present and make sense | ☐ |
| **No recipient names, email addresses or personal details** in the post | ☐ |
| Formatting looks right in Slack/Teams (bold, links, bullets; thread replies if long) | ☐ |
| Nothing was changed in Salesforce, HubSpot or inboxes | ☐ |
| **No email was sent to anyone** | ☐ |
| (Optional) Disconnect-all test: failure notice wording is correct (check the text in the skill, no need to break real connections) | ☐ |
4. Fix anything that failed, re-run, then ask the user whether to post the approved version to `{TEAM_CHANNEL}` now or wait for Monday. The user deletes the test email if Option B was used.
## 9. Final status checklist
When you finish, send the user a status summary in this format:
**✅ Done by me**
- [ ] Discovery table shared
- [ ] Placeholder values confirmed
- [ ] Required skills/operators attached: …
- [ ] Optional add-ons attached: …
- [ ] Weekly Updates Recap skill created (or full text handed over for copy-paste)
- [ ] Scheduled task "Monday Customer Updates Recap" created for `{RUN_TIME}`
- [ ] Test run completed and posted to `{TEST_CHANNEL}` / shown in chat; results: …
**⏳ Waiting on you**
- [ ] Sign in to: …
- [ ] Add me to `{TEAM_CHANNEL}` (and `{TEST_CHANNEL}`)
- [ ] Subscribe `{SEED_ADDRESS}` to customer lists and give me access to it
- [ ] Give me access to `{SUPPORT_INBOX}` (if used)
- [ ] Start applying `{SEND_LABEL}` to hand-sent customer emails
- [ ] Save the Weekly Updates Recap skill (if I handed it over)
- [ ] Delete the test email (if one was sent)
**💡 Optional next steps**
- [ ] Connect Salesforce or HubSpot, and HubSpot marketing, for logging checks and open/click stats
- [ ] Set up the Automated Customer Email Program use case for consistent CRM logging
- [ ] Adjust content types, stats or audience detail
- [ ] Add a short leadership version to a second channel
- [ ] Review the first month of recaps and tighten filters
Requirements
Requirements: Weekly Customer Updates Recap
Version 1.1.0 · Last updated 2026-10-22 · Estimated setup time: 30–45 minutes
Use this checklist before you hand CLONE-INSTRUCTIONS.md to your clone. Your clone will also check most of this during discovery.
1. Required skills / operators
Use the exact names below. 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 | GoogleGmailOperator (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 |
2. Required connections and permissions
| Connection | Minimum permission | Why |
|---|---|---|
| Email (Gmail or Outlook) | Read messages, Sent folder and labels/categories | Find hand-sent customer emails and seed copies. No send needed |
| Slack / Teams | Post messages and thread replies in {TEAM_CHANNEL} | Publish the recap. Clone must be a member of the channel |
| Salesforce or HubSpot (if used) | Read tasks/activities and email activity | Find [Customer Email] logs and synced sends. No write access needed |
| HubSpot marketing (if used) | Read marketing emails, lists, and reports (opens/clicks) | Send list and stats |
| Seed / support inbox (if used) | Read (connected, delegated, or forwarded to the clone) | Catch marketing copies and support announcements |
All connections are made by you through sign-in (OAuth). Your clone never needs your password.
3. Optional add-ons
| Add-on | Adds | Operators |
|---|---|---|
| Salesforce or HubSpot | The [Customer Email] log, synced marketing activity, and the "Missing from CRM log" gap check | SalesforceActivityOperator, SalesforceAccountOperator; or HubspotEngagementOperator, HubspotCompanyOperator |
| HubSpot marketing | Full send list, lists/audiences, open/click totals, top email | HubspotMarketingOperator |
Seed address ({SEED_ADDRESS}) | Catches every list send even without a HubSpot marketing connection | A team mailbox subscribed to your customer lists |
Shared support inbox ({SUPPORT_INBOX}) | Customer announcements sent by support | support@ / help@ mailbox |
| Automated Customer Email Program use case | Consistent CRM logging of each send | Companion use case in this library |
Strongly recommended: Salesforce or HubSpot, or HubSpot marketing. With only the inbox, the recap still works but has no stats and no logging check.
Salesforce to HubSpot concept mapping
| Generic concept | Salesforce | HubSpot |
|---|---|---|
| Account / company (not used in the post) | Account (SalesforceAccountOperator) | Company (HubspotCompanyOperator) |
| Contact (never shown in the post) | Contact (SalesforceContactOperator) | Contact (HubspotContactOperator) |
Activity / task ([Customer Email] log) | Task, Status = Completed (SalesforceActivityOperator) | Task (completed), note or logged email (HubspotEngagementOperator) |
| Synced marketing email activity | Synced Tasks / email activity | Marketing email engagements (HubspotMarketingOperator) |
| Subject field | Subject | Task title / Email subject |
| Custom fields (e.g. list/audience) | Custom field on Task | Custom property |
Field and object names vary by setup and integration. Your clone confirms what it can read during discovery.
Google to Microsoft 365, and Slack to Teams
| Concept | Google Workspace | Microsoft 365 |
|---|---|---|
| Gmail (GoogleGmailOperator) | Outlook email operator | |
{SEND_LABEL} | Label | Category |
| Shared support inbox | Delegated mailbox or Google Group | Shared mailbox |
| Seed address | Any Gmail mailbox you can connect or forward | Any mailbox you can connect or forward |
| Concept | Slack | Microsoft Teams |
|---|---|---|
{TEAM_CHANNEL} | Channel (e.g. #customer-updates) | Team › Channel |
| Add the clone | /invite @{CLONE_NAME} in the channel | Add the app to the team/channel (admin may need to allow the app) |
| Formatting | mrkdwn: *bold*, <url\|title> | Markdown: **bold**, [title](url) |
| Long recaps | Thread replies under the main post | Replies under the main post |
4. Data prerequisites
- At least one source of sends exists: Salesforce or HubSpot log, HubSpot marketing, labeled Sent items, or a seed address.
- CRM logging convention (Salesforce or HubSpot, if used): sends logged as completed tasks with subject
[Customer Email] {Type} – {Title}. - Seed address subscribed to every customer list/audience, and not suppressed or unsubscribed.
- Hand-sent customer emails are labeled with
{SEND_LABEL}in mailboxes the clone can read. - Consistent titles: the same piece of content uses the same title across sources (helps de-duplication).
- Web version links enabled in HubSpot marketing (so the recap can link to each email).
- You know your
{YOUR_COMPANY_DOMAINS}so internal mail can be excluded.
5. Supported platforms
| Area | Supported | Notes |
|---|---|---|
| Gmail (GoogleGmailOperator), Outlook / Microsoft 365 | Read-only | |
| Chat | Slack, Microsoft Teams | Delivery only. Clone must be a member of the channel |
| CRM | Salesforce, HubSpot | See mapping above |
| Marketing platform | HubSpot (HubspotMarketingOperator) only | If read tools fail, the source is skipped and noted |
6. Roles and permissions
| Who | Needs to |
|---|---|
| Clone admin (owner of the clone in the Clone platform) | Attach skills/operators, approve the plan, save the skill, create/approve the scheduled task |
| Connection owner(s) | Complete OAuth sign-in for email, chat, Salesforce or HubSpot, and HubSpot marketing (a CRM or marketing admin may need to grant read access) |
| Slack / Teams admin or channel owner | Add the clone to {TEAM_CHANNEL}; in Teams, allow the app if apps are restricted |
| Marketing owner | Subscribe {SEED_ADDRESS} to customer lists in HubSpot; confirm reporting access |
| Mailbox owner(s) | Delegate {SUPPORT_INBOX} or the seed inbox to the clone; apply {SEND_LABEL} to hand-sent updates |
| Team (CS, Marketing, Support, Leadership) | Read the recap on Mondays |
7. Estimated setup time
| Step | Time |
|---|---|
| Pre-flight check (this doc) | 5 min |
| Clone discovery + placeholders + plan | 10 min |
| Your sign-ins, channel invite, seed and inbox access | 10–15 min |
| Save skill + scheduled task | 5 min |
| Test run | 5–10 min |
| Total | 30–45 min |
8. Pre-flight checklist
- I'm the clone admin (or have one available)
- Email operator (Gmail or Outlook) attached (or can be), with read access to Sent and labels
- Slack or Teams connection attached (or can be), able to post
- I can add the clone to
{TEAM_CHANNEL}(or know who can) - I can create scheduled tasks (or the clone can)
- (Optional) Salesforce or HubSpot operators available and I can sign in with read access
- (Optional) HubspotMarketingOperator available, with reporting access
- (Optional) Seed address exists and is subscribed to customer lists
- (Optional) Support inbox can be shared with the clone
- I've decided
{TEAM_CHANNEL},{RUN_TIME}and{RECAP_TIME_ZONE} - I have a private test channel (or I'm fine reviewing the draft in chat)
9. You're ready when…
- ✅ Every required item in section 1 is attached and its connection is signed in.
- ✅ The clone is a member of
{TEAM_CHANNEL}. - ✅ At least one source of customer sends is readable by the clone.
- ✅ You have answers for the placeholder questions.
- ✅ You've set aside ~10 minutes for the test run.
Then download CLONE-INSTRUCTIONS.md and give it to your clone.
Was this use case helpful?
Thanks!