What this category's data looks like
This page focuses on the enterprise sales product training category, with materials drawn from three sources: product manuals, sales response scripts, and channel training schedules. Product manuals provide product fields and version numbers, sales response scripts carry Q&A wording and scenario responses, and channel training schedules record time, sessions, and participants. Materials are updated quarterly, manuals iterate with versions, response scripts adjust with channel feedback, and schedules refresh monthly. Field characteristics include name, quantity, date, signature, and receipt; it is common for the same record to have mismatched name, quantity, or date across two materials, unsynchronized versions, or missing signatures or receipts. After entering the question acceptance and missing-item follow-up feature, product manuals serve as the factual basis, sales response scripts serve as response templates, and channel training schedules serve as the source for scheduling and personnel verification; together, the three support missing-item identification and follow-up questions.
Configuration and implementation checks
This step is executed by the tool calling node in the workflow (the model decides whether to call, and the node executes), outputting the tool call result (the inputs and returns in the call record). "Acceptance records and items to be completed" are then handled by subsequent AI nodes or manual verification. Based on the tool description, parameter descriptions, and whether parameters are required, the model determines whether to call the tool this time; when there are no required parameters, the model may fabricate parameter values on its own, and when there are required parameters but no suitable value in the context, it may not call.
| Object | Check | Verification action |
|---|---|---|
| Product manual | Category verification dimension: whether fields, dates, and signatures are consistent with the sales response scripts; whether the name, quantity, and date of the same record match | Open the description field in the tool node and check whether this description can be understood on its own; run a test with a question missing that field to see whether it asks a follow-up first instead of fabricating directly |
| Sales response scripts | Category verification dimension: whether fields, dates, and signatures are consistent with the channel training schedules; whether versions are synchronized and whether signatures or receipts are missing | Open each parameter configuration one by one and check the two items: description and whether required; verify the diamond connectors and node status on the canvas |
| Channel training schedules | Category verification dimension: whether fields, dates, and signatures are consistent with the product manuals; whether the name, quantity, and date of the same record are mismatched across the two materials | Check the tool calling node connections and that the diamond interface is connected to the target tool; run a test with a question missing a required parameter and check the inputs and returns in the call record |
| Tool calling node | Based on the tool description, parameter descriptions, and whether parameters are required, the model determines whether to call the tool this time | Check the toolChoice and functionCall related configurations; confirm that when there are no required parameters the model may fabricate parameter values on its own, and when there are required parameters but no suitable value in the context it may not call |
Three common errors
- Symptom: the name, quantity, and date of the same record are mismatched between the product manual and the sales response scripts. Cause: the two materials' versions are not synchronized, update cadences are inconsistent, and field definitions are not unified.
- Symptom: the channel training schedule lacks signatures or receipts, making it impossible to confirm participants and sessions. Cause: the material circulation step does not require signatures or receipts, and archival fields are missing.
- Symptom: the model does not call the tool and directly gives an answer; values that do not exist in the business materials appear in the returned result. Cause: the tool description or parameter descriptions are unclear, and required parameters are not guided for the user to provide.
How to verify the setup
Acceptance for this feature: run a test with a question missing a required parameter, check the inputs and returns in the call record, and confirm whether it asks a follow-up or calls according to the description; check whether the toolChoice and functionCall related configurations take effect.
Business test: ask a question missing key information and see whether it asks a follow-up before answering.
- Open the description field in the tool node and check whether this description can be understood on its own; open each parameter configuration one by one and check the two items: description and whether required.
- Verify the diamond connectors and node status on the canvas; run a test with a question missing that field to see whether it asks a follow-up first instead of fabricating directly.