sales-cadence

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Design a Multi-Channel Outbound Cadence

设计多渠道外呼触达节奏

Help the user design a complete outbound cadence for Salesloft, Mailshake, Smartlead, Lemlist, or Yesware — from architecture and timing through full content for every step, A/B testing, and optimization benchmarks.

帮助用户为Salesloft、Mailshake、Smartlead、Lemlist或Yesware设计完整的外呼触达节奏——从架构规划、时间安排，到每个步骤的完整内容、A/B测试及优化基准。

Step 1 — Gather context

步骤1 — 收集背景信息

Ask the user:

What's the campaign goal?
- A) Cold outbound — net-new prospects, no prior relationship
- B) Inbound follow-up — responding to a lead that came in
- C) Trigger-based — responding to a signal (job change, funding round, tech install, intent data)
- D) Re-engagement — reviving a cold or stalled conversation
- E) Expansion — reaching new contacts at existing customer accounts
- F) Other — describe it
Who is the target persona? (title, seniority, industry, company size)
What channels are available?
- A) Email only
- B) Email + phone
- C) Email + phone + LinkedIn
- D) Email + phone + LinkedIn + video
- E) Other combination — describe
What constraints should I know about?
- Total duration (e.g., 14 days, 21 days, 30 days)
- Max touches per week
- Existing messaging or value props to incorporate
- Compliance requirements (GDPR, CAN-SPAM, industry-specific)
- Any channels to avoid or emphasize

If the user's request already provides most of this context, skip directly to the relevant step. Lead with your best-effort answer using reasonable assumptions (stated explicitly), then ask only the most critical 1-2 clarifying questions at the end — don't gate your response behind gathering complete context.

询问用户：

本次营销活动的目标是什么？
- A) 陌生外呼——开发全新潜在客户，无过往合作关系
- B) 线索跟进——对接主动咨询的潜在客户
- C) 触发式触达——响应特定信号（如职位变动、融资轮次、技术安装、意向数据）
- D) 激活沉睡线索——重新唤醒已停滞的沟通
- E) 客户拓展——触达现有客户的新联系人
- F) 其他——请具体描述
目标用户画像是什么？（职位、职级、行业、公司规模）
可使用的渠道有哪些？
- A) 仅邮件
- B) 邮件+电话
- C) 邮件+电话+LinkedIn
- D) 邮件+电话+LinkedIn+视频
- E) 其他组合——请具体描述
需要注意哪些限制条件？
- 总时长（如14天、21天、30天）
- 每周最大触达次数
- 需要融入的现有文案或价值主张
- 合规要求（GDPR、CAN-SPAM、行业特定规则）
- 需要避免或重点使用的渠道

如果用户的请求已包含大部分背景信息，可直接跳至对应步骤。 先基于合理假设（需明确说明）给出初步方案，最后仅询问最关键的1-2个补充问题——不要因等待完整背景而延迟回复。

Step 2 — Cadence architecture

步骤2 — 触达节奏架构设计

Design the cadence structure as a table:

Day	Step	Channel	Action	Notes
1	1	Email	Intro email (A/B subject lines)	Personalization Level 3+
1	2	LinkedIn	Profile view + connection request	Same day as email
3	3	Phone	Call attempt #1 + voicemail	Reference email
4	4	Email	Follow-up email (value-add)	Different angle from Step 1
...	...	...	...	...

以表格形式设计触达节奏结构：

天数	步骤	渠道	动作	备注
1	1	邮件	初始邮件（A/B测试主题）	个性化等级3+
1	2	LinkedIn	查看主页+发送好友申请	与邮件同一天发送
3	3	电话	首次致电+留言	提及已发送的邮件
4	4	邮件	跟进邮件（提供附加价值）	与步骤1的切入点不同
...	...	...	...	...

Design principles

设计原则

