How to Make Customer Support Videos with Synthesia

Most “AI support video” posts skip the two facts that actually decide the project. First: a help-center explainer is not a welcome, not a pitch, and not a course. It is a 45–90 second reading of the article a customer already opened — reset the password, find the shipment, start the return — with the clicks on screen. Second: the tool this site sends for that talking-head file is Synthesia (synthesia.io). This guide is the working path for Support when you will not film an agent every time a button label moves: script, host, step list, generate, shelf.

When a help article needs an avatar — and when it doesn't

Use an avatar when the same three-to-six clicks keep generating tickets and you cannot or will not sit an agent at a desk every time the reset timer, the carrier, or the return window changes. Edit the line, fix the on-screen list, generate again. That is the economic case.

Skip the avatar if the article is one screenshot or a silent GIF. Skip it if the customer needs a human on a locked account — the video closes with “reply here,” it does not replace chat. Skip it if the file is a Day-1 welcome — the HR how-to is the other desk. Skip it if the file is a buyer walkthrough — the product-demo how-to lands a trial card. Skip it if you are translating a locked English master — the localization how-to starts after this file exists.

The seven-step Synthesia support explainer

1. 01

   Write a 45–90 second script from the live help article

   A support explainer is the article, spoken. Open on the job (“reset your password,” “find the tracking number,” “start a return”), then walk the same clicks a customer will make, then close on what to do if it still fails. Copy button labels, timers, and policy lines the way they appear in the published article — 30-minute reset link, 30-day return window, carrier name. Time it out loud. Most help-center clips should sit between 45 and 90 seconds. If you wanted a Day-1 welcome, that is the HR how-to. If you wanted a buyer demo, that is the product-demo how-to.

2. 02

   Confirm a talking-head explainer is the right support format

   Use a presenter when the ticket queue needs a face walking three to six clicks and you will not film an agent every time the UI or the policy moves. Password reset, shipping track, and returns are the fit. Skip the avatar for a single screenshot, a GIF of one click, or a live chat that has to be a human. Skip it if the file is really a scored lesson — that is training. The avatar is a support host reading the current article, not a substitute for an agent on a broken account.

3. 03

   Open Synthesia (synthesia.io) — check the domain

   Synthesia is the presenter desk this page is written for. Synthesys (synthesys.io) is a different company. HeyGen and a screen-only recorder show up in the same “AI help-center video” search; they are editorial mentions here, not hops. Mixing the names is the expensive mistake. This page sends you to Synthesia only. Intercom and Zendesk are article shelves, not hops.

4. 04

   Cast one stock avatar as the support host

   Open the Avatar tab in the top menu, pick one stock presenter, and keep that face for the whole help-center library. A support read is calm, second-person, and specific: you, this email, this order. Head-and-shoulders. Do not commission an agent likeness until Support and Legal have watched a stock cut of the real article. Do not clone an agent’s voice unless you have written consent. One host. One crop.

5. 05

   Put a numbered step list on the canvas with Text

   Select Text at the top of the canvas and add a Body (or Title) block. Type the same numbered steps the avatar will say — usually four to six lines, one click each. Keep the list on the side or under a head-and-shoulders crop so it stays readable on a phone inside a help article. Do not invent a “step list” preset; this is ordinary on-screen text. If a click needs the real UI, add a screen recording from the Record control in the editor toolbar, or upload an MP4. The list and the voice have to match the live article, not last quarter’s labels.

6. 06

   Generate, then watch the article against the VO

   Use Generate at the top right. If you want captions burned into the file for a muted help-center tile, turn Burned-in captions on in that panel before you generate. Preview a scene first if you only need to check framing — Synthesia’s help says a preview does not spend credits. Then watch the export against the live article: first second, button names, timers, the on-screen list. Mouth-sync is consistently strong in English and major European languages. Hand gestures loop. These are narrators. Edit the line and generate again instead of re-booking an agent.

7. 07

   Download the MP4 or copy the embed, then drop it in the help article

   A clean download starts on a paid plan — Basic is an audition, not a help-center file. After generate, use the three-dot menu and choose Download, then the MP4. Or open Share, create a link, and copy the embed code; Synthesia’s help says an embed updates when you edit. Paste the embed into the Intercom or Zendesk-style article, or upload the MP4 if that editor wants a file. Put the clip above the written steps, not instead of them. Name the export so the next recut is obvious: help-password-reset_en_v1. When the UI or the policy moves, change that line, generate, bump the version, replace the object in the article.

Support-host avatar vs screenshots vs filming an agent

“AI customer support video” is a search, not a product. The decision is the format. Plan names and download gates on the Synthesia column match the live synthesia.io/pricing page as of August 2026. Confirm the current grid before you tell Support the export is included. Unused minutes do not roll over.

A 45–90s support script is the article, spoken

Do not write a brand film and hope Support catches up. Open the live password-reset, shipping, or returns article. Those sentences are the script. Spell the button the customer will press, the inbox the link arrives in, and the window before it expires. If a number is still in review, that clip waits. An avatar reading last year’s return window is worse than a still, because it sounds finished.

Three beats, in this order. Name the job in the first sentence. Walk the clicks. Close on the fallback — check spam, reply to the article, do not send us your password. Second person. No joke about the queue. Time it out loud: 45 seconds is a tight reset; 90 seconds is a shipping track with a carrier name. Longer than that and you are making a course.

A password-reset read that fits the window sounds like this — about a minute when you say it, not when you skim it:

If you cannot sign in, start here. On the sign-in page, choose Forgot password. Enter the email on the account — the address you used at checkout, not a work alias you never registered. We send a reset link that expires in 30 minutes. Open that email, choose the link, and set a new password with at least eight characters. Then sign in again. If the email is missing, check spam and check that you typed the same address. Still nothing? Reply on this article and we will look up the account. Do not send us your old password.

