Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

YouTube Marketing › Channel Strategy

Building a Customer Help Video Library

How to build a YouTube library of help videos for customers: pick questions from support data, one task per video, playlists by stage and links from help pages.
Guideintermediate12 min readUpdated

Why help videos belong on a marketing channel

The channel strategy hub uses the See-Think-Do-Care framework to decide what a channel's promise covers, and names Care content as the videos that keep existing customers getting value. The video SEO hub lists the business's own search and support logs as a source of keywords for Care-stage videos. Neither goes further, and the customer experience guides that own the help centre do not mention video at all. This guide fills that gap.

Help videos are usually made by a support team and left on a help page, or not made at all because nobody owns them. There are good reasons for a marketing channel to take them on. Customers search YouTube for how to set up and fix what they own, and a business that does not answer those searches leaves them to resellers, forums and other channels whose answers it does not control. Help videos are also read by people who have not bought yet: an installation video shows an evaluator how much work the product involves, which is a consideration question as much as a support one. And they are Evergreen Content: a pairing tutorial stays useful for as long as the product is sold, which makes it a steady part of the channel's library rather than a one-week upload.

The channel and the support function still have different jobs. The guide to support channels and self-service treats the help centre as a product with its own users, owners and backlog, and decides which channels a business should offer. A help video library sits inside that decision: it is one more way the help centre answers a question, and its videos are only as good as the help articles they belong to.

Choosing questions from support data

Start from what customers actually ask, not from what the product team thinks they should know. The best source is a contact reason list: the short set of categories every agent uses to record why a customer got in touch, which the tutorial on tagging support contacts by reason builds. A monthly count of contacts by reason shows which questions are asked most, in the customers' own words.

Not every frequent reason is a video. A question about a delivery date or a refund is answered with a fact, and a help article or a saved reply does it better. The reasons worth filming share a few properties:

Kind of questionVideo or article first?Why
A physical task with a sequence: fitting, wiring, assemblingVideo first, with a written articleSeeing the hands, parts and order removes most of the ambiguity
A setting or screen in an app or deviceEither; a short video when the path is longScreens change often, so the article is easier to keep current
A fault with a visible symptomVideo for diagnosis, article for the fix listThe customer can compare what they see with what the video shows
A policy, price or delivery questionArticle or saved replyNothing to show, and the facts change
A question asked before buyingVideo when it shows effort or fitThe same video serves evaluators and new customers
A rare edge caseArticleA video costs too much for the few customers who need it

Then check the words. The reason list records how customers describe the problem, and the help centre and documentation SEO guide shows how to write for the question as customers phrase it. Help searches are usually specific and long, the territory of the Long-Tail Keyword, and their Search Intent is plain: the viewer wants to finish a task. A short list of questions, ranked by how often they are asked and whether a video would answer them better than text, is the first production plan.

A single task per video

A help video answers a single question. "Installing and setting up your device" is several tasks bundled together; "Connecting the device to existing wiring" is a single task. The jobs-to-be-done framework is a useful lens here: name the job the customer is trying to finish at that moment, and make the video end when the job is done.

Single-task videos are easier to find, because the title can match the exact question; easier to watch, because nobody has to scrub through steps they do not need; and easier to keep current, because a change to one part of the product means replacing one video rather than re-cutting a long one. Long overview videos still have a place, as the head of a playlist or for customers who want the whole picture, but they should link to the single-task videos rather than replace them.

A video brief keeps each help video to its task: the question it answers, the customer it is for, the product version it shows, what the viewer must have ready, and the next video or article to send them to.

Structure, chapters and captions

A help video opens with the result: what the viewer will have done by the end, and what they need before they start. Then the steps, in order, at a pace the viewer can follow with the product in front of them, and a close that confirms how to tell the task worked and what to do if it did not. Branded introductions and long greetings cost a viewer who is standing at a half-fitted device more than they cost anyone else.

