Define what the employee needs to do
A product deck may describe everything the company wants to announce. A training lesson needs a narrower objective. For sales, that might be identifying whether a customer requires a feature the product does not offer. For support, it might be asking the right questions before choosing a troubleshooting step.
Write the task in observable terms: explain a limitation accurately, identify an unsuitable use case or locate the current source for a commercial claim. “Know the new release” is too broad to assess with a useful scenario.
Keep role-specific practice separate where the decisions differ. A shared introduction can cover the product's purpose and terminology. Sales and support can then work through different customer situations using the same approved facts.
Prepare a small set of approved source material
Start with the current product overview, feature availability, known limitations and the process for resolving uncertainty. Remove conflicting drafts and outdated screenshots from the training set. Give every source a version or review date and a named owner.
- State which customer needs the product is intended to address.
- List available capabilities separately from roadmap ideas.
- Include conditions and limitations alongside the feature they qualify.
- Provide approved examples and responses to common misunderstandings.
- Specify who should confirm a detail that the source does not answer.
If employees need to discuss pricing, use the current approved commercial material and define who can authorize an exception. A training conversation should not invent a discount, delivery date or integration commitment to make a scenario feel complete.
A fictional customer scenario with an answer rubric
Imagine a scheduling product that supports browser-based appointment booking but does not work offline. This is an invented product for the exercise, not a description of Tutezy. A customer says: “Our team sometimes loses connectivity. Can we keep creating bookings while the internet is down?”
A suitable response acknowledges the need, states the offline limitation and asks how often the team faces it. The employee should avoid promising that the feature will arrive soon unless an approved source authorizes that statement.
| Criterion | Evidence of a useful answer | Problem to flag |
|---|---|---|
| Accuracy | Clearly states that offline booking is unavailable. | Claims bookings will automatically work without connectivity. |
| Clarification | Asks how the limitation affects the customer's workflow. | Moves to a sales pitch without understanding the requirement. |
| Boundaries | Checks uncertain details with the appropriate owner. | Invents a roadmap date or unsupported workaround. |
| Next step | Suggests evaluating fit using the confirmed requirements. | Promises the product will meet every need. |
Ask the learner to explain why an inaccurate answer could cause a problem later. Then change the customer situation. For example, the customer has reliable connectivity but needs a feature not mentioned in the source. Check whether the employee asks for confirmation rather than assuming availability.
Pilot the lesson with a real team
Choose one product module and a small group from the intended role. Ask a subject expert to review the lesson and test several incorrect answers. Include an uncertainty case where the correct behavior is to ask for confirmation.
After practice, use a new scenario without tutor hints. Have a manager review the response using the same rubric. Track inaccurate claims, useful clarifying questions and correct escalation decisions. Include staff preparation time and cases where the tutor's feedback needed correction.
Connect the practice to the team's existing coaching routine. Our speaking practice guide offers a structure for improving how an employee explains a correct answer. For the wider new-hire sequence, see AI-led onboarding training.
Keep a change record for the lesson
When a feature changes, identify the source, explanation, scenario and expected answer that depend on it. Revise those parts together. Updating the product deck while retaining an old rubric can lead the tutor to mark a newly correct response as wrong.
Before release, test the changed scenario and an unchanged one to check for unintended differences. Tell managers which knowledge employees need to refresh. Keep the record simple: source version, lesson owner, review date and the decisions that changed.
Where Tutezy fits
What we built for this
Tutezy supports corporate lessons from existing decks and documents, including situational questions. Explore Tutezy for corporate training with one reviewed product module and its answer rubric. Confirm the content-update workflow before extending the programme.
Frequently asked questions
What is AI product knowledge training?+
It uses AI-supported lessons and practice to help employees explain a product and make appropriate decisions in customer situations. The content should come from reviewed product information and include limits, exceptions and escalation routes.
Can the same lesson serve sales and support?+
Some core facts can be shared, but the practice should reflect each role. Sales may need to establish fit and explain limitations; support may need to clarify a reported issue and choose the next troubleshooting or escalation step.
How often should product training be updated?+
Review a lesson whenever a relevant feature, price, policy or process changes. Assign an owner who can identify affected material, revise it and check the learner experience before it is used again.
See it teach
Take a 10-minute lesson, then book a demo on your own content.
No sign-up for the lesson. The call is 20 minutes and we convert one of your chapters live. We're in India. Calls run 9:30 am–3:30 pm ET (7 pm–1 am IST), Monday to Friday.