Bulk Telegram reactions

A reaction is the cheapest public action in Telegram. It needs no text and no membership, yet everyone who opens the post sees it, and one tap reveals the list of who reacted. This module scales that across your target list: either a single pass over published messages, or a standing watch that reacts to new ones.

Launch flow

• Select accounts, a target dataset and at least one reaction.
• Set the reaction cycle, the probability and the limits.
• Start the job and read the per-target refusals.

Before you launch

• Accounts with proxies, warmed up if possible.
• A target dataset of channels or chats. Build it with a parser, or add entries by hand when picking the source.
• At least one selected emoji. Without it the start button stays disabled: the panel will not launch a job without knowing what to react with.

Reaction cycle: which one to pick

• Existing messages. A single pass: accounts walk the targets and react to what is already out. Suited to volume, where reaction speed does not matter.
• New messages. The module keeps targets under watch for a set window and reacts to fresh posts. Suited to being among the first reactions under a new post.

The second mode costs more in time but is worth more: the first reactions under a fresh post are seen by everyone who arrives later, while a reaction added to a hundred existing ones disappears.

Reaction probability

This is the main naturalness control. At a hundred per cent an account marks every message in a row, and it reads as exactly what it is. Around 70 per cent leaves part of the messages untouched, the way a real reader behaves. The panel draws from your selected emoji at random, so two or three that suit the audience work better than the whole list.

Limits: how they split across streams

• Reactions per target: 1 to 100. The panel spells this out in the settings: each stream spends that budget on its current target and then moves to the next one, and accounts work in parallel.
• Total reaction limit: up to 1000 for the whole run, a ceiling shared by every stream.
• In the new-messages mode the per-target slider is replaced by a Watch window of up to 180 minutes, and a Check interval of 1 to 30 seconds sits in the advanced settings.

Joining and rotation

• Join when required. The account joins only when Telegram will not accept the reaction otherwise. Left alone, it joins nothing.
• Account rotation with a Reactions until rotation threshold from 10 to 500. After that many confirmed reactions the stream hands over to the next account.
• With rotation off, the first account will happily drain the whole total limit while the rest sit idle. An even spread across the fleet is the entire point of the switch.

The allow-list threshold

The advanced settings carry an Allow-list threshold slider from 50 to 100 per cent. The panel puts it plainly: targets below the threshold go to the blocklist, the rest go to the allowlist. Targets are sorted by their share of successful reactions, so the ones where almost nothing landed stop consuming your accounts. Useful on a large unvetted dataset where some channels are closed from the start.

Run progress

• Each account has its own lane with a reaction counter and its remaining budget.
• The log shows which reaction went to which target.
• Every refusal carries a reason, and it tells you at a glance whether the target or the account was at fault.
• Pause and stop can be applied to a single account without touching the others.
• In watch mode the log stays clean: the panel writes one start event and then only real reactions, errors and the window outcome.

Why a reaction did not go through

• Reactions are disabled in this target for everyone: the author closed them and nothing can be done.
• This account is barred from reacting in this target: a restriction on that specific account.
• Telegram did not accept the reaction because its own reaction limit was hit, not yours.
• Membership or access to the target is required first: switch on Join when required.
• The account is banned in that chat or channel.
• The available accounts hit their rotation reaction limit: the rotation threshold is lower than the run needs.
• FloodWait: Telegram demanded a pause, and the stream waits instead of pushing on.

Common mistakes

• A hundred per cent probability: the most visible automation tell in this module.
• The whole emoji set at once. Ten different reactions under one post from different accounts look like a flood, not like readers.
• Rotation left off, so one account drains the entire total limit.
• Targets with reactions closed: the run burns through with nothing to show, and every log line carries the same reason.
• Too narrow a watch window on channels that rarely post: there will be nothing to react to.