Chapters suit help videos well. YouTube's help page on chapters, which the titles, descriptions and chapters guide summarises, documents that manual chapters come from a list of timestamps in the description and must meet documented requirements on where the list starts, how many entries it has, their order and each chapter's length; a list that breaks them produces no chapters. Label each chapter with the step as the customer would describe it, so a viewer who only needs the last step can jump to it. The same guide notes that Google can show key moments drawn from chapters, without promising when.

Captions are part of the job, not a finishing touch. The Web Content Accessibility Guidelines, as the site's accessibility guides state them, expect video with sound to have captions and information shown visually to have a text alternative. For a help video, that means reviewed captions, since automatic ones often get model numbers, product names and settings wrong, and it means saying aloud or writing in the description anything shown only on screen, such as which wire goes to which terminal. The guide to AI for alt text, captions and transcripts covers the review a caption file needs. A transcript or a written article beside the video also helps the customer who cannot watch at all.

Organising the library with playlists

Help videos need an order a customer can follow. Playlists provide it: YouTube documents playlists as a feature, and the channel strategy hub notes that a playlist is also a traffic source in its own right. Group help videos by stage of ownership rather than by product team or by the date they were made.

A common arrangement follows the customer's path: before buying (what is in the box, will it fit, what fitting involves), getting started (installation and first setup), everyday use (the features customers ask about most), fixing problems (faults by symptom), and changes (moving, replacing parts, upgrading). The guide to onboarding customers for services and products draws the path from purchase to first value, and the getting-started playlist should follow that path step by step.

Where the library grows into named, regular episodes, it starts to look like a series, and the tutorial on planning a YouTube video series applies: a name, a consistent thumbnail style and a playlist a viewer can follow from episode to episode. Keep help playlists separate from the channel's other formats on the channel page, so a customer looking for a fix finds the fixes, and so the channel's other viewers are not shown a wall of support videos.

Linking videos from help pages and the product

A help video that customers cannot find at the moment they need it does little. Link or embed each video on the help article that answers the same question, so the article and the video support each other; the article holds the text a customer can scan and copy, the video shows the movement. Link the article from the video's description in turn, in the first lines, so a viewer who arrives from YouTube search can get the written steps.

Then place links where the question arises. The help centre SEO guide sets out how help content should be linked from the main site, within the help centre and from the product, and the same routes suit video: a link from the setup screen in an app to the setup video, a printed code or short address in the box that leads to the getting-started playlist, and a link in the post-purchase emails that the onboarding guide plans. Support agents can use the videos in replies, linked rather than described.

The guide to reducing customer effort explains why this matters: every time a customer has to switch channel to find an answer, the business has moved work onto them. A video linked from the screen where the customer is stuck removes a step; a video they have to search for adds one.

Keeping help videos current

An out-of-date help video is worse than none, for the same reason the support channels guide gives for articles: it creates contacts and damages trust. Video is harder to correct than text, so plan for change from the start.

  • Give each video an owner and a review date, recorded alongside the help article it belongs to, and link both to the release process so a product change triggers a review of the videos that show it.
  • Record the product version in the brief and in the description, so it is clear which videos a change affects.
  • Correct before replacing. When a step changes, add a correction near the top of the description and pin a comment, then plan a replacement video if the change is large.
  • Retire carefully. Before taking a help video down, move every link, playlist entry and help-page embed that points to it to the replacement.

The tutorial on auditing a YouTube video library covers the regular pass over a channel's back catalogue, and help videos belong in it, marked with their own job.

Reading what the library does

Help videos are easy to count and hard to credit. Views show that customers found the video; they do not show that the customer finished the task or that a contact was avoided. Read the library on several measures together, and set the channel's KPI for help content on what it can show.

The core reading puts two records side by side. Each month, take the contacts for each reason that has a video, from the reason list, and the views of the video that answers it, from YouTube Analytics. Note every other change made to that reason in the same period: a product fix, a rewritten article, a new reply. If contacts for a reason fall while views of its video rise and nothing else changed, the video is a likely contributor; if contacts hold steady while views climb, either the video is not answering the question or it is reaching people who would not have contacted support anyway. Neither reading is proof of prevention, and neither should be reported as a saving.