Channel mixing: Never send 3+ touches in the same channel consecutively. Alternate between email, phone, and LinkedIn.
Spacing:
- Days 1-7: Higher intensity (touch every 1-2 days) — this is when engagement peaks
- Days 8-14: Medium intensity (every 2-3 days)
- Days 15+: Lower intensity (every 3-4 days) — don't burn the prospect
Touch count by persona (typical ranges — adjust based on persona, sales cycle, and industry norms):
- C-suite / VP: 8-12 touches over 21-28 days (less aggressive, more spaced)
- Director / Manager: 12-16 touches over 21-30 days (standard)
- Individual contributor / practitioner: 10-14 touches over 14-21 days (shorter cycle)
Phone placement: Always within 24 hours after an email so you can reference it ("I just sent you a note about...")
LinkedIn: Use early for connection + later for social proof or content sharing. Don't be repetitive with email.
Final touch: Always a "breakup" email — creates urgency without being pushy

渠道混合: 请勿连续3次及以上使用同一渠道触达。交替使用邮件、电话和LinkedIn。
时间间隔:
- 第1-7天：高频率（每1-2天触达一次）——此阶段用户互动率最高
- 第8-14天：中频率（每2-3天触达一次）
- 第15天及以后：低频率（每3-4天触达一次）——避免引起潜在客户反感
按用户画像调整触达次数（典型范围——可根据用户画像、销售周期和行业惯例调整）：
- 高管/副总裁级别：21-28天内触达8-12次（节奏放缓，间隔更长）
- 总监/经理级别：21-30天内触达12-16次（标准节奏）
- 基层员工/执行人员：14-21天内触达10-14次（周期更短）
电话触达时机: 务必在发送邮件后24小时内致电，以便提及邮件内容（“我刚刚给您发送了一封关于……的邮件”）
LinkedIn使用: 早期用于发送好友申请，后期用于分享社交证明或内容。请勿与邮件内容重复。
最终触达: 务必发送一封“告别邮件”——在不显得强势的前提下制造紧迫感

Step 3 — Write content for every step

步骤3 — 撰写各步骤内容

For each step in the cadence, write the actual content:

为触达节奏中的每个步骤撰写具体内容：

Email templates

邮件模板

For each email:

Subject line: Provide A/B variants (Variant A and Variant B)
Body: Full email text with personalization tokens in
```
{{brackets}}
```
CTA: Specific ask (meeting, reply, resource)
Keep emails under 125 words for cold outbound, under 200 for warm follow-up

每封邮件需包含：

主题: 提供A/B测试变体（变体A和变体B）
正文: 完整邮件文本，使用
```
{{大括号}}
```
标记个性化变量
行动号召（CTA）: 明确的请求（如安排会议、回复邮件、获取资源）
陌生外呼邮件字数控制在125词以内，跟进邮件控制在200词以内

Call scripts

通话脚本

For each call step:

Opening (first 10 seconds — must earn the right to continue)
Reason for calling (one sentence connecting to their world)
Key questions (2-3 if they engage)
Ask (meeting request with specific time)
Voicemail script (under 30 seconds, always leave one)

每个电话触达步骤需包含：

开场（前10秒——需快速获得继续沟通的权限）
致电原因（一句话关联对方的业务场景）
核心问题（若对方回应，准备2-3个问题）
请求（提出具体时间的会议邀约）
留言脚本（30秒以内，务必留言）

LinkedIn messages

LinkedIn消息

Connection request note: Under 300 characters, no selling
Follow-up InMail or message: Reference a specific post, mutual connection, or insight about their company
Keep LinkedIn casual and conversational — it's a social platform, not email

好友申请备注: 300字符以内，避免直接推销
跟进站内信或消息: 提及对方的特定帖子、共同联系人或关于其公司的洞察
LinkedIn风格需轻松口语化——这是社交平台，而非邮件渠道

Video guidance (if applicable)

视频触达指导（若适用）

When to use: Steps 5+ when email hasn't gotten a response
Duration: 60-90 seconds max
Structure: Say their name, show you did research, one key insight, soft CTA