Shipping and returns use the same skeleton. Shipping: order number, where the tracking code lives, which carrier, what “out for delivery” means, who to reply to if the date slips. Returns: start the return in the account, the window in days, print or show the label, the drop-off, when the refund shows. One clip, one job. Do not stack reset, shipping, and returns in a single file.

Do not write a learning objective. Do not write a trial CTA. Do not ask the avatar to “sound warmer than the help center.” These presenters are narrators: blink cadence, micro head-tilt, a looping hand. On a head-and-shoulders framing that is enough. Full breakdown of what the avatars actually do is in our Synthesia review.

Pick one support host. Keep that face.

Open the Avatar tab in the top menu. Choose one stock presenter and keep that face for reset, shipping, and returns so the help center does not look like a new hire every week. A support host says you and this order. It is not a people partner and it is not an enablement lead.

A custom agent likeness is a later decision, not the first invoice. Prove the script on a stock presenter. Personal avatars sit on paid plans; Synthesia’s pricing grid lists a Studio Express-1 avatar as a $1,000/year add-on that can take up to ten days. Clone a voice only with written consent. The consent rule is the same one in How to clone your voice for YouTube.

The on-screen step list is Text, not a hidden preset

Customers watch these muted, on a phone, inside an article. The voice is not enough. Select Text at the top of the canvas and add a Body or Title block. Type the numbered clicks in the same words the avatar will say:

1. Open sign-in
2. Choose Forgot password
3. Enter the account email
4. Open the reset link
5. Set a new password
6. Sign in again

Four to six lines. Place the block beside or under the presenter. Drag a corner to size it; keep it readable on a narrow help-center column. We do not invent a “support template” or a “step list” control — if your workspace has a saved layout, use it; if it does not, this Text block is the whole move.

When a click is easier to show than to say, add the real UI. Synthesia’s editor toolbar includes Record for a live capture, and you can upload an MP4 if you already have the path. Crop the chrome you do not want in a public article. The list still stays on screen. A talking head over a blank canvas is a welcome; a talking head over the wrong button is a new ticket.

Captions: Synthesia’s help lists closed captions, dynamic captions (Captions in the top menu), and a Burned-in captions toggle in the Generate panel. For a muted help-center tile, turn burned-in captions on before you generate. After generate you can also download .srt or .vtt from the video menu if the help center wants a separate track.

Generate, then export into the article

Generate sits at the top right. Title the file the way the article is titled. Watch the first second and the on-screen list against the live page. Proper nouns, timers, and button labels are where these reads go wrong — fix the script, generate again. That loop is the product. An agent re-book is what you are not buying.

A logo-off download starts on Starter. After the render, open the three-dot menu and choose Download, then the MP4 (Synthesia’s help lists Full HD 1080p). Or open Share, create a link, and copy the embed code. The embed is the better shelf when you will recut the same article; the MP4 is the better shelf when the help-center editor wants a file. Interactive buttons and branching cannot go out as an MP4 — leave those off a support cut.

Paste the embed, or upload the file, into the Intercom or Zendesk-style article the ticket already links. Put the video above the written steps. Keep the written steps. A customer who cannot play video still needs the clicks. Intercom and Zendesk are ordinary article editors on this page, not hops — use whatever control that editor already has for an embed or an upload. We do not invent a “Synthesia app” inside those products.

Name the object so the next person can find it: help-password-reset_en_v1, help-shipping-track_en_v1, help-start-a-return_en_v1. When the reset window or the carrier changes, edit that line, generate, bump the version, replace the object. Leave the clips that are still true.

Which Synthesia plan ships a help-center file in 2026

The live pricing page (August 2026) lists Basic at $0 with 9 avatars and 10 minutes a month. Downloads and logo removal start on Starter at $29/month, or $18/month billed yearly. Creator is $89/month, or $64/month yearly, with more minutes and personal avatars. Languages and voices are published as 160+ on every tier. Unused minutes do not roll over. Confirm the current grid on synthesia.io/pricing before you tell Support the download is included — we do not invent a checkout total or a commission rate.

For a first support cut, start on Basic with a real article paragraph, not a placeholder sentence. Move to a paid plan when you need a logo-off file or an embed you will actually publish. Buy Creator for a personal support-host avatar or more minutes — not for “more cinema.” Buy Enterprise when IT asks for SSO or you are ready to localize a locked English master. Confirm internal-use and customer-facing terms on the plan you will export from.

Localization and other desks are next steps, not this brief

Ship the home-market help article first. A second language is a translation of a signed article, not a reason to start in Enterprise. When you are ready, lock this cut, then follow how to localize training videos — same loop, different packet. A Day-1 welcome is the HR how-to. A ramp file for new AEs is sales enablement. A landing-page walkthrough is the product demo.

Customers still deserve a plain-language note when the presenter is synthetic. Say it in the article, above or under the player: this is a support-host avatar reading the current help article. If you later publish the same file outside the help center, you also need the current platform disclosure for synthetic media. That is separate from the vendor license. You need both.

The comparison of presenter platforms — including where Synthesys sits as a different company — lives on Synthesia vs Synthesys and Best AI Avatar Video Tools 2026. This page does not hop there. The only Try button here is Synthesia.

HeyGen, a Loom, and a filmed agent — editorial only

Those names sit in the same “AI help-center video” search. HeyGen is the usual Synthesia alternative in reviewer write-ups: faster custom-avatar turnaround, punchier social presenters, less of the help-center shelf. A Loom or a native screen recorder is the right tool when you do not need a face. A filmed agent is the right tool when the face has to be that person and the file will not be recut. None of them have a live hop on this page, so there is no Try button. If you need the support explainer we can route, it is Synthesia.