A daily customer email, picked, built and queued by your clone
Your clone chooses the update worth sending today, builds it in your brand template and sends it once you approve.
Every day your clone looks at your content calendar and the updates customers haven't heard about yet, picks the most important one, and builds an on-brand email. You approve it, it sends through HubSpot or your own inbox, and every send is logged so nothing goes out twice.
What your clone does
You ship features, videos and posts that customers never hear about, because writing the email is always tomorrow's job. Your clone makes it today's job, every day.
Most companies ship far more useful things than their customers ever hear about. New features land in release notes nobody reads. Great videos and blog posts get one social post and disappear. Customer emails go out when someone finds the time, which is rarely.
The Automated Customer Email Program fixes that. Every day at {RUN_TIME} your clone:
- reads your content calendar and a backlog of unsent updates (release notes, blog, videos, social posts, knowledge base),
- picks the day's best email using a fixed priority order,
- writes it in one of six email types (plus a fallback for slow days),
- builds it in your branded HTML template,
- checks send history so nobody gets the same thing twice,
- sends a preview to you for approval (always, during the first
{APPROVAL_PERIOD}), - sends it through the right channel: HubSpot marketing email for list sends, or 1:1 from Gmail or Outlook for personalized ones,
- logs every send (inbox label/category, Salesforce or HubSpot task for 1:1 sends, HubSpot's own send history for list sends) and emails you a short summary.
What you get:
| Benefit | What it looks like |
|---|---|
| A steady drumbeat | Customers hear from you on a predictable cadence, not "when someone has time" |
| More feature adoption | Every new feature and update gets a proper customer email |
| Content that works twice | Videos, blogs and posts get a second life in the inbox (videos can optionally be produced with Clone Automated Video) |
| Personal touch at scale | Role and use-case highlights go 1:1, written for that person |
| No duplicates | Send history is checked before every send |
| You stay in control | Nothing goes out without your "approve" until you choose auto-send |
The six email types (plus a fallback)
| # | Type | What it is | Usual channel |
|---|---|---|---|
| 1 | Video highlight | Short intro + video thumbnail with a play button, linking out to the video | HubSpot marketing email |
| 2 | Blog / long-form | A blog post or article rewritten for the email (not just a link) | HubSpot marketing email |
| 3 | "Did you know?" tip | One practical tip, how to use it, one button | HubSpot marketing email |
| 4 | Role / use-case highlight | "How teams like yours use X", personalized per contact | 1:1 from inbox |
| 5 | Skill / feature highlight | A new or updated feature: what it does, why it matters, how to start | HubSpot marketing email (or 1:1 for a targeted segment) |
| 6 | Industry / comparison | Industry trend, benchmark or "how we compare" piece | HubSpot marketing email |
| Fallback | Social post highlight | A recent social post worth sharing, for slow days | HubSpot marketing email |
Daily priority order
When more than one thing is ready, the clone picks the first available in this order:
New feature → Feature update → Video (relevant, not yet sent) → Blog → Tip → Industry / comparison → Social post (fallback)
Anything already scheduled for today in {CONTENT_CALENDAR} wins over the priority order.
Who it helps
- Marketing teams who want a consistent customer newsletter-style program without building every email by hand.
- Customer Success teams who want customers to adopt new features and see relevant use cases.
- Product marketing who need every release to reach customers, not just the changelog.
- Small teams with lots of content (videos, blogs, docs) and no one with time to turn it into emails.
It is built for current customers (as defined by {CUSTOMER_DEFINITION}). It is not a cold outreach or prospecting tool.
How it runs
┌───────────────────────────────────────────────────────────────────┐
│ Your content: {CONTENT_CALENDAR} + {CONTENT_SOURCES} │
│ (release notes · blog feed · video channel · social · KB) │
└───────────────────────────────┬───────────────────────────────────┘
│
Every day at {RUN_TIME} (scheduled task)
│
▼
┌───────────────────────────────────────────────────────────────────┐
│ "Customer Email Program" skill │
│ │
│ 1. Read calendar + backlog ──► candidate items │
│ 2. Check send history ──► drop anything already sent │
│ 3. Pick today's email ──► calendar first, then │
│ new feature > update > video > blog > tip > │
│ industry/comparison > social fallback │
│ 4. Choose audience + channel ──► {LIST_ALL} / {LIST_SEGMENT} │
│ or 1:1 personalized │
│ 5. Apply {CADENCE_RULES} ──► who is due today │
│ 6. Write copy + build branded HTML ({BRAND_COLORS}, {LOGO_URL}) │
│ 7. Preview to {APPROVER} ──► wait for "approve" │
└───────────────────────────────┬───────────────────────────────────┘
│ "approve"
▼
┌───────────────────────────────────────────────────────────────────┐
│ Send │
│ List send ──► HubSpot marketing email ──► HubSpot CRM records │
│ 1:1 ──► {CLONE_INBOX} / {SENDER_INBOX} (Gmail/Outlook) │
│ ──► label/category {SEND_LABEL} │
│ ──► completed Salesforce/HubSpot task per contact │
│ Daily summary ──► {APPROVER} │
└───────────────────────────────────────────────────────────────────┘How it routes each email
| Situation | Channel | How it's logged |
|---|---|---|
| Same message for everyone | HubSpot marketing email, to {LIST_ALL} | HubSpot send history + HubSpot CRM records |
| Same message for one group (e.g. one product tier) | HubSpot marketing email, to {LIST_SEGMENT} | HubSpot send history + HubSpot CRM records |
| Personalized per contact (role / use-case highlight) | 1:1 from {CLONE_INBOX} or {SENDER_INBOX} | Inbox label/category {SEND_LABEL} + completed task (Salesforce or HubSpot) |
The CRM task subject is internal only: [Customer Email] {Type} – {Title} (for example [Customer Email] Feature – Bulk export). Customers never see it. The customer-facing subject line never contains tags or internal labels.
Set it up, step by step
- Check requirements (10 min)Open REQUIREMENTS.md and run through the pre-flight checklist. You need Gmail or Outlook, HubSpot marketing email (HubSpot Marketing Operator), a Salesforce or HubSpot CRM operator, access to your content calendar (Google Sheets, Excel or a doc), and scheduled tasks.
- Hand the instructions to your clone (2 min)Paste or upload CLONE-INSTRUCTIONS.md and say: "Please set up this use case for me. Show me a plan before changing anything."
- Review the discovery table (5 min)The clone reports which skills/operators and connections it has and which are missing.
- Answer the placeholder questions (10–15 min)See section 6. The list names and cadence rules take the most thought.
- Approve the plan (2 min)Say "yes" only when the plan looks right.
- Do your part (20–40 min)- Sign in (OAuth) to Gmail or Outlook, HubSpot, your CRM (Salesforce or HubSpot) and any content source connections. - Share {CONTENTCALENDAR} and content folders with the clone. - Create a custom coded template in HubSpot (Design Manager). The clone gives you the HTML to paste. - Make sure your logo and email images are publicly hosted. - Create the {SENDLABEL} label (Gmail) or category (Outlook) if the clone can't.
- Save the skill and scheduled tasks (10 min)If the clone can't create custom skills directly, it gives you the full text to paste. Read it before you save it.
- Run the test plan (20–30 min)The clone sends test emails to internal test addresses only. You check them in real inboxes (Gmail, Outlook desktop, Apple Mail, phone).
- Go live with approval onFor the first {APPROVALPERIOD}, approve each day's email. After that, you can switch to auto-send with a daily summary.
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. Your clone will report the names it finds in your catalog.
Skill names can differ slightly between orgs. Confirm the exact names in your skill catalog before saving the skill.
| # | Skill / operator | What it's used for | Notes |
|---|---|---|---|
| 1 | Gmail (Google Gmail Operator) or Outlook (email operator) | Previews, 1:1 sends, daily summary, reading approval replies, labeling sends | The clone's own inbox ({CLONE_INBOX}), plus send access to {SENDER_INBOX} if used |
| 2 | HubSpot marketing email (HubSpot Marketing Operator) | Build, test-send and send list/segment emails; read send history and unsubscribes | Required for list sends. Lists and segments live in HubSpot. If it can only create drafts, you click Send after approving |
| 3 | Salesforce: Salesforce Contact Operator, Salesforce Activity Operator or HubSpot: HubSpot Contact Operator, HubSpot Engagement Operator | Find contacts for 1:1 emails, check opt-outs, log completed tasks, read past send tasks | Choose one CRM; see the mapping in section 3 |
| 4 | Content calendar: Google Sheets Operator or Microsoft Excel (or a doc via Google Docs Core Operator / Microsoft Word) | Read {CONTENT_CALENDAR} | Google Sheet, Excel file or document |
| 5 | Scheduled task (platform) | Daily run at {RUN_TIME} and the approval check until {SEND_WINDOW_END} | Platform feature; the clone may be able to create it |
Good to know
- Send fatigue is the biggest risk. Daily email is only right for customers who want it. Start lighter than you think, watch unsubscribes, and use
{CADENCE_RULES}to keep free or low-engagement users on a weekly digest. - Outlook renders email differently. Outlook desktop ignores a lot of modern CSS. The template uses tables, inline CSS and a 600px width for this reason. Always test in real inboxes: Gmail (web and app), Outlook desktop, Apple Mail and a phone. A preview pane is not a real test.
- Image formats. Avoid Web P (it breaks in some Outlook versions). Use PNG, JPG or GIF. Keep images under ~1 MB.
- Host images publicly. Images must load without a login. Images in Google Drive, SharePoint or behind your app's login show as broken boxes. Use HubSpot's file manager, your website, or a CDN for
{LOGO_URL}and thumbnails. - HubSpot needs a custom coded template to accept raw HTML. Drag-and-drop editors will rewrite or reject pasted HTML. Create a coded template in HubSpot's Design Manager and use that.
- Keep internal sales language out of customer copy. Words like "upsell", "expansion", "at-risk", "health score", "tier 1 account" or deal details must never appear in customer emails. The skill checks for this, but read your previews.
- Never put tags in customer-facing subject lines.
[Customer Email]belongs in the internal CRM task subject only. - Laws and consent (CAN-SPAM, GDPR, CASL and others). Every commercial email needs a working unsubscribe and your physical address. Only email people who are allowed to receive it. 1:1 emails from an inbox still count: the clone honors opt-outs and includes a simple opt-out line. Check with whoever owns compliance at your company.
- List hygiene. Bounces, unsubscribes and do-not-email flags must be respected in both HubSpot list sends and 1:1 sends (a HubSpot unsubscribe does not automatically update a Salesforce opt-out flag, so check both if you use Salesforce). Keep
{LIST_ALL}a dynamic list that excludes them automatically. - Link tracking. HubSpot rewrites links for click tracking. That's normal, but it can break links that are already shortened or redirected. Use full, direct URLs. Add UTM tags if you want website analytics to show the source.
- 1:1 sending limits. Gmail and Microsoft 365 have daily sending limits, and bulk-looking 1:1 email can hurt deliverability. Keep
{DAILY_1TO1_CAP}modest and personalize for real. - The clone can only see what's shared with it. If the content calendar, a video channel or a release notes folder isn't shared or connected, it can't use it.
- Read every instruction before saving it into a skill. You're responsible for what your clone sends.
Questions, answered
Which marketing email tool does this use?
HubSpot marketing email (HubSpot Marketing Operator) is the only tool for list and segment sends today. If you don't use HubSpot marketing email, you can still use the 1:1 types from Gmail or Outlook.
What if the HubSpot operator can only create drafts?
Then the clone builds the draft and test send, and you click Send in HubSpot after approving. It still logs everything else.
Does this work with my CRM?
Yes, if your CRM is Salesforce or HubSpot. The clone logs each 1:1 send as a completed task (Salesforce Activity Operator or HubSpot Engagement Operator). List sends are logged through HubSpot's own CRM records. See the Salesforce to HubSpot mapping in REQUIREMENTS.md.
Will the clone email customers during setup?
No. During setup and testing it only emails internal test addresses that you give it.
Can I keep approval on forever?
Yes. Many teams do. Auto-send is optional.
Who do 1:1 emails come from?
From {CLONEINBOX} by default, or from {SENDERINBOX} if you give the clone send access to a team inbox. Replies go to that inbox, so make sure someone (or the clone) watches it.
What happens to replies?
Replies land in the sending inbox. The clone flags them in the daily summary. It does not answer customers on its own as part of this use case.
What if there's nothing new to send?
It sends a tip or social post highlight, or skips the day and tells you why.
Ready when you are. So is your clone.
Build your clone, paste in the Automated Customer Email Program instructions, and approve the plan it shows you.

