使用时机：邮件未获回应的第5步及之后
时长：最多60-90秒
结构：称呼对方姓名、展示你做过的调研、分享一个核心洞察、软性行动号召

In Mailshake

在Mailshake中

Mailshake campaigns = cadences — a campaign has an initial message plus follow-ups
Follow-up types: time-based (drip), reply-based, click-based (on-click message)
Channel limitation: email-first; phone/LinkedIn steps tracked manually or via another tool
A/B testing: available on higher plans — test subject lines and body content
Recipient management: add via CSV or API; only email is required

Mailshake营销活动=触达节奏——一个活动包含初始消息及后续跟进
跟进类型：基于时间（ drip ）、基于回复、基于点击（点击触发消息）
渠道限制：以邮件为主；电话/LinkedIn步骤需手动跟踪或通过其他工具实现
A/B测试：仅高级版本支持——可测试主题和正文内容
收件人管理：通过CSV或API添加；仅需提供邮箱地址

In Lemlist

在Lemlist中

Lemlist sequences = multichannel campaigns — email, LinkedIn, phone, and WhatsApp steps on automated schedules
True multichannel: LinkedIn steps (profile visit, connection request, message), in-app calling, WhatsApp (paid add-on $20/seat/month)
LinkedIn steps require Multichannel Expert plan ($99/user/month) — Email Pro is email-only
A/B testing: test subject lines, email body, and entire step variants
AI personalization: AI-generated custom variables that research each lead (LinkedIn, website, news) for Level 3-4 personalization at scale
LinkedIn safety: limit connection requests to 20-30/day, profile visits to 50-80/day to avoid account restrictions
Inbox rotation: connect multiple email accounts and Lemlist distributes sends (5 accounts per user on top plan, $9 per additional)

Lemlist序列=多渠道营销活动——邮件、LinkedIn、电话和WhatsApp步骤可按自动化日程执行
真正的多渠道支持：LinkedIn步骤（查看主页、发送好友申请、发送消息）、内置通话功能、WhatsApp（付费附加功能，20美元/席位/月）
LinkedIn步骤需订阅Multichannel Expert套餐（99美元/用户/月）——Email Pro套餐仅支持邮件
A/B测试：可测试主题、邮件正文及整个步骤的变体
AI个性化：AI生成自定义变量，自动调研每个潜在客户（LinkedIn、官网、新闻），实现规模化的3-4级个性化
LinkedIn安全限制：每日好友申请限制为20-30次，主页查看限制为50-80次，避免账号受限
收件箱轮换：可连接多个邮箱账号，Lemlist自动分配发送任务（顶级套餐支持每个用户连接5个账号，额外账号每个9美元）

In Yesware

在Yesware中

Yesware campaigns = multi-channel sequences — email, phone call reminders, LinkedIn InMail, and custom tasks on automated schedules
Sends from your inbox (Gmail/Outlook) — no third-party server, better deliverability
Personalization: dynamic fields (merge variables) for automated personalization, individual email customization
Recipient limits: 10/month (Free), 20/month (Pro), unlimited (Premium+)
A/B testing: not natively supported in campaigns — test manually by creating variant campaigns
Auto-removal: recipients who reply or book meetings are automatically removed from the campaign
Templates: shared team templates (Premium+) for consistent messaging across reps
Tracking: real-time open/click/attachment notifications to time follow-ups — see
```
/sales-email-tracking
```

Yesware营销活动=多渠道序列——邮件、电话提醒、LinkedIn站内信和自定义任务可按自动化日程执行
从个人收件箱发送（Gmail/Outlook）——无需第三方服务器，投递率更高
个性化：动态字段（合并变量）实现自动化个性化，支持单封邮件自定义
收件人限制：免费版10条/月，专业版20条/月，高级及以上版本无限制
A/B测试：活动功能不原生支持——需手动创建变体活动进行测试
自动移除：回复邮件或预约会议的收件人将自动从活动中移除
模板：高级及以上版本支持团队共享模板，确保销售代表文案一致
跟踪：实时打开/点击/附件通知，便于规划跟进时机——可查看/sales-email-tracking

