A developer wants to ask users their preferred contact method and route the conversation based on the answer. What is the best approach?
Select an answer to reveal the explanation.
Short Explanation and Infographic
Todd Lammle: 'Imagine you're building a chatbot and this exact situation comes up — present the user with button options (phone; email) and branch based on the selection is your go-to move. Presenting button options and branching based on the selected value is the cleanest approach; providing a guided experience without relying on free-text parsing. This is a classic Domain 1: Build Conversations concept you'll want locked in before exam day.'
Full explanation below image
Full Explanation
Presenting button options and branching based on the selected value is the cleanest approach; providing a guided experience without relying on free-text parsing. Separate instances add unnecessary infrastructure overhead. Free-text keyword matching is fragile. A pattern entity detects phone number formats; not the user's preference choice. The correct answer, "Present the user with button options (phone; email) and branch based on the selection", directly satisfies the scenario because it aligns with watsonx Assistant's design principles and the specific capability being tested. The incorrect options ("Create two separate assistant instances for each contact method", "Use a free-text input step with keyword matching", "Use a pattern entity to detect phone numbers in any message") 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 Conversations section of the certification exam.