sales-mailshake

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Mailshake Platform Help

Mailshake平台帮助文档

Help the user with Mailshake platform questions — from campaign setup and Lead Catcher through recipient management, deliverability settings, API, and integrations.

为用户提供Mailshake平台相关问题的帮助 — 从营销活动搭建、Lead Catcher配置到收件人管理、送达率设置、API使用及集成功能等全场景支持。

Step 1 — Gather context

步骤1 — 收集上下文

Ask the user:

What area of Mailshake do you need help with?
- A) Campaigns — creating, managing, or optimizing email campaigns (route to
```
/sales-cadence
```
  for strategy)
- B) Recipients — importing, managing, CSV formatting
- C) Lead Catcher — capturing and managing leads from replies
- D) Deliverability — sender settings, warmup, domain auth (route to
```
/sales-deliverability
```
  for cross-platform)
- E) Analytics — campaign performance, open/reply/click rates
- F) Webhooks & API — automation, push events, API access
- G) Senders & Team — connected accounts, team management
- H) Integrations — Salesforce, HubSpot, Pipedrive, Zapier, Slack
- I) Admin — billing, plan features, account settings
- J) Something else — describe it
What's your role?
- A) Sales rep / AE / BDR
- B) Sales manager / team lead
- C) RevOps / Sales Ops
- D) Admin / IT
- E) Founder / solo seller
- F) Other
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.

向用户询问：

你需要Mailshake哪方面的帮助？
- A) 营销活动 — 创建、管理或优化邮件营销活动（策略相关请跳转至
```
/sales-cadence
```
  ）
- B) 收件人 — 导入、管理、CSV格式设置
- C) Lead Catcher — 捕获并管理来自回复的线索
- D) 送达率 — 发件人设置、邮箱暖养、域名认证（跨平台相关请跳转至
```
/sales-deliverability
```
  ）
- E) 数据分析 — 营销活动表现、打开/回复/点击率
- F) Webhooks与API — 自动化、事件推送、API访问
- G) 发件人与团队 — 关联账户、团队管理
- H) 集成功能 — Salesforce、HubSpot、Pipedrive、Zapier、Slack
- I) 管理后台 — 账单、套餐功能、账户设置
- J) 其他 — 请具体描述
你的角色是什么？
- A) 销售代表/AE/BDR
- B) 销售经理/团队主管
- C) 营收运营/销售运营
- D) 管理员/IT人员
- E) 创始人/独立销售
- F) 其他
你想要达成什么目标？（描述你的具体需求或问题）

如果用户的请求已包含大部分上述上下文，可直接跳至对应步骤。 先基于合理假设给出初步解答（需明确说明假设），再仅询问最关键的1-2个补充问题 — 不要要求用户提供完整上下文后才给出回复。

注意：如果用户的需求属于特定细分场景，请引导至对应技能模块并简要说明原因。

Step 2 — Route or answer directly

步骤2 — 引导至对应模块或直接解答

If the request maps to a specialized skill, route:

List building / prospecting →
```
/sales-prospect-list
```
Contact enrichment / data hygiene →
```
/sales-enrich
```
Cadence strategy / sequence design →
```
/sales-cadence
```
Cross-platform deliverability →
```
/sales-deliverability
```
Tool integration architecture →
```
/sales-integration
```

Otherwise, answer directly from platform knowledge using the reference below.

如果用户的请求对应特定细分技能，请进行引导：

客户列表构建/潜在客户开发 →
```
/sales-prospect-list
```
联系人信息补全/数据清洗 →
```
/sales-enrich
```
触达节奏策略/序列设计 →
```
/sales-cadence
```
跨平台送达率优化 →
```
/sales-deliverability
```
工具集成架构设计 →
```
/sales-integration
```

否则，直接基于平台知识库给出解答。

Step 3 — Mailshake platform reference

步骤3 — Mailshake平台参考指南

Provide module-by-module guidance based on the user's area:

根据用户的需求领域提供分模块指导：

Campaigns

营销活动

What it is: A campaign in Mailshake is a multi-step email sequence — an initial message plus follow-ups sent automatically on a schedule
Key concepts: Campaign = sequence, messages = steps, follow-up types (time-based drip, reply-based, click-based on-click message)
Campaign statuses: draft, active, paused, ended
A/B testing: Available on higher plans — test subject lines and body content across variants
Best practices: Keep initial emails under 125 words, personalize with merge fields ({{first}}, {{company}}), test one variable at a time