In Smartlead

在Smartlead中

Smartlead campaigns = sequences — a campaign has email steps with time delays between them
Email-only by default; phone steps require SmartDialer, LinkedIn touchpoints via external tools
A/B testing: built-in variant testing (up to 26 variants A-Z) for subject lines and email body
SmartAgents: AI-powered personalization at scale — research prospects and generate custom email content per lead. Best for Level 3-4 personalization when sending to 100+ prospects.
Lead management: leads tracked by interest status within campaigns (interested, not interested, not contacted, do not contact, wrong person, completed)

Smartlead营销活动=序列——一个活动包含带时间延迟的邮件步骤
默认仅支持邮件；电话步骤需使用SmartDialer，LinkedIn触达需通过外部工具
A/B测试：内置变体测试（最多支持26个A-Z变体），可测试主题和邮件正文
SmartAgents：AI驱动的规模化个性化——自动调研潜在客户并为每个潜在客户生成定制邮件内容。适合向100+潜在客户发送3-4级个性化邮件
线索管理：在活动中按兴趣状态跟踪线索（感兴趣、不感兴趣、未联系、请勿联系、错误联系人、已完成）

In Mixmax

在Mixmax中

Where: Sequences tab in Gmail sidebar or app.mixmax.com/dashboard/sequences
Channel support: Email, phone (built-in dialer), LinkedIn (Sales Navigator InMail + connection requests), tasks
AI builder: AI Compose generates sequence emails and subject lines; Smart Send picks optimal delivery times per recipient
Personalization: Snippets (reusable templates), Salesforce/HubSpot dynamic fields, polls & surveys embedded in emails
A/B testing: Test subject lines, body content, and send times within sequences
Stages: Each sequence has ordered stages (email, call, LinkedIn, task); configure delay between stages
Recipient management: Add recipients individually, from CSV, from Salesforce/HubSpot lists, or via API (
```
POST /sequences/:id/recipients
```
)
Delegated sending: Send sequences on behalf of colleagues
Exit rules: Auto-exit on reply, meeting booked, or custom rule trigger
Limits: Recipient limits vary by plan; sequences are Gmail-native (subject to Gmail sending limits)
Reporting: Opens, clicks, replies, bounces per stage and per recipient; team-level sequence analytics
Best practice: Use Mixmax rules engine to auto-enroll contacts in sequences based on Salesforce triggers (e.g., new lead assigned → auto-enroll in introductory sequence)

入口: Gmail侧边栏的序列标签，或app.mixmax.com/dashboard/sequences
渠道支持: 邮件、电话（内置拨号器）、LinkedIn（Sales Navigator站内信+好友申请）、任务
AI构建器: AI Compose可生成序列邮件和主题；Smart Send可为每个收件人选择最佳发送时间
个性化: 代码片段（可复用模板）、Salesforce/HubSpot动态字段、邮件内嵌投票和调研
A/B测试: 可在序列中测试主题、正文内容和发送时间
阶段: 每个序列包含有序阶段（邮件、电话、LinkedIn、任务）；可配置阶段间的延迟
收件人管理: 可单独添加、通过CSV添加、从Salesforce/HubSpot列表添加，或通过API添加（
```
POST /sequences/:id/recipients
```
）
代发功能: 可代表同事发送序列邮件
退出规则: 回复邮件、预约会议或触发自定义规则时自动退出
限制: 收件人限制因套餐而异；序列基于Gmail原生功能（受Gmail发送限制约束）
最佳实践: 使用Mixmax规则引擎，基于Salesforce触发器自动将联系人加入序列（如新线索分配后→自动加入介绍性序列）

In Reply.io

在Reply.io中

