Brett LindenbergVideo for ecommerce usually means product video for shoppers. This guide covers the other use: training the people who answer tickets, explain products, and pack orders. A practical format for ecommerce training is a short scenario built from a real ticket. The video stops at the decision your team gets wrong, the employee picks a response, and the next scene shows what that response does for the customer. Hotspots on a product close-up do the same job for product knowledge. If you want shoppers to click products inside your videos, our guide to video hotspots for ecommerce covers that. The 33-second demo below is a support scenario: a customer reports a cracked mug, and you choose what the agent does next.
What to train with video in an ecommerce business
Start where a wrong answer costs you money or a customer: refunds, replacements, late orders, product questions, and packing. Then pick the format that matches the mistake.
| Team and task | Common mistake | Video format | What the report shows |
|---|---|---|---|
| Support: damaged or wrong items | Asking for a return the policy does not require, or denying a claim the photo supports | Branching scenario from a real ticket | Each agent's choice, and how many agents chose each response |
| Support: late orders | Promising a new date without offering to cancel | Scenario that ends in a question about the rule | Each agent's answer and score |
| Pre-sale chat: product questions | Guessing about fit, compatibility, or care | Product close-up with a hotspot on each part | Which parts each person opened, and their answer to a follow-up question |
| Fulfillment: picking and packing | Skipping a check when the line is busy | Short video filmed at the station, with a question at each check | Answers per person, and where people stopped watching |
| New and seasonal hires | Missing a policy in the first week | Ordered playlist of short videos | Completion across the playlist |
How to build a support scenario from your own tickets
The demo above uses one ticket type and one decision. Build yours the same way.
1. Choose the ticket type
Export recent tickets from your help desk and sort them by tag. Pick the type that leads to the most refunds, escalations, or reopened tickets. Common starting points are where-is-my-order tickets, damaged items, and returns outside the window.
2. Find the decision agents disagree on
Read a sample of tickets of that type and mark where agents answered differently. In a damaged-order ticket, the split is often whether to ask for the item back. That decision is where your video stops.
3. Write the right response and the wrong ones agents really give
Take the wrong answers from real tickets, word for word where you can. Answers you invent tend to be easy to rule out, and the scenario stops testing anything. For each response, write a short result scene: what the customer says next, which policy applies, and what the agent should do.
4. Record the scenes
A phone and a quiet room are enough for internal training, and a screen recording covers the steps in your help desk. You can also reuse video you already have. Mindstamp adds interactions on top of an uploaded file or a video linked from a host such as Vimeo or Wistia (see supported video sources).
5. Add the choice in Mindstamp
Add one button for each response at the decision point. Set each button's click action to Change time, so it jumps to that response's result scene. For longer results, Switch video sends the learner to a separate video, and the branching map shows every route. In each button's Timing settings, set Pause to At show time and Pause length to Until interaction, so the video waits at the decision until the learner clicks. At the end of each result scene, add a Change time interaction that jumps to a shared recap, as the demo does.
6. Test it as a learner, then assign it
Open the share link in a private browser window and take every route. Signed-in owners keep full player controls and their required clicks reset, so a private window shows what an agent sees. To stop people from dragging past the decision, turn off seeking and turn on Prevent passing required interactions (Core plan and higher; see how to stop learners from skipping ahead).
Check the scenario against the law
A scenario teaches whatever rule is in the script, so have the person who owns your policies review it. Two rules that touch everyday ecommerce tickets are set by law:
- Late orders in the US. Under the FTC's Mail, Internet, or Telephone Order Merchandise Rule, a seller must ship within the time it advertised, or within 30 days of a completed order if it gave no time. When it cannot, it must tell the buyer before that deadline, give a revised date if it knows one, and offer the choice to accept the delay or cancel for a refund (FTC business guide, edited January 2025). A late-order scenario should reward the agent who offers that choice.
- Faulty goods sold to buyers in the EU. Buyers get a legal guarantee of at least two years from delivery, and the seller must repair or replace a faulty item at no cost, or refund all or part of the price when it cannot (Your Europe: guarantees, checked October 2026). EU buyers can also cancel most online purchases within 14 days of delivery without giving a reason (Your Europe: returns).
This is general information, not legal advice.
The demo's fictional policy looks at the item itself, so the "box looks fine" answer leads to a scene titled "Damage evidence ignored."
Teach product knowledge with hotspots
Support and pre-sale chat agents answer questions about parts and care. A product close-up with hotspots lets them inspect each part the way a customer would. A hotspot is a clickable area over something in the frame, and each one can run a click action, for example:
- Show message, for a spec or a care instruction
- Play video clip, for a short demonstration of that part
- Open link modal, for the product page or a knowledge-base article in a window over the video
To make every learner check every part, give the hotspots the same hide time and set each one to require a click. The video then waits until all of them are clicked (see require a click before the video continues). After the hotspots, ask a question taken from a real ticket, such as which part a customer means when they say "the handle came loose." The report shows which parts each person opened and how they answered. If the product moves in the shot, a trackable hotspot can follow it. The packable jacket example uses the same pattern for shoppers, and it works as well for a new chat agent.
Short station videos for fulfillment and seasonal staff
For picking and packing, film each station on a phone and keep one task in each video. Add a question at each check that matters, such as whether a dented box can ship, and turn off skipping on that question so the learner must answer it. Put the videos in an ordered playlist (Core plan and higher) for the first week: new hires get one link, you can make them finish the videos in order, and completion is reported across the playlist.
Shared tablets at a station need a way to record who is watching. Turn on lead capture so each person enters a name or an employee ID, or add an ID to the link with a URL parameter such as ?custom_id= (see viewer identity). Staff do not need a Mindstamp account to watch.
Where your team watches the training
- In your help center or internal wiki. Embed the video on the page agents already use. Mindstamp videos embed in Zendesk, Intercom, HubSpot, or your own documentation (see interactive video for support). To name each agent in the report, pass URL parameters into the embed.
- In your LMS. On the Core plan and higher, Mindstamp exports a SCORM 1.2, SCORM 2004 3rd edition, or SCORM 2004 4th edition package. The LMS records completion and score, and the answers stay in Mindstamp reports (see SCORM export).
- By link to named people. An access list asks each person for an email address and a code, and records the view under that name.
How to measure whether the training worked
Mindstamp reports show each learner's answers, clicks, branch path, and score, plus an answer breakdown for each question. Look at the breakdown first. If many agents choose the same wrong response, you have found a real gap, and you may need to rewrite the policy as well as the training.
Then check the help desk number tied to the ticket type you trained. For damaged-order training, that could be the reopen rate or the share of claims resolved in the first reply. Compare the weeks before and after the training. Carriers, stock, and staffing change in the same weeks, so treat a change as a reason to look closer. It does not prove the training caused it.
Published figures on video ROI describe marketing video. SundaySky's 2025 roundup of video marketing statistics, for example, reports from a Wyzowl survey that 93% of marketers see a positive ROI from video. For training, use your own ticket data as the evidence.
Common questions
Can we reuse our product videos for training?
Yes. Mindstamp adds interactions on top of a video you already have, so a product video can get hotspots and questions for agents without a new edit. Use an uploaded file or a host you control. YouTube links are for testing only.
How long should a training scenario be?
Keep one decision in each video. Across 8.07 million views of 18,315 Mindstamp videos (2018 to October 2026), videos of one minute or less averaged 59.4% watched, the highest of any length group. Those are mostly training, marketing, and sales videos made by Mindstamp customers, and the figure shows a pattern, not a cause. The demo asks for its one decision 10 seconds in and ends at 33 seconds.
Do employees need a Mindstamp account?
No. Viewers do not need an account. They open a link or an embedded video, and you identify them with lead capture, URL parameters, an access list, or your LMS.
Can we sell the training we build to other stores?
Yes. Our guide to selling video training online covers sales channels, pricing per seat or license, and delivery into a buyer's LMS.
Where should we start?
Pick the ticket type that led to the most refunds or reopened tickets last month. Script one decision from it, build it with the steps above, and send it to your support team. The Mindstamp free trial lasts 14 days and needs no payment card.
