Delayed filters

Delayed filters hold a new post from a source instead of publishing it right away, and release it once it collects the views, reactions, forwards or replies you set. Only what resonated with the source's audience reaches your destination. Available on the Ultra plan and above, and only for a source read through your account — Telegram's Bot API does not expose a message's views or reactions, so a source read by the bot has nothing to wait for.

Setting it up

1. Open the source, go to Delayed filters and turn the switch on.
2. In Waiting window, set From — how long after publication in the source to check first — and To — the deadline; both in hours and minutes, up to a week. Re-check every hour has the bot try again on every hour in between, once there are conditions and a window to re-check in.
3. In Publishing conditions, set the metrics: minimum views, reactions, forwards and replies, plus the per-view ratios — reactions, forwards and replies per view, as a fraction (1 reaction per 10 views = 0.1). 0 means the metric is not checked; every metric you set must be met at the same time.

How it works

The post first goes through the regular filters and the similarity check; a post they reject counts as an ordinary filtered post and is not held for metrics.

A post that passes waits. AI processing, AI filters and the template are applied when it goes out, not in advance: no AI is spent on posts that never reach the metrics, and a post an AI filter rejects after the wait is not published either. The bot checks its metrics at the start of the window and at the end; once every condition is met the post is published right away, and with Re-check every hour on it also tries on every hour in between. If the conditions still aren't met once the window closes, the post is not published and shows up in the events log as filtered. Without any conditions set, the post simply goes out at a random moment inside the window — or right after From, if To isn't set past it.

The section only shows up for a source read through your account. For a source read by the bot it shows a note explaining why metrics aren't available instead.