Back to Details

sales-reply

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Reply.io Platform Help

Reply.io平台帮助

Help the user with Reply.io platform questions — from multichannel sequence setup and Jason AI SDR through B2B database, email warmup, deliverability, unified inbox, analytics, integrations, and agency features.
为用户解答Reply.io平台相关问题——覆盖多渠道序列搭建、Jason AI SDR、B2B数据库、邮件预热、送达率、统一收件箱、数据分析、集成能力、代理商功能等全模块。

Step 1 — Gather context

步骤1——收集上下文信息

Ask the user:
  1. What area of Reply.io do you need help with?
    • A) Sequences — creating, managing, or optimizing multichannel sequences
    • B) Jason AI SDR — configuring the autonomous AI agent for prospecting and reply handling
    • C) Deliverability — email warmup, domain health, SPF/DKIM/DMARC, branded links
    • D) Integrations — Salesforce, HubSpot, Pipedrive, Zapier, Make, n8n
    • E) Analytics — sequence performance, channel efficiency, team reporting
    • F) Agency — managing multiple clients, agency-specific features
    • G) B2B Database — finding contacts, email finder, Chrome extension, data credits
    • H) Unified Inbox — managing conversations across channels
    • I) Templates — creating, sharing, and tracking message templates
    • J) API — automation, programmatic access, webhooks
    • K) Something else — describe it
  2. What's your role?
    • A) Sales rep / AE / BDR
    • B) Sales manager / team lead
    • C) RevOps / Sales Ops
    • D) Admin / IT
    • E) Agency owner / operator
    • F) Founder / solo seller
    • G) Other
  3. What are you trying to accomplish? (describe your specific goal or question)
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.
Note: If the user needs a specialized skill, route them there with a brief explanation of why that skill is a better fit.
询问用户以下问题：
  1. 你需要Reply.io哪个模块的帮助？
    • A) 序列——创建、管理或优化多渠道触达序列
    • B) Jason AI SDR——配置用于线索开发和回复处理的自主AI Agent
    • C) 送达率——邮件预热、域名健康、SPF/DKIM/DMARC、品牌链接
    • D) 集成——Salesforce、HubSpot、Pipedrive、Zapier、Make、n8n
    • E) 数据分析——序列表现、渠道效率、团队报表
    • F) 代理商——管理多个客户、代理商专属功能
    • G) B2B数据库——查找联系人、邮箱查询、Chrome扩展、数据积分
    • H) 统一收件箱——管理跨渠道会话
    • I) 模板——创建、分享和追踪消息模板
    • J) API——自动化、程序化访问、Webhook
    • K) 其他——请描述具体问题
  2. 你的角色是什么？
    • A) 销售代表 / AE / BDR
    • B) 销售经理 / 团队负责人
    • C) RevOps / 销售运营
    • D) 管理员 / IT
    • E) 代理商所有者 / 运营人员
    • F) 创始人 / 独立销售
    • G) 其他
  3. 你想要达成什么目标？（描述你的具体目标或问题）
**如果用户的请求已经提供了大部分上下文信息，可以直接跳到对应步骤。**优先基于合理假设（需明确说明假设内容）给出你力所能及的回答，最后仅补充1-2个最关键的澄清问题即可——不要等收集完所有上下文才给出回复。
注意：如果用户需要的是专项能力，引导用户使用对应工具，并简要说明该工具更适配的原因。

Step 2 — Route or answer directly

步骤2——引导跳转或直接解答

If the request maps to a specialized skill, route:
  • Cadence strategy / sequence design → 
    /sales-cadence
  • Cross-platform email deliverability → 
    /sales-deliverability
  • Email tracking strategy → 
    /sales-email-tracking
  • List building / prospecting strategy → 
    /sales-prospect-list
  • Connecting tools / integration architecture → 
    /sales-integration
  • Agency outbound strategy → 
    /sales-agency-outbound
