# 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 |
|---|---|---|
| Email | 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 |
|---|---|---|
| Email | 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.