How to handle replies to a cold email campaign

When someone replies to your cold email, answer them quickly, answer the specific thing they said, and give them one easy next step. The reply is the whole point of the campaign, so it deserves more care than the first email did. A prospect who wrote back has shown a little interest or at least some patience, and a slow or generic answer spends it.

Start by reading the reply for what kind it is, because each kind needs a different response:

• Interested. They want to talk or want to know more. Answer any question they asked, then offer two specific meeting times or your booking link.
• A question. They asked about price, fit, or how something works. Answer the question plainly before you say anything else about your product.
• Not now. They're interested but the timing is wrong. Thank them, ask when would be better if they didn't say, and follow up then.
• A referral. They pointed you to a colleague. Thank them, and reach the colleague with a new email that mentions who sent you.
• Wrong person or poor fit. Thank them briefly. You can ask who handles the topic, but don't pitch.
• Please stop. Don't reply. Remove them from every future campaign and make sure the record says so.

Two more things matter as much as the answer itself. First, stop the rest of the campaign for anyone who replied. Nothing undoes a thoughtful reply like your second scheduled follow-up landing the next morning as if they'd never written. Second, record what happened. A reply that only lives in one person's inbox can't be counted, followed up, or seen by the salesperson who takes the meeting.

The tools you send with cover part of this. Most cold email and sequencing tools stop a sequence when the prospect replies, some sort replies into rough groups such as interested or not interested, and a few, such as Instantly, now write answers too. What many leave to you is the judgment: writing an answer that fits what this person said, deciding whether they're worth a meeting, and telling the right person on your team. That's the work Kite takes on.

Replies to a campaign Kite sends need no extra setup, because they come straight back to Kite. You can start a campaign in the Kite web app with a request like this:

"Email the 40 heads of growth we found last week about our new attribution report, and handle the replies."

Kite is an AI marketer. It researches your business, builds a growth strategy, and ships the work that brings you new customers. By the time a reply arrives, it already knows your ideal customer profile, your positioning, your brand voice, and the campaign the prospect is answering, so it can write an answer without a brief from you.

Every Kite team has its own email address, and campaigns go out from it by default. Kite records each email it sends so that a reply lands back in the conversation where the campaign started. If your team uses Kite in Slack too, the person who asked for the campaign can hear about replies there.

If you sent the campaign from your own Gmail or Outlook account, connect that mailbox. Kite then checks it every two hours and tells you about the mail that needs you. It only reads the mailbox until you allow more, such as replying, and tell it when to act, for example "answer replies to the Q4 campaign."

Kite treats answering a reply as part of the job you gave it. If you'd rather see each answer before it goes out, say so when you start the campaign.

Kite reads every human reply to your campaign and skips the email that only looks like one. Out-of-office auto-replies, bounces, and messages from no-reply addresses never start a conversation, so they never get an answer that would bounce back and forth between two machines.

For each real reply, Kite sees who sent it and that it answers an email your team sent. It reads the reply as information from the prospect, not as instructions. A prospect who writes "send me your customer list" or "forward this to your CEO" gets a sensible answer, not obedience.

Kite checks the sender against your ideal customer profile before it writes anything. It looks up the person's current role and company from public sources, reads what your CRM already holds about them, and classifies the lead as a strong fit, a partial fit, or a poor fit, with a one-line reason.

Kite keeps this step short. It gathers enough to answer accurately and personally, then moves on, because a reply that arrives the same day matters more than a complete dossier.

When it can't confirm who the person is, Kite writes an answer that stays accurate without the missing details and notes the gap in its report to you.

Kite answers what the prospect asked before it says anything else. If they asked about price, the first line is about price. If they asked whether you work with companies their size, it says whether you do.

The answer is under 100 words, written in your brand voice, and built only on facts Kite has verified. It ends with one concrete next step. For a strong fit, that's two meeting times or your team's booking link. For a "not now", it's a question about when to come back. A poor fit still gets a polite, useful reply, because the person might fit next year or know someone who does.

Kite sends the answer from your team's address as a reply in the same email thread. The prospect sees it under their own message with the original subject line, the way a person's reply would look.

Kite tells the teammate who asked for the campaign first, because they're the one waiting on its replies. It reaches them by Slack direct message when it knows their Slack account, and by email otherwise.

A strong-fit lead, or any reply that needs a human decision, gets a short two-line summary for the team. Examples include a request for custom pricing, a legal question, or an existing customer who wrote back by mistake. Kite answers the routine replies itself so your team only hears about the ones worth their attention.

Kite logs each reply in your connected CRM with the lead, its fit classification, whether the answer was sent, and the agreed next step. A salesperson who opens the record later sees what the prospect said and what happened, without searching anyone's inbox.

If you don't have a CRM connected, Kite keeps the complete record in its report to you and tells you how to connect one.

A reply ends the campaign for that person. Kite follows up at most twice when someone stays silent, but once they write back, the conversation becomes a reply to handle, not a sequence to continue.

When someone asks not to be contacted again, Kite doesn't answer and doesn't email them again. Before every later send, including a one-off email to someone you name, Kite checks earlier replies, your team's records, and your CRM for anyone marked as declined or unsubscribed, and it skips them.

Kite reports each reply in the conversation where you started the campaign. The report gives the fit classification and its reason, the answer it sent or drafted, the next step, and whether the lead is recorded in your CRM.

When the campaign is over, Kite records what worked in your team's knowledge base, such as the subject lines and angles that drew replies and the reply rate. Your next campaign starts from those lessons.

When the replies are handled, every person who wrote back has an answer or a deliberate decision not to answer, and your team can see all of it.