Convert any file, nothing uploaded
All articles
Scripts, prompts and styles/

50 AI Video Prompts for Training and Explainers

10 min read

✦ Summary

Fifty copy-ready AI video prompts for training teams, in five groups, with the four parts that make a prompt work and when to use a document instead.

AI video prompts for training that give you a usable first draft

These are 50 AI video prompts for training and explainer videos, grouped into compliance, onboarding, product training, customer education and soft skills. Copy one, replace the words in [brackets] with your own, and paste it into the composer. Each prompt names who the video is for, the one thing they should do afterwards, the points in order, and a tone.

That structure is the whole trick. A vague prompt gets a vague video. A prompt with an audience and three ordered points gets a scene plan you can approve with a few edits.

The four parts of a prompt that works

Audience. Say who is watching: "for new warehouse staff", "for people managers", "for customers moving from [old tool]". The narration's vocabulary follows from this.

One outcome. What should they do after watching? Report a breach, book time off, calibrate a sensor. One video, one outcome. Two outcomes means two videos.

Three to five points, in order. Interlace plans scenes from your points, so list them in the order you want them shown. With fewer than three, there is little to show. With more than five, each point gets only a few seconds, so split the topic into two videos.

Tone. One or two words is enough: "calm and direct", "warm, informal", "factual, no marketing".

Prompt 2 split into four parts: Audience, for all staff; One outcome, report a data breach; Points in order, what counts, who to tell, what not to do; Tone, calm and direct
Prompt 2 from this pack, split into its four parts.

What to leave out: the length, the shape and the look. Those have their own buttons under the prompt (style, voice, language, length, 16:9 or 9:16), so writing "a 60-second whiteboard video" in the prompt only adds noise. Keep Review script switched on so you read the scene plan before anything is drawn.

Here is the difference in practice:

  • Weak. "Make a video about phishing."
  • Strong. "Three signs an email is phishing: check the sender, hover before you click, and slow down when it sounds urgent."

The strong version is short, but it gives the planner three scenes and their order.

A real render of a prompt from this pack

We ran that phishing prompt, exactly as printed as prompt 1 below, in the Paper Collage style.

The phishing prompt typed into the composer, with Prompt mode selected
Prompt 1, typed into the composer

Interlace planned three scenes, one per sign: "Check the Sender", "Hover Before Clicking" and "Pause at Urgency".

Three Paper Collage scenes: Check the Sender with an unfamiliar domain, Hover Before Clicking with a cursor over a link, and Pause at Urgency with a phone showing a verify check
Made with Interlace: the three scenes it drew for prompt 1.
The finished video in the editor, first scene titled Check the Sender, with three scenes listed
The result: one scene per point, in the order the prompt gave

Compliance and policy prompts

Compliance videos have to be accurate. Use these for awareness and refreshers. When the exact wording of a rule matters, read the section on documents at the end.

  1. Three signs an email is phishing: check the sender, hover before you click, and slow down when it sounds urgent.
  2. For all staff: how to report a data breach at [Company]. Cover what counts as a breach, who to tell in the first hour, and what not to do (don't delete anything, don't try to fix it yourself). Calm, direct tone.
  3. Explain our gifts and hospitality rule to sales and procurement staff: the [amount] limit, when you must declare a gift, and two examples, one allowed and one not. Neutral, factual.
  4. For people managers: what to do in the first 24 hours after an employee reports harassment. Listen and write it down, don't investigate yourself, contact HR the same day, and keep it confidential. Serious, supportive tone.
  5. Clean desk and clear screen in a shared office: lock your screen when you stand up, leave no printed customer data out, and what the evening check looks for. Short and friendly.
  6. Explain conflicts of interest to new employees with three everyday examples: a relative applying to your team, a side business with a supplier, and shares in a competitor. End with how to declare one.
  7. Anti-bribery basics for staff who deal with government officials in [country]: what a facilitation payment is, why we never make one, and what to say if someone asks. Firm, plain language.
  8. Password and MFA rules for everyone: use the password manager, never reuse a work password, and only approve MFA prompts you started. End with what to do if you approved one by mistake.
  9. For warehouse staff: our speak-up policy. Anyone can report a safety or ethics concern, reports can be anonymous, and retaliation is a firing offense. Show the three ways to report.
  10. What data protection means for our support team day to day: ask only for the data you need, verify identity before sharing account details, and send deletion requests to [team]. Practical, no legal jargon.

Onboarding prompts

Use one style and one voice for a whole onboarding set, so it feels like one program. Prompt mode suits the welcome and the "how we work" videos; policies are better from the handbook itself.

  1. Welcome video for new hires at [Company]: what we make, who we make it for, and the three things people wish they had known in their first week. Warm, informal.
  2. Your first day at [site]: where to park, where to collect your badge, who meets you at reception, and what your first morning looks like. Friendly and specific.
  3. How we work across time zones: default to written updates, share decisions in [channel], keep core hours of [hours], and don't expect replies outside them. Relaxed tone.
  4. For new managers, the first 30 days: meet each report one to one, learn the team's priorities before changing anything, and book a check-in with your own manager at day 30.
  5. How to submit expenses: what you can claim, photograph the receipt the same day, submit in [tool] within [number] days, and what happens if it is late. Plain, step by step.
  6. How to book time off at [Company]: the request in [tool], how much notice to give, and how to set an out-of-office that says who covers for you.
  7. Our values, each with one real behavior: [value 1], [value 2], [value 3]. For each, show what it looks like on a normal Tuesday, not on a poster.
  8. For new engineers, how code reaches production here: branch, pull request with one reviewer, automated tests, deploy on merge. Say who to ask when a deploy fails.
  9. IT setup on day one: sign in to your laptop, set up MFA, install [tools], and join [channels]. End with how to get help from IT. One step per scene.
  10. Meet the departments: one scene each for [Sales], [Support], [Product] and [Finance], saying what the team does and when a new hire will need them.

