Telegram: Skip Voice Notes, Keep Audio Files

To stop forwarding Telegram voice notes while keeping uploaded audio files, enable the task’s Voice filter in RedFox Auto Forward Telegram (@AutoForwardNew_Bot) and leave Audio off. The official Filter By Type guide lists Voice and Audio separately and says an enabled filter excludes that message type. This is a selection rule for one forwarding task—not a mute button for the source group.

This guide is for an existing Telegram-to-Telegram feed that already delivers written notices and media. Your source team also records informal voice notes, but the destination should receive written instructions and deliberately uploaded recordings instead. The goal is to exclude the voice-note format, not every message that contains sound. Other task rules still determine which remaining messages can be sent.

The featured image is a concept illustration, not product UI or an observed forwarding result. The example and checks below are a reader-run procedure based on documentation reviewed on October 25, 2026.

Choose the policy before choosing a toggle

Imagine a training team’s source group contains written room changes, uploaded lesson recordings and quick microphone updates between instructors. A separate participant feed should keep the room changes and lesson recordings, without carrying the informal microphone chatter. That is a skip voice notes, keep audio files policy.

Do not call this a “text-only feed”: you still want useful audio files. If participants need every instruction in writing, ask the source team to publish an approved written version of important spoken updates. Excluding a recording does not transcribe it or judge whether its contents matter.

Telegram’s Message reference distinguishes voice, audio, video_note, video and document. Those platform categories explain why “it makes a sound” is not a useful filter definition. They do not establish RedFox’s internal processing order or prove an account-specific forwarding result.

Voice, Audio and Video Note are different exclusions

Use the names in RedFox’s type-filter guide rather than guessing from a filename or what the recording sounds like.

Off means “not excluded by this filter,” not “guaranteed delivery.” An audio file can still be rejected by another active rule or encounter a delivery problem. Likewise, a short video is not necessarily a Video Note. Match the actual source format before diagnosing a missing item.

For this job, use Filters → Voice, not Cleaner → Voice. RedFox describes Filters as skipping whole messages and Cleaner as removing matched content. You want to exclude the voice-note message, not experiment with removing parts of it. Keep unrelated Cleaner options unchanged while checking the exclusion.

Set Voice on one controlled task

Use harmless content and a private source and destination you control. If your route does not deliver yet, follow the existing Telegram forwarding setup guide first. Do not reconnect a working account just to adjust one type filter.

1. Open the right route. In the RedFox Web App or official mobile app, select the intended task. Read its source and target names or IDs. Record the current task status, delays, type filters and Cleaner settings so you can restore the prior policy.
2. Find the task’s Filters area. Open the message-type controls and locate Voice. RedFox’s task-settings guide identifies Filter and Cleaner as separate controls.
3. Enable Voice to exclude voice notes. Leave Audio off for the training-feed policy. Decide separately whether round video notes should be excluded; do not enable Video or Document merely because some files contain sound.
4. Save and read back. Complete any save or confirmation shown by your interface, reopen the task and check the saved Voice and Audio states. Check access to these controls under your account’s current plan if the interface restricts them; basic forwarding access is not proof of access to every filter.
5. Check for another delivery path. Make sure a second task is not sending the same source into the same test destination. Otherwise an unfiltered route can deliver a voice note even when the task you changed excludes it.

If you manage tasks through the Telegram bot, the documented entry is /settings → Manage Forwarding Tasks → select the task → Advanced Configuration → Filter. Web and mobile layouts may differ; follow the current labels on your chosen surface rather than expecting the bot menu everywhere.

Check the excluded format and the formats you want to keep

The following are hypothetical specimens, not results from a connected account. Create fresh source messages after saving the change, use distinct content and wait through the task’s configured delays before interpreting an absence. Do not replay a source history or send repeated trials to a live audience.

