Telegram Keyword Confirmation: Forward After 3 Matching Posts
To forward a Telegram update only after several messages mention the same configured keyword, use RedFox Auto Forward Telegram’s Keyword Confirmation add-on. Set a match rule, a required message count, a counting period and a cooldown. When the threshold is reached, the message that completes the rule is forwarded—not a bundle of all the earlier messages.
This is useful when you want a private review feed to stay quiet until a routine topic appears repeatedly. It is not proof that the messages came from independent sources, that their claims are true, or that two posts describe the same event.
The official Keyword Confirmation guide, checked October 9, 2026, calls the feature Signal Confirmation in its overview. This tutorial turns that documented message-count rule into a small, testable review workflow. Auto-Bot.io is an editorial publisher covering RedFox Auto Forward Telegram, not its developer or operator. The previous bot has moved to @AutoForwardNew_Bot. Use this current handle to access RedFox Auto Forward Telegram.
The featured image is a conceptual illustration of a timed message gate, not a software screenshot or a tested delivery result.
Choose a message-count gate, not a duplicate detector
Suppose your team watches release discussions in a few Telegram rooms. You do not need every mention in the review channel; you want one message to inspect after the topic has appeared three times within an hour. Keyword Confirmation can apply that rule across the sources selected for one task.
A public TelegramBots question illustrates a related need: a reader wanted to cross-reference two channels and forward content after finding repeated messages. That question asks about identical-message comparison. The workflow here is narrower: it counts messages matching your words or hashtags. Do not treat it as an answer to exact duplicate comparison or semantic event matching.
| Your actual goal | Appropriate starting point | What not to assume |
|---|---|---|
| Forward an announcement as soon as its marker appears | A task-scoped word or sender rule; see the focused group-update guide | A count threshold is unnecessary if the first message matters. |
| Wait for several matching messages, then send the threshold-completing message | Keyword Confirmation with an explicit counting period | Three messages do not mean three independent channels. |
| Investigate repeated-looking arrivals | The duplicate-message diagnosis guide | A repeated keyword does not make messages duplicates. |
| Summarize a day’s discussion | The daily digest workflow | Keyword Confirmation does not combine earlier messages into a digest. |
Use a count gate for routine monitoring where waiting is acceptable. Do not make it the only path for an urgent outage, a safety notice or a time-sensitive instruction: a one-off message may never reach the configured threshold.
Build one narrow review rule
Start with sources you are allowed to redistribute and a private destination you control. If the route itself is new, follow the existing Telegram forwarding setup guide rather than changing several production tasks at once.
For this fictional release-monitoring example, agree on a distinctive hashtag, #releasewatch. It is a routing label, not a verified release status. Use one rule first:
| Setting | Example value | Why it matters |
|---|---|---|
| Signal Name | Release review | Identifies this rule for the operator. |
| Words or Hashtags | #releasewatch | Defines the topic to count. |
| Match Style | hashtag_exact | Matches one complete hashtag, not a longer tag such as #releasewatchdog. |
| Required Matches | 3 | Waits for three matching source messages. |
| Counting Period | 1 hour | Prevents indefinitely accumulating unrelated old mentions. |
| Pause After Forwarding | 6 hours | Pauses this rule after a successful forward. |
These are example settings, not a claim that they suit every feed. The current guide allows 2–100 required matches, a counting period from 5 minutes to 7 days, a cooldown from 0 to 7 days, and up to 10 rules. Its defaults are 10 matches, 24 hours and a 6-hour pause. Check the values you actually save; leaving the defaults in place will not run the three-message example.
- Open the intended task. Confirm its sources and private review destination before enabling the feature. A normal forwarding task can begin sending when created, so keep setup away from a live audience.
- Check add-on access. Review the available Keyword Confirmation configuration and your account’s current entitlement. Confirm any displayed purchase terms before paying; this article does not quote a price or promise plan inclusion.
- Enter the single rule. Use the example name, exact hashtag, threshold, counting period and pause above, then enable the feature and save the configuration.
- Read it back. Reopen the task and confirm the saved values. Rule identifiers and revisions are handled automatically; you do not need to invent or edit them.
- Check other routes into the review destination. An ordinary task posting the same source messages there can make the destination look as if the count gate is being bypassed.
If the control is missing despite active access, keep the task isolated and ask RedFox support through the official product entry point. Do not switch on unrelated filters or apply a new rule to every task to compensate.
Read the timeline: only the completing message is sent
The following is an illustrative expectation from the documented rule, not a test performed on a connected account. All three matching messages are distinct new posts within the one-hour period.
| Time | Source message | Expected result from this rule |
|---|---|---|
| 09:00 | Message A: #releasewatch — release notes are being prepared. | First match; not forwarded by this rule. |
| 09:10 | Message B: #releasewatch — a review build is available. | Second match; not forwarded by this rule. |
| 09:20 | Message C: #releasewatch — review build notes and link. | Third match; Message C completes the rule and is forwarded. |
| 09:25 | Message D: another #releasewatch update. | The successfully triggered rule is in its six-hour pause. |
The destination receives Message C, not A+B+C, not automatically the first message, and not an AI summary. Put enough context in each source update for a reader to understand it alone. If Message C says only “same as above,” the count rule cannot repair that missing context.
Also distinguish a counting period from a delivery schedule. The rule does not wait until the hour ends to produce a digest: the completing message is eligible when the required count is reached. The cooldown starts after a successful forward, as the guide specifies.
Test the matches and the silence
Use harmless fresh text posts in controlled sources and the private target. Record the task, saved rule, message identities, source times and destination observations. Do not use customer data or urgent operational messages as test material.
- Below-threshold check: send two separate matching posts. They should not arrive through this rule.
- Completion check: send the third matching post within the counting period. Confirm that this exact third post arrives and the earlier two are not released as a bundle.
- Nonmatch check: on an isolated test rule or separate clean test run, use
#releasewatchdogand an untagged message. Neither should count as the exact#releasewatchhashtag. - Repeated-word check: a single post containing
#releasewatchseveral times is still one source message, not the three-message test. Send distinct posts to verify the threshold. - Cooldown check: after confirmed delivery, send another matching test update during the pause and check that this rule does not immediately forward it.
- Window check: in a separate run, place matching messages outside the configured counting period. Do not assume old matches are still available to complete the threshold.
Keep the threshold and timers unchanged during each run. For a quicker cooldown experiment, use a separate test configuration with a shorter permitted pause; record the different value rather than calling it evidence for six-hour behavior. Do not assume that toggling or editing a rule clears previous counts—use distinguishable test rules and record the actual starting conditions.
Do not promote the route if the negative checks fail. Receiving the third post proves only that one positive case worked. The below-threshold, nonmatch and cooldown cases establish whether your intended quiet feed is actually quiet.
Confirmation means matching messages, not independent verification
The feature counts matching source messages across the task’s sources. It does not require that each match come from a different channel. Three posts from one busy room can satisfy a three-message rule; repeated reports copied among several rooms can also create apparent corroboration without independent evidence.
For review monitoring, choose sources deliberately and inspect the forwarded post against the original material. A common tag such as #release can combine unrelated products or events. A distinctive project-specific marker reduces that ambiguity, but it is still a text rule, not an event classifier or fact-checker.
Do not use the name “confirmation” to imply that a release happened, a news report is accurate or a trading signal is safe. If you need several independent sources to agree on the same fact, that is a separate review requirement—not a conclusion supplied by this keyword count.
Troubleshoot before raising the threshold
| What you observe | Check first | Safe next action |
|---|---|---|
| Every matching post arrives immediately | Another task may be sending to the same destination; the feature may be disabled or not saved on this task. | Isolate the test route and read back its configuration before retesting. |
| Nothing arrives after three posts | Actual required count, exact match style, counting period, active entitlement and a previous cooldown. | Use the saved values and distinct fresh posts; do not infer failure from the example settings alone. |
| A longer hashtag appears to count | Whether hashtag_exact was saved, or another rule/route matched the post. | Test the exact hashtag and longer-tag control separately. |
| The output seems unrelated to earlier mentions | Overbroad aliases or a tag shared by several subjects. | Narrow the rule’s topic and keep the destination private while testing. |
| The first two posts never appear | Whether you expected a bundle, digest or archive. | This rule forwards the completing message; use a separate workflow for the other job. |
If a controlled run still disagrees with the documented behavior, pause the affected task and retain sanitized settings, times and observed results for support. Changing destinations or repeatedly resending the same material into a production channel can add noise without explaining the original result.
FAQ
Does one post containing the keyword three times count as three confirmations?
No. The documented unit is a matching source message. Repeating the word or adding several aliases for the same rule is not a substitute for separate matching messages.
Must the three matches come from three different channels?
No. The guide describes matching messages across the task’s selected sources, not a distinct-channel requirement. Keep source independence as a separate human review question.
Will the earlier messages be forwarded when the threshold is reached?
The guide says the message completing the rule is forwarded. It does not describe releasing the earlier messages as a bundle.
Can I use words instead of hashtags?
Yes. The guide provides literal matching for words or phrases and hashtag_exact for one complete hashtag. Select the style that matches your actual convention, then test near-matches.
Is this suitable for urgent alerts?
Not as their only route. A threshold intentionally withholds below-threshold messages, so a single important alert may not be forwarded. Keep urgent communication on a separately verified path.
Open one task and verify the three-message rule
Use Auto Forward Web, the official iOS app or Android app. Choose the surface you prefer; Web and the mobile apps are recommended for fuller management than the limited Telegram-bot entry point, @AutoForwardNew_Bot. Active tasks run in RedFox’s cloud; you do not need to keep the management interface open.
Next step: review the official rule fields, confirm your add-on access, and test one private route before connecting the intended audience. The goal is a readable threshold-completing update—not more copies and not an automated claim of truth. See the Auto Forward Telegram product overview for the broader workflow.
Test One Message-Count Rule Before Going Live
Confirm add-on access, save one keyword rule and verify the completing post, nonmatches and cooldown in a private review route.
Message counts are not independent fact-checking