sales-lemlist

name	sales-lemlist
description	Lemlist platform help — multichannel sequences, lead database, enrichment, Lemwarm, unified inbox, AI personalization, LinkedIn automation, calls, WhatsApp, API, integrations. Use when Lemlist sequences not sending, emails landing in spam despite Lemwarm, leads not importing correctly, integrations not syncing, People Database search returning poor matches, or Lemlist API calls failing. Do NOT use for building prospect lists (use /sales-prospect-list), designing cadence strategy (use /sales-cadence), cross-platform deliverability (use /sales-deliverability), or enriching contacts outside Lemlist (use /sales-enrich).
argument-hint	[describe what you need help with in Lemlist]
license	MIT
version	1.0.1
tags	["sales","outbound","cold-email","sequences","platform"]

Lemlist Platform Help

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.

Step 1 — Gather context

If references/learnings.md exists, read it first for accumulated knowledge.

Ask the user:

1. What area of Lemlist do you need help with?

   • A) Sequences — creating, managing, or optimizing multichannel sequences (for strategy, hand off: /sales-cadence {your question})
   • 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.

Step 2 — Route or answer directly

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.

Step 3 — Lemlist platform reference

Read references/platform-guide.md for the full module-by-module reference — Sequences, the Lead Database, Enrichment, Lemwarm, the Unified Inbox, LinkedIn automation, Calls, WhatsApp, AI Personalization, the data model, and the API/integrations quick reference. For the full API endpoint catalog, auth, rate limits, and webhook payloads, see references/lemlist-api-reference.md.

Answer using only the section relevant to the user's area — don't dump the full reference.

Step 4 — Actionable guidance

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."

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. The current plans (per lemlist.com/pricing) are Email $39/user/mo ($31 annual), Multichannel $109/user/mo ($87 annual, marked POPULAR), and Enterprise (custom) — both Email and Multichannel include 5 senders/user. Unlike Instantly or Smartlead which offer unlimited mailboxes on flat-fee plans, Lemlist costs scale with team size. Always check the user's plan before recommending adding more sender accounts. (Note: lemlist has historically charged ~$9/mo per additional sender beyond the included allotment, but that line item is not shown on the current pricing page — confirm in-app before quoting it.)

• 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 (plus calls, SMS, and the WhatsApp add-on) requires the Multichannel plan ($109/user/mo, $87 annual). The Email plan ($39/user/mo, $31 annual) is email-only. (Plan names changed from the older "Email Pro"/"Multichannel Expert"/"Outreach Scale" labels — don't quote those.) 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.

• Self-improving: If you discover something not covered here, append it to references/learnings.md with today's date.

Step 5 — Related skills

• /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.

Examples

Example 1: Multichannel sequence setup

User says: "How do I create a multichannel sequence in Lemlist with email and LinkedIn?" Skill does:

1. Confirms user is on the Multichannel 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

Example 2: Lemwarm setup and deliverability check

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

Example 3: API lead import and sequence enrollment

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

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.

LinkedIn steps not executing

Symptom: LinkedIn steps in sequence show as skipped or failed Cause: LinkedIn connection expired, daily limits hit, or user on the Email plan (no LinkedIn access) Solution: Verify plan is Multichannel ($109/user/mo, $87 annual). 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.

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.