Slots, not a wish list
Each item has a rubric, a day and a time in the channel's zone. The scheduler reads the same grid.
Content plan
A Telegram content plan that ends in published posts
A content plan is a promise about cadence and rubrics. AwrAiter turns it into a weekly grid of slots in the channel's own time zone, so the team sees what is due, what is still empty and what already went out. Fill the slots by hand, from your news sources, or let your ChatGPT or Claude draft straight into them through the MCP connector.
01 — How it works
From rubrics to a calendar in four steps
-
01
Pick rubrics and cadence
The plan wizard asks what the channel posts and how often: news digest three times a week, one explainer, one poll. It lays the slots out over one or two weeks.
-
02
See the grid
Every slot has a day, a time and a rubric. Empty slots are visible at a glance; the earliest free one is a single click — or a single MCP call — away.
-
03
Fill the slots
Type the post, pull a draft from a connected news source, or ask your assistant: “fill next week's empty slots from my sources”. Drafts land in the slot, not in a chat.
-
04
Approve and step back
Approve the plan; every filled slot is published at its time and verified afterwards. Once scored, top and flop posts tell you what to change in the next plan.
02 — What you get
A plan the whole team can see
Autofill from sources
Connect sites and Telegram channels as sources; the system proposes drafts for empty slots from fresh items; you approve before anything goes out.
Next plan in one click
When a plan ends, the next one opens pre-filled with the same rubrics and cadence. Nobody rebuilds the table on Monday.
Assistant-ready
Through MCP the assistant reads the plan, finds the next free slot and creates a post bound to it — the slot closes when the draft is in.
Autopilot (beta)
Switch it on per channel and empty slots get drafts queued automatically. Publishing still waits for your approval.
Scored afterwards
Every published post is scored against the channel's 30-day median, so the plan learns which rubrics and slots this audience answers.
03 — Template
A starting plan for a channel that posts daily
Use it as the first wizard input and adjust after two weeks of scores. Times are in the channel's zone.
| Rubric | Cadence | Slot | What goes there |
|---|---|---|---|
| News digest | Mon, Wed, Fri | 09:00 | Three to five items from your sources with one line of context each and the source link. |
| Explainer | Tue | 12:00 | One topic explained without jargon; the post people forward to a colleague. |
| Opinion | Thu | 20:30 | A take on the week's news. Short, first person, ends with a question. |
| Community question | Sat | 11:00 | One question, no link. The cheapest post with the highest reaction rate. |
| Weekly recap | Sun | 18:00 | What happened in the channel this week, with links back to the posts. |
Five rubrics, seven posts a week. Drop the recap first if the team is small; keep the digest — it is what subscribers came for.
04 — Questions
Before you build a plan
How many posts a week should a Telegram channel publish?
Enough that a subscriber remembers the channel exists and not so many that reach per post collapses. For most channels the sweet spot is three to ten posts a week; watch ERR (reach) in analytics and stop adding posts when it starts to fall.
Can several people work on one plan?
Yes. Members see only the channels you allow; the plan, the drafts and the approval are shared inside the team.
Can the assistant fill the plan?
Yes. Through the MCP connector it reads the plan, finds the next free slot and creates a post bound to that slot with create_post_from_text and schedule_post.
How far ahead can I plan?
One or two weeks at a time. When a plan ends, the next one is created pre-filled with the same rubrics and cadence, so the horizon is effectively continuous.
Who writes the posts?
Your team, your sources, or your own ChatGPT or Claude over MCP. AwrAiter keeps the grid, the schedule and the scores.
Build the first plan in five minutes
One channel is free, forever. The wizard does the grid; you do the posts.