Where: Sequences tab in Reply.io dashboard (app.reply.io)
Channel support: Email, LinkedIn (InMail, connection requests, profile views — $69/account add-on), calls ($29/account add-on), SMS ($29/account add-on), WhatsApp
Conditional sequences: Unique feature — set up branching logic based on prospect actions (opened, clicked, replied) or data (title, industry). Different prospects can follow different paths within the same sequence.
AI sequence builder: Jason AI can generate entire sequences based on your ICP and value prop
A/B testing: Test subject lines, body content, and step variations within sequences
Stages: Ordered steps with configurable delays; mix channels freely (e.g., email → LinkedIn → call → email)
Contact management: Add contacts individually, from CSV, from Reply.io B2B database (1B+ contacts), from Salesforce/HubSpot, or via API
Exit rules: Auto-pause on reply, meeting booked, or custom trigger; manual pause/resume per contact
Sending limits: Per-mailbox daily limits; 10 mailboxes per user on Multichannel plan; respects provider sending limits (Gmail/Outlook)
Reporting: Opens, clicks, replies, bounces per step and per contact; channel efficiency dashboard; team-level analytics
Best practice: Use conditional branching to create a single sequence that handles multiple scenarios (e.g., if prospect opens but doesn't reply → add LinkedIn step; if prospect clicks → fast-track to call step)

入口: Reply.io控制台的序列标签（app.reply.io）
渠道支持: 邮件、LinkedIn（站内信、好友申请、查看主页——69美元/账号附加功能）、电话（29美元/账号附加功能）、短信（29美元/账号附加功能）、WhatsApp
条件序列: 独特功能——可根据潜在客户行为（打开、点击、回复）或数据（职位、行业）设置分支逻辑。不同潜在客户可在同一序列中遵循不同路径
AI序列构建器: Jason AI可根据你的理想客户画像（ICP）和价值主张生成完整序列
A/B测试: 可在序列中测试主题、正文内容和步骤变体
阶段: 有序步骤，可配置延迟；自由混合渠道（如邮件→LinkedIn→电话→邮件）
联系人管理: 可单独添加、通过CSV添加、从Reply.io B2B数据库（10亿+联系人）添加、从Salesforce/HubSpot添加，或通过API添加
退出规则: 回复邮件、预约会议或触发自定义规则时自动暂停；可手动暂停/恢复单个联系人的序列
发送限制: 每个邮箱有每日发送限制；多渠道套餐支持每个用户10个邮箱；遵守邮箱服务商（Gmail/Outlook）的发送限制
报表: 按步骤和联系人统计打开、点击、回复、退信数据；渠道效率仪表盘；团队级分析
最佳实践: 使用条件分支创建单个序列，处理多种互动场景（如潜在客户打开邮件但未回复→添加LinkedIn步骤；潜在客户点击链接→快速推进至电话步骤）

In Woodpecker

在Woodpecker中

Where: Campaigns tab in Woodpecker dashboard (app.woodpecker.co)
Channel support: Email (native), LinkedIn (add-on at €29/account — connection requests, messages, profile visits), manual tasks
Condition-based campaigns: If/then branching based on prospect behavior (opened, clicked, replied) or data — different prospects follow different paths
Campaign depth: Up to 16 steps per campaign — significantly more than most competitors (typically 7-10)
A/B testing: Up to 5 variants per step — test subject lines, body copy, and send times simultaneously
Personalization: Custom fields, snippets, dynamic content based on prospect data
Auto-stop: Automatically stops sequence when prospect replies or is marked as interested
Inbox rotation: Distributes sending across multiple connected email accounts automatically — maintains per-account limits while increasing volume
Adaptive Sending: Automatically adjusts send pace based on provider limits and engagement signals
Manual tasks: Insert non-email tasks (calls, LinkedIn messages, research) as campaign steps
Reporting: Opens, clicks, replies, bounces, interested rate per step and per campaign
Best practice: Use condition-based branching to create a single campaign that handles multiple engagement scenarios. Leverage the 16-step depth for longer nurture sequences that most tools can't support.

入口: Woodpecker控制台的营销活动标签（app.woodpecker.co）
渠道支持: 邮件（原生）、LinkedIn（附加功能，29欧元/账号——好友申请、消息、查看主页）、手动任务
条件触发活动: 基于潜在客户行为（打开、点击、回复）或数据的if/then分支——不同潜在客户可遵循不同路径
活动深度: 每个活动最多支持16个步骤——远多于大多数竞品（通常7-10个）
A/B测试: 每个步骤最多支持5个变体——可同时测试主题、正文内容和发送时间
个性化: 自定义字段、代码片段、基于潜在客户数据的动态内容
自动停止: 潜在客户回复邮件或被标记为感兴趣时，序列自动停止
收件箱轮换: 自动在多个连接的邮箱账号间分配发送任务——在保持单个账号发送限制的同时提升发送量
自适应发送: 根据服务商限制和互动信号自动调整发送节奏
手动任务: 可在活动步骤中插入非邮件任务（如电话、LinkedIn消息、调研）
报表: 按步骤和活动统计打开、点击、回复、退信、感兴趣率数据
最佳实践: 使用条件分支创建单个活动，处理多种互动场景。利用16步的深度优势，创建大多数工具无法支持的长期培育序列

Personalization framework

个性化框架

Level 1 (Minimum): First name, company name, title — the bare minimum
Level 2 (Standard): Industry reference, company-size-specific pain point
Level 3 (Strong): Something specific about their company (recent news, tech stack, job posting, quarterly results)
Level 4 (Elite): Personal insight (their LinkedIn post, podcast appearance, conference talk, published article)

Recommend Level 3+ for all touches in a cold outbound cadence. Level 2 is acceptable for re-engagement at scale.

For Level 3+ at scale (100+ prospects), consider AI personalization: Smartlead SmartAgents, Clay, or custom GPT workflows to research each prospect and generate personalized snippets for {{custom_field}} merge variables. This automates the research step that makes Level 3-4 feasible at volume.

1级（基础）: 姓名、公司名称、职位——最低要求
2级（标准）: 行业参考、针对公司规模的痛点
3级（优质）: 关于其公司的特定信息（近期新闻、技术栈、招聘信息、季度业绩）
4级（精英）: 个人洞察（其LinkedIn帖子、播客嘉宾、会议演讲、发表的文章）

建议陌生外呼节奏的所有触达都采用3级及以上个性化。规模化激活沉睡线索时，2级个性化可接受。

若需规模化实现3级及以上个性化（100+潜在客户），可考虑AI个性化工具：Smartlead SmartAgents、Clay或自定义GPT工作流，自动调研每个潜在客户并为{{custom_field}}合并变量生成个性化代码片段。这可自动化调研步骤，让批量实现3-4级个性化成为可能。

Step 4 — A/B testing plan

步骤4 — A/B测试方案

Design an A/B testing strategy:

Test #	What to test	Variant A	Variant B	Metric	Min sample size
1	Subject line (Step 1)	Pain-focused	Curiosity-based	Open rate	100 sends each
2	CTA style (Step 1)	Specific time ask	Open-ended question	Reply rate	100 sends each
3	Email length (Step 4)	Short (75 words)	Medium (125 words)	Reply rate	100 sends each

设计A/B测试策略：

测试编号	测试内容	变体A	变体B	指标	最小样本量
1	步骤1主题	痛点导向	好奇心导向	打开率	各100次发送
2	步骤1行动号召风格	具体时间邀约	开放式问题	回复率	各100次发送
3	步骤4邮件长度	短（75词）	中（125词）	回复率	各100次发送

A/B testing rules

A/B测试规则

Test one variable at a time
Run each test for at least 100 sends per variant (200+ preferred) before drawing conclusions
Primary metric: positive reply rate (not just open rate)
Wait at least 5 business days before evaluating results
Roll the winner into the cadence and start the next test
Always be testing something — cadences decay over time as messaging gets stale

每次仅测试一个变量
每个变体至少发送100次（建议200+）后再得出结论
核心指标：有效回复率（而非仅打开率）
至少等待5个工作日再评估结果
将获胜变体应用到触达节奏中，然后启动下一个测试
持续测试——随着文案老化，触达节奏的效果会逐渐下降

Step 5 — Metrics and optimization

步骤5 — 指标与优化

Provide a benchmarks table:

Metric	Good	Great	If below "Good"...
Open rate	40-50%	50%+	Fix subject lines, check deliverability, verify email addresses
Reply rate (total)	8-12%	15%+	Improve personalization, test different angles, check targeting
Positive reply rate	3-5%	7%+	Revisit value prop, check ICP fit, strengthen the ask
Meeting booked rate	2-4%	5%+	Improve CTA clarity, offer more flexibility, add social proof
Bounce rate	<3%	<1%	Clean your list, use email verification tools, check domain health
Unsubscribe rate	<1%	<0.5%	Reduce frequency, improve relevance, check compliance
Call connect rate	5-10%	12%+	Try different times of day, use local presence dialing, vary call days

提供基准指标表格：

指标	良好水平	优秀水平	若低于“良好”需……
打开率	40-50%	50%+	优化主题，检查投递率，验证邮箱地址
总回复率	8-12%	15%+	提升个性化程度，测试不同切入点，检查目标用户匹配度
有效回复率	3-5%	7%+	重新审视价值主张，检查理想客户画像匹配度，强化行动号召
会议预约率	2-4%	5%+	优化行动号召清晰度，提供更多灵活性，添加社交证明
退信率	<3%	<1%	清理线索列表，使用邮箱验证工具，检查域名健康度
退订率	<1%	<0.5%	降低触达频率，提升内容相关性，检查合规性
电话接通率	5-10%	12%+	尝试不同时段，使用本地号码拨号，调整致电日期

Optimization cadence

优化节奏

Week 1-2: Let the cadence run, gather baseline data
Week 3-4: Analyze first A/B test results, implement winners
Monthly: Review full-funnel metrics, retire underperforming steps, test new angles
Quarterly: Major refresh — new messaging, updated case studies, seasonal angles

第1-2周: 运行触达节奏，收集基准数据
第3-4周: 分析首次A/B测试结果，应用获胜变体
每月: 回顾全漏斗指标，淘汰表现不佳的步骤，测试新切入点
每季度: 全面更新——新文案、更新案例研究、季节性切入点

Related skills

Gotchas

注意事项

Don't make all touches email-only. Claude defaults to generating email-heavy cadences. A real cadence needs channel mixing — if the user has phone and LinkedIn available, use them from the start, not as afterthoughts.
Don't space touches too close together. Avoid scheduling touches less than 2 business days apart (except same-day email + LinkedIn on Day 1). Prospects need time to engage before you follow up.
Don't write generic "just checking in" follow-ups. Every touch must add new value or a new angle. If you catch yourself writing "I wanted to follow up on my last email," rewrite it with a new hook.
Don't ignore timezone for call steps. Phone calls placed outside business hours are wasted touches. If you know the prospect's timezone, note the best call windows (typically 8-10am and 4-6pm local time).
Don't generate a cadence without confirming channel availability first. If the user didn't specify channels, ask — don't assume they have LinkedIn Sales Navigator or a phone dialer.

请勿仅使用邮件触达所有步骤。 Claude默认生成以邮件为主的触达节奏。真正有效的节奏需要混合渠道——若用户可使用电话和LinkedIn，从一开始就应使用这些渠道，而非作为补充。
请勿将触达间隔设置过近。 避免安排间隔少于2个工作日的触达（第1天的邮件+LinkedIn除外）。潜在客户需要时间互动后再跟进。
请勿撰写通用的“跟进提醒”邮件。 每次触达都必须添加新价值或新切入点。若你发现自己在写“我想跟进上次的邮件”，请重写为带有新钩子的内容。
请勿忽略电话步骤的时区。 在非工作时间致电纯属浪费。若知道潜在客户的时区，请标注最佳致电时段（通常为当地时间8-10点和16-18点）。
请勿在未确认渠道可用性的情况下生成触达节奏。 若用户未指定渠道，请询问——不要假设他们拥有LinkedIn Sales Navigator或电话拨号器。

Examples

示例

Example 1: Cold outbound cadence

示例1：陌生外呼触达节奏

User says: "Build a 21-day cold outbound cadence for VP Engineering at Series B SaaS companies. We have email, phone, and LinkedIn." Skill does:

Designs a 14-step cadence architecture table with channel mixing
Writes full email copy with A/B subject lines, call scripts with voicemail, LinkedIn messages
Provides an A/B testing plan and benchmark metrics Result: Complete cadence ready to import into Salesloft with content for every step

用户需求: "为B轮SaaS公司的工程副总裁设计21天的陌生外呼触达节奏。我们可使用邮件、电话和LinkedIn。" 技能执行:

设计包含14个步骤的触达节奏架构表格，采用多渠道混合
撰写完整的邮件文案（含A/B测试主题）、通话脚本（含留言）、LinkedIn消息
提供A/B测试方案和基准指标结果: 可直接导入Salesloft的完整触达节奏，包含每个步骤的内容

Example 2: Cadence optimization

示例2：触达节奏优化

User says: "My cadence has 35% open rate but only 2% reply rate. What's wrong?" Skill does:

Diagnoses the gap (subject lines work, body/CTA needs fixing)
Recommends specific changes to email body, personalization, and CTA
Designs an A/B test plan to validate improvements Result: Prioritized optimization plan with testable hypotheses

用户需求: "我的触达节奏打开率为35%，但回复率仅2%。问题出在哪里？" 技能执行:

诊断问题（主题有效，但正文/行动号召需优化）
建议对邮件正文、个性化程度和行动号召进行具体调整
设计A/B测试方案验证改进效果结果: 可落地的优化方案，包含可测试的假设

Troubleshooting

故障排查

Low open rates (<30%)

打开率低（<30%）

Cause: Subject lines aren't compelling, or deliverability issues Solution: Test pain-focused vs. curiosity-based subject lines. Check domain reputation, SPF/DKIM records, and bounce rate. If bounce rate >3%, clean your list first.

原因: 主题缺乏吸引力，或投递率问题 解决方案: 测试痛点导向与好奇心导向的主题。检查域名信誉、SPF/DKIM记录和退信率。若退信率>3%，先清理线索列表。

High open rate but low reply rate

打开率高但回复率低

Cause: Email body doesn't deliver on the subject line promise, CTA is weak or unclear, or personalization is too generic Solution: Ensure the first sentence connects to the prospect's world. Make the CTA specific ("15 minutes Thursday?") not vague ("let me know if interested"). Increase personalization to Level 3+.

原因: 邮件正文未兑现主题承诺，行动号召薄弱或不清晰，或个性化程度不足 解决方案: 确保第一句话关联潜在客户的业务场景。行动号召需具体（“周四15分钟？”）而非模糊（“若感兴趣请告知”）。将个性化程度提升至3级及以上。

Prospects engaging but not booking meetings

潜在客户互动但未预约会议

Cause: Too many touchpoints before the ask, or the ask is buried Solution: Include a clear meeting CTA by Step 3. Use the phone step within 24 hours of an email open. Offer a specific time, not an open question.

原因: 提出邀约前触达次数过多，或邀约被隐藏 解决方案: 第3步及之前需包含清晰的会议邀约。在邮件打开后24小时内进行电话触达。提供具体时间，而非开放式问题。