Auto-Delete Forwarded Telegram Notices Without Deleting the Source

To remove temporary Telegram notices without deleting the originals, configure Auto Delete Messages on one RedFox forwarding task, match a distinctive notice marker and keep unmatched messages. The add-on schedules deletion of successfully forwarded destination messages after a chosen delay. Your source stays intact, while durable destination posts can stay visible.

That is useful for a team bulletin that mixes short-lived reminders with reference material: a “review room opens shortly” notice should not clutter the feed tomorrow, but the onboarding instructions should not disappear with it. Start in a private test destination before enabling deletion for readers.

The featured image is a conceptual illustration of selective destination cleanup, not a product screenshot or an observed deletion test. Auto-Bot.io is a separate editorial publisher, not the developer or operator of RedFox Auto Forward Telegram (@AutoForwardNew_Bot). This guide uses RedFox documentation checked October 10, 2026; the specimens below are controlled examples for you to test.

Define what expires—and what must remain

The Auto Delete Messages documentation says the add-on affects messages sent to destination chats, not original source messages. It supports a default delay, keyword rules, content-type selection and per-task configuration. The documented delay range is 60 seconds to 30 days.

For a mixed team bulletin, use this policy: only notices carrying the agreed marker TEMP_NOTICE receive a timer; ordinary reference posts are kept. Agree on the marker with the people writing source messages. A keyword match is not an understanding of whether an announcement is still useful.

Only route content you own or are authorized to redistribute. Target-only deletion is a useful boundary, not a recall of screenshots, downloads or copies that recipients have made elsewhere.

A delay is not an event deadline

The timer is associated with a successful forward. It does not read an event time in the text and calculate when the event ends. A notice forwarded later also starts its deletion delay later.

Illustrative timing: if a copy is successfully forwarded at 09:50 and its delay is 10 minutes, its intended removal point is 10:00. If the same notice is not forwarded until 09:58, that same delay instead points to 10:08. These are arithmetic examples, not a promise of exact execution timing.

If a notice must stop being visible at a specific wall-clock deadline, an operator must account for actual delivery and check the destination. Do not treat “delete after 10 minutes” as automatic event-end detection. For changes to the underlying event, use the reschedule and cancellation runbook; deletion alone does not tell readers what changed.

Prepare one controlled forwarding task

1. Choose your source and test destination. Use a source you control and a private destination with no real audience. Confirm the selected sending account or bot can post there and has the rights needed to delete its target messages.
2. Create or isolate the route. RedFox's task guide documents Forwarding List → Create Task +, source selection, target selection, a label and Create Task. It says creation activates the task, so choose the test destination first. If you already have a working route, do not rebuild your whole setup for a deletion rule.
3. Check add-on access. In Menu → My Addons, inspect Auto Delete Messages and its current access period. RedFox's add-on guide describes credit-based, time-limited access with price and duration reviewed before unlocking. Do not assume this optional feature is included in every plan or commit to a price copied from an old article.
4. Open this task's Auto Delete Messages configuration. Keep the scope to the controlled route. Record its original settings, sending identity and destination before changing anything.

For account connection and first-route details, follow the existing Telegram forwarding setup guide. If the source is a mixed discussion group, selecting group announcements is an earlier decision: which messages enter the bulletin. Auto Delete decides how long the selected copies remain there.

Configure selective deletion without clearing the bulletin

The documentation says the add-on checks forwarded message text or media captions and applies the first enabled matching keyword rule. For the initial test, use just one rule:

• Keyword: TEMP_NOTICE.
• Match mode: Any Match. With one keyword, one match is enough; All Match becomes useful when every configured keyword must be present.
• Case sensitivity: enabled, if your writers will use the exact uppercase marker. Then temp_notice should not match this uppercase rule.
• Delete after: 60 seconds for the disposable test, the documented minimum. Choose a practical longer delay for the real bulletin only after the test passes.
• Unmatched behavior: Keep Unmatched Messages.
• Content types: Text for the first test. Add Photo only when you have also checked the caption case.

