Ins Autopilot Start free

How Stop on Reply works

How Ins Autopilot detects a reply, why remaining steps are cancelled immediately, and why an unreadable reply holds the send.

Applies to Ins Autopilot 3.22 and later · Updated 2026-10-18

What this helps you do

1 A sequence is running A follow-up step is scheduled for a contact you already messaged. 2 The contact answers A reply is read from the Instagram thread. 3 The sequence stops before its next step Sending again to someone who already answered would look careless. 4 The reply stays on the record It appears on the contact timeline, and the contact moves into Today.
Figure 1Stop on Reply is a rule about not sending, not a feature that sends. It only ever removes a future message.

The hardest part of any follow-up is knowing when to stop. Sending a second message to someone who already answered looks careless and wastes a contact you might otherwise have kept.

Stop on Reply is the rule that prevents that. It watches for a reply from the person you are following up with, and as soon as a reply is confirmed, the rest of the sequence is voided.

What counts as a reply

Reply detection reads your Instagram Direct conversations. It is read-only: the extension looks at the thread and never writes to it.

A detected reply is recorded as a durable fact on the contact. Once that fact exists, it does not quietly disappear — it stays on the record and keeps the sequence stopped.

What happens when a reply arrives

  • The remaining steps are voided immediately, even if they have not come due yet. Nothing waits for the next scheduled time.
  • The reply appears on the contact's Activity timeline as a recorded fact.
  • If you use Today, the contact can appear there under Replied.
  • The messages that were already sent are not undone or deleted. Stop on Reply stops the future; it does not rewrite the past.
  • The contact itself stays in Relationships with everything you recorded about them.
The Relationships panel with a contacts activity timeline open, showing recorded events in order.12
Figure 2A reply is recorded as a fact on the timeline. Because it is recorded, the next scheduled step has something to stop on.
  • 1 Relationships, where the timeline lives.
  • 2 The recorded events, newest first.

When the reply cannot be read, nothing is sent

Reply detection has to read the Instagram conversation to know the truth. If that read does not succeed, the extension does not assume the person stayed silent.

When the reply state for a contact is unknown, the due step does not send. The sequence holds instead of guessing.

This is deliberate, and it is the more careful direction to fail in. Guessing "no reply" and sending anyway risks an awkward double message to someone who already answered you.

The same rule appears in the delivery record: an unknown result is never treated as a confirmed outcome and is never retried automatically.

Reply read The thread was read and a reply was found The sequence stops before the next step Reply not readable The thread could not be read The state is reported as unreadable, not as no reply Nothing is sent on a guess
Figure 3When the extension cannot read the thread it says so. It does not treat an unreadable thread as proof that nobody answered.

Fail-closed means a failed read costs you a delay, not an unwanted message.

The honest limit

The extension can only cancel a step when it can see the conversation. Reply detection reads Instagram from your browser, so it works while the relevant Instagram pages are open and readable.

If the browser is closed, or the page cannot be read, the extension cannot promise to notice a reply the moment it arrives. What it can promise is that a due step will not be sent on an unknown reply state — the step waits rather than fires.

Do not read Stop on Reply as an always-on, instant guarantee. It is a rule the extension applies whenever it has the facts, and a hold when it does not.

What it stops The next scheduled step of a follow-up sequence for that contact. stops What it does not stop Anything you start by hand, and anything already sent. does not stop What it never does It never sends a reply, and it never writes an outcome for you. never
Figure 4The boundary matters: Stop on Reply is a read-only rule about the next step, nothing more.

A reply that arrives while nothing is being read may be noticed only later, when the conversation becomes readable again. The step that was waiting is then cancelled.

Limits and important behavior

  • Stop on Reply applies to follow-up sequences, and to the reminders that feed them. It does not send anything itself.
  • It only sees replies in existing Direct Message threads on the account you are signed in to.
  • Reads are per account. Switching Instagram accounts changes what the extension can see.
  • A reply stops the sequence; it does not create a new message, a new task or an automatic answer.
  • Follow-up sequences are Pro, so on Free there is no running sequence for Stop on Reply to stop.

Troubleshooting

Someone replied but the follow-up still went out.
Check the timing in the Activity timeline. A reply cancels steps that have not been sent yet; a step that was already sent before the reply was read cannot be recalled. Reply detection also needs the conversation to be readable to see the reply at all.
The sequence is sitting still and I cannot see why.
The reply state for that contact is probably unreadable, so the due step is being held rather than sent. Open the Instagram conversation in the browser and let the extension read it.
Does Stop on Reply answer the person for me?
No. It never sends anything. When a reply is detected, the sequence stops and the reply is reported so you can answer it yourself.
I closed my browser overnight. Did I miss anything?
The extension cannot read pages it cannot reach, so a reply that arrived while nothing was open may be noticed later. It will never be turned into an automatic send in the meantime.

Related guides

Ready to try it? Ins Autopilot runs in your own browser session — no password, no remote control.

Open Ins Autopilot

Not installed yet? Start with the setup guide.