Terminology
Tags
The [Tags] is equivalent to a folder or directory, and each channel/group, draft and button group supports one or more tags for easy search, modification, and management of scheduled tasks.
[Tags] support dynamic data reading, for example, when you set up a scheduled task, you can select channels/groups, drafts or even button groups by the tags. In the future, new channels/groups, drafts or button groups only need to be associated with the corresponding tags, which can automatically join the existing scheduled task, without manually modifying the task.
[Tags] for channels/groups: You can organize channels/groups by the tags. When you select the tags in a scheduled task, the task triggers all channels/groups by the tags.
[Tags] for drafts: You can organize drafts by the tags. If you enable the [Select Drafts By Tags] option in a [Scheduled Post] or [Recurring Post], a random draft from the specified tags will be used each time the task is executed.
[Tags] for button groups: You can organize button groups by the tags. When manually adding or importing drafts, if the [Select the button group by tags] option is enabled, a button group is randomly selected from the specified tags to be used.
Disable Notification
When the [Disable Notification] switch is on, sends the message silently (users will receive a notification with no sound).
Protect Content
When the [Protect Content] switch is on, protects the contents of the sent message from forwarding and saving.
Pin
When the [Pin] switch is on, message will be pinned in the top of channel/group.
Auto Delete
When the [Auto Delete] switch is on, draft will be automatically deleted after successful delivery. Note: If the draft belongs to [Recurring Posts], please turn this switch off, otherwise the draft in the task will not work properly after sending due to insufficient drafts.
Auto Forward
When the [Auto Forward] switch is on, the post will be automatically forwarded to the specified channel/group. Before using this function, please configure the username of the channel/group you need to forward to, in the Control Panel [Drafts] -> [Settings] -> [Auto Forward Settings] page, and set the bot as an administrator of the channel/group. When the main channel/group successfully publishes a post, the bot will forward the post to the channel/group you specify to help promotion of the main channel/group.
Paid Media
Draft support sets images or videos as paid media. Subscribers will have to pay for stars to unlock them. To prevent content from being viewed for free after being forwarded, you are advised to enable the [Protect Content] function.
Star Payment is an official function provided by Telegram and has nothing to do with us. All revenue is directly distributed by Telegram officials and has no connection with this bot.
Authorization
A virtual administrator does not need to be the actual administrator of the channel/group, but can manage all channels and groups that you have authorized to him.
For example, if you manage posts for 10 channels and 10 groups using @aoloo, you simply send your Token to the virtual administrator. After registering his account via @aoloo , he can request authorization by your Token. Once authorized, he can manage all your channels and group posts through the bot.
In addition, a virtual administrator can manage posts for all channels and groups of multiple Telegram accounts by requesting authorization for each account separately.
Recurring Posts
Repeat posts without interruption: You can set up one post, multiple posts, or even select a group of posts by tags as the content to be repeated. Each time a task is triggered, the system deletes the last bottom-posted post and then randomly posts a post from the selected post.
Channel bottom posts: Support for automatic bottom keeping. When the channel content is updated within 1 minute, the " bottom post" task is automatically executed, so that the specified post always comes first. It also supports regular release, and the release logic is to delete the old post first, and then publish the new "bottom post".
Group bottom post: In the group, because the frequent bottom of the message will cause too much information, so only the periodic post is supported for the time being. The publishing logic is also to delete the old post first, and then publish the new "bottom post".
The deletion and publication of each task is performed independently based on the respective "bottom post" task. You can set up multiple "bottom post" tasks to run at the same time, each task does not interfere with each other, so that you can flexibly manage different bottom content.