Social media · Lesson 2.6
A One Week Plan to Get Mobile Content Approval Working
Most people stall on mobile content approval because the whole thing feels like one big project. It is not. It is seven small steps over a week. This post lays them out day by day, with a worked example and a scorecard.
To be clear: this is a plan, not a report of my own results. The example is made up to show the idea, and the numbers on the scorecard are for you to fill in. The setup itself is taught in Lesson 2.6: Approve every post from your phone.
In one week you can have posts arriving on your phone with an approve button, if you do one small step a day and measure your own results.
Before day one
Decide what you are approving. One kind of post is enough to start, such as your daily tip or product photo. Make sure your AI can already draft it. Install Telegram on your phone if you do not have it. Then block about 20 minutes on day one. The lesson is listed at 18 minutes.
The week
- Day 1, make the botMessage @BotFather in Telegram, send /newbot, and follow the questions. Save the token somewhere private. Telegram's docs say the token authenticates the bot and can be revoked through BotFather if needed.
- Day 2, get a draft on your phoneSay hello to the bot, then have your AI send one draft to the chat. Do not publish anything yet. Just check you can read it comfortably.
- Day 3, add the buttonsAdd Approve and Change under the draft. Inline keyboard buttons in Telegram sit under the message and work without posting a new message in the chat. Test both.
- Day 4, publish one approved postTap Approve on a real draft and check it goes out the way you expect. Look at the live post, not just the chat.
- Day 5, try the voice noteTap Change and send a short voice note with one fix. Telegram bots can receive voice messages, so this is supported. Check the result.
- Day 6, turn a fix into a rulePick a change you made twice and tell your AI to keep it as a rule. The lesson covers how this works.
- Day 7, review the weekFill in the scorecard below and decide what to change next week.
What can go wrong, by day
- Day 1. Pasting the token somewhere public. Revoke it if you did.
- Day 2. No first message sent to the bot, so nothing arrives.
- Day 3. Buttons appear but do nothing, because the listening part is not running.
- Day 5. A voice note is misread. Use one short, clear sentence.
- Day 6. Making rules too broad. "Be better" is not a rule. "No exclamation marks" is.
A worked example (illustrative)
Say you teach yoga and post one class tip a day. On day four you tap Approve on a draft about a Tuesday evening class. On day five, the draft says "class at 6" when it is at 7, so you send a voice note, "it is seven, not six." On day six you notice you have removed the word "amazing" three times and tell your AI to avoid it.
None of this proves a result for anyone else. It shows what each day is for.
Your scorecard
Copy this and fill it in on day seven with your own numbers.
| Measure | Your number |
|---|---|
| Drafts received this week | |
| Approved without changes | |
| Changed by voice note | |
| Rejected | |
| Same fix needed twice | |
| Minutes spent reviewing, roughly |
Reading the scorecard
If most drafts were approved as they were, your setup is working. If most needed changes, the rules are too thin, so spend next week on those. If you spent more review time than writing by hand would take, either the drafts need better rules or this kind of post suits manual writing.
After the week
Keep the loop going for another two weeks before judging it. The first week includes setup and learning, so it is not a fair picture. Compare week three with week one on the same scorecard. For a fuller look at what to track, read measuring mobile content approval.
If you only have 10 minutes a day
The plan works on short sessions, because each day has one job. Do not try to merge days. Merging usually means a half tested bot, and the first sign is a button that does nothing when you need it.
If a day goes wrong, repeat it the next day rather than moving on. A token you cannot find or a draft that never arrives is better solved on day two than discovered on day six.
What to decide on day seven
At the end of the week you have three options. Keep going unchanged if most drafts were fine. Tighten the rules if many needed changes. Or pause if the setup took more effort than the posts were worth, which is a perfectly good result. This is a trial, and one of its purposes is to find out that this does not suit you.
Write down your decision and the one change you will make next week. A single change is easier to judge than five.
Keeping it going after week one
Many trials fade in week two. To avoid that, fix your review times now and put them in your calendar as repeating events. Tell the one person who might otherwise ask you for posts that you review at those times. And keep the scorecard in the same place each week, so filling it in takes two minutes and not a search.
Questions people ask
Can I really do this in a week?
A basic version, yes, if you can spend about 20 minutes on setup and a few minutes a day after. Your pace may differ.
Do I need to buy anything?
Telegram is free to use and the lesson describes the start as costing nothing extra. Check current terms for your AI tool.
What if I fall behind?
Take the days as a list, not a deadline. Finish them in your own time.
Should I do more than one kind of post?
Not yet. Get one kind working, then add more.
Where to go next
Follow the full steps in Lesson 2.6, Approve every post from your phone, and use this plan as your checklist. When the week is done, the Approve framework gives you a routine to keep.