A 311 request-status page needs to re-ask the citizen for a missing case number rather than firing the no-match event handler every time that required slot is empty. What should the team configure instead?
Select an answer to reveal the explanation.
Short Explanation
A citizen who forgot to mention their case number hasn't said anything unrecognizable — the agent understood them fine, it's just missing one piece. A transition route condition built around that missing required parameter re-asks for exactly that piece instead of treating it as a failure to understand.
Full Explanation
A missing required parameter is a distinct condition from a no-match failure: the resident's utterance was understood, but a slot the page needs to proceed, like a case number, wasn't filled, and the correct fix is a transition route condition that specifically checks for that missing parameter and re-prompts for it rather than routing through the generic no-match path, which is meant for unrecognized input rather than incomplete input. A no-input handler only fires on silence within a response window, which is unrelated to a parameter simply not being provided during an otherwise normal exchange. A system instruction stating the agent shouldn't proceed without a case number describes a policy but doesn't implement the mechanics of detecting the gap and re-asking for it within the page flow. Few-shot examples of valid formats could help validate a case number once given, but they don't address the scenario where the resident hasn't provided one at all. Scope caveat: repeated missing-parameter re-prompts should still have an escalation path if the citizen genuinely doesn't have the case number available. Operational check: submit a status request with the case-number field left blank and confirm the page re-prompts for it specifically rather than falling into the no-match path.