Communitygithub.com

電子郵件序列設計

當使用者想要建立或優化電子郵件序列、滴灌式行銷活動、自動化電子郵件流程或生命週期電子郵件方案時使用。

電子郵件序列設計 是什麼?

此技能旨在幫助 AI 代理設計高效的電子郵件行銷序列,涵蓋歡迎、培育、重新參與、入職等多種情境。它強調整封郵件一個任務、先提供價值再要求行動、以及品質重於頻率的原則。技能中包含詳細的策略指南,例如序列長度(歡迎序列3-7封)、發送時機(B2B避免週末)、主旨行模式(提問、教學、列舉)以及預覽文字的最佳實務。它也支援多種工具整合,如 Customer.io、Mailchimp、SendGrid 等,並提供輸出格式(序列概覽、每封郵件細節、指標計畫)。此外,技能會檢查產品行銷背景文件以減少重複提問,適合用於 Claude Code、Cursor、Codex 等 AI 代理平台,幫助使用者自動化或優化郵件行銷策略。

相容平台✓Claude Code~Codex CLI~Cursor
npx skills add https://github.com/coreyhaines31/marketingskills/tree/main/skills/emails

在你喜歡的 AI 中提問

開啟一個已預先載入此 Agent Skill 的新對話。

說明文件

電子郵件序列設計 是做什麼的?

您是電子郵件行銷與自動化的專家。您的目標是建立能夠培養關係、驅動行動,並推動人們邁向轉換的電子郵件序列。

初始評估

首先檢查產品行銷背景: 如果 .agents/product-marketing.md 存在(或 .claude/product-marketing.md,或舊版設定中的 product-marketing-context.md 檔案),請先閱讀它。利用這些背景資訊,僅針對尚未涵蓋或需特定於此任務的資訊提問。

建立序列前,需了解:

  1. 序列類型

    • 歡迎/入職序列
    • 潛在客戶培育序列
    • 重新參與序列
    • 購買後序列
    • 事件觸發序列
    • 教育序列
    • 銷售序列
  2. 受眾背景

    • 他們是誰?
    • 是什麼觸發他們進入此序列?
    • 他們已經知道/相信什麼?
    • 他們目前與您的關係如何?
  3. 目標

    • 主要轉換目標
    • 關係建立目標
    • 分眾目標
    • 如何定義成功?

核心原則

1. 一封郵件,一個任務

  • 每封郵件只有一個主要目的
  • 每封郵件只有一個主要 CTA
  • 不要試圖一次完成所有事情

2. 先提供價值,再要求行動

  • 以實用性為開端
  • 透過內容建立信任
  • 贏得銷售的權利

3. 相關性勝於數量

  • 較少但更好的郵件勝出
  • 針對相關性進行分眾
  • 品質 > 頻率

4. 明確的前進路徑

  • 每封郵件都將他們導向某處
  • 連結應具有實用目的
  • 讓下一步清晰可見

電子郵件序列策略

序列長度

  • 歡迎:3-7 封
  • 潛在客戶培育:5-10 封
  • 入職:5-10 封
  • 重新參與:3-5 封

取決於:

  • 銷售週期長度
  • 產品複雜度
  • 關係階段

發送時機/延遲

  • 歡迎郵件:立即
  • 前期序列:間隔 1-2 天
  • 培育:間隔 2-4 天
  • 長期:每週或每兩週

考量:

  • B2B:避免週末
  • B2C:測試週末
  • 時區:在當地時間發送

主旨行策略

  • 清楚 > 聰明
  • 具體 > 模糊
  • 以利益或好奇心驅動
  • 理想長度 40-60 個字元
  • 測試表情符號(它們具有兩極化效果)

有效的模式:

  • 提問:「還在為 X 困擾嗎?」
  • 教學:「如何在 [時間] 內達成 [成果]」
  • 列舉:「3 種 [好處] 的方法」
  • 直接:「[名字],您的 [東西] 已準備好」
  • 故事預告:「我在 [主題] 上犯的錯誤」

預覽文字

  • 延伸主旨行
  • 約 90-140 個字元
  • 不要重複主旨行
  • 完成想法或增添懸念

序列類型概述

歡迎序列(註冊後)

長度:5-7 封郵件,為期 12-14 天 目標:激活、建立信任、轉換

關鍵郵件:

  1. 歡迎 + 提供承諾價值(立即)
  2. 快速勝利(第 1-2 天)
  3. 故事/原因(第 3-4 天)
  4. 社會證明(第 5-6 天)
  5. 克服異議(第 7-8 天)
  6. 核心功能亮點(第 9-11 天)
  7. 轉換(第 12-14 天)

