sales-apollo-sequences

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Manage Apollo Sequences

管理Apollo序列

Help the user create, configure, and optimize outbound sequences in Apollo.io — from sequence setup through deliverability management, A/B testing, and performance analysis. For cadence strategy and messaging content, use

/sales-cadence

— this skill covers the Apollo-specific execution layer.

帮助用户在Apollo.io中创建、配置和优化外发序列——从序列设置到送达率管理、A/B测试和性能分析。如需节奏策略和消息内容相关帮助，请使用/sales-cadence——本技能仅覆盖Apollo特定的执行层面操作。

Step 1 — Gather context

步骤1 — 收集上下文信息

Ask the user:

What do you need help with?
- A) Create a new sequence from scratch
- B) Fix deliverability issues (emails going to spam, low open rates)
- C) Set up A/B testing in a sequence
- D) Analyze sequence performance and optimize
- E) Configure mailboxes and sending settings
- F) Troubleshoot a sequence that's not sending
- G) Import a sequence from another tool
- H) Other — describe it
What's your current setup?
- How many mailboxes/email accounts are connected?
- What's your daily sending volume per mailbox?
- How long have the mailboxes been active?
- Are SPF, DKIM, and DMARC configured for your sending domain?
What Apollo plan are you on?
- Free (2 active sequences, limited features)
- Basic (unlimited sequences, no A/B testing)
- Professional (A/B testing, dialer, workflows)
- Organization (advanced analytics, custom reports)

询问用户：

你需要哪方面的帮助？
- A) 从零开始创建新序列
- B) 修复送达率问题（邮件进入垃圾邮箱、打开率低）
- C) 在序列中设置A/B测试
- D) 分析序列性能并优化
- E) 配置邮箱和发送设置
- F) 排查无法发送的序列问题
- G) 从其他工具导入序列
- H) 其他——请描述具体需求
你当前的设置是什么？
- 已连接多少个邮箱/电子邮件账户？
- 每个邮箱的每日发送量是多少？
- 这些邮箱已激活多久？
- 你的发送域名是否配置了SPF、DKIM和DMARC？
你使用的是哪个Apollo套餐？
- 免费版（2个活跃序列，功能受限）
- 基础版（无限制序列，无A/B测试功能）
- 专业版（支持A/B测试、拨号器、工作流）
- 企业版（高级分析、自定义报告）

Step 2 — Sequence setup in Apollo

步骤2 — Apollo中的序列设置

Creating a sequence

创建序列

Navigate: Engage > Sequences > Create Sequence
Name: Use a descriptive name:
```
[Persona] - [Campaign type] - [Date]
```
(e.g., "VP Eng - Cold Outbound - Mar 2026")
Settings to configure:

Key settings — configure these for every sequence (non-negotiable):

Stop on reply: Always enable. Auto-pause the sequence when a prospect replies. There is zero reason to keep emailing someone who responded — it damages trust and wastes sends.
Stop on meeting booked: Always enable. Once the goal is achieved, stop the sequence.
Business hours sending: Always enable. Send during the recipient's business hours (typically 8am-6pm in their timezone). Emails arriving at 2am look automated and get buried.
Daily send limits: Start conservative — 50-100 emails/day per mailbox for warm, established mailboxes. For new mailboxes, start at 20-30/day and ramp up over 2-3 weeks. Exceeding safe limits tanks sender reputation fast.
Delay between steps: Use 2-3 business days between email steps. Shorter gaps feel aggressive; longer gaps lose momentum. Increase to 4-5 days after 3+ unreplied emails to avoid fatigue.
Sequence type: Use Automatic for email-only sequences (hands-off, sends on schedule). Use Manual for multi-channel sequences that include calls or LinkedIn steps — Auto mode skips non-email steps entirely.

Full settings reference:

