A prospect answers your email at 10 a.m. A LinkedIn follow-up to the same person is due tomorrow. Whether that message goes out depends on more than a tool's “stop on reply” label. The tool must see the email, match it to the right person and campaign, and remove or hold the LinkedIn step. Test all three before putting a mixed sequence in front of prospects.
A reply can stop one sequence and leave another running
Distro's current help says an email or LinkedIn reply stops later steps on both channels in one Email + LinkedIn campaign. Its separate stop-on-reply guide draws the boundary: the reply stops that person's place in that campaign; another campaign involving the same person can continue. This is Distro's documented behavior, not a rule shared by every tool.
lemlist describes a Replied status for email or LinkedIn responses, but says automatic stopping depends on campaign settings. A Replied badge therefore answers only part of the question. Before buying, ask the vendor to show the exact next LinkedIn action for the lead after an email response. If the action is hidden rather than removed, ask how the operator can tell it will not run.
Sources: Distro: Email + LinkedIn campaign behavior, Distro: stop-on-reply scope and missed replies, lemlist: lead statuses and reply settings
The mailbox is part of the feature
Distro says it recognizes a reply in the campaign's email thread, or one that references that thread, when it arrives in the connected sending Google mailbox. It says a brand-new email, a response sent to another mailbox, or a disconnected sender may escape detection. Wiggli likewise documents a manual mark-as-replied action for a forwarded thread, different inbox, or delayed signal that it cannot match. Those are useful vendor disclosures because they name cases the slogan omits.
Automatic replies deserve their own check. Distro says an out-of-office email does not count as a person replying in its mixed campaign. That may be the right classification for your workflow, but it means the next LinkedIn step can remain scheduled. Do not assume every vendor handles auto-replies the same way, or that an email you can see in a shared inbox is one the campaign has matched.
Sources: Distro: stop-on-reply scope and missed replies, Distro: Email + LinkedIn campaign behavior, Wiggli: cross-channel stop and manual fallback
Rehearse the handoff before the next message is due
Use a colleague who agrees to receive a test email and LinkedIn message. Put that person in one mixed campaign with an email step followed by a LinkedIn step scheduled far enough ahead to inspect the queue. Record the email address, LinkedIn profile, sender mailbox, campaign, and next action before the colleague replies in the original email thread. Then inspect the lead timeline and queued LinkedIn action. The pass condition is a visible hold or cancellation for the correct person before its due time, not just a reply count rising on a dashboard.
Run a second controlled case with a new email sent to the same connected mailbox rather than a thread reply. If the vendor does not document or demonstrate that path, plan for a human to mark the lead as replied and clear the queue. Finally, place the consenting test contact in another paused campaign and check its pending action too. Distro explicitly limits ordinary reply stopping to the campaign that received the reply; do not infer account-wide suppression from the first successful case.
- Can the operator see which incoming email was matched to which prospect record?
- Is the next LinkedIn step cancelled, paused, or still waiting?
- What happens in a second campaign, under another sender, or after a mailbox disconnects?
- Who can apply a manual stop when the response arrives outside the connected thread?
Sources: Distro: stop-on-reply scope and missed replies, Wiggli: cross-channel stop and manual fallback
Keep a person responsible for replies the system cannot see
A prospect might answer a rep's other inbox, start a fresh email, call, or reply in a second campaign. Those events need an owner who can stop queued contact across the tools the team actually uses. Give that owner a way to inspect all pending steps for the person and record why they were cleared. A do-not-contact request needs the team's suppression process, not a reversible pause in one sequence. The related LinkedIn-reply guide covers what to verify when the response itself arrives on LinkedIn; this guide tests the crossing from email into a LinkedIn queue.
LinkedIn says unauthorized software that automates activity on its service can lead to account restrictions. A successful stop-on-reply test measures the vendor's workflow; it does not establish LinkedIn approval or remove that policy exposure. If the team cannot accept it, keep the email reply in the normal inbox, assign the follow-up to a person, and use LinkedIn's native messaging manually.
Sources: Distro: stop-on-reply scope and missed replies, LinkedIn: prohibited software guidance