潛在客戶培育序列(銷售前)

長度:6-8 封郵件,為期 2-3 週 目標:建立信任、展示專業、轉換

關鍵郵件:

  1. 提供誘餌 + 介紹(立即)
  2. 擴展主題(第 2-3 天)
  3. 問題深入探討(第 4-5 天)
  4. 解決方案框架(第 6-8 天)
  5. 案例研究(第 9-11 天)
  6. 差異化(第 12-14 天)
  7. 異議處理(第 15-18 天)
  8. 直接提案(第 19-21 天)

重新參與序列

長度:3-4 封郵件,為期 2 週 觸發條件:30-60 天不活躍 目標:贏回用戶或清理名單

關鍵郵件:

  1. 關懷問候(真誠關心)
  2. 價值提醒(有什麼新功能)
  3. 誘因(特別優惠)
  4. 最後機會(停留或取消訂閱)

入職序列(產品用戶)

長度:5-7 封郵件,為期 14 天 目標:激活、驅動至驚喜時刻、升級 注意:與應用內入職協調——郵件支援而非重複

關鍵郵件:

  1. 歡迎 + 第一步(立即)
  2. 開始使用協助(第 1 天)
  3. 功能亮點(第 2-3 天)
  4. 成功故事(第 4-5 天)
  5. 進度檢查(第 7 天)
  6. 進階技巧(第 10-12 天)
  7. 升級/擴展(第 14 天以上)

詳細範本:請參閱 references/sequence-templates.md


按分類的郵件類型

入職郵件

  • 新用戶系列
  • 新客戶系列
  • 關鍵入職步驟提醒
  • 新用戶邀請

留存郵件

  • 升級為付費
  • 升級至更高方案
  • 邀請評價
  • 主動提供支援
  • 產品使用報告
  • NPS 調查
  • 推薦計畫

帳單郵件

  • 切換為年付
  • 付款失敗補救
  • 取消調查
  • 即將續約提醒

使用郵件

  • 每日/每週/每月摘要
  • 關鍵事件通知
  • 里程碑慶祝

贏回郵件

  • 試用過期
  • 已取消客戶

行銷活動郵件

  • 每月精選/電子報
  • 季節性促銷
  • 產品更新
  • 業界新聞摘要
  • 定價更新

詳細郵件類型參考:請參閱 references/email-types.md


郵件文案指南

結構

  1. 鉤子:第一行抓住注意力
  2. 背景:為什麼這對他們重要
  3. 價值:有用的內容
  4. 行動呼籲(CTA):下一步要做什麼
  5. 結尾:人性化、溫暖的結束

格式

  • 短段落(1-3 句)
  • 區塊間留白
  • 項目符號便於掃讀
  • 粗體強調(適量使用)
  • 行動裝置優先(多數在手機上閱讀)

語氣

  • 對話式,非正式
  • 第一人稱(我/我們)和第二人稱(你)
  • 主動語態
  • 大聲朗讀——聽起來像人類嗎?

長度

  • 交易型:50-125 字
  • 教育型:150-300 字
  • 故事驅動型:300-500 字

CTA 指南

  • 主要動作使用按鈕
  • 次要動作使用連結
  • 每封郵件一個明確的主要 CTA
  • 按鈕文字:動作 + 成果

詳細文案、個人化和測試指南:請參閱 references/copy-guidelines.md


輸出格式

序列概覽

序列名稱:[名稱]
觸發條件:[啟動序列的條件]
目標:[主要轉換目標]
長度:[郵件數量]
發送時機:[郵件間隔]
退出條件:[何時離開序列]

每封郵件

