Missed replies in cold email: we found about 100 nobody had answered
The fastest way to find missed replies in a cold email inbox is to sweep it systematically instead of relying on whoever happens to be watching it. Pull every reply through your sending tool's API or export, compare it against what was answered, and work the unanswered ones first. When I did this with an AI connected to our sending tool, it surfaced about 100 replies nobody had answered, wrote the follow-ups, and booked meetings from them.
That number still bothers me. A hundred people raised their hand and nobody noticed. Every one of them had been through the whole machine: list, domain, warmup, copy, send. And then the most valuable moment in the process, the reply, sat there.
The reply graveyard
On August 10 I told Charles on our call what the AI had found. I had connected it to Instantly through the API and asked it to go through the replies. It came back with about 100 that had never been answered.
Some were simple yeses. Some were questions. Some were "not now, maybe later." Some were people asking to be sent more information. All of them deserved an answer, and none had gotten one.
The AI drafted the follow-ups, they went out, and meetings got booked from replies that would otherwise have died quietly.
It happened to land the same week we'd decided to call National Follow-Up Week. We already had 24 follow-ups queued and were going hard on closing. Finding 100 more conversations we'd dropped was humbling, and useful.
Why replies get missed at volume
Nobody decides to ignore a hundred interested people. It happens through a handful of ordinary failures.
Replies land in a tool you don't live in. Most founders spend their day in Gmail, Slack and their calendar. The sending tool's inbox is somewhere else, and it gets checked when someone remembers.
Volume hides individuals. When you have hundreds of mailboxes and thousands of sends, replies arrive in a steady trickle across many accounts. It's easy to see the total and miss the person.
Ambiguous replies get deferred. "Can you send more info?" or "What does this cost?" need a thoughtful answer, so they get starred for later. Later doesn't come.
Ownership is fuzzy. If two or three people can see the inbox, each assumes someone else answered.
And some replies get answered outside the thread, from someone's personal email, so the tool still shows them as open while the conversation lives elsewhere. That makes it hard to trust any count.
Letting an AI sweep the inbox
The thing that made the difference was not more discipline. It was a systematic sweep.
An AI connected to the sending tool's API can read every reply, classify it, check whether a response went out, and draft one where it didn't. It doesn't get tired at reply number seventy. It doesn't assume someone else got it. It doesn't defer the awkward ones.
The judgment still matters. A draft is a draft. Someone who knows the offer should read it before it goes out, especially for replies with real questions in them. But the hard part, finding the needles, is exactly what software is good at.
That's the principle we built into gtm showrunner. Every reply lands in one inbox, with a draft already written in your voice and the right link for the show. You read it, change what you want, and approve it. Nothing is sent without you. The sweep happens continuously, so the graveyard never forms.
What we answer first
When you find a backlog, the order matters. People who replied two weeks ago are cooler than people who replied yesterday, and some replies are worth more than others. This is the order I'd work it.
Clear yeses first. Anyone who said yes, sure, interested or let's talk. Apologize briefly for the delay if it was long, give them the booking link, and keep it short.
Direct questions next. "What does it involve?" "How does this work?" Answer the question in a few sentences, then give the link.
Referrals after that. "Talk to my colleague" is a warm introduction. Thank the person, then reach out to the colleague mentioning who sent you.
"Not now" replies last. Thank them and ask when to check back, then actually put it on the calendar.
Leave the out-of-office replies and auto-responders out of the queue. They're noise.
How to reply to someone you ignored for two weeks
The awkward part of a sweep is that some of these people waited a long time. It's tempting to skip them because it feels embarrassing. Don't. Most people don't mind a late reply nearly as much as you'd think. They mind no reply.
Keep it honest and short. Something like: sorry for the slow reply, your note got buried, and I didn't want to leave it unanswered. Then answer whatever they asked, and give them the link.
Don't invent an excuse. Don't write three paragraphs of apology. Don't pretend it was intentional. One line of ownership and then move to what's useful for them.
You'll be surprised how many say "no worries" and book. They replied for a reason, and the reason usually hasn't gone away.
Make the sweep a habit, not a rescue
Finding 100 missed replies once is a good day. Finding them again a month later means nothing changed.
The fix is making the sweep continuous. Every reply gets classified when it arrives, gets a draft, and sits in one place until someone approves or dismisses it. Nothing waits in a tool nobody opens.
If you're doing it by hand, pick a fixed time every day, even fifteen minutes, and make one person the owner. If you're using software, make sure it surfaces unanswered replies instead of just listing all of them.
Speed is part of the answer
A reply that waits a week isn't the same reply anymore. The person who wrote "sounds interesting" on Monday has moved on by the next Monday. They'll still remember you if you answer, but the energy is lower.
The goal isn't just to answer every reply. It's to answer while the moment is still warm. That's hard for a founder who's also running the company, and it's the main reason we put drafts in front of you instead of asking you to write from scratch. Approving a good draft takes seconds.
If you're running outbound today, set aside an hour this week and do a sweep yourself. Export every reply from the last 60 days. Note which ones got an answer. I'd be surprised if you don't find at least a few people who raised their hand and heard nothing back.
The cheapest pipeline you'll ever build
Every other part of outbound costs money: data, domains, mailboxes, tools, time. Answering replies you already have costs almost nothing. They're people who already said something to you. Some of them already said yes.
Before you buy more contacts or spin up more mailboxes, make sure you've answered everyone who wrote back. It's the highest-return hour in the whole system.
If you want a starting point that does this for you, connect Gmail and start free. Invites and replies land as drafts you approve.
Frequently asked questions
How fast should I answer a cold email reply?
As fast as you reasonably can, ideally the same day. A reply loses energy quickly. Having a draft ready in your voice makes it easy to answer in seconds instead of putting it off.
Can AI answer cold email replies for me?
AI is very good at finding replies, classifying them and drafting answers. We still have a person approve each one before it goes out, because some replies need judgment about the offer.
How do I find replies I missed?
Export or pull every reply from your sending tool for a period, mark which ones got an answer in the thread, and work the rest. An AI connected to the tool's API can run that sweep for you.