Otherwise, answer directly from platform knowledge using the reference below.
如果用户的请求对应专项能力，引导跳转：
  • 触达节奏策略 / 序列设计 → 
    /sales-cadence
  • 跨平台邮件送达率 → 
    /sales-deliverability
  • 邮件追踪策略 → 
    /sales-email-tracking
  • 列表搭建 / 线索开发策略 → 
    /sales-prospect-list
  • 工具对接 / 集成架构 → 
    /sales-integration
  • 代理商外拓策略 → 
    /sales-agency-outbound
否则，基于下方的平台知识库直接解答。

Step 3 — Reply.io platform reference

步骤3——Reply.io平台参考指引

Provide module-by-module guidance based on the user's area:
根据用户咨询的模块，给出对应指引：

Multichannel sequences

多渠道序列

  • What it is: A sequence in Reply.io is a multichannel outreach campaign — a series of automated steps across email, LinkedIn, calls, SMS, and WhatsApp
  • Conditional sequences: Branching logic based on prospect behavior (opened, clicked, replied) or contact data (title, industry) — routes prospects down different paths automatically
  • Channels: Email, LinkedIn (InMail, connection requests, profile views), calls, SMS, WhatsApp
  • Sequence builder: Drag-and-drop step editor — add, reorder, and configure steps visually
  • A/B testing: Test different message variants within any sequence step to optimize performance
  • Auto-pause triggers: Sequence automatically pauses a contact on reply, meeting booked, or custom triggers you define
  • Sequence statuses: Active, Paused, New, Archived
  • LinkedIn automation add-on: $69/account — required for LinkedIn steps (connection requests, InMail, profile views). Not included in base Multichannel plan.
  • Calls/SMS add-on: $29/account — required for phone and SMS steps. Not included in base plans.
  • 定义：Reply.io中的序列是多渠道外拓活动——由一系列跨邮件、LinkedIn、电话、SMS、WhatsApp的自动化步骤组成
  • 条件序列：基于潜在客户行为（打开、点击、回复）或联系人数据（职位、行业）的分支逻辑——自动将潜在客户分配到不同触达路径
  • 支持渠道：邮件、LinkedIn（InMail、好友申请、主页访问）、电话、SMS、WhatsApp
  • 序列编辑器：拖拽式步骤编辑器——可视化添加、重排和配置步骤
  • A/B测试：在任意序列步骤中测试不同的消息变体，优化表现
  • 自动暂停触发条件：当联系人回复、预约会议，或者你定义的自定义触发条件满足时，序列自动暂停对该联系人的触达
  • 序列状态：活跃、暂停、新建、已归档
  • LinkedIn自动化附加包：$69/账号——使用LinkedIn步骤（好友申请、InMail、主页访问）需要单独购买，不包含在基础多渠道套餐中
  • 电话/SMS附加包：$29/账号——使用电话和SMS步骤需要单独购买，不包含在基础套餐中

Jason AI SDR

Jason AI SDR

  • What it is: An autonomous AI agent that handles prospecting, outreach, and reply management end-to-end
  • How it works: Trains on your business, product, and target audience. Finds leads from a 1B+ contact database, launches multichannel campaigns with personalized messages, and handles replies autonomously.
  • Reply handling: Qualification questions, objection handling, meeting booking — all handled by AI
  • Language support: Works 24/7 in 50+ languages
  • Pricing: $139/user/month — separate plan tier, not an add-on to cheaper plans
  • Key limitation: Jason AI is its own plan tier. You cannot add it to the Email Volume or Multichannel plans.
  • 定义：端到端处理线索开发、外拓和回复管理的自主AI Agent
  • 工作原理：基于你的业务、产品和目标受众进行训练，从1B+联系人数据库中挖掘线索，发送带有个性化内容的多渠道活动，并且自主处理回复
  • 回复处理能力：资质判断问题、异议处理、会议预约——全部由AI自主完成
  • 语言支持：支持50+语言，7*24小时运行
  • 定价：$139/用户/月——属于独立套餐层级，不能作为附加包添加到更低价格的套餐中
  • 核心限制：Jason AI是独立的套餐层级，你无法将其添加到邮件量套餐或多渠道套餐中

B2B database & email finder

