| Product change | Product knowledge training action | Timing or condition |
|---|---|---|
| Major launch | New modules for both sellers and support, with a check for every learner | Released before customers can buy |
| Feature release | Replace the affected walkthrough clip and add a short note on what changed for sellers | Short single-topic clips mean one change never forces re-recording a whole course |
| Change to plans or packaging | Update the reference card and the positioning clip | The same day; modules avoid quoting figures that change often |
| Recurring support issue | Add it to the known-issues module with approved wording for the fix | Once the fix and wording are approved |
| Quiet period between launches | A short recall check on core facts | So knowledge does not fade between launches |
| Every module | An owner and a review date; withdraw anything describing a feature that no longer exists | The product owner signs off the content |
Product knowledge training for sales and support should cover what the product does, who it's for, how it compares, what it can't do and how to fix common problems. Sellers need the buyer-facing depth, support teams the troubleshooting depth. Then schedule refreshes around product changes, not around the calendar.
Last reviewed: November 2026
Put simply, it's the set of modules, references and checks that keep everyone who talks to customers accurate about the current product.
What Should Product Knowledge Training Include?
A product knowledge checklist for customer-facing teams has eight items. Build each from current product documentation and have the product owner sign it off.
- The problem the product solves and the customer it suits, in one plain sentence.
- Core features translated into outcomes a buyer cares about.
- Packaging and plans: what is included where, without quoting figures that change often.
- Competitor positioning: where the product is stronger, where it's not, and how to say so honestly.
- Limits and exclusions: what the product doesn't do, so nobody promises it.
- Setup and first use: what a new customer sees in week one.
- Known issues and their fixes, with the approved wording for each.
- Where to check before answering: the release notes, the product owner, the internal FAQ.
The last two items are the ones most often missing, and they cause the most damage when a seller or agent guesses.
How Does Product Knowledge Differ for Sellers and Support Teams?
Sellers need buyer-facing depth and support staff need troubleshooting depth, drawn from the same approved facts. Splitting content by role keeps modules short and stops each group sitting through material meant for the other.
| Topic | What sellers need | What support teams need |
|---|---|---|
| Features | Outcomes, use cases, a short demo path | Settings, dependencies, step-by-step use |
| Comparisons | Honest positioning against named alternatives | Migration questions and data import |
| Limits | What not to promise | Workarounds and escalation routes |
| Known issues | How to answer if a prospect raises one | Diagnosis, fix and approved customer wording |
| Releases | What is new and who it matters to | What changed in the interface and what breaks |
Distributors and channel partners usually need the seller column in their own language, plus the support rows they handle first. Our guide to dealer training in India covers that audience in more detail.
Which Formats Suit Each Kind of Product Knowledge?
The right format depends on whether the knowledge is shown, explained or looked up.
- Product walkthrough videos suit anything people must see: an interface, a setup flow, a physical product in use.
- Short explainer videos suit positioning and outcomes, where tone and a consistent message matter.
- One-page references and battlecards suit facts people look up mid-call, such as plan contents or compatibility.
- Scenario videos followed by practice suit conversations: a buyer objection, an angry customer with a known issue.
Keep each video to one task or idea. In a 2014 study of 6.9 million video sessions on edX, Guo, Kim and Rubin recommended segmenting lessons into videos shorter than six minutes (Guo et al.). Those learners were online course students, not sales teams, so treat the figure as a starting point. Short single-topic modules also make updates cheaper, which is why a microlearning video series fits product content well.
What Belongs in a Product Knowledge Refresh Plan?
A refresh plan ties each type of product change to a training action, an owner and a deadline relative to release. Without one, modules drift out of date while still being assigned to new starters.
- Major launch: new modules for both roles, released before customers can buy, with a check for every learner.
- Feature release: replace the affected walkthrough clip and add a short "what changed" note for sellers.
- Change to plans or packaging: update the reference card and the positioning clip the same day.
- Recurring support issue: add it to the known-issues module once the fix and wording are approved.
- Quiet period: a short recall check on core facts, so knowledge doesn't fade between launches.
Give every module an owner and a review date, and retire anything that describes a feature that no longer exists. For the wider programme around this, including sequencing and release cycles, see how to build a product training programme that survives updates.
How Do You Check That Product Knowledge Has Stuck?
Product knowledge sticks best when people must recall it, not just recognise it, and are tested more than once. In a 2006 experiment, Roediger and Karpicke found that students who took recall tests on a passage remembered more a week later than students who restudied it (Psychological Science). Their material was prose passages, so treat it as support for frequent checks, not a promise of a particular result.
Useful checks for customer-facing teams include short scenario questions ("A buyer asks whether the product works offline. What do you say?"), a recorded demo scored against a rubric, and spot reviews of real calls or tickets. Track where answers go wrong and feed those gaps back into the next refresh. If learners use the content outside your LMS, agree beforehand how completions and scores will be recorded and reported.
Where Probbit Fits
Probbit produces product and sales enablement videos: product walkthroughs, explainers and scenario modules for sellers, support teams and partners, in the languages they work in. Delivery timing depends on approved source material, module scope, languages and review rounds, and revision ownership is agreed in the scope. To plan modules and a refresh routine for your product, schedule a call.