1. Written-notice control. Send “Training check A: Room Cedar opens at noon.” Verify it reaches the private destination. If ordinary text fails, first recover the working-route baseline; a missing voice note alone would not prove the filter works.
2. Voice-note exclusion. Record a short harmless voice note directly in Telegram. Confirm it exists in the source and is not delivered by the filtered task. Record its time and how it was created.
3. Audio retention. Upload a different harmless lesson recording as an audio message. With Audio off, it remains eligible under that exclusion. Verify the actual destination item and playback rather than accepting the saved toggle as proof.
4. Document boundary. Send a separate harmless recording as a file/document. Inspect its source presentation and the Document filter. This checks your real upload workflow; a filename ending in an audio extension is not enough to assume it was sent as an audio message.
5. Round-video boundary. If the source uses circular video notes, make a fresh one. Judge it against Video Note, not Voice. Record whether your policy deliberately leaves these eligible or excludes them too.
6. Ordinary-video control. If regular lesson videos are part of the feed, send a small approved video separately. Verify it remains usable under the task’s unchanged Video policy. Do not infer video handling from a successful audio check.

Keep one short result note: task, source item type and timestamp, saved relevant filter states, expected result and observed destination result. “Not seen yet” is an unresolved observation until you have checked timing, route health and competing paths. If a lesson depends on an excluded voice note, fix the editorial policy or publish a written instruction; do not silently discard essential context.

If the wrong recordings still arrive—or useful files disappear

• A voice note still arrives: reopen the exact task, verify Voice is enabled and inspect the item in the source. Check for another forwarding task, manual repost or a recording sent as audio/document rather than as a voice note.
• Lesson audio disappears too: inspect Audio and Document according to how the source item was sent. Review other active rules and Cleaner settings without switching off every protection on a live task. Change one relevant setting at a time in the controlled route.
• Circular videos still arrive: that is a separate Video Note policy. Do not broaden the meaning of Voice to cover a different documented type.
• Photos or their captions are missing: use the separate photo and caption filter diagnosis. Changing Voice is not a remedy for Photo, Photo With Text or Cleaner problems.
• Nothing arrives: check task activity, the selected source and destination, permissions, other rules and delays. Restore a known written-notice baseline before treating absence as successful exclusion.
• Old voice notes remain in the target: this procedure checks new-message selection. It does not establish retrospective deletion or automatic recovery of previously skipped messages.

If the policy is wrong, pause the affected route before restoring the recorded settings and read them back before resuming. Do not assume pausing clears queued work or that disabling Voice replays old skips. For support, share a sanitized task label, actual source format, saved states, timestamps and expected versus observed results—not login codes, passwords, tokens or confidential recordings.

FAQ

Does turning Voice on allow voice notes?

No. RedFox’s Filter By Type guide says turning a filter on excludes that message type. Voice is listed as ignoring voice messages or voice notes.

Should Audio also be enabled?

Only if you also want to exclude audio messages. For the policy in this guide, leave Audio off and check a genuine audio-file specimen. This does not override other task rules.

Will the filter turn voice notes into text?

No transcription is established by this type-filter setting. If a spoken update is important, arrange a written source notice or evaluate a separately documented transcription workflow; do not expect Voice to create one.

Keep the useful recordings, not every recorded aside

Open one task in Auto Forward Web, enable Voice and keep Audio off for this policy. Check a written notice, a real voice note and an uploaded audio message before applying the same change to the intended live feed. Include the document and video boundaries when your source actually uses them.

You can choose the official iOS app or Android app instead. Web and mobile apps are recommended for fuller management than the limited Telegram-bot entrypoint; see RedFox’s mobile-app guidance. Active tasks run in RedFox’s cloud without keeping the management interface open, consistent with its runtime FAQ.

See the Auto Forward Telegram overview for the wider workflow. Auto-Bot.io publishes this independent editorial guide; RedFox provides the product and its documentation. The previous bot has moved to @AutoForwardNew_Bot; use that current handle.