B2B数据库 & 邮箱查询

  • What it is: Built-in prospecting database for finding contacts and companies
  • Database size: 1B+ global contacts, 220M+ US contacts, 15M+ US companies
  • Chrome extension: Find emails directly from LinkedIn profiles and company websites
  • Data credits: Credits-based system — 200 free credits on all plans, additional credits on paid plans
  • Search filters: Industry, company size, job title, location, technology stack
  • Best practices: Verify emails before sequencing, use filters to narrow to your ICP, check credit balance before bulk searches
  • 定义：内置的线索开发数据库，用于查找联系人和企业信息
  • 数据库规模：1B+全球联系人、220M+美国联系人、15M+美国企业
  • Chrome扩展：直接从LinkedIn主页和企业官网查询邮箱
  • 数据积分：积分制体系——200免费积分在所有套餐赠送，付费套餐可获得额外积分
  • 搜索筛选器：行业、企业规模、职位、地点、技术栈
  • 最佳实践：在加入序列前验证邮箱有效性，使用筛选器缩小范围到你的理想客户画像（ICP），批量搜索前检查积分余额

Email warmup & deliverability

邮件预热 & 送达率

  • Built-in warmup: Peer-to-peer warmup network (no free or temporary email accounts — real business mailboxes)
  • Domain health checker: Dedicated tab in Reply.io to monitor domain reputation and configuration
  • Google Postmaster API: Integration for monitoring spam rate, IP reputation, and domain reputation directly in Reply.io
  • Domain authentication: SPF/DKIM/DMARC setup guidance built into the platform
  • Branded links: Custom tracking domains to improve deliverability and brand trust
  • Warmup timeline: 2-3 weeks recommended before sending cold sequences at full volume
  • Best practices: Enable warmup immediately after connecting a new mailbox, monitor domain health weekly, keep spam complaint rate below 0.1%
  • 内置预热功能：点对点预热网络（无免费或临时邮箱账号，全部是真实企业邮箱）
  • 域名健康检查器：Reply.io中的专属标签页，用于监控域名声誉和配置情况
  • Google Postmaster API集成：可直接在Reply.io中监控垃圾邮件率、IP声誉和域名声誉
  • 域名认证：平台内置SPF/DKIM/DMARC设置指引
  • 品牌链接：自定义追踪域名，提升送达率和品牌信任度
  • 预热周期：建议预热2-3周后再全量发送冷触达序列
  • 最佳实践：新邮箱绑定后立即开启预热，每周监控域名健康，将垃圾投诉率保持在0.1%以下

Unified inbox

统一收件箱

  • What it is: A single view for all conversations across all channels — email, LinkedIn, calls, SMS, WhatsApp
  • Key features: Manage messages from sequences and team members in one place
  • Filters: Filter by channel, sequence, contact status, team member
  • Best practices: Check unified inbox daily, respond to warm replies within 1 hour, use filters to prioritize hot leads
  • 定义：集中查看所有跨渠道会话的单一视图——覆盖邮件、LinkedIn、电话、SMS、WhatsApp
  • 核心功能：在一个地方管理来自序列和团队成员的消息
  • 筛选器：按渠道、序列、联系人状态、团队成员筛选
  • 最佳实践：每天查看统一收件箱，1小时内回复高意向回复，使用筛选器优先处理高价值线索

Analytics & reporting

数据分析 & 报表

  • Sequence performance: Opens, clicks, replies, bounces broken down per step — identify which steps perform best
  • Channel efficiency: Dashboard comparing performance across email, LinkedIn, calls, SMS, WhatsApp
  • Team analytics: Individual rep performance and team-wide comparisons
  • Statistics API: Programmatic access to email stats, call stats, LinkedIn stats, and click stats via API endpoints
  • Key metrics to track: Reply rate (not just opens), positive reply rate, meetings booked per sequence, bounce rate (<3% target)
  • 序列表现：按步骤拆分的打开、点击、回复、退信数据——识别表现最好的步骤
  • 渠道效率：对比邮件、LinkedIn、电话、SMS、WhatsApp表现的仪表盘
  • 团队数据分析：销售代表个人表现和团队整体对比
  • 统计API：通过API端点程序化获取邮件、电话、LinkedIn、点击数据
  • 需要追踪的核心指标：回复率（不只是打开率）、正向回复率、单序列预约会议数、退信率（目标低于3%）

