How do I actually check whether my sales staff know the product, not just the pitch?

This page may contain affiliate links from which Blur Studio earns commissions.

A confident delivery and real product knowledge aren't the same thing, and the gap usually only shows up when a customer asks something slightly off-script. The fix isn't trusting confidence as a proxy, it's asking specific questions that only someone who actually knows the product (or the listing, or the inventory) can answer correctly.

For a small team, skip the tool entirely

If you're checking 3 to 5 people, a short call where you ask real, specific questions, "what's the warranty on this model," "what's not included in this listing's price," is faster to set up and more revealing than building a quiz. You'll also hear the hesitation in their voice, which a written answer doesn't show you.

The free option past a handful of people

A Google Forms quiz, written with specific scenario questions rather than simple recall ("a customer asks X, what do you tell them" beats "what's feature Y"), costs nothing and works fine once calling everyone individually stops scaling. The manual part is writing good questions and tracking who's been tested on what, which gets tedious once you're covering several products or listings across several staff. The same approach for rules instead of products is in proving your staff understood a safety or compliance rule.

Where a dedicated tool saves time at scale

Trainual, a platform for writing up and assigning company process documentation, has a testing feature included on every plan that can use AI to generate quiz questions directly from your own product or listing content, rather than you writing each question by hand. It also tracks and reports results in one place, so you can see at a glance who's been tested on which product and how they scored, instead of cross-referencing a pile of form responses.

Pricing across all four plans (Core, Pro, Premium, Enterprise) is quote-only, with a $1,000 one-time setup fee on any new account regardless of tier. For a small team, that setup cost buys you automation you probably don't need yet; for a growing team testing knowledge across a growing product or listing catalog, it starts to make real sense. Before paying, read what to test in the first 14 days of a Trainual trial.

Step by step: building a real product-knowledge check

1. Write scenario questions, not recall questions. "A customer says X, what's your answer" tests understanding; "what's the spec sheet say" tests memorization of a document.
2. Pull the questions from real situations your team has actually hit, not hypothetical ones, so the check reflects what they'll genuinely face.
3. Set a real pass threshold, so passing means something, rather than treating completion as the goal.
4. Re-test when the product or listing details change, since knowledge of last quarter's catalog isn't knowledge of this quarter's. Your website needs the same upkeep: keeping prices, hours and listings up to date.
5. For a small team, just ask directly on a call instead of building any of this, since the overhead of a quiz system isn't worth it at that scale.

When this is not worth building

For a team of 3 to 5, building a quiz system, free or paid, is more setup than the problem deserves. A direct conversation gets you the same information faster and with more nuance. Save the formal testing approach for when the team or the catalog has actually grown enough that individual conversations stop being practical.

A worked example: a furniture retailer catching a knowledge gap before a customer did

A furniture retailer with twelve sales staff across two showrooms had noticed a pattern in a handful of lost sales: customers asking about a specific line's warranty terms or custom-order lead times sometimes got answers that turned out to be wrong, confidently delivered but inaccurate, which the retailer only discovered after a customer called back confused about a discrepancy between what they were told in-store and what the actual paperwork said. Checking knowledge individually across twelve people on a rotating, frequently updated catalog of roughly forty product lines was clearly past the point where informal calls scaled.

The retailer built a short, scenario-based quiz covering the ten product lines generating the most sales volume, specifically targeting the exact kind of question that had caused the earlier mix-ups: warranty terms, lead times, what's included versus sold separately. Results surfaced a clear pattern immediately: newer staff, hired within the last three months, scored meaningfully worse on lead-time questions specifically than on warranty questions, which pointed to a gap in how lead times were being communicated during onboarding rather than a general knowledge problem across the whole catalog. Fixing that one specific onboarding gap, rather than assuming the whole training program needed an overhaul, resolved the pattern within a month, confirmed by re-testing the same cohort.

A practical note on testing the right staff at the right time, not everyone on the same schedule

Blanket testing everyone on the same fixed schedule, quarterly for the whole team regardless of tenure or recent catalog changes, wastes effort on staff who've clearly demonstrated solid knowledge recently while under-checking the people and products that actually need it. A more useful approach ties testing to two specific triggers instead: a new hire's first ninety days on a newly assigned product line, and any product line that just had a meaningful spec, pricing or warranty change. That targets the testing effort at where knowledge gaps are actually most likely to exist, rather than treating every staff member and every product as equally in need of a check at the same arbitrary interval. It also makes the testing feel less like a generic recurring chore to staff and more like a relevant check tied to something real that just changed, which tends to get a more genuine, less resentful response than a quarterly quiz nobody understands the reason for.

How I'd approach this

For a small team, I'd tell you honestly to skip any tool and just ask people directly, it's faster and you'll learn more from the hesitation than from a score. Once you're genuinely past that size, whether a free Google Form or Trainual's AI-generated testing is the right fit depends on how often your product or listing catalog changes; a catalog that changes constantly needs the automation a manual quiz can't keep up with, which is usually the point where I'd also look at tying the knowledge check directly to your actual product database instead of maintaining it separately, so a spec or warranty update in the database automatically flags which staff need re-testing rather than someone having to remember to trigger it manually every time something changes, which is exactly the kind of manual step that gets forgotten during a busy week and quietly undoes the whole point of testing in the first place, leaving stale knowledge checks sitting unflagged until a real customer complaint eventually forces the exact same gap back into view months down the line.