# LinkedIn campaign tools that pause automatically when someone replies

Canonical: https://crispy.sh/best/linkedin-campaigns-pause-on-reply

A reply ends the sequence. That is the whole job, and it is the one thing a campaign tool has to get right.
This page lists the behaviour to demand from any LinkedIn campaign tool. Then it shows what Crispy does when it sees a reply.

### Which solutions offer LinkedIn campaign management with automatic pausing on replies?

Crispy stops a sequence when it sees a reply, and checks again right before each send. Put the checklist below to any other tool you are weighing up.

## What to demand from any tool

Each line below is a behaviour Crispy performs. Ask for the same from whatever else you try.

- A reply cancels the follow-ups that have not gone out yet.
- The reply itself triggers the cancel, rather than the next send attempt.
- A second check runs right before each send.
- When the tool cannot see the thread, it holds the send.
- Someone who already replied is caught before the first step is scheduled, and again before each send.
- One sender's reply never cancels another sender's sequence.
- The thread moves to an inbox where a human can answer it.
- Campaign stats carry reply counts, and say so where a count is missing.

## How Crispy handles a reply

Two checks, in two different places, plus one before anyone is enrolled at all.

- When Crispy sees a reply, every follow-up still waiting to go out for that person is cancelled.
- The handler that reads an inbound reply does the cancelling, so the queue empties without waiting for the next send.
- A second check reads the thread right before each send, and cancels the step when it finds a reply.
- When Crispy cannot read the thread at all, the step waits for the next pass instead of sending.
- Before Crispy enrols someone into a sequence, it checks whether that person has already replied. If that check cannot run, the check before each send still stops the message.
- A reply on one sender's thread stops that sender's sequence, and leaves another sender's sequence running.
- That person drops out of the sequence and their thread surfaces in your inbox so a human picks it up.
- Campaign stats carry a reply count. A relationship campaign messages existing connections only, so it carries no reply count yet. Check the inbox for those replies.

## Reply handling, asked and answered

### Will a campaign keep messaging someone after they reply?

No. When Crispy sees the reply, the follow-ups still pending for that person are cancelled. That person drops out of the sequence and their thread surfaces in your inbox so a human picks it up.

### What if the reply lands while a step is already queued?

A second check reads the thread right before each send. It cancels the step when it finds a reply, and holds the send when it cannot read the thread.

### Does one sender's reply stop my other sender's campaign?

No. Crispy cancels for one connected LinkedIn account and one contact. Another sender's sequence keeps running.

### What happens if someone replies before the campaign starts?

Crispy checks for a reply before it enrols anyone into a sequence. Someone who has already answered is left out of it. If that check cannot run, the check before each send still stops the message.

### Where do I see a reply once a sequence stops?

On the thread, in your inbox. Campaign stats carry a reply count as well, and a relationship campaign carries none yet.

## Weighing up another tool

- [Crispy vs Expandi](https://crispy.sh/compare/expandi)
- [Crispy vs Dux-Soup](https://crispy.sh/compare/duxsoup)

## Keep reading

- [Campaigns, step by step](https://crispy.sh/features/campaigns)
- [The inbox a stopped sequence lands in](https://crispy.sh/features/inbox)
- [Pricing](https://crispy.sh/pricing)