Templates

模板

  • What it is: Reusable email and message templates for consistent outreach
  • Team sharing: Share templates across your team for standardized messaging
  • Performance tracking: Track which templates drive the highest reply rates
  • Best practices: Create templates for common scenarios (intro, follow-up, breakup), A/B test template variants, update underperforming templates monthly
  • 定义：可复用的邮件和消息模板，保证外拓内容一致性
  • 团队共享：跨团队共享模板，实现消息标准化
  • 表现追踪：追踪哪些模板带来最高的回复率
  • 最佳实践：为常见场景（介绍、跟进、收尾）创建模板，对模板变体做A/B测试，每月更新表现不佳的模板

Integrations

集成

  • Salesforce: Native 2-way sync — contacts/leads, emails, statuses, tasks, calls. Multiple default sync scenarios plus custom workflows. Real-time sync.
  • HubSpot: Native 2-way sync with auto-sync every 2 hours — contacts, statuses, emails, calls, tasks. Configurable field mappings and filtering rules.
  • Pipedrive: Native integration for contact and deal sync
  • Zapier/Make/n8n: Automation connectors for non-native CRM connections and custom workflows
  • Copper, Close, Zendesk Sell: Available via Zapier (no native integration)
  • Best practices: Map Reply.io contact statuses to CRM stages before enabling sync, test with a small batch first, monitor sync logs for errors
  • Salesforce：原生双向同步——联系人/线索、邮件、状态、任务、通话。支持多个默认同步场景和自定义工作流，实时同步。
  • HubSpot：原生双向同步，每2小时自动同步——联系人、状态、邮件、通话、任务。可配置字段映射和筛选规则。
  • Pipedrive：原生集成，支持联系人和商机同步
  • Zapier/Make/n8n：自动化连接器，用于对接非原生CRM和自定义工作流
  • Copper, Close, Zendesk Sell：通过Zapier对接（无原生集成）
  • 最佳实践：开启同步前将Reply.io联系人状态映射到CRM阶段，先小批量测试，监控同步日志排查错误

Reply.io data model

Reply.io数据模型

Core entities — understand these to navigate the UI and work with the API:
ObjectDescriptionKey fields
SequenceMultichannel outreach campaignid, teamId, ownerId, name, status (Active/Paused/New/Archived), created, isArchived
ContactProspect recordid, email, firstName, lastName, company, title, status
Sequence StepIndividual step in a sequenceid, sequenceId, type (email/LinkedIn/call/SMS/WhatsApp), variant, order
Email AccountConnected sending mailboxid, email, provider, status
TemplateReusable message templateid, name, body, subject
TaskAction item for repid, type, contactId, dueDate, status
ListContact groupingid, name, contactCount
WebhookEvent subscriptionid, url, events, status
ScheduleSending schedule configid, name, timezone, days, hours
核心实体——理解这些实体可以帮助你操作界面和使用API：
对象描述核心字段
Sequence多渠道外拓活动id, teamId, ownerId, name, status (Active/Paused/New/Archived), created, isArchived
Contact潜在客户记录id, email, firstName, lastName, company, title, status
Sequence Step序列中的单个步骤id, sequenceId, type (email/LinkedIn/call/SMS/WhatsApp), variant, order
Email Account绑定的发件邮箱id, email, provider, status
Template可复用的消息模板id, name, body, subject
Task销售代表待办事项id, type, contactId, dueDate, status
List联系人分组id, name, contactCount
Webhook事件订阅id, url, events, status
Schedule发送时间配置id, name, timezone, days, hours

API quick reference

API快速参考