定义：Mailshake中的营销活动是一个多步骤邮件序列 — 包含初始邮件及按计划自动发送的跟进邮件
核心概念：营销活动=序列，邮件=步骤，跟进类型（基于时间的drip推送、基于回复的触发、基于点击的触发邮件）
营销活动状态：草稿、活跃、暂停、已结束
A/B测试：仅高级套餐可用 — 测试不同主题行和邮件内容变体
最佳实践：初始邮件字数控制在125词以内，使用合并字段（{{first}}, {{company}}）进行个性化，每次仅测试一个变量

Recipients

收件人

What it is: The contacts enrolled in a campaign — imported via CSV, API, or manual entry
Required fields: Only
```
emailAddress
```
is mandatory. Everything else is optional but recommended.
Recommended fields:
```
first
```
,
```
last
```
,
```
company
```
,
```
title
```
— these map to merge fields {{first}}, {{last}}, {{company}}, {{title}}
Custom merge fields: Any additional CSV column becomes a custom merge field automatically
Recipient statuses: active, paused, bounced, unsubscribed, completed
CSV import tips: UTF-8 encoding, first row = headers, one email per row, verify emails before import (Mailshake does not verify on upload)

定义：加入营销活动的联系人 — 可通过CSV、API或手动录入导入
必填字段：仅
```
emailAddress
```
为必填项，其余为可选但推荐填写
推荐字段：
```
first
```
,
```
last
```
,
```
company
```
,
```
title
```
— 对应合并字段{{first}}, {{last}}, {{company}}, {{title}}
自定义合并字段：CSV中的额外列会自动成为自定义合并字段
收件人状态：活跃、暂停、退回、退订、已完成
CSV导入提示：使用UTF-8编码，首行为表头，每行一个邮箱地址，导入前验证邮箱有效性（Mailshake不会在上传时自动验证）

Lead Catcher

What it is: Built-in lead management that automatically captures replies as leads for follow-up
Lead statuses: open (needs action), won/closed (converted), ignored (not a lead), lost (dead)
Key features: Auto-assign leads to team members, filter by status/campaign/assignee, view full conversation thread
Lead Catcher vs CRM: Lead Catcher manages the email conversation thread — your CRM manages the deal. Push qualified leads to CRM via integration or API.
Best practices: Check Lead Catcher daily, respond within 1 hour for best conversion, use status labels consistently

定义：内置线索管理工具，可自动将回复捕获为线索以便跟进
线索状态：待处理（需跟进）、已成交/已关闭（已转化）、忽略（非线索）、已流失（无效）
核心功能：自动将线索分配给团队成员，按状态/营销活动/负责人筛选，查看完整对话线程
Lead Catcher vs CRM：Lead Catcher管理邮件对话线程 — CRM管理交易流程。可通过集成或API将合格线索推送至CRM。
最佳实践：每日查看Lead Catcher，1小时内回复以获得最佳转化效果，统一使用状态标签

Deliverability Basics

送达率基础

Sender accounts: Connect Gmail, Outlook/O365, or SMTP. Each sender has a daily sending limit.
Sending limits: Varies by plan and email provider. Gmail caps at ~400-500/day, O365 at ~1,000/day. Mailshake enforces plan limits on top of provider limits.
Domain auth: Configure SPF/DKIM/DMARC for your sending domain. Use a custom tracking domain for link tracking.
Warmup: For new mailboxes, start with 20-30 emails/day and increase by 10-20 per week. See
```
/sales-deliverability
```
for a full warmup framework.
Sender rotation: Distribute sends across multiple sender accounts to protect reputation

发件人账户：可连接Gmail、Outlook/O365或SMTP账户。每个发件人有每日发送限额。
发送限额：因套餐和邮件服务商而异。Gmail每日限额约400-500封，O365约1000封。Mailshake会在服务商限额基础上额外执行套餐限额。
域名认证：为发件域名配置SPF/DKIM/DMARC。使用自定义跟踪域名进行链接跟踪。
邮箱暖养：对于新邮箱，从每日20-30封开始，每周增加10-20封。完整暖养框架请查看
```
/sales-deliverability
```
。
发件人轮换：在多个发件人账户间分配发送任务以保护发件人信誉