Setting	Recommended value	Why
Sequence type	Auto (for email-only) or Manual (if includes calls/LinkedIn)	Auto sends emails automatically; manual requires rep action per step
Send as thread	Yes for follow-ups, No for fresh angles	Threading increases reply association but can look automated
Stop on reply	Yes	Prevents embarrassing follow-ups after a reply
Stop on meeting booked	Yes	Same reason — stop once the goal is achieved
Business hours only	Yes — match prospect timezone	Emails sent at 2am look automated
Exclude weekends	Typically yes for B2B	Weekend sends have lower engagement in most B2B contexts
Sending window	9am-11am or 1pm-3pm prospect local time	Align with when prospects check email — avoid lunch hour and end-of-day
Throttle / max per day	50-75 emails/day per mailbox (mature); 20-30/day (new)	Exceeding these limits damages sender reputation

导航路径：Engage > Sequences > Create Sequence
命名规则：使用描述性名称：
```
[目标人群] - [营销活动类型] - [日期]
```
（例如："VP Eng - 冷外发 - 2026年3月"）
需配置的设置：

关键设置——所有序列必须配置（无例外）：

收到回复即停止：始终启用。当潜在客户回复时自动暂停序列。继续向已回复的用户发送邮件毫无意义——这会损害信任并浪费发送额度。
预约会议后即停止：始终启用。一旦达成目标，立即停止序列。
仅在工作时间发送：始终启用。在收件人的工作时间内发送邮件（通常为其所在时区的上午8点至下午6点）。凌晨2点发送的邮件看起来很机械，容易被忽略。
每日发送限制：保守起步——对于已养熟的邮箱，每个邮箱每日发送50-100封邮件。对于新邮箱，起步为每日20-30封，在2-3周内逐步提升。超过安全限制会迅速损害发件人信誉。
步骤间隔时间：邮件步骤之间间隔2-3个工作日。间隔太短会显得咄咄逼人；间隔太长会失去势头。如果3封邮件都未收到回复，间隔时间增加至4-5个工作日，避免让对方产生厌烦情绪。
序列类型：仅邮件序列使用**自动（Automatic）模式（无需手动干预，按计划发送）。包含电话或LinkedIn步骤的多渠道序列使用手动（Manual）**模式——自动模式会完全跳过非邮件步骤。

完整设置参考：

设置项	推荐值	原因
序列类型	自动（仅邮件）或手动（若包含电话/LinkedIn）	自动模式自动发送邮件；手动模式需要销售代表完成每一步操作
作为线程发送	跟进邮件选是，全新角度邮件选否	线程化可提升回复关联度，但可能显得机械
收到回复即停止	是	避免在对方回复后发送尴尬的跟进邮件
预约会议后即停止	是	同理——达成目标后立即停止
仅工作时间发送	�是——匹配潜在客户时区	凌晨2点发送的邮件看起来很机械
排除周末	B2B场景通常选是	大多数B2B场景中，周末发送的邮件参与度较低
发送窗口	潜在客户当地时间上午9点-11点或下午1点-3点	与潜在客户查看邮件的时间对齐——避开午餐时间和下班前
节流/每日最大发送量	成熟邮箱50-75封/天；新邮箱20-30封/天	超过此限制会损害发件人信誉

Recommended settings by sequence type

不同序列类型的推荐设置

Sequence type	Sequence mode	Stop on reply	Business hours	Sending window	Throttle
Cold outbound (email-only)	Auto	Yes	Yes — prospect timezone	9am-11am	50/day per mailbox
Warm follow-up / inbound	Auto	Yes	Yes	8am-12pm	75/day per mailbox
Multi-channel (email + calls + LinkedIn)	Manual	Yes	Yes	9am-5pm	30-50/day per mailbox
Event/conference follow-up	Auto	Yes	No (time-sensitive)	7am-7pm	75/day per mailbox
Re-engagement (cold leads)	Auto	Yes	Yes	1pm-3pm	30/day per mailbox

Always enable stop on reply and stop on meeting booked — there is no sequence type where you want to keep emailing someone who already responded. For throttling, start conservatively and increase only after 2+ weeks of clean sending (bounce rate <3%, spam complaints near zero).

序列类型	序列模式	收到回复即停止	仅工作时间发送	发送窗口	每日发送量
冷外发（仅邮件）	自动	是	是——潜在客户时区	上午9点-11点	每个邮箱50封/天
暖跟进/ inbound	自动	是	是	上午8点-12点	每个邮箱75封/天
多渠道（邮件+电话+LinkedIn）	手动	是	是	上午9点-下午5点	每个邮箱30-50封/天
活动/会议跟进	自动	是	否（时间敏感）	上午7点-下午7点	每个邮箱75封/天
重新激活（冷线索）	自动	是	是	下午1点-3点	每个邮箱30封/天