Do not leave Delete Unmatched Messages enabled for this mixed-feed policy. With that setting, unmatched messages use the default deletion delay. Although the documentation recommends it for general cleanup, it is the wrong choice when ordinary onboarding posts must remain.

Inspect the saved values, not only what you selected before saving. Check the final forwarded text or caption too: transformations may change whether your marker is present. Avoid broad words such as event or update that occur in permanent references.

When you later add rules, put the specific rule before a broad overlapping rule. The first enabled match determines the delay; the documentation does not say the shortest timer wins. It lists limits of 20 rules, 20 keywords per rule and 120 characters per keyword. A small deliberate rule set is easier to audit than filling every available slot.

Test arrival, removal and preservation separately

Use new disposable messages after saving the controlled configuration. The following expected results describe the documented policy, not outputs already observed by Auto-Bot.io.

Run the text checks first. Then explicitly include Photo and run both photo specimens. If you leave Photo excluded, do not interpret its survival as a failed text rule. An album is a separate documented content type: test all destination items if you intend to apply deletion to media groups rather than treating a single-photo pass as album proof.

Record the observed destination arrival time, configured delay, first check after that delay and whether the exact target copy still exists. Refresh or reopen the destination before deciding. Also check the unmatched reference and original source message. “The post never arrived” does not prove automatic deletion worked.

For an ordering check, add a short-lived second test rule matching TEMP_NOTICE plus URGENT_TEST in All Match mode, ahead of the broad rule, with a different delay. A specimen containing both should use that first rule. Restore the single-rule configuration after this test unless the distinction serves your real bulletin.

If the wrong message disappears—or the notice stays

Telegram also has its own chat-level auto-delete feature. Its February 23, 2021 announcement describes a chat timer for messages sent after it is set, with administrator control in groups and channels. That historical announcement explains why a separate timer can affect your test; it is not a current menu guide or an exhaustive list of today's timer choices. Isolate the RedFox test from other deletion policies before attributing a result to this add-on.

If a check fails, keep the rollout in the private destination and record the exact task, source/target message references, configured values and observed times for RedFox support. Never include login codes, passwords or bot tokens.

Roll out only the retention policy you tested

Choose the real notice delay based on how long recipients need the message, not on the fastest successful test. Keep permanent references unmarked and unmatched messages kept. Pause the task before changing test endpoints to real ones; recheck the target audience, sending identity and rule scope, then resume deliberately and inspect the first real eligible copy.

Keep a small operational note: task label, temporary marker, included content types, rule order, delay, add-on expiry date and the person responsible for checking removal. Source preservation lets you retain the original notice where appropriate; it does not automatically make the source a formal archive.

If you need to stop cleanup, do not assume disabling a rule cancels deletions already scheduled. The public guide does not define that cancellation behavior. Contain the affected task, inspect pending notices and ask support about already scheduled removals. Nor should you expect turning the feature off to restore copies already deleted.

FAQ

Can I expire only marked notices and leave the rest?

Yes. The documented combination is an enabled keyword rule, selected content types and Keep Unmatched Messages. Test both a marked notice and an unmarked reference before rollout.

Does the add-on delete the source post?

No. RedFox documents target-only deletion. A disappearing source post needs investigation of another timer, action or automation.

Can I use the rule as a daily feed reset?

A delay after each successful forward is not a single daily reset. Copies forwarded at different times reach their intended removal points at different times.

Does this remove old history when I switch it on?

The documented workflow schedules removal when a message is successfully forwarded. Do not rely on it as a retroactive purge of every older destination message.

Start with one temporary notice and one permanent reference

Open the RedFox Web app, choose one controlled task and check Auto Delete Messages access. Configure the marker, keep unmatched messages and verify the two outcomes: the temporary copy disappears, the reference and source remain. See the Telegram forwarding product overview for the wider workflow.

Use Web or the official iOS and Android apps for fuller visual task management; the Telegram bot is another entry point. Active forwarding tasks run in RedFox's cloud without keeping the management interface open. Selective cleanup reduces recurring manual removal while leaving you in control of which notices are disposable.