Back to Details

sales-lemlist

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Lemlist Platform Help

Lemlist平台使用帮助

Help the user with Lemlist platform questions — from multichannel sequence setup and Lemwarm through lead management, enrichment, AI personalization, LinkedIn automation, unified inbox, API, and integrations.
为用户解答Lemlist平台相关问题 — 从多渠道序列创建、Lemwarm邮箱预热，到线索管理、信息补全、AI个性化、LinkedIn自动化、统一收件箱、API及集成功能等全场景。

Step 1 — Gather context

步骤1 — 收集上下文信息

Ask the user:
  1. What area of Lemlist do you need help with?
    • A) Sequences — creating, managing, or optimizing multichannel sequences (route to 
      /sales-cadence
      for strategy)
    • B) Lead database — finding prospects with People Database, filters, intent signals
    • C) Enrichment — waterfall enrichment for emails and phone numbers
    • D) Lemwarm — warmup, deliverability score, sender reputation
    • E) Unified inbox — managing replies across channels
    • F) LinkedIn — automated LinkedIn steps, connection requests, messages
    • G) Calls — in-app dialer, call steps in sequences
    • H) WhatsApp — WhatsApp messaging steps (add-on)
    • I) AI personalization — dynamic variables, AI-generated content
    • J) Integrations — HubSpot, Salesforce, Pipedrive, Zapier, Make
    • K) API & Webhooks — automation, lead import, campaign management
    • L) Admin — billing, plan features, team settings
    • M) Something else — describe it
  2. What's your role?
    • A) Sales rep / AE / BDR
    • B) Sales manager / team lead
    • C) RevOps / Sales Ops
    • D) Agency owner / account manager
    • E) Admin / IT
    • 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. 你需要Lemlist哪方面的帮助？
    • A) 序列 — 创建、管理或优化多渠道序列（策略相关请跳转至/sales-cadence）
    • B) 线索数据库 — 使用人脉数据库查找潜在客户、设置筛选条件、获取意向信号
    • C) 信息补全 — 为邮箱和手机号进行瀑布式信息补全
    • D) Lemwarm — 邮箱预热、送达率评分、发件人信誉维护
    • E) 统一收件箱 — 管理多渠道回复
    • F) LinkedIn — 自动化LinkedIn操作、发送连接请求、消息触达
    • G) 电话 — 应用内拨号器、序列中的电话触达步骤
    • H) WhatsApp — WhatsApp消息触达步骤（附加功能）
    • I) AI个性化 — 动态变量、AI生成内容
    • J) 集成工具 — HubSpot、Salesforce、Pipedrive、Zapier、Make
    • K) API与Webhooks — 自动化操作、线索导入、营销活动管理
    • L) 管理设置 — 账单、套餐功能、团队设置
    • M) 其他 — 请详细描述
  2. 你的角色是什么？
    • A) 销售代表/AE/BDR
    • B) 销售经理/团队主管
    • C) RevOps/Sales Ops
    • D) 代理机构所有者/客户经理
    • E) 管理员/IT人员
    • F) 创始人/独立销售
    • G) 其他
  3. 你想要达成什么目标？（描述具体目标或问题）
如果用户的请求已包含大部分上述上下文信息，可直接跳转至对应步骤。 先基于合理假设给出初步解答（需明确说明假设内容），最后仅询问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 outside Lemlist → 
    /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
  • Lemlist外的联系人信息补全 → 
    /sales-enrich
  • 触达节奏策略/序列设计 → 
    /sales-cadence
  • 跨平台送达率优化 → 
    /sales-deliverability
  • 工具集成架构设计 → 
    /sales-integration
否则，直接基于平台知识库为用户解答。

Step 3 — Lemlist platform reference

步骤3 — Lemlist平台参考指南

Provide module-by-module guidance based on the user's area:
根据用户的需求模块提供针对性指导：

Sequences (Multichannel Campaigns)

