Some documentation is better watched than read. A setup guide with eight steps and three screenshots is a fine article — and a better ninety-second video. The problem has never been whether to make the video. It is noticing which article deserves one, and then finding an afternoon to produce it.
Reel is the seventh AI Writer you can hire in FinalDoc, and that is its entire job.
What Reel actually does
Reel runs on a schedule — weekly by default — and asks a narrow question: which of your most-read articles would readers rather watch, and does not already have a video?
It looks at your published articles ordered by real view counts, skips any article already covered by a video render, and keeps the ones that are genuinely instructional — a title that reads like a how-to, a guide, a tutorial, onboarding, a walkthrough, setup or configuration, with enough substance to narrate. Thin articles are filtered out, because a 90-word page makes a bad video.
Then it proposes. Up to three candidates land in your writer's activity feed with the reasoning attached: this is your most-read guide without a video.
Nothing renders until you approve
This is the part we care most about. Reel does not film anything on its own.
Each proposal sits in the feed as a card you can approve or ignore. Approving is what starts the work: FinalDoc checks your render queue has room, charges the render, creates the Video Studio job, and hands it to the video worker. The proposal then links to the job so you can watch it progress from the same card.
If the render fails, the credits are returned. If your queue is already full, Reel tells you to wait rather than silently dropping the request. And if none of your top articles need a video this week, it says exactly that — your top how-to articles are covered or too short — instead of inventing work to look busy.
What comes out
A narrated walkthrough in 16:9, using the article's own structure for pacing and on-screen steps, produced through Video Studio — the same pipeline you would use by hand, with the same voices. The video attaches to the article it came from, so readers get the choice of reading or watching without you maintaining two things in two places.
A real example
On our own knowledge base, Reel looked at the published articles, found that Create and manage articles was the most-read guide with no video attached, and proposed it. We approved the card. Video Studio rendered a classic-length walkthrough, and it completed.
That is the whole loop: notice, propose, approve, render. The only human step is the one that should be human — deciding it is worth making.
How Reel fits with the other writers
FinalDoc's AI Writers are hired teammates rather than buttons. Scribe drafts, Atlas organises, Beacon handles search, Pulse turns support signal into articles, Herald writes release notes, Forge documents APIs. Reel is the one that works in video.
Like the others, it runs on a cadence you choose and in the autonomy mode you choose — Suggest, where everything waits for your approval, or Draft, where it prepares work for you to review. For video we recommend leaving it on approval regardless of mode: a render costs credits and takes minutes, and "which article deserves a video" is a judgement call worth keeping.
Hiring Reel
Open AI Writers, hire Reel, and give it the Suggest videos from top articles task on a weekly cadence. You will see its first proposals after the next run — or nothing at all, if your best guides already have videos, which is a perfectly good answer too.