What needed to be done.
The client already had a content platform. The work focused on the editor’s process: selecting materials, reviewing text, approving it and moving on to media processing.
- Improved the bot and Telegram app screens and transitions between stages.
- Fixed errors that interrupted content preparation.
- Checked source selection and text approval using test examples.
- Handed over the updated system and operating instructions.
How it works.
- Open a material
The user picks a material in the library and starts working on it.
- Review the script
The editor reads the prepared text and decides on the content.
- Confirm the next stage
After approval the material moves on to processing. The editor stays responsible for the text.
Edited text is checked again.
After a script is edited, the checks run again. Time codes must be removed from narration text before approval so the voice does not read them aloud.
Materials cannot be deleted during processing.
Deletion is blocked while a related task is running or waiting in the queue. The editor sees the reason and can return later.
Implementation and example.
Local screens with test materials: the library, script review and further processing.
The result.
Editors work with the source and script in one place, review the text and approve the next stage. The team received the updated system and instructions.
Technologies and implementation details
Telegram bot, Mini App, APIs and media processing. The work covered stage logic, the approval interface, error analysis and operating instructions. Content review stays with a person.
Let's discuss your task.
Tell me how you publish content and where the work gets stuck. We can start with text approvals, a channel bot or connecting the services you already use.
Discuss your content workflow ↗︎