The send was the easy part
Building a campaign takes an afternoon. Living with it takes every morning after that. Once a sequence is running, the replies arrive mixed together: three people who want a call, a dozen out of office notes, a few who say try again in the spring, one who names the colleague you should have written to, and two who want to be left alone. The problem is never how many were sent. It is reading that many live replies without dropping the one that mattered.
A dropped reply is the most expensive failure in outreach, because everything before it was already paid for. The person answered, and nobody came back to them.
What you get back
A queue, as a file, with one row per reply: who it is from, which campaign it belongs to, the bucket, the reason in a few words, and the date that matters: when they wrote, when they are back, or when to try again. The rows that need a person today sit at the top with a suggested answer beside each. Unsubscribes are listed on their own so they can be honoured in one pass. Anything the agent could not place is marked for you to read.
Variations worth knowing
Any sequencer, from an export. If your campaign runs somewhere the agent cannot read replies, export them or forward them into a file. Everything after the first step is the same.
Follow the referral. When a reply points you to a named colleague, that person can be looked up and added to the list. It is a paid lookup, so the agent asks first: work email for business development, personal email and LinkedIn for a candidate.
Count interest, not replies. A fast no is not engagement. The share of replies that land in interested tells you whether the message works. If it is low, the fix is in how the sequence was built, not in sending more.
Where this goes wrong
Reply events are not the whole thread. The lemlist connection reads reply events for a campaign, not the inbox behind it. A long back-and-forth is best opened in lemlist itself, and where a reply's text does not come through, the row says so and is left for a person.
Polite is not interested. "Thanks, I will keep you in mind" reads warm and means no. The buckets come with a reason so you can spot a pattern you disagree with and correct it once.
An unsubscribe sorted is not an unsubscribe honoured. Removal from one campaign does not reach your other campaigns, other tools or your CRM. Suppression across those is yours to carry through.
Sending the draft unread. The draft answers the words on the page. It does not know what you agreed with that person on the phone.
Replies that never reached the sequencer. A call, a text or an answer sent to a different mailbox is invisible here.