For detailed API documentation including all endpoints, authentication, pagination, and webhook events, consult 
references/reply-api-reference.md
.
  • Base URL: 
    https://api.reply.io/v3
    (V3 beta) / 
    https://api.reply.io/v1
    and 
    /v2
    (legacy, currently active)
  • Auth: 
    X-API-Key
    header, 
    api_key
    query parameter, or JWT Bearer token
  • Pagination: 
    top
    /
    skip
    parameters (default 25, max 1000)
  • Errors: RFC 9457 Problem Details format; HTTP 429 for rate limits
  • Key endpoints: Sequences, Contacts, EmailAccounts, Templates, Tasks, Statistics, Reports, Webhooks, Lists, BlackList, BrandedLinks, Schedules
  • Note: V3 is in beta (request access from Reply.io). V1/V2 are currently active and stable.
Always reference 
references/reply-api-reference.md
 when answering API questions — point the user to it for the full endpoint catalog, request/response details, and error handling.
如需包含所有端点、认证、分页和Webhook事件的详细API文档，请参考
references/reply-api-reference.md
。
  • 基础URL：
    https://api.reply.io/v3
    （V3测试版） / 
    https://api.reply.io/v1
    和 
    /v2
    （旧版，当前仍可用）
  • 认证方式：
    X-API-Key
    请求头、
    api_key
    查询参数，或JWT Bearer令牌
  • 分页：
    top
    /
    skip
    参数（默认25条，最大1000条）
  • 错误格式：RFC 9457 Problem Details格式；触发限流时返回HTTP 429
  • 核心端点：Sequences, Contacts, EmailAccounts, Templates, Tasks, Statistics, Reports, Webhooks, Lists, BlackList, BrandedLinks, Schedules
  • 注意：V3处于测试阶段（需向Reply.io申请访问权限），V1/V2当前稳定可用。
解答API相关问题时务必参考
references/reply-api-reference.md
——引导用户查看该文档获取完整的端点列表、请求/响应详情和错误处理规则。

Native integrations

原生集成

  • CRM: Salesforce (native 2-way sync), HubSpot (native 2-way sync), Pipedrive (native)
  • Automation: Zapier, Make, n8n (triggers and actions for sequences, contacts, replies)
  • Non-native CRM: Copper, Close, Zendesk Sell (via Zapier)
  • AI: Jason AI SDR (built-in autonomous agent)
  • CRM：Salesforce（原生双向同步）、HubSpot（原生双向同步）、Pipedrive（原生集成）
  • 自动化：Zapier、Make、n8n（支持序列、联系人、回复相关的触发和动作）
  • 非原生CRM：Copper, Close, Zendesk Sell（通过Zapier对接）
  • AI：Jason AI SDR（内置自主Agent）

Pricing (as of 2026 — verify current pricing at reply.io)

定价（2026年数据——请以reply.io官网的当前定价为准）

PlanPriceKey features
Free$0AI sequence generator, Chrome extension, 200 data credits
Email Volume~$49/user/mo (annual)Email-only sequences
Multichannel~$89/user/moAll channels, unlimited contacts, 10 mailboxes/user
AI SDR (Jason)~$139/user/moAutonomous AI agent for full-cycle outreach
Agency~$166/moUnlimited clients and users
LinkedIn add-on$69/accountLinkedIn automation (connection requests, InMail, profile views)
Calls/SMS add-on$29/accountPhone dialer and SMS messaging
套餐价格核心功能
免费版$0AI序列生成器、Chrome扩展、200数据积分
邮件量套餐~$49/用户/月（年付）仅支持邮件序列
多渠道套餐~$89/用户/月全渠道支持、无限联系人、10个邮箱/用户
AI SDR（Jason）~$139/用户/月全周期外拓的自主AI Agent
代理商套餐~$166/月无限客户和用户
LinkedIn附加包$69/账号LinkedIn自动化（好友申请、InMail、主页访问）
电话/SMS附加包$29/账号电话拨号和SMS消息功能

Step 4 — Actionable guidance

步骤4——可落地的指导

Based on the user's specific question:
  1. Step-by-step instructions — numbered steps to accomplish their goal in Reply.io
  2. Configuration recommendations — specific settings to change, with navigation paths in the Reply.io UI
  3. Recommended setup order: Connect mailbox -> Enable warmup -> Wait 2-3 weeks -> Build sequence -> Add contacts -> Launch
  4. Verification steps — how to confirm the change worked (check domain health tab, test send, verify sync logs)
  5. For API questions — always include a pointer: "For the full endpoint catalog, authentication details, and error handling, see 
    references/reply-api-reference.md
    ."