Analytics

数据分析

Built-in dashboards: Campaign-level and account-level performance metrics
Key metrics: Sent, opens, clicks, replies, bounces, unsubscribes, Lead Catcher leads
Team analytics: Compare performance across team members and campaigns
Best practices: Monitor bounce rate weekly (<3% target), track positive reply rate not just opens

内置仪表盘：营销活动级和账户级的表现指标
核心指标：发送量、打开率、点击率、回复率、退回率、退订率、Lead Catcher线索量
团队数据分析：对比团队成员和营销活动的表现
最佳实践：每周监控退回率（目标<3%），重点跟踪正向回复率而非仅打开率

Senders & Team

发件人与团队

Senders: Connected email accounts used for sending. Each has its own daily limit and reputation.
Team: Members can be assigned campaigns and leads. Roles control access.
Sender management: Settings > Senders to connect, configure from-name, set daily limits

发件人：用于发送邮件的关联邮箱账户。每个账户有独立的每日限额和信誉。
团队：成员可被分配营销活动和线索。角色控制访问权限。
发件人管理：进入设置>发件人页面进行账户连接、配置发件人名称、设置每日限额

Mailshake data model

Mailshake数据模型

Core entities — understand these to navigate the UI and work with the API:

Entity	What it represents	Key relationships
Campaign	A multi-step email sequence	Has Messages (steps), has Recipients
Recipient	A contact enrolled in a campaign	Belongs to a Campaign, has Activity
Lead	A reply captured by Lead Catcher	Belongs to a Campaign, linked to a Recipient
Message	A step in a campaign (initial or follow-up)	Belongs to a Campaign
Sender	A connected email account	Used by Campaigns
Team Member	A user on the account	Can own Campaigns and Leads

核心实体 — 理解这些实体有助于导航UI和使用API：

实体	代表内容	关键关联
Campaign	多步骤邮件序列	包含Messages（步骤），关联Recipients
Recipient	加入营销活动的联系人	属于某个Campaign，关联Activity
Lead	Lead Catcher捕获的回复线索	属于某个Campaign，关联Recipient
Message	营销活动中的一个步骤（初始或跟进邮件）	属于某个Campaign
Sender	关联的邮箱账户	被Campaign使用
Team Member	账户下的用户	可拥有Campaign和Lead

API & Integrations

API与集成

For detailed API documentation including all endpoints, authentication, rate limits, and webhook event payloads, consult

references/mailshake-api-reference.md

Quick reference: Base URL

https://api.mailshake.com/2017-04-01

, API key auth (

apiKey

parameter), rate limit 100 requests/minute. Key capabilities: campaign CRUD, recipient management, activity tracking, Lead Catcher management, webhooks.

Always reference
references/mailshake-api-reference.md
when answering API questions — point the user to it for the full endpoint catalog, request/response schemas, and rate limit details.

如需包含所有端点、认证方式、速率限制和Webhook事件负载的详细API文档，请查阅

references/mailshake-api-reference.md

。

快速参考：基础URL

https://api.mailshake.com/2017-04-01

，API密钥认证（

apiKey

参数），速率限制为每分钟100次请求。核心功能：营销活动CRUD、收件人管理、活动跟踪、Lead Catcher管理、Webhooks。

回答API相关问题时请务必引用

references/mailshake-api-reference.md

— 引导用户查看完整的端点目录、请求/响应schema和速率限制详情。

Native integrations

原生集成

CRM: Salesforce (push leads, sync activity), HubSpot (push leads, sync activity), Pipedrive (push leads)
Automation: Zapier (triggers for opens, clicks, replies, new leads; actions for adding recipients)
Communication: Slack (notifications for replies, leads)
Enrichment: Voila Norbert, Hunter (email verification before import)

CRM：Salesforce（推送线索、同步活动）、HubSpot（推送线索、同步活动）、Pipedrive（推送线索）
自动化：Zapier（触发事件：打开、点击、回复、新线索；操作：添加收件人）
沟通工具：Slack（回复、线索通知）
信息补全：Voila Norbert、Hunter（导入前邮箱验证）

Step 4 — Actionable guidance

步骤4 — 可落地的指导方案