Other signals help. The retention curve shows whether viewers reach the step that solves the problem or leave before it. Traffic sources show whether viewers arrive from YouTube search, from the help article or from links in the product. Comments carry the follow-up questions the video did not answer, which are the next videos to make. The YouTube Analytics section covers where each report sits. Where a help video is also found by people who have not bought, its views from search are a consideration signal, read on the terms the Shorts versus long-form comparison gives long-form: a video that keeps being found for as long as the question exists.

A thermostat maker builds its help library (illustrative)

Illustrative example — not a real result

Yembrodix Heating films its most asked questions

Yembrodix Heating, an invented smart-thermostat maker, starts tagging support contacts by reason and after three months has a monthly picture of about 2,600 contacts. Five reasons account for 1,150 of them: wiring to the boiler (410), pairing with the app (290), the display showing no power (190), setting a schedule (150) and moving the thermostat to a new home (110). The team films eight single-task videos for the first three reasons, each with chapters per step, reviewed captions and the model and app version in the description, and two for scheduling. It groups them into playlists for getting started, everyday use and fixing problems, embeds each on the matching help article and adds a link from the app's pairing screen to the pairing video. Over the next three months the wiring videos are viewed 6,800 times, a third of the views coming from the help article and a quarter from YouTube search. Wiring contacts fall from 410 to 300 a month and pairing contacts from 290 to 260, while display contacts stay at about 190 even though that video is viewed 2,100 times. The team records that a firmware fix for pairing shipped in the same period, so it reads the wiring change as a likely effect of the videos and the pairing change as unclear. The comments on the display video show that most viewers have a different fault from the one it covers, which becomes the next video in the plan.

The figures belong to the example. What transfers is the method: questions chosen from tagged contacts, a single task per video, videos linked from the article and the screen where the question arises, and contacts by reason read beside views of the matching video with every other change noted, rather than a claimed saving.

Common mistakes

  • Filming what the product team wants to show. A tour of features nobody asked about fills the playlist and answers no contact. Start from the reason list.
  • Several tasks in one video. A long setup video makes the customer scrub for their step and is hard to update. Make one video per task and link them.
  • Raw automatic captions. Model numbers, settings and product names are where automatic captions fail, and they are what a customer needs. Review every caption file.
  • Videos with no home on the help centre. A help video that is not linked from the matching article or the product screen relies on customers searching YouTube for it.
  • No owner or review date. Product changes make help videos wrong quietly. Tie each video to the release process.
  • Mixing help into the channel's main shelf. Support videos crowd out the channel's other formats; give them their own playlists and sections.
  • Claiming deflection from views. Views do not show a contact was avoided. Read contacts by reason beside views, note other changes, and report a likely contribution rather than a saving.
  • Deleting old videos before moving their links. Every embed, playlist entry and printed link pointing at a removed video becomes a dead end at the moment a customer needs help.

Frequently asked questions

Should customer help videos go on the main YouTube channel or a separate one?

For most businesses the main channel is the better home, because help videos are often found by people searching before they buy as well as by existing customers, and they add to the library the channel already has. Organise them into their own playlists so they do not crowd the channel's other formats. A separate channel can make sense when the help library is very large or serves a product line with a different audience, but it starts with no subscribers and splits the effort of keeping both current.

Do help videos reduce support contacts?

They can help, but a channel cannot prove it from view counts. Contacts for a reason can fall for many other causes at the same time, such as a product fix, a clearer help article or a quieter season. Read contacts for each reason alongside views of the video that answers it, note every other change made in the same period, and treat a fall that coincides with the video as a sign worth following rather than a measured saving.

Do help videos need captions?

Yes. The Web Content Accessibility Guidelines, as the site's accessibility guides summarise them, expect video with sound to carry captions and information shown only visually to have a text alternative. For a help video that means reviewed captions rather than raw automatic ones, and on-screen settings, model numbers and button labels also said aloud or written in the description, so a customer who cannot see or hear part of the video can still complete the task.

Terms used on this page

Frameworks

Also related

Sources

  1. YouTube Help — YouTube Help
  2. Add video chapters and key moments — YouTube Help
  3. Web Content Accessibility Guidelines (WCAG) — W3C

Related