How-to

How to build a video knowledge base for customer support

By Omprakash Sah Kanu · August 2, 2026 · 9 min read

To build a video knowledge base, take the questions your support team answers repeatedly, record the answer on screen once, and turn each recording into a narrated video with a written guide beside it. With ScreenDub the narration writes and voices itself from the recording, so producing the answer costs minutes, not an afternoon with an editor. This guide covers which tickets deserve a video, the production workflow, how to keep the library consistent as it grows, and how to keep it true when your product changes.

Answer once, deflect forever

Every support queue has a top ten: the same how-to questions, asked by different customers, answered by hand every time. Each answer is written well once and then retyped forever. A video knowledge base inverts that. The best agent's answer gets recorded once, at its best, and every future ticket gets that answer as a link. The customer sees the fix performed in the real product, which closes the gap between "I read the steps" and "I found the button."

The economics are blunt. If a question arrives five times a week and costs ten minutes to answer well, that is over 40 hours a year for one question. The video that retires it takes minutes to make and works nights and weekends.

Which tickets deserve a video

Repeat how-tos. "How do I connect X", "where do I change Y". The core of the library. If it has been asked three times, record it.
Anything hard to describe in words. Multi-screen flows and settings buried three menus deep, where prose answers generate follow-up tickets.
Setup and onboarding. The first-week questions every new customer asks in the same order.
Not one-off bugs or account-specific issues. Those need a human. The video library exists so your agents have time for them.

The production workflow

Pull the list. Sort your help desk by ticket volume and take the top ten how-to questions. Volume decides production order; nothing else does.
Record the answer. Open the product and perform the fix on screen, in a demo account, silently and at a natural pace. Recording runs in the browser. Blur anything customer-like on the review step before it uploads.
Let the narration write itself. ScreenDub turns the recording into steps and drafts a line for each. Use the Support Answer script style: it writes the narration as a warm, direct reply to one person's question, which is exactly what a deflection video is.
Edit for the searcher. Say the feature's exact name early, since that is what the customer typed into your help center search. Cut any line that narrates the obvious and keep the ones that prevent the follow-up ticket.
Export and publish. Render the MP4 with captions and drop it into your help center article, LMS, or macro. It is a standard file, so it plays wherever your knowledge base already lives, and the step-by-step PDF from the same recording gives the article its written body with screenshots included.

Consistency is what makes it a library

A knowledge base recorded by whoever had time sounds like ten different companies. Three choices keep it coherent as it grows past a handful of videos.

One voice. Pick a single AI voice for the whole library and save it as your default. Every answer sounds like the same calm expert, whichever agent produced it, and nobody's throat or schedule is a bottleneck.
One look. Save your logo and brand color once and every video wears them: title card, chapter titles, accents. A customer pausing mid-video should still know whose help center they are in.
One shape per surface. Widescreen for the help center, vertical or square if answers also go to social. The same recording exports to any of them.

Captions and languages are not optional here

Support content gets watched at work, often muted, often by people troubleshooting under pressure in their second language. Turn captions on: they are timed to the audio word by word, and you can burn them in or ship a subtitle file alongside for players that toggle them. When a market grows, translate the answer instead of re-recording it, and the narration, titles, and captions all move to the new language from the same project. See how captions work.

Keeping the library true

A wrong video is worse than no video, because the customer trusts it. Treat freshness as part of the workflow, not a someday project.

When a release changes a flow, search the dashboard for the affected feature and re-record that one answer. One question per video keeps this cheap.
When only the wording is stale, edit the line and re-narrate that segment. The rest of the video does not change.
Watch the tickets. A deflection video that stops deflecting is your monitoring: the flow probably changed.

Ship the top three answers first and put the links in your agents' reply macros the same day. Deflection starts with the next ticket, not after the library is "done."

At a glance

Per video: One question, usually 1 to 4 minutes
Script style: Support Answer, written as a direct reply
Captions: Word-accurate, burned in or as a subtitle file
Languages: 80+ from the same recording
Publishing: Standard MP4 + PDF, works in any help center
Cost to start: Free plan, 10 minutes of narration a month

Mistakes that sink support video libraries

Producing by enthusiasm instead of ticket volume. The fun feature gets a video; the question that arrives daily does not. Let the queue set the roadmap.
One video that answers six questions. Nobody scrubs. Six short videos get linked; one long one gets skipped.
Recording with a live voice on a deadline. Take four sounds tired, and the library ends up frozen because re-recording narration is a chore. Generated narration keeps production and updates cheap.
Publishing the video without the written steps. Some customers will not press play. The PDF from the same recording covers them, screenshots included.

Common questions

What is a video knowledge base?

A help center where the recurring how-to questions are answered with short narrated screen recordings, each paired with written steps. Customers watch the fix performed in the real product instead of interpreting prose, and support agents answer repeat tickets with a link instead of retyping.

How many videos do we need to start?

Three. Take the three highest-volume how-to tickets, record those answers, and put the links in your reply macros. Grow the library from ticket data, not from a content calendar.

How long should a support video be?

One question, one to four minutes. If it runs longer, it is answering more than one question and should be split so each answer can be linked precisely.

Where do the videos live?

Wherever your knowledge base already is. The export is a standard MP4 with captions, so it embeds in help center platforms, LMSes, and internal wikis without anything special, and the PDF gives the article its written version.

What happens when the product UI changes?

Re-record the affected answer, which is one short video if each video covers one question. If only the wording changed, edit that line and re-narrate the segment without touching the rest.

Start with your top ticket

Open your help desk, sort by volume, and record the answer to the question at the top. Ship it today and let the next occurrence of that ticket be a link. Start free, or see the full tutorial-video workflow for the recording craft behind it.