基于用户的具体问题：
  1. 分步操作指引——帮助用户在Reply.io中完成目标的编号步骤
  2. 配置建议——具体需要修改的设置，以及Reply.io界面中的导航路径
  3. 推荐设置顺序：绑定邮箱 → 开启预热 → 等待2-3周 → 搭建序列 → 添加联系人 → 启动
  4. 验证步骤——如何确认修改生效（检查域名健康标签页、测试发送、验证同步日志）
  5. API相关问题——始终添加提示："For the full endpoint catalog, authentication details, and error handling, see 
    references/reply-api-reference.md
    ."

Gotchas

注意事项

Best-effort from research — verify against current Reply.io documentation for the latest behavior.
  • Don't skip warmup. Reply.io has built-in peer-to-peer warmup, but you must enable it and wait 2-3 weeks before sending cold sequences at full volume. Skipping warmup is the #1 cause of deliverability issues on new accounts.
  • LinkedIn automation is a paid add-on ($69/account). It's not included in the Multichannel plan base price. If you build a sequence with LinkedIn steps but haven't purchased the add-on, those steps will fail silently or be skipped.
  • Calls/SMS is also a paid add-on ($29/account). Plan your multichannel sequence budget accordingly — a "full multichannel" setup with LinkedIn + Calls/SMS costs $89 + $69 + $29 = $187/user/mo.
  • Jason AI SDR is a separate plan tier ($139/user/mo), not a feature add-on. You cannot add Jason AI to the Email Volume or Multichannel plans. It's its own plan with different capabilities.
  • V3 API is in beta. Most integrations and documentation still reference V1/V2 endpoints. Check which API version your integration targets before building — V3 endpoints may change without notice.
基于调研的最优参考——请以Reply.io当前官方文档的最新规则为准。
  • 不要跳过预热。 Reply.io有内置的点对点预热功能，但你必须手动开启，并等待2-3周后再全量发送冷触达序列。跳过预热是新账号出现送达率问题的首要原因。
  • LinkedIn自动化是付费附加包（$69/账号）。 不包含在多渠道套餐基础价格中。如果你搭建的序列包含LinkedIn步骤但未购买附加包，这些步骤会静默失败或被跳过。
  • 电话/SMS也是付费附加包（$29/账号）。 提前规划多渠道序列的预算——包含LinkedIn + 电话/SMS的「全渠道」配置成本为$89 + $69 + $29 = $187/用户/月。
  • Jason AI SDR是独立套餐层级（$139/用户/月），不是功能附加包。 你无法将Jason AI添加到邮件量套餐或多渠道套餐中，它是独立的套餐，拥有不同的能力。
  • V3 API处于测试阶段。 大多数集成和文档仍参考V1/V2端点。开发前确认你的集成目标的API版本——V3端点可能会无预警变更。

Step 5 — Related skills

步骤5——相关能力

  • /sales-cadence
    — Design outbound cadence strategy (platform-agnostic, works with Reply.io sequences)
  • /sales-deliverability
    — Cross-platform email deliverability — SPF/DKIM/DMARC, warmup, inbox placement
  • /sales-email-tracking
    — Email tracking strategy and best practices
  • /sales-prospect-list
    — Build prospect lists to import into Reply.io
  • /sales-integration
    — Connect Reply.io to other tools via webhooks, Zapier, Make, or API
  • /sales-agency-outbound
    — Agency outbound strategy for managing multiple clients
  • /sales-enrich
    — Enrich contacts with emails/phones before importing
  • /sales-apollo
    — Apollo.io platform help (if using Apollo instead of Reply.io)
  • /sales-salesloft
    — Salesloft platform help (if using Salesloft instead of Reply.io)
  • /sales-mailshake
    — Mailshake platform help (if using Mailshake instead of Reply.io)
  • /sales-do
    — Not sure which skill to use? The router matches any sales objective to the right skill. Install: 
    npx skills add sales-skills/sales --skills sales-do
  • /sales-cadence
    ——设计外拓节奏策略（平台无关，可适配Reply.io序列）
  • /sales-deliverability
    ——跨平台邮件送达率优化——SPF/DKIM/DMARC、预热、收件箱入箱率
  • /sales-email-tracking
    ——邮件追踪策略和最佳实践
  • /sales-prospect-list
    ——搭建可导入Reply.io的潜在客户列表
  • /sales-integration
    ——通过Webhook、Zapier、Make或API将Reply.io对接其他工具
  • /sales-agency-outbound
    ——管理多客户的代理商外拓策略
  • /sales-enrich
    ——导入前补充联系人的邮箱/电话信息
  • /sales-apollo
    ——Apollo.io平台帮助（如果你使用Apollo而非Reply.io）
  • /sales-salesloft
    ——Salesloft平台帮助（如果你使用Salesloft而非Reply.io）
  • /sales-mailshake
    ——Mailshake平台帮助（如果你使用Mailshake而非Reply.io）
  • /sales-do
    ——不知道该用哪个能力？路由工具会将任何销售目标匹配到合适的能力。安装命令：
    npx skills add sales-skills/sales --skills sales-do

