Concept illustration: one creator-owned post routed to selected member rooms.
One VIP post can reach the right member rooms without publishing it twice by hand. If you run a Telegram channel and separate discussion groups for your members, RedFox Auto Forward Telegram can route new posts from that channel into your chosen groups—even when the source has Protect Content enabled. This is a regular forwarding capability on every plan, including Free, rather than a special purchase for the standard Telegram setting. The useful decision is not whether a private channel can be selected; it is which audience should receive each kind of post.
Create a member-room route in the Web App, or manage it in the official Android or iOS app. RedFox runs active routes in its cloud, so the creator's phone or browser need not remain open.
Design the member route before creating a task
Imagine a creator with a protected Course Notes channel and two separate member groups, Spring Cohort and Mentor Room. An announcement meant for both groups can be distributed by selecting the intended destinations in the task flow, subject to the current plan's source, target and active-task capacity. A private Spring Cohort group is still the wrong destination for a Mentor-only answer if those members should not receive it. Choose the audience first, then choose the route.
| Content | Audience | Routing decision |
|---|---|---|
| Shared course update | All current course members | Use a dedicated source for shared posts, routed only to the member rooms that should receive them. |
| Mentor-only worksheet | Mentor members | Keep it in a Mentor-specific source and route only to Mentor Room; don't send the full post to a general group. |
| Public invitation or teaser | Prospective members | Write a separate public-safe post and route that source to the public channel. Do not point the full VIP source at a public target. |
Choose membership access and author any public teaser separately; the forwarding task carries posts to the destinations you select. Telegram's Restrict Saving Content affects ordinary forwarding and saving; it does not replace selecting the correct audience.
Create the channel-to-member-group route
Before setup: use a connected account that can access the channel and content you own or have permission to distribute. Check that the destination includes the intended members and that the selected posting identity can send there. Source membership, content rights and target posting permission are different checks. RedFox's private-source FAQ explains the account-access requirement; its sender guide distinguishes a personal account from a bot posting at the destination.
- Open the Web App or an official mobile app with the Telegram account that can read Course Notes.
- In Forwarding List, choose Create Task +. On Select Source Forward, filter by Channel, select the exact VIP channel and press Next Step.
- Under Select Target Forward, choose the intended member group and press Next Step. Check the selected destination before the last step: RedFox's task guide says a task is activated upon creation.
- Label the route, for example
course_members, and choose Create Task. Repeat or adjust the destination selection only for rooms meant to receive the same source content, within your plan's limits. There is no separate Protect Content toggle or Anti-Repasse purchase for this standard source setting.
For a split offer, the simplest design is often separate editorial sources: shared posts in one channel, premium-only posts in another. That keeps the routing logic legible to a nontechnical operator. If you later need rules to distinguish content within the same source, check the current plan's rule entitlement rather than assuming every filter is on Free. RedFox lists Free with three active regular tasks, three sources and three targets; basic protected forwarding is included in that regular capability.
Keep the public teaser separate from the VIP post
A public channel can be valuable for discovery: publish a short invitation, schedule or preview there, while the complete lesson stays in the member source. A dedicated teaser source and separate route make the boundary explicit. Do not rely on a change in destination privacy to redact the full content. If a VIP channel feeds a public target, the entire selected post may go to that audience; inspect the actual target before creating the task.
Likewise, a VIP subscription to somebody else's channel means your account may be able to read posts. VIP membership and individually paid Telegram media are different; ordinary accessible channel posts do not require a paid-media purchase.
Check one new post before inviting the audience
Start with an owned source and a controlled member destination. After the task is created, publish a disposable announcement such as “The Tuesday workshop starts at 18:00” and check whether the right room receives it, with the intended text and attribution. Follow with a photo and caption if your usual member update includes media. Confirm the audience, not merely the task's active label. A route for new posts does not copy your entire course archive: RedFox documents a separate Clone workflow for older messages, whose plan terms should be checked on its own.
For multiple photos or videos sent as a Telegram album, inspect item count, order and captions at the destination. RedFox's Album Delivery Mode offers Fast, Balanced, Stable and Careful handling with a timing tradeoff, but no mode guarantees every album item. Our album guide is the next step when your lessons depend on grouped media. If the source is not listed, check the connected account's membership and Channel/All picker choice before using the documented Reload action.
Make the next member update easier
Start with the route that has the clearest audience: one VIP source and one member group. Open RedFox Auto Forward Telegram on Web to connect your source and select the member destination, or use the official Android and iOS apps. The current bot is @AutoForwardNew_Bot; the older @Auto_Forward_Messages_Bot handle has migrated, so use the current one. Test a new post in the intended room, then let the cloud route carry subsequent updates. For other channel and group patterns, see our Telegram forwarding overview.
Auto-Bot.io is an editorial publisher covering RedFox Auto Forward Telegram, not the developer or operator of the bot.