Multi-Turn Conversation and Prompts for Kindergarten Safety and Emergency Drills: Handle Questions and Collect Missing Information

Kindergarten Safety: review conversation for question intake. Check source versions, input mappings and the values received by downstream nodes.

What this category's data looks like

This page addresses question intake for kindergarten safety protection and emergency drills. Materials fall into four categories: hazard items and rectification deadlines, drill headcount and sign-in, access control and school bus check items, responsible person signatures. Sources are daily inspection forms of the kindergarten, drill plans and sign-in sheets, access control and school bus inspection records, and scanned responsibility statements. The update cadence is daily inspection, monthly drills, and per-semester aggregation. Field characteristics are time, location, check item, rectification deadline, headcount, signature. When these materials enter the multi-turn dialogue and prompt features, they serve respectively as the context of historical messages and the current question: hazard items are used to follow up on rectification deadlines, drill headcount and sign-in are used to verify consistency with the plan, access control and school bus check items are used to follow up on missing items, and responsible person signatures are used to confirm closure. The intake records and the completed follow-up questions are produced by the model based on this.

Configuration and implementation checks

This part is executed by the memory turns and prompt configuration in the application settings, outputting the referenced historical message range and answer constraints. The intake records and the completed follow-up questions are then completed by the model. The external entry point and authorization are handled by the publishing service and file permissions.

ObjectCheckVerification action
Memory turnsMatches the range of prior context required by the question, and can cover follow-ups on hazard items and rectification deadlinesCheck the current value in the application settings, run a trial with two consecutive questions, and observe whether the second turn carries over the references from the first turn
Drill headcount and sign-inThe sign-in headcount is consistent with the drill plan headcount, and missing items are identified and followed upCompare the plan with the sign-in sheet, and check whether the reason for absence and the makeup sign-in record are followed up
Access control and school bus check itemsThere are no missing check items, and missing items trigger follow-upCheck the access control and school bus checklist item by item, and confirm whether missing items are followed up and completed
Responsible person signatureHazard items and rectification deadlines are closed, and signatures are completeCheck the signatures before and after rectification, and confirm whether items that are not closed are followed up

Three common errors

  • Symptom: hazard items are only registered but not rectified, and the deadline cannot be answered during follow-up. Cause: the materials lack rectification deadlines and responsible person signatures, and missing items are not identified.
  • Symptom: the answer follows the planned headcount despite a different count in the drill record. Cause: the sign-in sheet does not enter the reference range, and missing-item follow-up is absent.
  • Symptom: access control and school bus check items are missing, but the answer claims they are complete. Cause: checklist fields are missing, and the prompt does not constrain item-by-item verification.

How to verify the setup

Acceptance of this feature: with two consecutive follow-up questions, see whether the second question carries over the references from the first question; check the references of messages and chatId in the historical message range, and variables is used to bring in the kindergarten and date.

Business test: ask a question that lacks key information, and see whether it first follows up and then answers.

  • Check the memory turns value in the application settings, run a trial with two consecutive questions, and confirm that the second turn carries over the references from the first turn.
  • Compare the usage records of two runs, confirm the consumption change after adjusting the turns, and check that the opening message is not treated as prior context.