# One follow-up, never a sequence

> Why there is exactly one follow-up per person, no setting to add more, and why a reply cancels everything queued for that person, checked twice, right up to the send.

By Adarsh Mamgain, 29 September 2026. From the Hellofew blog at https://hellofew.com/blog.

Just circling back on this. Bumping this to the top of your inbox. Wanted to make sure this didn't get buried. I know you're busy, so I'll keep this short. Last one from me, promise. You have received that sequence. If you have ever bought an outbound tool, you have probably sent it, because the tool came with a five-step template and five seemed like a reasonable number of steps.

I have been on the receiving end of the whole sequence, and the fifth message is the one where I look for the block button. Then I imagine it going out from my own account, under my own name, to someone I would quite like to work with one day, and I have not read it before it went. That is the scene I built the sequence against.

## One follow-up

A single follow-up roughly doubles replies. The third and the fourth add almost nothing except complaints, and a complaint is not just a lost lead. LinkedIn's own help page lists invitations marked as spam as a reason to restrict an account, and a person who has been bumped four times is a person looking for the report button. The sources for that are on [the limits page](/limits).

So Hellofew sends one message after somebody accepts, and one follow-up if they do not answer it. That is the sequence. There is no setting to add a second follow-up, in the same way there is no setting to raise the 20-a-day ceiling: not because it would be hard to build, but because every version of this product that had the setting would eventually be run with it turned up.

## A reply cancels everything, and it is checked twice

The one thing that would make you stop trusting a tool that writes under your name is a follow-up arriving at somebody who already answered. Just circling back, to a person who replied yesterday, is worse than no outreach at all, because it tells them nobody is reading. So the moment a reply lands, everything still queued for that person is cancelled: the follow-up, a pending message, anything.

And because a reply can land in the minutes between the queue being planned and the message being sent, it is checked again at the last moment, right before the send goes out. Two checks, not one, because the gap between them is exactly where the embarrassing case lives. Anyone who asks not to be contacted goes on a do-not-contact list that is global across every customer and is never deleted, because deleting it would re-expose the person who asked to be left alone.

## Why fewer messages is also the safer account

Messages are less risky than invitations, because they go to people who just accepted and are expecting one. They are capped anyway, at 12 a day, because the failure of an uncapped loop is a hundred messages in an hour. In practice the real cap is acceptance: 5 invitations a day at a thirty percent accept rate is one or two messages a day, so 12 is headroom rather than a target. Each message waits at least 90 seconds after the last, because a real person takes that long to type one.

Nothing in the message loop sends the same day somebody accepted, either. A connection accepted at 10:04 and a pitch arriving at 10:06 is the clearest automation signature there is, and it is also rude. The message goes the next working day, inside your hours.

## What this costs you

Some replies, honestly. A five-step sequence does extract a few more answers from the people who would have answered anyway, and I am choosing not to collect them. What it buys is an account that is still sending next year, and an inbox where every reply is from somebody who was not harassed into it. Replies per week is the one number I think matters, and the one the product reports to you; what my own accounts got, week by week, is on [the numbers page](/numbers).