Home · Blog · Posts on Telegram, VKontakte and MAX from one window with a schedule
Posts on Telegram, VKontakte and MAX from one window with a schedule
When there is more than one channel, publishing turns into a routine: the same post must be manually transferred to Telegram, VKontakte and MAX, and each platform has its own limits, its own work with media and buttons. The “Editing” section in CHBT collects this in one window: write the material once, give each site its own version and send it as soon as possible (from a minute) or on schedule. Let's look at how the material is organized, what is delivered to each channel, how the schedule and delivery queue works, who publishes and how the AI draft helps - without promising anything that is not in the product.
One material - three sites
The material in the “Editorial” is a general heading and a separate option for each platform: Telegram channel or group, VKontakte community and MAX channel. You add platforms in advance in the section after you have connected channels in “Channels”, and CHBT checks the bot’s rights to publish.
The point of the individual options is that the sites are different. A short announcement with a button works well on Telegram, a detailed post with details on VKontakte, and a lengthy post on MAX. Therefore, each option has its own text, its own attachments and its own button. An unnecessary platform can be disabled for a specific post - for example, published only in Telegram and MAX.
How to connect the channels themselves is discussed on the pages bot for Telegram, bot for VKontakte and bot page for MAX; “Editorial” takes already connected channels and works on top of them.
For Telegram, the option can be created not as a regular post, but article with titles and pictures. Then CHBT creates a Telegra.ph page and posts a link to a channel or group - in Telegram it opens directly in the application as Instant View. Pictures in the article are taken from https links. On VKontakte and MAX, articles are not available through their API, so the same material goes there as a regular post.
What reaches each channel
Sites have different limits and work with buttons differently - “Editorial” takes this into account and honestly shows it in the preview of the option.
| Opportunity | Telegram | VK | MAX |
|---|---|---|---|
| Text length | up to 4096 characters; from media - up to 1024 in signature | up to 16000 characters | up to 4000 characters |
| Media | photo, video, files, album | text and images; leave videos and files in draft for now | photos, videos, files |
| Buttons under the post | up to 8 buttons; in the album there are links in the text | links in the text: the post does not have its own buttons | up to 8 buttons |
| Secured in the channel | yes, you need bot rights | yes, you need rights | no |
Separately about the buttons. You can set up to eight link buttons under a post. In Telegram (except for the album) and MAX they appear as a real keyboard under the post. A regular post on VKontakte does not have arbitrary buttons, and the album in Telegram does not support the keyboard - in these cases, CHBT adds each button with a link line in the text: “More details: link.” This way, links are not lost, even if the site does not allow you to draw buttons.
Schedule and statuses
The material can be sent as soon as possible (from a minute) or you can set a date and time - then it will go away on its own. Each site is published with its own line and has its own status, so you can see not “published/not” in general, but what happened at each of the three.
| Status | What does it mean |
|---|---|
| Draft | Material created, not yet sent and not scheduled |
| Agreed | Ready for publication, waiting to be sent |
| Scheduled | Scheduled for date and time |
| Published | The queue is sending a post to the site right now |
| Published / Error | Delivered to site or shipment failed |
Since delivery is calculated by site, one material at three sites equals three deliveries. Two can pass, and the third can go into error, and the line will show which one.
An already published post can be corrected (text and buttons) or deleted from the channel - on each site separately, with confirmation for deletion. The media of a published post does not change. Telegram limits the bot's time to edit and delete its messages, so the platform may refuse for old posts - then this can be seen in the delivery line, but the post itself remains the same.
You can publish regularly. In the weekly schedule, you select the days of the week and time - for example, on Mondays and Thursdays at 10:00 - and each time the “Editorial” itself creates a new post from this template (text, media, buttons and sites as saved) and sends it. Time is calculated in the selected zone without daylight savings; the schedule can be stopped at any time, and if one attack fails, the schedule will continue from the next time.
What happens when there is a site error
Platforms sometimes respond with an error: network, temporary API failure, request limit exceeded. “Editorial” is designed so that such a failure does not lose the post and does not publish it twice.
- Repeat temporary error. If the site fails for a reason that can go away on its own, the queue will re-send later. There is no point in repeating a permanent error - for example, the bot does not have the right to publish - and the line will go to “Error” with an obvious reason.
- Protection against duplicates. The queue marks the submission before contacting the site, so the replay does not create a second post. If the result of the submission remains unknown - the process was interrupted at the time of publication - the delivery goes into a state that requires verification, rather than being resubmitted blindly.
This is the same durable approach as in delivering responses and broadcasts: first we fix the intent, then we go to the external API. About the reliability of message delivery in general - in analysis why is the Telegram bot silent.
Who publishes: roles
Publishing is a responsible action, so rights are shared.
- Owner and administrator create materials, launch AI generation, change text, schedule and publish.
- Operator sees saved materials, but does not generate or edit them. Its zone is responses: replies in the thread, assignment, lead tag.
This way, the post will not accidentally go into the channel from the one who responds to the comments, and approval remains with those who maintain the content. How the roles in the project as a whole are structured and how an operator differs from an administrator is shown on the page section "Conversations".
AI draft: suggests, and you publish
If you need to write a post quickly, “Editorial” has a draft generation option. You set the brief, facts, audience, tone and language, mark the sites and, if necessary, a link button. The AI returns the text for these sites, and the server saves it regular draft - does not publish or approve it himself.
Then the material goes through the same path as written by hand: you edit the text for each site, approve it and send it. Control remains with the person: AI only speeds up the first option. He does not post himself and does not respond in comments - this is done intentionally.
Generation consumes AI credits from the overall balance of the project. AI is available from the Basic plan; on Free, the generation button will inform you that AI is not available, but you can publish and schedule posts manually there too. How loans work and the choice of models - in the article about knowledge base and AI.
What the results show and what they don't show
The Results page in Editorial for 7, 30, or 90 days boils delivery and response down to numbers. According to publications, these are: successful deliveries to sites, errors and shipments that are awaiting reconciliation, the latest delivered materials with a transition to the material itself.
What's on this page no: post views, reach, reactions, clicks on external buttons and revenue. The sites either don’t give these numbers, or they give them in such a way that they can’t be trusted, so we don’t show them so as not to mislead. We’ll add it later and only where the site provides it correctly.
What is really measured next to the publication are responses and transitions to the bot based on comments: how many people wrote under the post and how many went into conversation. How to turn these responses into leads is discussed in the article about sales through comments, and a full overview of the section is on the page “Posts and comments in channels”. You can try it with a free plan: open “Edit” →
Posts and comments in channelsSelling through commentsOne script on MAX and TelegramPlans