The usual story: someone starts an account, posts into it, watches the views stay near zero, and quits a month later. The conclusion drawn is normally the wrong one — that they need more followers. The real problem is that a new account's post has almost nobody to be shown to, while its reply does.
Why a post and a reply start from different audiences
Your post goes to your followers' timelines and, if the algorithm decides so, into recommendations. For an account without followers the first channel is empty, and the second has to be earned — which the algorithm has no reason to do, because the post has no engagement history behind it.
A reply lives differently. It sits in a thread under someone else's post and is read by people who came for that post. If the original pulled tens of thousands of views, some of those people will physically see your answer — regardless of your follower count. You are not bringing an audience, you are arriving at one.
Which leads to a conclusion many people get backwards: a new account should invest in replies, not posts. Posts start making sense once there is someone to show them to.
Where your reply actually lands
A reply thread is not shown in full, and not in publication order. Some replies are visible immediately, some sit behind a «show more» button, and some are collapsed with a note that the reply may break the rules. The difference between the first and the third position is the difference between thousands of views and none.
X does not publish the exact ranking formula, and anyone claiming otherwise is repeating guesswork. But the factors the platform itself names in describing its anti-spam systems and in its developer documentation are known: account reputation, how readers behave around your replies, signs of templating, and reports.
What sinks a reply
The same answer under different posts. The fastest route to the collapsed section. Platforms have long been able to compare texts, and a template match shows up even when the words are shuffled. If a reply could have been pasted under any post in the topic, it gets treated as exactly that.
A reply with nothing in it. «Great point», «agreed», «interesting» — nobody reads them, nobody answers them, nobody likes them. The algorithm sees a reply that held no one, and ranks the next one lower.
A link in the very first reply. Links in threads are handled more carefully than plain text, because that is the classic spam vector. A link from an account with no history is a combination that almost guarantees the bottom of the thread.
A pace no human has. Twenty replies in five minutes is not reader behaviour, it is script behaviour, and it looks like it.
What lifts one
A reply that adds what the post did not have: a number, a counter-example, a correction, disagreement with the argument. Those collect replies of their own, and a thread under your reply is the strongest signal available, because it keeps people inside the conversation.
Speed matters too, but not the way people assume. It is not that the algorithm favours the fast. It is that early replies are physically seen by more people: while the post is gathering views the thread is short, so everything in it gets read. A day later the same line sits under a hundred others.
And the size of the account you answer. A reply under a post with three views will be seen by nobody, however good it is. It pays to keep a list of accounts in your topic that reliably pull reach, and work that list.
About limits
There will be no specific numbers here, and here is why. X does not publish thresholds for actions taken from the interface; they change, and they depend on account age, subscription status and accumulated reputation. Any article promising «a safe 40 replies per hour» is passing off someone's private observation as a rule — and you find out it was not yours only after the restriction lands.
The practical approach is different: your own thresholds are found empirically, from below. Start noticeably lower than what feels normal, ramp up gradually, and watch for early signs rather than for a ban — replies stop collecting views, captchas appear, actions start getting rejected. A restriction almost never arrives without warning; the warnings just look like «something is working badly».
What to actually do
Collect 20–40 accounts in your topic that consistently pull reach. Reply early and with substance. Hold links back until the thread has a conversation of your own in it. Do not use pre-written lines that fit anywhere. And count profile clicks rather than followers — how many people went to see who wrote that.
How Sndwich does this
The auto-replier in Sndwich works from a list of accounts rather than blind keyword matching: you set who to watch and the rules for answering. The text is generated for the specific post instead of being pulled from a set of canned lines — which is precisely why the replies do not read as templates. Pacing is jittered, without the even intervals humans never produce.