始终启用收到回复即停止和预约会议后即停止——没有任何序列类型需要继续向已回复的用户发送邮件。关于发送量，保守起步，仅在连续2周发送数据健康（退信率<3%，垃圾邮件投诉接近零）后再逐步提升。

Adding steps

添加步骤

Step type	When to use	Apollo-specific notes
Auto email	Automated emails that send without rep action	Set sending window (9am-5pm prospect timezone)
Manual email	Emails that need personalization before sending	Appears as a task for the rep to complete
Phone call	Call steps (Professional+ plan)	Integrates with Apollo dialer; log call outcome
LinkedIn	Connection request, message, InMail	Creates a task — Apollo doesn't automate LinkedIn actions
Custom task	Any other action (send gift, research, internal follow-up)	Flexible — use for non-standard touches

步骤类型	使用场景	Apollo特定说明
自动邮件	无需销售代表操作即可自动发送的邮件	设置发送窗口（潜在客户时区上午9点-下午5点）
手动邮件	发送前需要个性化调整的邮件	会显示为销售代表需要完成的任务
电话呼叫	电话步骤（专业版及以上套餐）	与Apollo拨号器集成；记录呼叫结果
LinkedIn	连接请求、消息、InMail	创建任务——Apollo不会自动执行LinkedIn操作
自定义任务	任何其他操作（发送礼品、调研、内部跟进）	灵活——适用于非标准触点

Step timing

步骤时间设置

These are recommended defaults for Apollo step configuration. For full cadence strategy — including messaging arc, multi-channel touch patterns, and email copy — use

/sales-cadence

Between steps	Recommended gap	Apollo setting
Step 1 → Step 2	2-3 business days	Set "Wait" between steps
Email → Phone	0-1 days (same day or next)	Reference the email in the call
After no reply to 3 emails	4-5 business days	Longer gap prevents fatigue
Before breakup email	5-7 business days	Give them space before final touch

以下是Apollo步骤配置的推荐默认值。如需完整的节奏策略——包括消息架构、多渠道触点模式和邮件文案——请使用/sales-cadence。

步骤间隔	推荐间隔	Apollo设置
步骤1 → 步骤2	2-3个工作日	设置步骤之间的“等待（Wait）”时间
邮件 → 电话	0-1天（当天或次日）	在电话中提及邮件内容
3封邮件未收到回复后	4-5个工作日	更长的间隔避免对方厌烦
最终跟进邮件前	5-7个工作日	在发送最终触点前给对方留出空间

Step 3 — Deliverability management

步骤3 — 送达率管理

Domain authentication (required before sending)

域名认证（发送前必须完成）

Record	What it does	How to verify
SPF	Authorizes Apollo to send on behalf of your domain	`dig TXT yourdomain.com` — look for `include:_spf.apollo.io` or your ESP
DKIM	Cryptographically signs emails to prove they're from you	Check in Settings > Email > Domain Authentication
DMARC	Tells receiving servers what to do with unauthenticated emails	Start with `p=none` for monitoring, move to `p=quarantine` after validation

If any of these are missing, emails will land in spam regardless of content quality.

记录	作用	验证方式
SPF	授权Apollo代表你的域名发送邮件	`dig TXT yourdomain.com` ——查找 `include:_spf.apollo.io` 或你的ESP记录
DKIM	对邮件进行加密签名，证明邮件来自你	在Settings > Email > Domain Authentication中检查
DMARC	告知收件服务器如何处理未认证邮件	从 `p=none` 开始用于监控，验证后切换为 `p=quarantine`

如果缺少其中任何一项，无论内容质量如何，邮件都会进入垃圾邮箱。

Mailbox warmup checklist

邮箱预热清单