Based on the user's specific question:

Step-by-step instructions — numbered steps to accomplish their goal in Mailshake
Configuration recommendations — specific settings to change, with navigation paths
Common pitfalls — what can go wrong and how to avoid it
Verification — how to confirm the change worked
For API questions — always include a pointer: "For the full endpoint catalog, request/response schemas, and rate limits, see
```
references/mailshake-api-reference.md
```
."

根据用户的具体问题：

分步操作说明 — 完成目标的编号式步骤（在Mailshake中的操作流程）
配置建议 — 具体的设置修改项及导航路径
常见陷阱 — 可能出现的问题及规避方法
验证方式 — 如何确认设置已生效
API相关问题 — 务必包含提示：“如需完整的端点目录、请求/响应schema和速率限制，请查看
```
references/mailshake-api-reference.md
```
。”

Gotchas

注意事项

Don't confuse Lead Catcher with a CRM. Lead Catcher captures and tracks email replies — it's a triage tool, not a deal pipeline. Qualified leads should be pushed to Salesforce/HubSpot for pipeline management. Claude often treats Lead Catcher as a full CRM replacement.
Don't use "sequence" when talking about Mailshake. Mailshake calls them "campaigns." Using "sequence" (Apollo/Salesloft terminology) confuses the user and the UI. Always say "campaign" for Mailshake.
Don't assume deliverability is configured. New Mailshake accounts often have no SPF/DKIM/DMARC, no custom tracking domain, and no warmup plan. Always check domain auth status before troubleshooting send issues.
Don't recommend features available only on higher plans without asking. A/B testing, team analytics, and some integrations are plan-gated. Ask about the user's plan before recommending these features.
Don't ignore Mailshake's API rate limits. 100 requests/minute is strict. Bulk operations (adding thousands of recipients) must be batched with rate limiting. Claude tends to generate tight loops without delays.

不要将Lead Catcher与CRM混淆。 Lead Catcher捕获并跟踪邮件回复 — 它是一个分流工具，而非交易管道管理工具。合格线索应推送至Salesforce/HubSpot进行管道管理。Claude常误将Lead Catcher当作完整CRM使用。
在提及Mailshake时不要使用“sequence”一词。 Mailshake将其称为“campaigns”。使用“sequence”（Apollo/Salesloft术语）会混淆用户和UI。提及Mailshake时请始终使用“campaign”。
不要默认送达率配置已完成。 新的Mailshake账户通常未配置SPF/DKIM/DMARC、无自定义跟踪域名且无暖养计划。排查发送问题前请先检查域名认证状态。
推荐仅高级套餐可用的功能前请先询问用户套餐。 A/B测试、团队数据分析和部分集成功能是套餐专属的。推荐前请先确认用户的套餐类型。
不要忽略Mailshake的API速率限制。 每分钟100次请求的限制较为严格。批量操作（添加数千个收件人）必须分批处理并遵守速率限制。Claude常生成无延迟的紧凑循环。

Step 5 — Related skills

步骤5 — 相关技能模块

```
/sales-cadence
```
— Design outbound cadence strategy (platform-agnostic, works with Mailshake campaigns)
```
/sales-deliverability
```
— Cross-platform email deliverability — SPF/DKIM/DMARC, warmup, inbox placement
```
/sales-prospect-list
```
— Build prospect lists to import into Mailshake
```
/sales-enrich
```
— Enrich contacts with emails/phones before importing
```
/sales-integration
```
— Connect Mailshake to other tools via webhooks, Zapier, or API
```
/sales-apollo
```
— Apollo.io platform help (if using Apollo instead of Mailshake)
```
/sales-salesloft
```
— Salesloft platform help (if using Salesloft instead of Mailshake)
```
/sales-do
```
— Not sure which skill to use? The router matches any sales objective to the right skill.

```
/sales-cadence
```
— 设计outbound触达节奏策略（跨平台，适用于Mailshake营销活动）
```
/sales-deliverability
```
— 跨平台邮件送达率优化 — SPF/DKIM/DMARC、暖养、收件箱投递
```
/sales-prospect-list
```
— 构建可导入Mailshake的潜在客户列表
```
/sales-enrich
```
— 导入前补全联系人邮箱/电话信息
```
/sales-integration
```
— 通过Webhooks、Zapier或API连接Mailshake与其他工具
```
/sales-apollo
```
— Apollo.io平台帮助（若使用Apollo而非Mailshake）
```
/sales-salesloft
```
— Salesloft平台帮助（若使用Salesloft而非Mailshake）
```
/sales-do
```
— 不确定使用哪个技能？该模块可将任何销售目标匹配至对应技能。