Examples

示例

Example 1: Basic sequence setup

示例1：基础序列搭建

User says: "How do I set up a multichannel sequence in Reply.io with email and LinkedIn steps?" Skill does:
  1. Walks through creating a new sequence in the sequence builder
  2. Explains how to add email steps (subject, body, delay between steps) and LinkedIn steps (connection request, InMail, profile view)
  3. Notes that LinkedIn automation requires the $69/account add-on
  4. Explains conditional branching — e.g., if prospect opens email, send LinkedIn connection request; if not, send follow-up email
  5. Covers A/B testing within steps and auto-pause triggers Result: User has a multichannel sequence configured with email and LinkedIn steps, understands add-on costs, and knows how to use branching logic
用户提问："我如何在Reply.io中搭建包含邮件和LinkedIn步骤的多渠道序列？" 工具处理逻辑：
  1. 引导用户在序列编辑器中创建新序列
  2. 说明如何添加邮件步骤（主题、正文、步骤间间隔）和LinkedIn步骤（好友申请、InMail、主页访问）
  3. 提示LinkedIn自动化需要购买$69/账号的附加包
  4. 解释条件分支逻辑——比如如果潜在客户打开了邮件，发送LinkedIn好友申请；如果没有打开，发送跟进邮件
  5. 介绍步骤内的A/B测试和自动暂停触发条件 结果：用户配置好包含邮件和LinkedIn步骤的多渠道序列，了解附加包成本，掌握分支逻辑的使用方法

Example 2: Jason AI configuration

示例2：Jason AI配置

User says: "How do I set up Jason AI to handle my outbound prospecting?" Skill does:
  1. Confirms the user is on the AI SDR plan ($139/user/mo) — Jason AI is not available on cheaper plans
  2. Walks through training Jason AI on business context, product, and target audience
  3. Explains how Jason AI finds leads from the 1B+ database, launches campaigns, and handles replies
  4. Covers reply handling capabilities: qualification, objection handling, meeting booking
  5. Sets expectations: Jason AI works 24/7 but benefits from periodic review and feedback Result: User has Jason AI configured and understands how to train it, monitor its performance, and when to intervene
用户提问："我如何设置Jason AI来处理我的外拓线索开发工作？" 工具处理逻辑：
  1. 确认用户使用的是AI SDR套餐（$139/用户/月）——低价套餐不支持Jason AI
  2. 引导用户基于业务上下文、产品和目标受众训练Jason AI
  3. 说明Jason AI如何从1B+数据库中挖掘线索、启动活动、处理回复
  4. 介绍回复处理能力：资质判断、异议处理、会议预约
  5. 设定预期：Jason AI可7*24小时运行，但定期的审核和反馈可以提升效果 结果：用户完成Jason AI配置，了解如何训练它、监控表现，以及何时需要人工介入

Example 3: Salesforce integration setup

示例3：Salesforce集成设置