郵件 [#]:[名稱/目的]
發送時間:[時機]
主旨:[主旨行]
預覽文字:[預覽文字]
內文:[完整文案]
CTA:[按鈕文字] → [連結目的地]
分眾/條件:[如適用]

指標計畫

需要衡量的事項及基準


任務特定問題

  1. 進入此序列的觸發條件是什麼?
  2. 主要目標/轉換動作是什麼?
  3. 他們已經對您了解多少?
  4. 他們正在接收哪些其他郵件?
  5. 您目前的郵件成效如何?

工具整合

關於實作,請參閱工具註冊表。關鍵郵件工具:

工具最適合MCP指南
Customer.io行為基礎自動化-customer-io.md
MailchimpSMB 郵件行銷✓mailchimp.md
NitrosendAI 原生郵件(透過提示的序列)✓nitrosend.md
Resend開發者友好的交易郵件✓resend.md
SendGrid大規模交易郵件-sendgrid.md
Kit創作者/電子報聚焦-kit.md

相關技能

  • lead-magnets:用於規劃引導進入培育序列的誘餌
  • churn-prevention:用於取消流程、挽留方案和催繳策略(郵件支援此功能)
  • onboarding:用於應用內入職(郵件支援此功能)
  • copywriting:用於郵件連結的登陸頁面
  • ab-testing:用於測試郵件元素
  • popups:用於郵件捕獲彈出視窗
  • revops:用於觸發郵件序列的生命週期階段

Individual skills in this repo

This repo contains 20 individual skills — each has its own dedicated page.

ab-testing

When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions

ads

When the user wants help with paid advertising campaigns on Google Ads, Meta (Facebook/Instagram), LinkedIn, Twitter/X, or other ad platforms. Also use when the user mentions

ai-seo

When the user wants to optimize content for AI search engines, get cited by LLMs, or appear in AI-generated answers. Also use when the user mentions

analytics

When the user wants to set up, improve, or audit analytics tracking and measurement. Also use when the user mentions

aso

When the user wants to audit or optimize an App Store or Google Play listing. Also use when the user mentions

attribution

When the user wants to figure out which marketing actually drives conversions and revenue, choose or interpret an attribution model, or reconcile conflicting numbers across tools. Also use when the user mentions

churn-prevention

When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions

cold-email

Write B2B cold emails and follow-up sequences that get replies. Use when the user wants to write cold outreach emails, prospecting emails, cold email campaigns, sales development emails, or SDR emails. Also use when the user mentions

co-marketing

When the user wants to find co-marketing partners, plan joint campaigns, or brainstorm partnership opportunities. Use when the user says

community-marketing

Build and leverage online communities to drive product growth and brand loyalty. Use when the user wants to create a community strategy, grow a Discord or Slack community, manage a forum or subreddit, build brand advocates, increase word-of-mouth, drive community-led growth, engage users post-signup, or turn customers into evangelists. Trigger phrases: \

competitor-profiling

When the user wants to research, profile, or analyze competitors from their URLs. Also use when the user mentions

competitors

When the user wants to create competitor comparison or alternative pages for SEO and sales enablement. Also use when the user mentions

content-strategy

When the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also use when the user mentions

copy-editing

When the user wants to edit, review, or improve existing marketing copy, or refresh outdated content. Also use when the user mentions

copywriting

When the user wants to write, rewrite, or improve marketing copy for any page — including homepage, landing pages, pricing pages, feature pages, about pages, or product pages. Also use when the user says

coreyhaines31/ab-test-setup

When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program," or "experiment playbook." Use this whenever someone is comparing two approaches and wants to measure which performs better, or when they want to build a systematic experimentation practice. For tracking implementation, see analytics-tracking. For page-level conversion optimization, see page-cro.

coreyhaines31/analytics-tracking

When the user wants to set up, improve, or audit analytics tracking and measurement. Also use when the user mentions "set up tracking," "GA4," "Google Analytics," "conversion tracking," "event tracking," "UTM parameters," "tag manager," "GTM," "analytics implementation," "tracking plan," "how do I measure this," "track conversions," "attribution," "Mixpanel," "Segment," "are my events firing," or "analytics isn't working." Use this whenever someone asks how to know if something is working or wants to measure marketing results. For A/B test measurement, see ab-test-setup.

coreyhaines31/aso-audit

When the user wants to audit or optimize an App Store or Google Play listing. Also use when the user mentions 'ASO audit,' 'app store optimization,' 'optimize my app listing,' 'improve app visibility,' 'app store ranking,' 'audit my listing,' 'why aren't people downloading my app,' 'improve my app conversion,' 'keyword optimization for app,' or 'compare my app to competitors.' Use when the user shares an App Store or Google Play URL and wants to improve it.

coreyhaines31/competitor-alternatives

When the user wants to create competitor comparison or alternative pages for SEO and sales enablement. Also use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'comparison page,' '[Product] vs [Product],' '[Product] alternative,' 'competitive landing pages,' 'how do we compare to X,' 'battle card,' or 'competitor teardown.' Use this for any content that positions your product against competitors. Covers four formats: singular alternative, plural alternatives, you vs competitor, and competitor vs competitor. For sales-specific competitor docs, see sales-enablement.

coreyhaines31/email-sequence

When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," "lifecycle emails," "trigger-based emails," "email funnel," "email workflow," "what emails should I send," "welcome series," or "email cadence." Use this for any multi-email automated flow. For cold outreach emails, see cold-email. For in-app onboarding, see onboarding-cro.

相關技能