Product training prompts

For internal product training, Images under the prompt lets you add your own pictures, such as screenshots of the real screen, and the planner can place them in scenes.

  1. For our support team: what changed in [feature] in the [month] release. What it does now, the two questions customers will ask, and how to answer them.
  2. Train new sales reps on [product] in three points: the problem it solves, who buys it, and the one feature that wins most deals. Confident, not salesy.
  3. How to process a return in [system], for store staff: find the order, choose the reason, issue a refund or exchange, and print the label. One step per scene.
  4. Explain the difference between our [Standard] and [Pro] editions to front-line staff: who each is for, the three features that differ, and how to recommend one.
  5. For field technicians: how to calibrate the [model] sensor. The safety check first, then power down, attach the reference tool, run calibration from the menu, and record the reading.
  6. Walk account managers through the monthly usage report: where each number comes from, which one predicts churn, and when to call the customer.
  7. For new partners, how our quote builder works: the three inputs, how discounts apply, and the common mistake that underquotes a deal.
  8. For operations staff: how to handle a failed payment alert in [tool]. Check the reason code, retry once, contact the customer if it fails again, and log it.
  9. Train support agents on our ticket priorities: what counts as P1, P2 and P3, the response time for each, and when to escalate to engineering.
  10. For new analysts, how our data gets from [source] to the dashboard: collection, cleaning, the nightly job, and where to look when a number seems wrong.

Customer education prompts

Customer videos get watched once, at the moment of need. Keep each to one task and name the task in the first line.

  1. Getting started with [product] in three steps: create your workspace, invite your team, and set up your first [project]. Encouraging tone, for brand-new customers.
  2. How to export your data from [product]: where the export button is, which format to pick for a spreadsheet, and where the file arrives.
  3. For customers moving from [old tool]: what maps to what in [product], the one thing that works differently, and how to import your existing data.
  4. Fix the most common error in [product], "[error message]": what causes it, the two-minute fix, and when to contact support instead.
  5. Our security model for customer IT admins: where data is stored, who at [Company] can access it, how it is encrypted, and how to request our security documents. Factual, no marketing.
  6. How to connect [integration] to [product]: link the account, choose what syncs, and check that the first sync worked.
  7. For existing customers, [feature] is now available: what it does, who it helps most, and where to find it.
  8. For patients of [clinic]: how to book, move or cancel an appointment online, and what to bring to a first visit. Warm, simple language.
  9. How billing works for new customers of [product]: when you are charged, how to update your card, and where to download invoices.
  10. How to reset your [device]: find the reset button, hold it for [number] seconds, wait for the light to turn [color], and reconnect the app.

Soft skills prompts

Soft skills land best as a contrast. Asking for one good example and one poor one, as in prompt 41, gives the planner a scene to show each.

  1. How to give feedback that lands, for new team leads: describe the specific behavior, explain its impact, and agree on the next step. Show one good example and one vague one.
  2. A one-to-one that isn't a status update: let the report set the agenda, ask one open question about how things are going, and end with one action each.
  3. De-escalating an angry customer on the phone: let them finish, repeat the problem in your own words, say what you can do now, and give a time for the follow-up.
  4. How to write an email people act on: the ask in the first line, one topic per email, a clear deadline, and a subject line that says what is needed.
  5. Run a meeting in 25 minutes: put the goal in the invite, start with the decision needed, capture actions with owners, and finish five minutes early.
  6. Active listening for customer-facing staff: don't interrupt, repeat back what you heard, and ask one clarifying question before offering a fix.
  7. Handling a disagreement with a colleague: talk in private, start from the goal you share, separate the problem from the person, and agree what happens if you still disagree.
  8. Presenting to executives: lead with the recommendation, give three reasons, show the one number that matters, and keep the detail ready but out of the opening.
  9. Delegating as a new manager: pick the task, explain the outcome rather than the method, agree on check-in points, and resist taking it back.
  10. Hybrid meetings that include everyone: remote people speak first, questions go in the chat, materials go out before the call, and note-taking rotates.

When to switch from a prompt to a document

A prompt is right when the content lives in your head. When it already lives in a file, use the file. Switch the composer from Prompt to Document and upload the PDF, Word file or deck when:

  • The wording is fixed. A policy clause, a safety instruction, a regulated disclosure. From a prompt, Interlace writes its own words.
  • The numbers are yours. Limits, thresholds, dates and part numbers belong in a source, not in a prompt you retype.
  • The content is long. A 20-page procedure will not fit in a sentence, and cutting it down by hand loses steps.

In Document mode you choose how closely the video follows the file. Source of truth keeps the script close to your document. Reference & context lets your prompt drive the video while the document supplies the facts; the prompt box then asks for your angle. The AI explainer video maker page shows both routes, and if you want a full script before you open Interlace, the free training video script generator writes one from a topic.

Whichever you use, the look matters as much as the words. How to choose a visual style for a training video matches each of the 18 styles to the kind of content it suits.

Start with one prompt you would actually use

Pick the prompt closest to a video someone has asked you for this month, fill in the brackets, and read the scene plan it produces before you change a word. That first plan tells you more about writing prompts than any list. Join Interlace and try it on your own prompt.