Playbook, online course
When the video will not play, and what an assistant can usefully say
Playback problems on a course platform look like one fault and are usually several. A corporate firewall, an aggressive extension, a browser refusing autoplay, a slow connection and a genuine outage all present as a video that will not start, and they need checking in a specific order.
Why this is not the general answer
The handling pattern for technical troubleshooting holds across every trade. What follows is the part that does not.
- The single largest cause on a professional course is a workplace network, and the learner has no ability to change it, so identifying it early saves an hour of pointless steps.
- The failure is silent and non specific, so unlike most software problems there is no error message to search for.
- Downloads and offline access, where offered, are a genuine workaround rather than a consolation, which makes them worth mentioning early.
- A real outage looks identical to a local problem from the learner's side, which is the argument for a status page the assistant can read.
How it arrives
- the video will not play
- the video keeps buffering
- i get a black screen where the video should be
- it works at home but not at work
- can i download the lessons
- is the site down
What has to be indexed for this to work
| A troubleshooting page in cause order | Network first, then browser and extensions, then account and access. Ordered by how often each is the cause rather than by how easy it is to describe. |
|---|---|
| What a corporate network needs to allow | Written so a learner can forward it to their own technical team, because that is what actually fixes it. A page addressed to the learner alone is not usable here. |
| Supported browsers and known conflicts | Kept current. This is fast rotting material, and a page listing a browser version from two years ago makes the whole answer look stale. |
| A status page | The only way an assistant can distinguish an outage from a local problem, and worth indexing precisely because it changes. |
The reply
If it plays at home but not at work, it is almost certainly your workplace network, and our troubleshooting page has a section you can forward to your technical team. If it fails everywhere, try a different browser with extensions disabled, which rules out the second most common cause. Our status page will say if there is a wider problem. If none of that helps, leave your name and email and support will pick it up.
It leads with the diagnostic the learner already gave, which is the fastest route to the answer, and gives each branch one concrete action. It ends with a handover rather than a fourth step, because past this point the assistant is guessing.
Where it stops
The trigger. The published steps have been tried, the problem is intermittent, or the learner reports something that does not match any documented cause.
That is past what I can work out from here. Leave your name, your email and which browser and device you are on, and support will take a proper look.
It stops answering before it guesses, says who will pick it up, and asks for the one thing that makes a reply possible. Nothing about it reads as a dead end.
Never say this here
Out of bounds
- That there is or is not an outage, unless the status page says so.
- A fix that involves the learner changing their employer's network settings themselves.
- That the problem is on the learner's side without evidence.
- Ask for account credentials as part of troubleshooting.
Questions
- Why put the network cause first?
- Because on a course sold to professionals it is the most common one, and it is the only one where every other step is wasted effort. Ordering troubleshooting by frequency rather than by simplicity is what makes it useful.
- How do we stop it giving advice for an old browser version?
- Point it at the compatibility page you actually maintain rather than uploading a copy. This is the material that rots fastest in this whole trade.
- Should it collect device details?
- Yes, in the handover message. Browser, device and whether it happens on another network are the three things support asks first, and having them already saves a round trip.
Keep reading
- Everything for a online courseWhat is included, how long access lasts, refund and cooling off rights, and the honest limit that it cannot see a learner's own progress.
- Handling technical troubleshooting in generalThe dominant failure is an answer taken from the wrong release. A refusal beats a confident step list for software nobody is running.
- A learner who paid and cannot get in, handled in one stepSomebody who paid and cannot get in is the most urgent conversation on a course site. Route it in one step.
- Two prices for one curriculum, and the difference is a dateWhy a cohort costs more than the self paced version, what lifetime access is worth, and how a three payment plan changes the total.
- The receipt has a person's name and finance will not accept itA learner paid, then finance wants a document with the company name and number on it. What can be changed after checkout and what cannot.
Try it on your own material
Upload a document or point it at your site, paste one line of HTML, then ask it something only your business could answer.