What this category's data looks like
This page addresses the enterprise sales product training scenario, and the materials come from three categories: product manuals, sales response scripts, and channel training schedules. Product manuals carry product parameters and configuration processes, sales response scripts carry common Q&As and objection handling, and channel training schedules carry course scheduling and attendance records. After the three material categories enter the workflow, they respectively take on the roles of factual basis, response script, and schedule verification. Materials are updated monthly, response scripts are synchronized with product versions, and schedules roll over quarterly. Field characteristics include product name, quantity, effective date, version number, signature field, and receipt field. The same record may show inconsistent names, quantities, or dates across the three materials; when versions are not synchronized, field values diverge, and missing signatures or receipts can prevent the acceptance record from closing the loop.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. "Acceptance records and items to be completed" are continued and completed by subsequent nodes according to the branch. When the user selection node is triggered, the conversation enters an interactive state and records the workflow state; after the user completes the selection, execution continues along the branch corresponding to the selected option.
| Object | Check | Verification action |
|---|---|---|
| Product manual | Whether the name, quantity, effective date, and version number are consistent with the sales response script and channel training schedule, and whether signatures or receipts are complete | Compare the name, quantity, and date fields in the product manual one by one against those in the sales response script and channel training schedule; check the options and branch connections one by one in the node to confirm that each option corresponds to one branch; trigger the user selection node once and view the node status in the run record; reference the selection result variable in a subsequent node and run a trial once |
| Sales response script | Whether the name, quantity, and date of the same record match the product manual, and whether the version is synchronized | Extract the Q&A entries in the response script and compare them field by field against the product manual; check the version number and effective date; check whether signatures or receipts are missing; verify the branch direction corresponding to nodeId in the run record |
| Channel training schedule | Whether the course name, attendance quantity, and scheduling date are consistent with the product manual and response script, and whether receipts are complete | Compare the course name, quantity, and date in the schedule against those in the product manual and sales response script; check version synchronization; check receipt signatures; reference variables in a subsequent node and run a trial once to confirm that the selection result has been passed in |
| Acceptance records and items to be completed | Whether missing items are identified and followed up on, and whether answers are based on materials | Ask a question missing key information and observe whether it follows up before answering; check whether the follow-up items correspond to fields in the product manual, response script, and schedule; check whether the branch direction and interaction state records are complete |
Three common errors
- Symptom: The name, quantity, and date of the same record do not match between the product manual and the sales response script. Cause: The two materials have different update rhythms, fields are not cross-checked, and versions are not synchronized.
- Symptom: The scheduling date in the channel training schedule is inconsistent with the effective date in the product manual, and the attendance quantity does not match. Cause: The schedule rolls over quarterly while the manual is updated monthly, and signature or receipt confirmation is missing.
- Symptom: After selecting an option, it still follows the default branch, and the process stops after the interaction is completed. Cause: The options and branch connections were not checked one by one, and the selection result variable was not passed to subsequent nodes.
How to verify the setup
This feature acceptance: run trials for each option one by one, and check the branch direction and interaction state in the run record; reference variables in a subsequent node and check the branch corresponding to nodeId to confirm that the selection result has been passed in.
Business test: ask a question missing key information and see whether it follows up before answering; check whether the follow-up items correspond to fields in the product manual, sales response script, and channel training schedule.
- Check the options and branch connections one by one in the node to confirm that each option corresponds to one branch; trigger the user selection node once and view the node status in the run record.
- Reference the selection result variable in a subsequent node and run a trial once; compare the name, quantity, date, and signature receipt in the product manual, sales response script, and channel training schedule.