序列（多渠道营销活动）

  • What it is: A sequence in Lemlist is a multichannel outreach campaign — email steps, LinkedIn actions, phone calls, and WhatsApp messages on an automated schedule
  • Key concepts: Sequence = multichannel campaign, steps = touchpoints across channels, leads = enrolled contacts
  • Channels available: Email, LinkedIn (connection requests, profile visits, messages), phone (in-app dialer), WhatsApp (paid add-on at $20/seat/month)
  • A/B testing: Test subject lines, email body content, and entire step variants
  • Lead statuses: interested, not interested, contacted, not contacted
  • Best practices: Keep initial emails under 125 words, mix channels (don't do 3+ email steps in a row), use AI personalization for Level 3+ at scale
  • 定义：Lemlist中的序列是一种多渠道触达营销活动 — 包含按自动排期执行的邮件步骤、LinkedIn操作、电话沟通及WhatsApp消息
  • 核心概念：序列 = 多渠道营销活动，步骤 = 跨渠道触达节点，线索 = 已加入序列的联系人
  • 支持渠道：邮件、LinkedIn（连接请求、主页访问、消息）、电话（应用内拨号器）、WhatsApp（付费附加功能，20美元/席位/月）
  • A/B测试：可测试邮件主题、正文内容及完整步骤变体
  • 线索状态：感兴趣、不感兴趣、已联系、未联系
  • 最佳实践：初始邮件字数控制在125词以内，混合使用多种渠道（不要连续发送3封以上邮件），针对大量潜在客户（100+）使用AI个性化功能实现3级以上的个性化触达

Lead Database (People Database)

线索数据库（人脉数据库）

  • What it is: Built-in B2B lead database with 600M+ contacts and smart filtering
  • Key features: Search by title, seniority, industry, company size, location, tech stack
  • Intent signals: Identifies prospects actively researching relevant topics (newer feature)
  • Credit model: Pay per lead revealed — credits deducted on export/use
  • Pre-verification: Leads from People Database are verified before delivery
  • Best practices: Use filters to narrow before revealing — don't burn credits on broad searches
  • 定义：内置B2B线索数据库，包含6亿+联系人及智能筛选功能
  • 核心功能：可按职位、职级、行业、公司规模、地域、技术栈进行搜索
  • 意向信号：识别正在主动研究相关主题的潜在客户（较新功能）
  • 积分模式：按解锁的线索数量付费 — 导出或使用线索时扣除积分
  • 预验证：从人脉数据库获取的线索在交付前已完成验证
  • 最佳实践：先使用筛选条件缩小范围再解锁线索 — 不要在宽泛搜索上浪费积分

Enrichment

信息补全

  • What it is: Built-in waterfall enrichment — find verified emails and phone numbers for your leads
  • How it works: Lemlist tries multiple data providers in sequence (waterfall) to maximize match rates
  • Email finder: Find professional email addresses from name + company
  • Phone finder: Find direct/mobile phone numbers
  • Verification: Emails are verified before delivery to reduce bounce rates
  • Best practices: Enrich leads before adding to sequences — don't send to unverified addresses
  • 定义：内置瀑布式信息补全功能 — 为你的线索查找已验证的邮箱和手机号
  • 工作原理：Lemlist会依次尝试多个数据提供商（瀑布式）以最大化匹配率
  • 邮箱查找：通过姓名+公司信息查找专业邮箱地址
  • 手机号查找：查找直线/手机号码
  • 验证机制：邮箱在交付前会经过验证以降低退信率
  • 最佳实践：在将线索加入序列前先完成信息补全 — 不要向未验证的地址发送邮件

Lemwarm (Deliverability)

Lemwarm（送达率优化）

  • What it is: Built-in email warmup tool included with every Lemlist seat at no extra cost
  • How it works: Sends automated warmup emails to a premium network of 10,000+ real users, generating real opens and replies to build sender reputation
  • Deliverability score: Score out of 100 showing inbox placement quality (target 90+)
  • Warmup settings: Configure emails/day (recommended 30/day for accounts <6 months, 40/day for older) and ramp-up increment
  • Warmup timeline: Minimum 3-5 weeks before adding cold outbound
  • Inbox rotation: Distribute sends across multiple email accounts connected to a sequence
  • Best practices: Enable Lemwarm on every connected email account immediately. Keep warmup running even during active campaigns — it maintains reputation.
  • 定义：内置邮箱预热工具，所有Lemlist席位免费使用
  • 工作原理：向由10000+真实用户组成的优质网络发送自动化预热邮件，生成真实的打开和回复记录以提升发件人信誉
  • 送达率评分：满分100分的评分，反映邮箱投递质量（目标90分以上）
  • 预热设置：可配置每日发送邮件数量（推荐使用未满6个月的账户每天30封，老账户每天40封）及增量提升节奏
  • 预热周期：至少需要3-5周的预热时间，之后再启动冷触达
  • 邮箱轮换：在多个已连接的邮箱账户间分配发送任务
  • 最佳实践：立即为所有已连接的邮箱账户启用Lemwarm。即使在活跃营销活动期间也要保持预热运行 — 这有助于维护发件人信誉。

Unified Inbox

统一收件箱

  • What it is: Single view for all replies across email, LinkedIn, and other channels
  • Key features: Reply tracking, conversation threads, label conversations, draft responses
  • Channel aggregation: See email replies, LinkedIn messages, and WhatsApp responses in one place
  • Best practices: Check unified inbox daily, respond within 1 hour for best conversion
  • 定义：可查看所有渠道（邮件、LinkedIn及其他渠道）回复的统一视图
  • 核心功能：回复追踪、对话线程、对话标签、草稿回复
  • 渠道聚合：在同一界面查看邮件回复、LinkedIn消息及WhatsApp回复
  • 最佳实践：每日查看统一收件箱，在1小时内回复以获得最佳转化率

LinkedIn Automation

LinkedIn自动化

  • What it is: Automated LinkedIn steps within sequences — profile visits, connection requests, and messages
  • Step types: Visit profile, send connection request (with note, under 300 chars), send message (to existing connections)
  • Limits: LinkedIn has daily action limits — Lemlist respects these but monitor your LinkedIn account for warnings
  • Plan requirement: Multichannel Expert plan ($99/user/month) required for LinkedIn steps
  • Best practices: Always visit profile before sending connection request. Keep connection request notes casual and non-salesy. Don't exceed 20-30 connection requests/day.
  • 定义：序列中的自动化LinkedIn操作 — 主页访问、连接请求、消息发送
  • 操作类型：访问主页、发送连接请求（附备注，字数不超过300字符）、发送消息（仅针对已连接联系人）
  • 限制说明：LinkedIn有每日操作限制 — Lemlist会遵守这些限制，但请你关注自己的LinkedIn账户是否收到警告
  • 套餐要求：需要Multichannel Expert套餐（99美元/用户/月）才能使用LinkedIn步骤
  • 最佳实践：发送连接请求前先访问对方主页。连接请求备注要保持随意，避免过于商业化。每日发送的连接请求不要超过20-30个。

Calls (In-App Dialer)

电话（应用内拨号器）

  • What it is: Built-in calling within Lemlist sequences — add phone steps alongside email and LinkedIn
  • Key features: Click-to-call from lead record, call logging within sequence activity
  • Plan requirement: Multichannel Expert plan required
  • Best practices: Place call steps within 24 hours of an email step — reference the email in your opener
  • 定义：Lemlist序列中的内置电话功能 — 可在邮件和LinkedIn步骤之外添加电话触达步骤
  • 核心功能：从线索记录一键拨号、在序列活动中记录通话
  • 套餐要求：需要Multichannel Expert套餐
  • 最佳实践：在邮件步骤后的24小时内安排电话触达 — 在开场白中提及之前发送的邮件

WhatsApp

WhatsApp

  • What it is: WhatsApp messaging steps within sequences (paid add-on at $20/seat/month)
  • How it works: Add WhatsApp steps to multichannel sequences alongside email, LinkedIn, and calls
  • Requirement: WhatsApp Business account + Lemlist WhatsApp add-on
  • Best practices: Use WhatsApp for warm follow-ups after email/LinkedIn engagement, not cold first-touch
  • 定义：序列中的WhatsApp消息触达步骤（付费附加功能，20美元/席位/月）
  • 工作原理：在多渠道序列中添加WhatsApp步骤，与邮件、LinkedIn及电话触达配合使用
  • 使用要求：需要WhatsApp Business账户 + Lemlist WhatsApp附加功能
  • 最佳实践：在邮件/LinkedEngagement触达后使用WhatsApp进行跟进，不要用于首次冷触达

AI Personalization

AI个性化

  • What it is: AI-powered content generation that pulls data from LinkedIn profiles, company websites, and other sources to create personalized outreach at scale
  • How it works: Configure AI variables that research each lead and generate custom snippets (icebreakers, pain points, company references)
  • Dynamic variables: Standard merge fields ({{firstName}}, {{companyName}}) plus AI-generated custom variables
  • Best for: Level 3-4 personalization at scale (100+ prospects) — finding specific talking points per lead
  • Not for: Simple {{firstName}} personalization — just use standard variables for that
  • 定义：AI驱动的内容生成功能，可从LinkedIn主页、公司网站及其他来源提取数据，实现规模化的个性化触达
  • 工作原理：配置AI变量，系统会针对每个线索进行调研并生成自定义片段（破冰话术、痛点分析、公司参考信息）
  • 动态变量：标准合并字段（{{firstName}}, {{companyName}}）加上AI生成的自定义变量
  • 适用场景：针对大量潜在客户（100+）实现3-4级个性化触达 — 为每个线索找到特定的沟通切入点
  • 不适用场景：简单的{{firstName}}个性化 — 此类场景直接使用标准变量即可

Lemlist data model

Lemlist数据模型

Core entities — understand these to navigate the UI and work with the API:
EntityWhat it representsKey relationships
Campaign/SequenceA multichannel outreach sequenceHas Steps, has Leads, uses Email Accounts
LeadA contact enrolled in a sequenceBelongs to a Campaign, has activity tracking
ContactA person in your databaseCan be enrolled in multiple Campaigns
CompanyAn organizationHas Contacts, has firmographic data
Email AccountA connected sending mailboxUsed by Campaigns, has Lemwarm status
StepA touchpoint in a sequence (email, LinkedIn, call, WhatsApp)Belongs to a Campaign
ScheduleSending window and timezone configAssociated with Campaigns
核心实体 — 了解这些有助于你导航UI界面并使用API：
实体代表内容关键关联
Campaign/Sequence多渠道触达序列包含步骤、关联线索、使用邮箱账户
Lead已加入序列的联系人属于某个营销活动，有活动追踪记录
Contact数据库中的联系人可加入多个营销活动
Company企业组织关联联系人，包含企业画像数据
Email Account已连接的发件邮箱被营销活动使用，有Lemwarm状态
Step序列中的触达节点（邮件、LinkedIn、电话、WhatsApp）属于某个营销活动
Schedule发送窗口及时区配置与营销活动关联

API & Integrations

API与集成

For detailed API documentation including all endpoints, authentication, rate limits, and webhook event payloads, consult 
references/lemlist-api-reference.md
.
Quick reference: Base URL 
https://api.lemlist.com/api
, Basic auth (
:apiKey
base64-encoded) or Bearer token, rate limit 20 requests per 2 seconds. Key capabilities: campaign CRUD, lead management, sequence steps, enrichment, Lemwarm control, People Database search, inbox/messaging, webhooks.
Always reference 
references/lemlist-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/lemlist-api-reference.md
。
快速参考：基础URL 
https://api.lemlist.com/api
，支持Basic认证（API密钥Base64编码）或Bearer令牌，速率限制为每2秒20次请求。核心功能：营销活动增删改查、线索管理、序列步骤、信息补全、Lemwarm控制、人脉数据库搜索、收件箱/消息、Webhooks。
回答API相关问题时，请务必引用："如需完整的端点目录、请求/响应 schema及速率限制详情，请查看
references/lemlist-api-reference.md
。"

Native integrations

原生集成工具

  • CRM: HubSpot (native — push leads, sync activity), Salesforce (native — 2-way sync), Pipedrive (native)
  • Enrichment: Apollo, Clay, Clearout, Uplead, Lusha, Pharow
  • Automation: Zapier (triggers for opens, clicks, replies; actions for adding leads), Make, n8n, Pabbly, Relay.app
  • Calling: Aircall, Ringover, Trellus
  • Communication: Slack, WhatsApp (add-on)
  • Data: Airtable, Google Sheets
  • Intent: Snitcher, Lonescale, Phantombuster, Trigify, Albacross
  • Chrome extension: LinkedIn prospecting
  • CRM：HubSpot（原生集成 — 推送线索、同步活动）、Salesforce（原生集成 — 双向同步）、Pipedrive（原生集成）
  • 信息补全：Apollo、Clay、Clearout、Uplead、Lusha、Pharow
  • 自动化工具：Zapier（针对打开、点击、回复的触发事件；添加线索的操作）、Make、n8n、Pabbly、Relay.app
  • 电话工具：Aircall、Ringover、Trellus
  • 沟通工具：Slack、WhatsApp（附加功能）
  • 数据工具：Airtable、Google Sheets
  • 意向数据工具：Snitcher、Lonescale、Phantombuster、Trigify、Albacross
  • Chrome扩展：LinkedIn潜在客户开发

Step 4 — Actionable guidance

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

Based on the user's specific question:
  1. Step-by-step instructions — numbered steps to accomplish their goal in Lemlist
  2. Configuration recommendations — specific settings to change, with navigation paths
  3. Common pitfalls — what can go wrong and how to avoid it
  4. Verification — how to confirm the change worked
  5. For API questions — always include a pointer: "For the full endpoint catalog, request/response schemas, and rate limits, see 
    references/lemlist-api-reference.md
    ."
根据用户的具体问题：
  1. 分步操作指南 — 完成目标的编号式步骤说明
  2. 配置建议 — 需修改的具体设置及导航路径
  3. 常见陷阱 — 可能出现的问题及规避方法
  4. 验证方法 — 如何确认设置已生效
  5. API相关问题 — 务必包含提示："如需完整的端点目录、请求/响应 schema及速率限制详情，请查看
    references/lemlist-api-reference.md
    。"

Gotchas

注意事项

Best-effort from research — review these, especially items about plan-gated features and integration gotchas that may be outdated.
  • Don't confuse Lemlist's per-seat pricing with unlimited-mailbox tools. Lemlist charges per user/month and limits sending accounts (5 per user on highest plan, $9 per additional inbox). Unlike Instantly or Smartlead which offer unlimited mailboxes on flat-fee plans, Lemlist costs scale with team size and mailbox count. Always check the user's plan before recommending adding more sender accounts.
  • Don't use "campaign" interchangeably with "sequence." Lemlist calls them "sequences" in the UI and "campaigns" in the API. This inconsistency confuses users. Use "sequence" when discussing the UI and "campaign" when discussing the API. If the user says "campaign," clarify which they mean.
  • Don't assume LinkedIn steps are available. LinkedIn automation requires the Multichannel Expert plan ($99/user/month). The Email Pro plan ($69/user/month) is email-only. Ask about the user's plan before building multichannel sequences with LinkedIn steps.
  • Don't skip Lemwarm setup. Lemwarm is free with every seat — there's no reason not to enable it. New accounts without Lemwarm warmup will land in spam. Enable it immediately on every connected email account with at least 30 emails/day warmup volume.
  • Don't ignore LinkedIn daily limits. Lemlist automates LinkedIn actions but LinkedIn still enforces daily limits. Exceeding ~20-30 connection requests/day or ~50-80 profile visits/day risks LinkedIn account restrictions. Claude tends to suggest aggressive LinkedIn step volumes that exceed safe limits.
基于研究的最佳实践 — 请重点关注这些内容，尤其是套餐专属功能及集成相关的注意事项，这些信息可能会随时间更新。
  • 不要混淆Lemlist的按席位定价与无限邮箱工具。Lemlist按用户/月收费，并限制发件邮箱数量（最高套餐每个用户可添加5个邮箱，额外邮箱每个9美元/月）。与Instantly或Smartlead等固定费用提供无限邮箱的工具不同，Lemlist的成本会随团队规模和邮箱数量增加而上升。在建议添加更多发件邮箱前，请先确认用户的套餐。
  • 不要混用“campaign”和“sequence”。Lemlist在UI界面中称为“sequences”，在API中称为“campaigns”。这种不一致容易让用户混淆。讨论UI时使用“sequence”，讨论API时使用“campaign”。如果用户提到“campaign”，请明确他们指的是UI还是API。
  • 不要默认LinkedIn功能可用。LinkedIn自动化需要Multichannel Expert套餐（99美元/用户/月）。Email Pro套餐（69美元/用户/月）仅支持邮件功能。在构建包含LinkedIn步骤的多渠道序列前，请询问用户的套餐类型。
  • 不要跳过Lemwarm设置。Lemwarm对所有席位免费 — 没有理由不启用它。未进行Lemwarm预热的新账户邮件会被归入垃圾邮件。请立即为所有已连接的邮箱账户启用Lemwarm，且每日预热邮件数量至少为30封。
  • 不要忽视LinkedIn每日限制。虽然Lemlist可自动化LinkedIn操作，但LinkedIn仍会执行每日限制。每日发送超过20-30个连接请求或50-80次主页访问可能导致LinkedIn账户受限。Claude通常会建议超出安全限制的LinkedIn操作量，请避免这种情况。

Step 5 — Related skills

步骤5 — 相关技能

  • /sales-cadence
    — Design outbound cadence strategy (platform-agnostic, works with Lemlist sequences)
  • /sales-deliverability
    — Cross-platform email deliverability — SPF/DKIM/DMARC, warmup, inbox placement
  • /sales-prospect-list
    — Build prospect lists to import into Lemlist
  • /sales-enrich
    — Enrich contacts with emails/phones outside of Lemlist's built-in enrichment
  • /sales-integration
    — Connect Lemlist to other tools via webhooks, Zapier, or API
  • /sales-mailshake
    — Mailshake platform help (if using Mailshake instead of Lemlist)
  • /sales-smartlead
    — Smartlead platform help (if using Smartlead instead of Lemlist)
  • /sales-apollo
    — Apollo.io platform help (if using Apollo instead of Lemlist)
  • /sales-salesloft
    — Salesloft platform help (if using Salesloft instead of Lemlist)
  • /sales-do
    — Not sure which skill to use? The router matches any sales objective to the right skill.
  • /sales-cadence
    — 设计 outbound触达节奏策略（平台无关，适用于Lemlist序列）
  • /sales-deliverability
    — 跨平台邮件送达率优化 — SPF/DKIM/DMARC、邮箱预热、收件箱投递
  • /sales-prospect-list
    — 构建潜在客户列表并导入Lemlist
  • /sales-enrich
    — 在Lemlist内置信息补全功能外，为联系人补充邮箱/手机号信息
  • /sales-integration
    — 通过Webhooks、Zapier或API将Lemlist与其他工具连接
  • /sales-mailshake
    — Mailshake平台使用帮助（如果使用Mailshake而非Lemlist）
  • /sales-smartlead
    — Smartlead平台使用帮助（如果使用Smartlead而非Lemlist）
  • /sales-apollo
    — Apollo.io平台使用帮助（如果使用Apollo而非Lemlist）
  • /sales-salesloft
    — Salesloft平台使用帮助（如果使用Salesloft而非Lemlist）
  • /sales-do
    — 不确定使用哪个技能？该路由可将任何销售目标匹配到合适的技能。

Examples

示例

Example 1: Multichannel sequence setup

示例1：多渠道序列创建

User says: "How do I create a multichannel sequence in Lemlist with email and LinkedIn?" Skill does:
  1. Confirms user is on Multichannel Expert plan (LinkedIn requires it)
  2. Walks through creating a sequence with email step 1, LinkedIn profile visit day 1, LinkedIn connection request day 2, email follow-up day 4
  3. Explains LinkedIn step configuration — connection request note under 300 chars, daily limit awareness
  4. Recommends enabling Lemwarm on all connected email accounts before launching
  5. Suggests A/B testing subject lines on the first email step Result: User has a multichannel sequence with email + LinkedIn steps ready to launch after warmup
用户提问：“如何在Lemlist中创建包含邮件和LinkedIn的多渠道序列？” 技能执行操作：
  1. 确认用户使用的是Multichannel Expert套餐（LinkedIn功能需要此套餐）
  2. 引导用户创建序列：第1天发送邮件+访问LinkedIn主页，第2天发送LinkedIn连接请求，第4天发送跟进邮件
  3. 说明LinkedIn步骤配置 — 连接请求备注不超过300字符，提醒用户注意每日操作限制
  4. 建议在启动序列前为所有已连接的邮箱账户启用Lemwarm
  5. 建议对第一封邮件的主题进行A/B测试 结果：用户完成包含邮件+LinkedIn步骤的多渠道序列创建，可在预热完成后启动

Example 2: Lemwarm setup and deliverability check

示例2：Lemwarm设置及送达率检查

User says: "I just connected 3 new email accounts to Lemlist. How do I warm them up?" Skill does:
  1. Walks through enabling Lemwarm on each email account — Warm up section, set to 30 emails/day with gradual ramp-up
  2. Explains the deliverability score (target 90+) and where to monitor it
  3. Stresses minimum 3-5 weeks warmup before adding to sequence rotation
  4. Recommends verifying SPF/DKIM/DMARC and setting up a custom tracking domain
  5. Points to 
    /sales-deliverability
    for full domain auth framework Result: User has Lemwarm running on all 3 accounts with monitoring plan
用户提问：“我刚在Lemlist中连接了3个新邮箱，如何进行预热？” 技能执行操作：
  1. 引导用户为每个邮箱账户启用Lemwarm — 进入Warm up板块，设置每日30封邮件并逐步增量
  2. 解释送达率评分（目标90分以上）及查看位置
  3. 强调至少需要3-5周的预热时间，之后再将邮箱加入序列轮换
  4. 建议验证SPF/DKIM/DMARC设置并配置自定义追踪域名
  5. 引导用户查看
    /sales-deliverability
    获取完整的域名认证框架 结果：用户为3个邮箱账户启用了Lemwarm，并制定了监控计划

Example 3: API lead import and sequence enrollment

示例3：API线索导入及序列加入

User says: "I want to use the Lemlist API to add leads from our CRM to a sequence" Skill does:
  1. Points to 
    references/lemlist-api-reference.md
    for full API docs
  2. Explains the 
    POST /campaigns/{id}/leads
    endpoint — email required, custom fields for personalization variables
  3. Shows authentication method (Basic auth with API key)
  4. Warns about rate limits (20 requests per 2 seconds) and recommends batching
  5. Suggests setting up webhooks for reply and interest events to sync back to CRM Result: User knows the endpoint, auth method, required fields, and how to build a bidirectional sync
用户提问：“我想使用Lemlist API将CRM中的线索添加到序列中” 技能执行操作：
  1. 引导用户查看
    references/lemlist-api-reference.md
    获取完整API文档
  2. 说明
    POST /campaigns/{id}/leads
    端点 — 需提供邮箱信息，可包含用于个性化变量的自定义字段
  3. 展示认证方式（使用API密钥的Basic认证）
  4. 提醒用户速率限制（每2秒20次请求）并建议使用批量操作
  5. 建议设置Webhooks以将回复和意向事件同步回CRM 结果：用户了解所需端点、认证方式、必填字段及如何构建双向同步

Troubleshooting

故障排除

Low open rates

打开率低

Symptom: Sequence open rates below 30% Cause: Insufficient warmup, missing domain authentication, poor sender reputation, or weak subject lines Solution: Check Lemwarm deliverability score on all email accounts — target 90+ before sequence sends. Verify SPF/DKIM/DMARC in your DNS. Set up a custom tracking domain. A/B test subject lines. See 
/sales-deliverability
for a full diagnosis framework.
症状：序列打开率低于30% 原因：预热不足、缺少域名认证、发件人信誉差或邮件主题吸引力弱 解决方案：检查所有邮箱账户的Lemwarm送达率评分 — 启动序列前目标达到90分以上。验证DNS中的SPF/DKIM/DMARC设置。配置自定义追踪域名。对邮件主题进行A/B测试。查看
/sales-deliverability
获取完整诊断框架。

LinkedIn steps not executing

LinkedIn步骤未执行

Symptom: LinkedIn steps in sequence show as skipped or failed Cause: LinkedIn connection expired, daily limits hit, or user on Email Pro plan (no LinkedIn access) Solution: Verify plan is Multichannel Expert ($99/user/month). Re-authenticate LinkedIn connection in Lemlist settings. Check if daily LinkedIn action limits were exceeded — reduce volume to 20-30 connection requests/day. Verify the lead has a LinkedIn URL in their profile.
症状：序列中的LinkedIn步骤显示为跳过或失败 原因：LinkedIn连接过期、达到每日限制或用户使用的是Email Pro套餐（无LinkedIn访问权限） 解决方案：确认用户使用的是Multichannel Expert套餐（99美元/用户/月）。在Lemlist设置中重新认证LinkedIn连接。检查是否超出LinkedIn每日操作限制 — 将连接请求数量减少至每日20-30个。验证线索资料中是否包含LinkedIn URL。

Enrichment returning low match rates

信息补全匹配率低

Symptom: Waterfall enrichment finding emails for less than 50% of leads Cause: Leads are in niche industries, use uncommon domains, or have limited public data Solution: Ensure you're providing name + company (minimum for email lookup). Try supplementing with external enrichment tools (Clay, Apollo, Lusha) via 
/sales-enrich
. For senior executives with low match rates, consider LinkedIn-first outreach instead of email.
症状：瀑布式信息补全仅能为不足50%的线索找到邮箱 原因：线索来自小众行业、使用不常见域名或公开数据有限 解决方案：确保提供了姓名+公司信息（邮箱查找的最低要求）。通过
/sales-enrich
使用外部信息补全工具（Clay、Apollo、Lusha）补充。针对匹配率低的高管，可考虑优先使用LinkedIn触达而非邮件。