New mailboxes (or mailboxes that haven't sent outbound before) must be warmed up before sequencing. Skipping warmup is the second most common deliverability killer after missing domain auth.

Week 1: Send 10-20 emails/day — personal, conversational emails to real contacts (colleagues, partners, existing customers). Use a warmup tool (Lemwarm, Warmbox, or Apollo's built-in warmup if available on your plan) to generate positive engagement signals automatically.
Week 2: Increase to 20-40 emails/day. Continue warmup tool usage. Monitor inbox placement rate — aim for >95% inbox (not spam). Monitor bounce rate and keep it under 3%. Track spam complaints — any spike means pause and investigate.
Week 3: Increase to 40-60 emails/day. Begin adding the mailbox to low-volume sequences (re-engagement or warm follow-up). Only proceed if warmup metrics remain healthy.
Week 4: If inbox placement is consistently >95%, ramp to full sending volume (50-75/day). Add to cold outbound sequences. Do not start cold outbound sequences until warmup shows >95% inbox placement — launching too early will burn the mailbox.

Warmup rules:

Warm up new mailboxes for a minimum of 2-4 weeks before any cold outbound; 3-4 weeks is safer for brand-new domains
Start with 10-20 emails/day, increase by 10-20/day each week
Use a warmup tool (Lemwarm, Warmbox, or Apollo's built-in warmup) — manual warmup alone is not sufficient for cold outbound volumes
Keep the warmup tool running even after you start sequencing — it maintains positive engagement signals
Monitor bounce rate throughout warmup (keep under 3%) and watch for spam complaints — these are early warning signs
If deliverability drops at any point, pause outbound and return to warmup-only for 1 week
Never skip warmup for a mailbox on a new sending domain — domain age and reputation start at zero
Don't start sequences until warmup shows >95% inbox placement consistently
Enable Apollo's Inbox Ramp Up feature (Settings > Email > Inbox Ramp Up) as an additional safeguard

新邮箱（或从未发送过外发邮件的邮箱）在开始序列发送前必须进行预热。跳过预热是仅次于缺少域名认证的第二大送达率杀手。

第1周：每天发送10-20封邮件——给真实联系人（同事、合作伙伴、现有客户）发送个性化、对话式的邮件。使用预热工具（Lemwarm、Warmbox，或套餐包含的Apollo内置预热功能）自动生成正向互动信号。
第2周：增加至每天20-40封邮件。继续使用预热工具。监控收件箱投递率——目标是>95%进入收件箱（而非垃圾邮箱）。监控退信率并保持在3%以下。跟踪垃圾邮件投诉——任何激增都意味着暂停并调查原因。
第3周：增加至每天40-60封邮件。开始将该邮箱添加到低容量序列（重新激活或暖跟进）。仅在预热指标保持健康的情况下继续。
第4周：如果收件箱投递率持续>95%，提升至完整发送量（50-75封/天）。添加到冷外发序列。在预热显示>95%收件箱投递率前，不要启动冷外发序列——过早启动会毁掉邮箱信誉。

预热规则：

新邮箱在进行任何冷外发前，至少预热2-4周；全新域名的邮箱预热3-4周更安全
从每天10-20封开始，每周增加10-20封
使用预热工具（Lemwarm、Warmbox或Apollo内置预热）——仅手动预热不足以支持冷外发的发送量
即使开始序列发送后，也要继续运行预热工具——它能维持正向互动信号
预热全程监控退信率（保持在3%以下）并关注垃圾邮件投诉——这些是早期预警信号
如果任何时候送达率下降，暂停外发，仅进行预热1周
绝不要跳过全新发送域名的邮箱预热——域名年龄和信誉从零开始
直到预热持续显示>95%收件箱投递率后，再启动序列
启用Apollo的Inbox Ramp Up功能（Settings > Email > Inbox Ramp Up）作为额外保障

Mailbox management

邮箱管理

Practice	Recommendation
Mailboxes per sequence	Rotate 3-5 mailboxes per sequence to distribute sending volume
Daily send limit per mailbox	Start at 20-30/day for new mailboxes, ramp to 50-75/day over 2-3 weeks
Total daily volume	Keep total sends across all sequences under 200/day per mailbox at peak
Inbox Ramp Up	Enable for any mailbox less than 3 months old (Settings > Email > Inbox Ramp Up)
Mailbox rotation	Apollo auto-rotates across connected mailboxes — connect multiple for redundancy
Separate domain	Consider a secondary sending domain (e.g., `outreach.yourcompany.com` ) to protect your primary domain reputation

操作	建议
每个序列的邮箱数量	每个序列轮换3-5个邮箱，分散发送量
每个邮箱的每日发送限制	新邮箱从20-30封/天开始，在2-3周内逐步提升至50-75封/天
总每日发送量	峰值时每个邮箱所有序列的总发送量保持在200封/天以下
Inbox Ramp Up	对使用时间不足3个月的邮箱启用（Settings > Email > Inbox Ramp Up）
邮箱轮换	Apollo会在已连接的邮箱之间自动轮换——连接多个邮箱以实现冗余
独立域名	考虑使用二级发送域名（例如 `outreach.yourcompany.com` ）以保护主域名的信誉

Deliverability checklist

送达率检查清单

Step 4 — A/B testing (Professional+ plan)

步骤4 — A/B测试（专业版及以上套餐）

What to test

测试内容

Test	Variant A	Variant B	Metric	Min sample
Subject line	Pain-focused	Curiosity-based	Open rate	100 sends each
Email length	Short (75 words)	Medium (125 words)	Reply rate	100 sends each
CTA style	Specific time ask	Open-ended question	Reply rate	100 sends each
Send time	Morning (9-10am)	Afternoon (2-3pm)	Open rate	100 sends each
Personalization level	Company mention only	Role-specific pain point	Reply rate	100 sends each

测试项	变体A	变体B	指标	最小样本量
主题行	痛点聚焦型	好奇心驱动型	打开率	各100次发送
邮件长度	短（75词）	中（125词）	回复率	各100次发送
CTA风格	特定时间请求	开放式问题	回复率	各100次发送
发送时间	上午（9-10点）	下午（2-3点）	打开率	各100次发送
个性化程度	仅提及公司	角色特定痛点	回复率	各100次发送

Setting up A/B tests in Apollo

在Apollo中设置A/B测试

In your sequence, click the email step you want to test
Click "Add Variant" to create Variant B
Change one variable only (subject line OR body OR send time — not multiple)
Set the split percentage (50/50 for balanced testing)
Apollo automatically distributes and tracks per variant
Wait for at least 100 sends per variant before evaluating
Apollo will show open rate, reply rate, and click rate per variant

在你的序列中，点击要测试的邮件步骤
点击“Add Variant”创建变体B
仅更改一个变量（主题行或正文或发送时间——不要同时更改多个）
设置拆分比例（50/50以获得平衡测试）
Apollo会自动分配并跟踪每个变体的数据
等到每个变体至少发送100次后再评估结果
Apollo会显示每个变体的打开率、回复率和点击率

Testing rules

测试规则

Test one variable at a time — multi-variable tests give muddy results
Let tests run for at least 5 business days before drawing conclusions
Primary metric: positive reply rate (not just opens — opens can be inflated by tracking pixels)
Roll the winner into the sequence and start the next test
Always be testing — messaging decays as prospects see similar patterns from other sellers
For deeper A/B testing frameworks, email copy strategy, and multi-channel cadence design beyond Apollo's built-in testing, use
```
/sales-cadence
```

一次仅测试一个变量——多变量测试会导致结果模糊
测试至少运行5个工作日后再得出结论
主要指标：正向回复率（不仅仅是打开率——打开率可能被跟踪像素夸大）
将获胜变体应用到序列中，然后开始下一个测试
持续测试——随着潜在客户看到类似模式，消息效果会下降
如需更深入的A/B测试框架、邮件文案策略和Apollo内置测试之外的多渠道节奏设计，请使用/sales-cadence

Step 5 — Sequence analytics

步骤5 — 序列分析

Key metrics to monitor

需监控的关键指标

Metric	Healthy range	If below...
Open rate	50-70%	Check subject lines, deliverability, and send times
Reply rate	5-15%	Improve personalization, test different angles, check targeting
Positive reply rate	2-5%	Revisit value prop, check ICP fit, strengthen CTA
Bounce rate	<3%	Clean list, verify emails before adding to sequence — see `/sales-enrich`
Unsubscribe rate	<1%	Reduce frequency, improve relevance, tighten targeting
Meeting booked rate	1-3%	Improve CTA clarity, add social proof, follow up faster on positive replies

指标	健康范围	若低于该范围...
打开率	50-70%	检查主题行、送达率和发送时间
回复率	5-15%	提升个性化程度，测试不同角度，检查目标定位
正向回复率	2-5%	重新审视价值主张，检查ICP匹配度，强化CTA
退信率	<3%	清理列表，发送前验证邮箱——请使用/sales-enrich
退订率	<1%	降低发送频率，提升相关性，收紧目标定位
预约会议率	1-3%	提升CTA清晰度，添加社交证明，更快跟进正向回复

Analyzing in Apollo

在Apollo中进行分析

Sequence dashboard: Engage > Sequences > select sequence > Analytics tab
Step-by-step analysis: See which steps have the highest drop-off — this tells you where the sequence is losing people
Compare sequences: Look at your top-performing vs. worst-performing sequences. What's different? (Targeting, messaging, timing)
Rep-level analytics: If multiple reps use the same sequence, compare performance to identify coaching opportunities

序列仪表盘：Engage > Sequences > 选择序列 > Analytics标签页
分步分析：查看哪些步骤的流失率最高——这会告诉你序列在哪个环节失去了潜在客户
对比序列：查看表现最佳和最差的序列之间的差异（目标定位、消息内容、时间设置）
销售代表级分析：如果多个销售代表使用同一个序列，对比他们的表现以确定辅导机会

Optimization cadence

优化节奏

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

第1-2周：让序列运行，收集基准数据
第3-4周：分析首次A/B测试结果，应用获胜方案
每月：回顾全漏斗指标，淘汰表现不佳的步骤
每季度：重大更新——新的消息内容、更新的案例研究、季节性角度

Gotchas

注意事项

Don't launch sequences without verifying domain authentication. Claude often generates sequence setup guides without checking SPF/DKIM/DMARC. Missing domain auth is the #1 cause of emails landing in spam. Check it before anything else.
Don't set high daily sending limits on new mailboxes. New mailboxes must be ramped up gradually (20-30/day → 50-75/day over 2-3 weeks). Claude defaults to recommending 100+ sends/day, which will tank deliverability on a fresh mailbox.
Don't use Apollo's "Auto" sequence type for multi-channel cadences. Auto sequences only work for email steps. If the cadence includes calls or LinkedIn touches, use "Manual" sequence type — otherwise those steps are skipped entirely.
Don't evaluate A/B tests too early. Claude will analyze test results after 30-40 sends. You need at least 100 sends per variant for statistically meaningful results. Premature conclusions lead to wrong optimizations.
Don't ignore the Deliverability Command Center. Apollo has a built-in deliverability monitoring dashboard that most users never check. It shows domain health, bounce rates, spam complaints, and sending patterns. Review it weekly.

不要在未验证域名认证的情况下启动序列。Claude经常生成序列设置指南但未检查SPF/DKIM/DMARC。缺少域名认证是邮件进入垃圾邮箱的头号原因。先检查这一点。
不要给新邮箱设置高每日发送限制。新邮箱必须逐步提升发送量（20-30封/天 → 50-75封/天，2-3周内完成）。Claude默认推荐100+封/天，这会毁掉新邮箱的送达率。
不要对多渠道节奏使用Apollo的“自动（Auto）”序列类型。自动序列仅适用于邮件步骤。如果节奏包含电话或LinkedIn触点，请使用“手动（Manual）”序列类型——否则这些步骤会被完全跳过。
不要过早评估A/B测试结果。Claude会在30-40次发送后分析测试结果。每个变体至少需要100次发送才能获得统计上有意义的结果。过早得出结论会导致错误的优化。
不要忽略Deliverability Command Center。Apollo有一个内置的送达率监控仪表盘，大多数用户从未查看过。它显示域名健康状况、退信率、垃圾邮件投诉和发送模式。每周查看一次。

Related skills

Examples

示例

Example 1: Setting up a new sequence

示例1：设置新序列

User says: "I need to set up a 5-step email sequence in Apollo for cold outbound to VP Marketing" Skill does:

Configures sequence settings (auto type, business hours, stop on reply)
Sets up 5 steps with recommended timing gaps
Configures mailbox rotation across 3 connected email accounts
Walks through the deliverability checklist Result: Sequence configured and ready for contacts — user runs
```
/sales-cadence
```
to write the actual email copy

用户需求："我需要在Apollo中为VP Marketing的冷外发设置一个5步邮件序列" 技能操作：

配置序列设置（自动类型、工作时间发送、收到回复即停止）
设置5个步骤并配置推荐的间隔时间
配置3个已连接邮箱的轮换规则
引导完成送达率检查清单结果：序列配置完成，可添加联系人——用户运行/sales-cadence来撰写实际的邮件文案

Example 2: Fixing deliverability

示例2：修复送达率问题

User says: "My Apollo sequence open rate dropped from 55% to 25% over the past month" Skill does:

Checks domain authentication (SPF/DKIM/DMARC) status
Reviews sending volume and mailbox health in Deliverability Command Center
Identifies likely cause (sending volume spike, domain reputation issue, or content triggering spam filters)
Recommends remediation steps (reduce volume, warm up new mailbox, adjust content) Result: Deliverability diagnosis with a recovery plan

用户需求："我的Apollo序列打开率在过去一个月从55%下降到25%" 技能操作：

检查域名认证（SPF/DKIM/DMARC）状态
在Deliverability Command Center中查看发送量和邮箱健康状况
确定可能的原因（发送量激增、域名信誉问题或内容触发垃圾邮件过滤器）
推荐修复步骤（降低发送量、预热新邮箱、调整内容）结果：送达率问题诊断及恢复计划

Example 3: A/B test setup

示例3：设置A/B测试

User says: "I want to A/B test my first email's subject line in Apollo" Skill does:

Verifies the user is on Professional+ plan (A/B testing not available on Basic)
Walks through creating Variant B in the sequence editor
Sets 50/50 split and defines success metric (open rate for subject line tests)
Recommends waiting for 100+ sends per variant before evaluating Result: A/B test configured with clear evaluation criteria

用户需求："我想在Apollo中对我的第一封邮件的主题行进行A/B测试" 技能操作：

验证用户是否使用专业版及以上套餐（基础版无A/B测试功能）
引导在序列编辑器中创建变体B
设置50/50拆分比例并定义成功指标（主题行测试的打开率）
推荐每个变体至少发送100次后再评估结果结果：A/B测试配置完成，带有明确的评估标准

Troubleshooting

故障排查

Sequence not sending

序列未发送

Symptom: Contacts added to sequence but no emails going out Cause: Mailbox not connected, sequence paused, contact missing email, or daily limit reached Solution: Check sequence status (active?), verify mailbox connection in Settings > Email, confirm contacts have email addresses, review daily send limits.

症状：联系人已添加到序列，但未发送任何邮件原因：邮箱未连接、序列已暂停、联系人缺少邮箱地址或已达到每日发送限制 解决方案：检查序列状态（是否活跃？），在Settings > Email中验证邮箱连接，确认联系人有邮箱地址，查看每日发送限制。

Emails going to spam

邮件进入垃圾邮箱

Symptom: Open rates below 20%, recipients reporting spam Cause: Missing domain auth, volume too high, spammy content, or domain reputation damage Solution: Verify SPF/DKIM/DMARC. Reduce volume to 20-30/day per mailbox. Remove spam trigger words. Check domain reputation via Google Postmaster Tools.

症状：打开率低于20%，收件人报告垃圾邮件原因：缺少域名认证、发送量过高、内容类似垃圾邮件或域名信誉受损 解决方案：验证SPF/DKIM/DMARC。将每个邮箱的发送量降低至20-30封/天。移除垃圾邮件触发词。通过Google Postmaster Tools检查域名信誉。

High bounce rate

高退信率

Symptom: Bounce rate above 3% Cause: Stale email data, unverified addresses, or catch-all domain issues Solution: Stop the sequence immediately. Verify remaining contacts via

/sales-enrich

. Remove bounced contacts. Clean your list before resuming.

症状：退信率高于3% 原因：陈旧的邮箱数据、未验证的地址或catch-all域名问题 解决方案：立即停止序列。通过/sales-enrich验证剩余联系人。移除已退信的联系人。重新开始前清理列表。