How to Add Videos to Your Help Center (and Keep Them Up to Date)
Your help center has the answer. The customer opened the article, read “go to Settings, then Team, then Roles”, could not find Roles, and opened a ticket anyway. Written steps are easy to misread, and screenshots go stale after the first redesign. A short video at the top of the article shows the exact clicks on the real screen, in under a minute. This guide shows which articles need a video first, where to put it in the page, how to make it without recording your screen, and how to keep every video current after each release.
Why add videos to help articles
Most people who open a help article are stuck in the middle of a task. They want to see where to click, not read a paragraph about it. A video shows the exact button, the exact menu and the result, and it works for the people who skip text. The written steps still matter, so the best article has both.
| Article style | What the customer gets | Weak point |
|---|---|---|
| Text only | Steps to read and follow | Easy to misread, hard to find the right button |
| Text + screenshots | Still pictures of each screen | Pictures go out of date after a redesign |
| Text + 💬 short video | The steps shown working, with a voice and subtitles, in 30–60 s | Needs updating when the screens change (see below) |
Which articles need a video first
You do not need a video on every page on day one. Start where a video saves the most tickets:
- Your most-viewed articles. Your help center tool shows which pages people open most. The top ten are usually a good first batch.
- Articles that still lead to tickets. If customers read the article and then ask the same question, the words are not enough.
- Tasks with several steps across one or two screens: inviting a teammate, setting up a payment, exporting a report.
- Settings that are hard to find, buried in a menu or behind a tab.
Skip the video where text is faster: one-line answers, prices, policies and legal pages.
Where to put the video in the article
- At the top, right under the title and a one-sentence summary, so the fastest answer comes first.
- The written steps under it, for people who prefer to read, search or copy.
- One question per video. If an article answers three questions, it probably should be three articles.
- Subtitles on. Many people watch help videos at work with the sound off.
- The same words in the video and the text. If the article says “Roles”, the video should say “Roles” too.
How to make a help center video with DashCast
Recording, editing, voicing and subtitling even a one-minute clip takes time, and a help center needs dozens of them. With DashCast there is no recording:
- Start a new video and choose the type 💬 Support answer. It is made for exactly this: 30 to 60 seconds, two to four scenes, and a simple structure: restate the question, show the exact steps, confirm the result. No intro and no tour of other features. For a longer task, choose 🎓 Tutorial instead.
- Choose ✨ Write it for me automatically: paste your app link, a test login and the question your article answers, for example “How do I give a teammate the Editor role?”
- Pick the language and the screen: Desktop, or Mobile if most of your customers use your app on a phone.
- The AI opens your app, writes each scene with its sentence, zoom and highlight, and checks every click on your real screens. Change anything you like in the Scene Designer.
- Press Render. You get an MP4 with a natural voice and a subtitles file.
Want to see a real render first? Try it live on the home page, with no account.
A whole help center at once
Have twenty articles that need a video? Choose Lesson series with the 💬 Support answer type and list the questions. Each lesson answers one question, with no shared intro, so every video fits its own article. You check and render them one by one, but you write the brief only once.
Putting the video into your help center
- Upload the file. Use ⬇ Video and ⬇ Subtitles, then add both to the article in your help center tool, or to the video host it uses.
- No caption support? In Customize settings, tick Burn subtitles into the video when you create it, so the subtitles are part of the picture.
- Or link to it. Publish the video to your DashCast video page, which shows it with a step-by-step transcript, and link to that page from the article.
- In your customers' languages. Open Other versions of this video to make a copy in another of the 14 narration languages, for the same article in another language.
Keeping help videos up to date
This is where most help center videos fail. A button moves, a menu is renamed, and the video starts showing a screen that no longer exists. Customers follow it, get lost and open a ticket. Re-recording dozens of videos after every release is not realistic, so the old ones stay up.
A DashCast video is a written scenario, not a recording, so it can be checked. After each release, press “🔍 Check selectors” on a video: it lists every step that no longer finds its button or field on your live app. Fix those steps, render again, and replace the file in the article. Videos that still pass need nothing. More in updating video docs without re-recording.
A simple habit helps: keep a list of which article uses which video, and go through it on release day.
Tips for better help center videos
- Start with the question. The first sentence repeats what the customer asked, so they know they are in the right place.
- Use a test account with real-looking data. An empty list shows nothing. Blur anything private that still shows.
- Your app must be reachable from the internet. DashCast opens it with a username and password, so use an account without a code sent to a phone.
- End on the result. Once the change is visible on screen, the video is done.
- Link to the next step. Under the video, link the article that usually comes next.
What it costs. A free account includes 10 minutes of video with no credit card, enough for about ten help center answers. After that, video minutes start at $5 for 100 minutes, or plans from $9 a month. A failed render is never charged.
Answering the same questions in support tickets? Read how-to videos for support tickets.
Frequently asked questions
Should a video replace the text of a help article?
No. Keep the written steps: search engines and your help center search read them, and many people skim or copy them. Put the video at the top as the fastest way to the answer, and the text under it.
How long should a help center video be?
Between 30 and 60 seconds for one question: say the question, show the exact steps, show the result. For a longer task, use a Tutorial video of a few minutes, or split it into several short ones.
Do I need to record my screen?
No. In DashCast you choose the 💬 Support answer type, give your app link, a test login and the article's question. The AI writes the scenes, and DashCast plays them in a real browser and adds the voice and subtitles.
How do I keep the videos current when the app changes?
After a release, press “🔍 Check selectors” on each video. It lists every step that no longer finds its button or field. Fix those steps, render again and replace the file in the article.
Your help center, with a video on every answer.
Sign up free and get 10 minutes of video with no credit card. Choose 💬 Support answer, paste your app link and the question your article answers.