A user initiating a hotel check-in flow skips providing their reservation ID when asked. The engineer wants the assistant to respond with a specific message—'I still need your reservation ID to continue. It is a six-digit number on your confirmation email.'—and wait again. What should be configured to achieve this?

In watsonx Assistant slot filling, each slot can have its own clarification prompt—a specific message displayed when the user's response doesn't satisfy that slot's requirement. This allows the engineer to craft targeted, helpful re-asks (including format hints) rather than generic error messages. A global fallback or human handoff would be disproportionate for a simple missing value. The correct answer, "A clarification prompt on the reservation ID slot that contains the targeted re-ask message", directly satisfies the scenario because it aligns with watsonx Assistant's design principles and the specific capability being tested. The incorrect options ("A fallback action that completely restarts the conversation from the welcome message", "A 'Connect to human agent' step that fires whenever any required field is empty", "A global error handler that sends a generic 'I didn't catch that' message for all input failures") may appear relevant but each misses a key requirement or introduces a step that is either unnecessary or belongs to a different workflow. Mastering the distinction between these approaches is essential for effective watsonx Assistant implementations and is a core focus of the Domain 1: Build Conversational Flows section of the certification exam.