Examples

示例

Example 1: Lead Catcher setup

示例1：Lead Catcher搭建

User says: "How do I set up Lead Catcher in Mailshake?" Skill does:

Explains Lead Catcher's purpose — automatic lead capture from campaign replies
Walks through enabling Lead Catcher and configuring auto-assignment rules
Explains lead statuses (open, won/closed, ignored, lost) and when to use each
Clarifies the distinction between Lead Catcher and CRM pipeline management Result: User has Lead Catcher enabled with assignment rules and understands how to triage leads

用户提问：“如何在Mailshake中搭建Lead Catcher？” 技能模块操作：

解释Lead Catcher的用途 — 自动从营销活动回复中捕获线索
引导完成Lead Catcher启用及自动分配规则配置
解释线索状态（待处理、已成交/已关闭、忽略、已流失）及适用场景
明确Lead Catcher与CRM管道管理的区别结果：用户启用了带分配规则的Lead Catcher，并理解如何分流线索

Example 2: API recipient import

示例2：API导入收件人

User says: "I want to use the Mailshake API to add 500 recipients to a campaign" Skill does:

Points to
```
references/mailshake-api-reference.md
```
for full API docs
Explains the
```
/recipients/add
```
endpoint — emailAddress required, fields for merge vars
Warns about rate limits (100 req/min) and recommends batching
Shows how to check import status with
```
/recipients/addStatus
```
Result: User knows the endpoint, required fields, and how to batch large imports within rate limits

用户提问：“我想使用Mailshake API向营销活动添加500个收件人” 技能模块操作：

引导查看
```
references/mailshake-api-reference.md
```
获取完整API文档
解释
```
/recipients/add
```
端点 — 必填emailAddress字段，支持合并变量字段
提醒速率限制（100次请求/分钟）并推荐分批处理
展示如何使用
```
/recipients/addStatus
```
检查导入状态结果：用户了解所需端点、必填字段及如何在速率限制内完成批量导入

Troubleshooting

故障排查

Low open rates

打开率低

Symptom: Campaign open rates below 30% Cause: Missing domain authentication, poor sender reputation, or weak subject lines Solution: Verify SPF/DKIM/DMARC in your DNS. Set up a custom tracking domain. Check sender reputation. A/B test subject lines. See

/sales-deliverability

for a full diagnosis framework.

症状：营销活动打开率低于30% 原因：缺少域名认证、发件人信誉差或主题行吸引力不足 解决方案：在DNS中验证SPF/DKIM/DMARC配置。设置自定义跟踪域名。检查发件人信誉。A/B测试主题行。完整诊断框架请查看

/sales-deliverability

。

Emails bouncing

邮件退回

Symptom: Bounce rate above 3% Cause: Unverified email list or stale data Solution: Verify emails before import using a verification tool (NeverBounce, ZeroBounce). Remove hard bounces immediately. Mailshake does not verify on upload — this is your responsibility.

症状：退回率高于3% 原因：邮箱列表未验证或数据过时 解决方案：导入前使用验证工具（NeverBounce、ZeroBounce）验证邮箱有效性。立即移除硬退回邮箱。Mailshake不会在上传时自动验证 — 这是您的责任。

Lead Catcher not capturing replies

Lead Catcher未捕获回复

Symptom: Replies come in but don't appear in Lead Catcher Cause: Lead Catcher not enabled for the campaign, or reply detected as out-of-office/bounce Solution: Check campaign settings — Lead Catcher must be enabled per campaign. Auto-replies and OOO messages are filtered out by default. Check the Activity > Replies tab to confirm the reply was received.

症状：收到回复但未出现在Lead Catcher中原因：营销活动未启用Lead Catcher，或回复被识别为自动回复/退回 解决方案：检查营销活动设置 — 需为每个营销活动单独启用Lead Catcher。自动回复和外出办公消息默认会被过滤。进入活动>回复标签页确认是否收到该回复。