Last year a friend who runs cross-border news came to me. His Telegram channel was losing subscribers badly.
I asked how often he posted. He said it used to be every day, then every two or three days once he got busy, then two or three times a week. The drop started then.
How long does one post take? Under two minutes, he said. Pick an image, write two lines, add a link, send.
Two minutes is short enough that it never gets its own slot, so it always sits behind other work. It also has to happen every day, and it stops as soon as you are busy. A channel loses subscribers starting from a broken streak.
Retention follows the rhythm: prepare by the week, post by the day
A channel has no recommendation feed pushing traffic for you. Subscribers add themselves, and they leave just as freely. Retention follows a steady posting rhythm. If you are there every day, they get used to looking. Break the streak for a while and the habit scatters. It is hard to gather again.
A small thing that has to happen every day is the thing people drop first. Take “post” out of what you have to remember each day.
A lot of people post whatever they feel like posting that day. That works when you are in form. When you are not, it stops. Switch to preparing by the week and posting by the day.
Before the weekend, spend an hour and prepare the whole coming week at once. Put it in a table:
| Time | Type | Text | Image |
|---|---|---|---|
| Mon 09:00 | Image + text | … | 03 |
| Mon 18:00 | Forward | … | — |
| Tue 09:00 | Image + text | … | 04 |
Once the table is written, the week’s content is fixed. Each day you no longer decide whether to post or what to post. That decision was made at the weekend. “Should I post” and “what do I post” move from every day to once a week.
How to set the flow, and how to pick the times
The posting actions are short: open Telegram, enter the channel, tap the posting entry, choose an image, fill in the text, tap send. Five steps.
On the conversation page, select the phone, switch to refinement, and say it once:
Open Telegram, go to the channel I name, tap the posting entry at the bottom, choose the image I name from the album, fill in the text I give you, and stop in front of the send button. Do not send yet.
Leave a manual confirm the first time. Once it runs cleanly, save it as a workflow. Leave the text, the image number, and whether it is a forward as parameters.
A forward sits in the same flow. It adds one step to an image-and-text post: find that item in the source channel, tap forward, choose the destination channel. That step can be saved into the flow too, with one more parameter for the source post.
Active hours follow where the subscribers are. If they cluster in one region, put the main slot in that region’s evening.
Start with one or two main slots. You do not yet know which slot works. Spread five or six times from the start and the review gets complicated.
Once the schedule is on, run it for two weeks and look at the numbers. Drop the weak slots. Keep the ones that work.
Three conditions. Miss one and the task does not move: the workstation on the computer is open, the computer is not asleep, and the target phone is online.
Several channels, and what a group can share
One channel per phone. Set the alias to the channel name. Group by language or region. Each channel can keep its own content table. A Chinese channel and an English channel differ in topics and in rhythm. Separate parameters keep them from getting mixed.
Part of group work can go to the computer. House rules, a welcome for new members, event reminders, and mute notices are like posts: the form is fixed, the content changes.
Handling a dispute, judging who is causing trouble, and deciding whether to remove someone have to stay with a person. Those are judgements about people. Handing them to a computer is too risky.
When the time passes and nothing went out
After a run, check Execution History line by line. Posting fails in three common ways.
The device is offline. Go back to the device page and look at the phone.
The wait is too short. An image takes time to upload. The next tap fires before the page has moved on. Widen it by a second or two.
A button is not recognised. For a bare icon, add an image template.
This setup covers execution: content that is already decided, sent at a time that is already decided. What to cover, how to write something people will forward, and when to follow a news cycle stay with you. Once the flow is in place, use the hour you get back on the content. Do not move it onto something else.
The news friend now spends an hour at the weekend lining up the next week, and leaves publishing alone on weekdays. The channel is daily again, and the subscriber drop has stopped. He said it used to be “I still have not posted today”. Now it is “today’s post is already in the table”.
Connect one phone from the install selection page first. Start with a daily post on one channel. Once that holds, copy it to the others.
Frequently asked questions
- What is genuinely hard about Telegram channel operations?
- Sustaining it. A channel keeps subscribers through regular posting, and two quiet weeks shows in the numbers. But the daily cost of posting by hand is high enough that a busy week becomes two quiet weeks. What has to be solved is continuity, not speed.
- How should channel content be scheduled?
- By the week, not by the day. Prepare the whole coming week in one sitting before the weekend, then let each item go out on its slot. A day when you are not in the mood no longer breaks the streak.
- Can mixed image-and-text posts and forwards be automated?
- Yes. A forward is the same flow aimed at an existing item plus a destination. An image-and-text post is the same flow with a couple of extra steps for choosing and ordering images. Fixed actions in a fixed order fit a template.
- How do several channels get managed separately?
- One channel per phone, aliased with the channel name, grouped by language or region. Each channel keeps its own content table and parameters, so the schedules never contaminate each other.
- A scheduled post did not go out. Where do I look?
- Execution History records the source, status, target device and error for every task. The usual causes are a device that is offline, a wait that is too short, or an icon button that could not be recognised.
- Does the posting time matter?
- It does. Active hours differ by region and by content type. Start with one or two main windows based on where your subscribers are, run it for two weeks, and adjust from the data rather than launching with five slots.
- Can content preparation be automated?
- No. What to cover, how to write it, when to jump on a news cycle: those are the core judgement. What can be handed over is the act of posting, plus recording what went out.
- Does Telegram group management fit the same approach?
- Partly. Recurring house rules, welcome messages, event reminders and mute notices are fixed in form and variable in content, so they template well. Handling disputes and judging who is causing trouble must stay with a person.
Move the posting out
Line up the content in the morning, let it go out on time
Software is completely free and runs on your own computer.