Updated September 28, 2026 | 12 min read
Updated September 28, 2026 | 12 min read
Ready to launch?
Convert strategy into pipeline
Launch your first outbound campaign with verified leads, AI sequences, and multichannel outreach from one platform.
I Built a Claude Skill That Classifies All 5 Cold Email Reply Types (Here's the Prompt)
Last month, we watched a rep lose a $40k deal. The prospect replied “sounds interesting, tell me more” on a Tuesday. The rep didn’t respond until Thursday afternoon, four paragraphs deep into product specs nobody asked for. By then, the prospect had already signed with a competitor.
That one thread cost more than all the domain warm-up, ICP filtering, and A/B testing that led to it. And it happens constantly. We’ve seen it across hundreds of campaigns in lemlist, and it’s the reason we built a Reply Handler Claude Skill.
In this post, I’ll walk you through the five reply types every outbound team needs to classify, show you exactly how the Claude Skill handles each one, and give you the install steps to start using it today.
If you search “reply handler” online, most results talk about Apple XPC sessions or mail server configs. Different world entirely. In sales, a reply handler is the system (or AI skill) that sits between a prospect hitting reply and a rep deciding what to say next.
As Sendspark’s cold email reply guide explains, the process covers reading a prospect’s response, classifying its intent, and answering with the shortest path to a decision: a meeting, a clear no, or a specific answer to their question.
A reply handler typically covers four things:
- Sorting each response into a category (interested, objection, not now, not interested, wrong person) so the rep knows which playbook to follow
- Drafting a reply that matches the prospect’s tone and moves the conversation toward a clear next step
- Using what you know about the prospect’s role, company, or prior touchpoints to personalize the response
- Getting the right reply out before the prospect’s attention moves on
We built a Reply Handler Claude Skill that automates classification and response drafting, following a relationship-first approach rather than a “close at all costs” one. ColdIQ’s Claude Code Skills Directory lists it alongside dozens of other GTM-focused skills. You can grab the skill from GitHub.
Why most reps lose deals after the first reply
Teams pour weeks into ICP filters, domain warm-up, subject line testing, and cadence sequencing. Then a prospect actually replies, and the process quietly falls apart. That’s the part nobody optimizes for.
Here’s where it usually breaks down:
- A rough two-line reply sent in fifteen minutes tends to outperform a polished paragraph sent the next morning. Interest fades fast once someone hits send.
- A prospect writes “tell me more,” and the rep responds with four paragraphs of feature detail. The mismatch kills the momentum instantly.
- At volume, with several reps juggling hundreds of open threads, reply quality often depends on whoever happens to be fastest that day, not on a shared standard.
- Replies land in email, LinkedIn DMs, and sometimes SMS. Without one unified view, messages slip through.
Most outbound platforms, lemlist included, pause a sequence automatically once a prospect replies (this is often called “stop-on-reply”). That’s helpful, but it only solves half the problem. The gap between the pause and the rep’s actual response is where pipeline quietly leaks.
G2 shows a 4.6/5 rating from over 1,500 reviews (Lemlist Review 2026: Features, Pros & Cons, Alternatives) for lemlist, and the consistent feedback from our users is that reply speed is one of the biggest factors in converting outbound replies into booked meetings. In our own data, we’ve found that replies sent within 30 minutes of a prospect responding convert to meetings at roughly 2x the rate of replies sent 24+ hours later.
How most teams handle replies today (and where each approach breaks)
Before diving into the Claude Skill, it’s worth looking at what most teams actually do today.
Manual triage. A rep reads every reply, decides the category in their head, and writes each response from scratch. This works when you’re running 50 leads. It collapses at 500. Quality becomes inconsistent, speed drops, and the best reps spend half their day answering “not now” replies instead of working hot leads.
Native platform features. Tools like Outreach, Salesloft, and Reply.io have built-in reply detection that can flag sentiment (positive, negative, neutral) and auto-tag threads. Outreach’s “Smart Reply Assist” and Salesloft’s “Conductor AI” can suggest next steps. These features are useful, but they stay inside their own platform walls and typically don’t draft full responses. They also tend to classify replies into only two or three buckets (interested, not interested, other), which misses the nuance of timing deferrals and wrong-person redirects.
Instantly’s AI Reply Agent takes it a step further, auto-classifying across six categories and even sending responses autonomously. It’s a strong option for email-only teams that want full automation.
The Claude Skill approach sits in a different spot. You bring the reply and the context. Claude classifies it into five types, picks the matching response strategy, and drafts a reply you can edit before sending. It works across any channel (email, LinkedIn, SMS) because it operates on the text itself, not on a platform integration. And because it’s a markdown file you attach to Claude, you can customize the classification logic and response templates to match your voice.
Each of these approaches has tradeoffs. Manual triage gives you maximum control but doesn’t scale. Native tools scale but lack depth. The Claude Skill gives you depth and customization but requires a human in the loop. Pick based on your volume and how much you trust fully automated replies.
Five cold email reply types every handler must classify
Not every reply deserves the same response. Treating a hard “no” the same way you’d treat “sounds good, let’s talk” is one of the fastest ways to burn a lead that was actually still warm.
Interested replies
These look like “Sounds good, let’s talk” or “Can you send more info?” The goal here is simple: book the meeting without re-selling or adding friction. The most common mistake is sending a wall of features when the prospect already said yes.
Questions and objections
Pricing questions, competitor comparisons, “we already use X.” These tend to be your highest-quality replies, even though they don’t feel like it at first. Answer the specific question, then ask one question back to keep the thread moving.
Not now (timing deferrals)
“Circle back next quarter” or “not a priority right now” gets treated as a loss more often than it should. It usually isn’t one. The better move is locking in a concrete follow-up date and adding the lead to a nurture track.
Not interested (hard rejections)
“Not interested” or “please remove me” calls for a graceful exit. Honor the opt-out, thank them, and move on. Arguing or ignoring these replies can hurt your sender reputation.
Wrong person and out-of-office
“I’m not the right person for this” is really an opening, not a dead end, if you ask who the right person is. An out-of-office reply gives you a return date to re-time your outreach around.
Worked example: Here’s what this looks like in practice. A prospect replies: “We’re evaluating vendors next quarter. Can you reach back out in January?”
The Claude Skill classifies this as Not now (timing deferral), then drafts:
“Makes sense, January works. I’ll reach back out the first week. Quick question so I can make that follow-up useful: are you comparing tools for [specific use case], or is this a broader evaluation? Either way, happy to send a short overview in the meantime if that’d help.”
One question. Concrete date. No pressure. That’s the difference between a reply that keeps the thread alive and one that kills it.
Reply type | Example phrases | Primary goal | Common mistake |
|---|---|---|---|
Interested | “Let’s talk,” “Send more info” | Book meeting immediately | Over-pitching with features |
Question/Objection | “How much?”, “We use X already” | Answer, then ask one question | Sending a defensive paragraph |
Not now | “Maybe next quarter” | Set concrete follow-up date | Accepting vague timing |
Not interested | “Remove me,” “No thanks” | Close gracefully | Arguing or ignoring |
Wrong person/OOO | “I’m not the right person” | Get referral or re-time | Dropping the lead entirely |
How to respond to each cold email reply type
Every reply is a person who gave you a bit of their attention. That’s worth treating carefully, whether the answer is a yes or a no.
- Reference something from their reply so it’s clear you actually read it. Never open with a calendar link or a feature dump.
- A one-line reply gets a two-line response. A detailed objection gets a detailed (but tight) answer. Five paragraphs in response to eight words feels off, and prospects notice.
- Multiple questions create decision fatigue. “Would Thursday at 2pm work?” is easier to answer than “What does your calendar look like, and who else needs to be involved?”
- For hard rejections, a simple “understood, appreciate you letting me know” closes the thread without begging and leaves room for the future.
Tip: Enrichment data (LinkedIn activity, recent company news, CRM history) can make even a two-line reply feel personal rather than templated. lemlist’s AI Agentic Enrichment pulls this automatically, so reps don’t have to do manual research before every response. You can also browse our cold email reply templates for ready-made frameworks by reply type.
How the reply handler Claude skill for sales works
Here’s the mechanism behind it. You give Claude a prospect’s reply along with some context, and the skill runs the classification and drafting steps described above, but automatically.
- Paste the prospect’s reply, plus your product description, the original outreach message, and anything you know about their role or company
- The skill sorts the reply into one of the five types, picks the matching response strategy, and folds in the context you gave it
- Out comes a draft reply, matched in tone and length to the original message, ready for your review
The skill triggers on phrases like “how to reply to this,” “handle this objection,” or “interested reply.” It’s one of several Claude skills lemlist has built for GTM teams, alongside ones for sequence writing, campaign benchmarking, and prospecting. You can grab it from GitHub.
Skills are folders of instructions, scripts, and resources that Claude loads dynamically to improve performance on specialized tasks. (GitHub - anthropics/skills: Public repository for Agent Skills · GitHub) For a deeper look at how the system works, check Anthropic’s official Agent Skills documentation.
How to install and run the reply handler in Claude
Setup is quick. No code, no terminal.
- Download the skill file: Head to the GitHub repo and download the .md file.
- Attach it in Claude: On claude.ai, click the paperclip icon and select the file. On Claude Desktop, drag and drop it into the chat window.
- Paste the reply and add context: Include the prospect’s reply, your product description, the original outreach message, and their role or company. More context tends to mean a sharper draft.
- Review before sending: Claude generates a classified response with a suggested reply. Adjust the tone if anything feels off, then send from your outbound platform.
Where reply handling fits in a multichannel outbound workflow
Reply handling sits in the middle of a longer motion: lead gen, enrichment, sequencing, reply, conversation, meeting. It’s the step where automation hands off to human judgment, and where most teams have no real process at all.
At volume, cold outreach can generate dozens or hundreds of replies a day. Manual handling breaks down fast under that load, and the problem gets worse once replies start arriving across different channels.
In lemlist, multichannel campaigns route replies from email, LinkedIn, and other channels into a single inbox. Paired with the Reply Handler skill, reps can classify and draft responses across channels from one place instead of juggling tabs. Teams wanting the full loop automated can look at lemlist MCP, which connects AI agents to prospecting, sequencing, reply handling, and campaign analytics by pasting a server URL and API key into Claude, Cursor, or Windsurf.
Run your outbound reply workflow with lemlist and Claude
Getting a reply costs real money: domains, warm-up time, data, copywriting. Handling that reply well is where the return actually shows up. Combine lemlist’s unified inbox with the Reply Handler skill, and reps spend less time guessing and more time in real conversations.
FAQs about cold outreach reply handling
Can the reply handler Claude skill classify LinkedIn DMs or only email replies?
Yes. It classifies based on the text of the message, so it works for email, LinkedIn, SMS, or any channel, as long as you paste the reply into Claude.
Does the reply handler write a ready-to-send response or just a draft?
It generates a draft matched to the reply type and the context you provide. Reviewing tone before sending is worth doing, especially for objections or timing deferrals where intent can be misread.
How is a Claude skill different from a lemlist MCP integration?
A Claude Skill is a file you attach for on-demand use in a single conversation. lemlist MCP connects directly to an AI client so an agent can take outbound actions (searching leads, launching campaigns, pulling analytics, and updating sequences) without leaving the chat.
How does lemlist compare to other tools for reply handling?
lemlist scores 4.6 out of 5 on both G2 (1,500-plus reviews) and Capterra (387 reviews) (Lemlist Review 2026: Is It Still the Best Cold Email Tool for Personalized Outreach? - Ecommerce Paradise – Build & Scale High-Ticket Ecommerce Businesses). The Reply Handler Claude Skill adds AI classification and drafting on top of lemlist’s built-in reply scoring, which auto-tags replies as “Interested” or “Not Interested” and pauses sequences accordingly. For teams that want deeper classification across all five reply types, the Claude Skill fills that gap.
Over to you
Reply handling is the most under-built part of most outbound workflows. Teams spend weeks on lead sourcing, enrichment, and sequencing, then wing it the moment a prospect actually responds.
We built this Claude Skill because we kept seeing the same pattern: good pipeline, generated at real cost, leaking out through slow or mismatched replies. The fix doesn’t need to be complicated. Classify the reply. Match the tone. Move toward a decision.
If you want to see how the Reply Handler skill, Unified Inbox, and MCP work together in practice, the fastest way is to try it.
Share this post