User says: "How do I connect Reply.io to Salesforce for 2-way sync?" Skill does:
  1. Walks through the native Salesforce integration setup in Reply.io settings
  2. Explains default sync scenarios: contacts/leads, emails, statuses, tasks, calls
  3. Covers custom workflow configuration for non-default sync rules
  4. Warns about field mapping — map Reply.io contact statuses to Salesforce stages before enabling sync
  5. Recommends testing with a small batch before enabling full sync Result: User has Salesforce connected with appropriate sync rules and field mappings configured
用户提问："我如何将Reply.io对接Salesforce实现双向同步？" 工具处理逻辑：
  1. 引导用户在Reply.io设置中完成原生Salesforce集成配置
  2. 解释默认同步场景：联系人/线索、邮件、状态、任务、通话
  3. 介绍非默认同步规则的自定义工作流配置方法
  4. 提醒字段映射注意事项——开启同步前将Reply.io联系人状态映射到Salesforce阶段
  5. 建议开启全量同步前先小批量测试 结果：用户完成Salesforce对接，配置好合适的同步规则和字段映射

Troubleshooting

问题排查

Emails landing in spam

邮件进入垃圾邮箱

Symptom: Low inbox placement, recipients reporting emails in spam folder Cause: Warmup not completed, missing domain authentication, or poor sender reputation Solution: Check the domain health tab in Reply.io. Verify SPF/DKIM/DMARC are configured correctly. Enable built-in warmup and wait 2-3 weeks before full-volume sending. Check Google Postmaster integration for spam rate (keep below 0.1%). Set up branded links (custom tracking domain) to avoid generic tracking domain flags. See 
/sales-deliverability
for a full diagnosis framework.
症状：入箱率低，收件人反馈邮件进入垃圾文件夹 原因：未完成预热、缺少域名认证、发件人声誉差 解决方案：检查Reply.io中的域名健康标签页，验证SPF/DKIM/DMARC配置正确。开启内置预热功能，等待2-3周后再全量发送。查看Google Postmaster集成的垃圾邮件率（保持在0.1%以下）。设置品牌链接（自定义追踪域名）避免通用追踪域名被标记。可使用
/sales-deliverability
获取完整的诊断框架。

Low reply rates

回复率低

Symptom: Sequence reply rates below 2-3% Cause: Poor targeting, weak messaging, wrong channel mix, or sending to unverified contacts Solution: Review sequence analytics per step — identify where prospects drop off. A/B test subject lines and message body. Check if LinkedIn steps are executing (requires $69 add-on). Verify contact data quality — bounces above 3% indicate bad data. Consider adding conditional branches to route non-responsive prospects to different channels. Use 
/sales-cadence
for cadence strategy optimization.
症状：序列回复率低于2-3% 原因：定位不准确、内容质量差、渠道组合不合理、发送给未验证的联系人 解决方案：按步骤查看序列数据分析，识别潜在客户流失节点。对主题行和消息正文做A/B测试。检查LinkedIn步骤是否正常执行（需要购买$69的附加包）。验证联系人数据质量——退信率高于3%说明数据质量差。考虑添加条件分支，将无响应的潜在客户分配到其他渠道。可使用
/sales-cadence
优化触达节奏策略。

Salesforce sync not working

Salesforce同步异常

Symptom: Contacts or activities not syncing between Reply.io and Salesforce Cause: Integration misconfigured, field mapping errors, or sync paused Solution: Check integration settings in Reply.io — verify the Salesforce connection is active. Review sync logs for error messages. Confirm field mappings are correct (Reply.io contact fields must map to valid Salesforce fields). Check that sync scenarios are enabled for the data types you expect (contacts, emails, tasks, calls). Test with a single contact before troubleshooting bulk sync issues.
症状：联系人或活动未在Reply.io和Salesforce之间同步 原因：集成配置错误、字段映射错误、同步暂停 解决方案：检查Reply.io中的集成设置，确认Salesforce连接处于活跃状态。查看同步日志的错误信息。确认字段映射正确（Reply.io联系人字段必须映射到有效的Salesforce字段）。确认你需要同步的数据类型（联系人、邮件、任务、通话）的同步场景已开启。排查批量同步问题前先测试单个联系人的同步。