When transferring a frustrated user to a live agent, the engineer wants the agent to receive the user's name, account number, and issue category—already collected in session variables—so the agent does not have to ask again. How should the engineer configure this context passing?

The 'Connect to human agent' step in watsonx Assistant allows the engineer to define a transfer context payload that includes session variable values (name, account number, issue category). The contact center integration reads this payload and surfaces the information on the agent's screen, enabling a warm handoff where the agent already has full context. Email or cookie approaches are brittle, asynchronous, and not supported by standard contact center integrations. The correct answer, "Configure the 'Connect to human agent' step to include the relevant session variable values in the transfer context or handoff body", directly satisfies the scenario because it aligns with watsonx Assistant's design principles and the specific capability being tested. The incorrect options ("Instruct the assistant to ask the user to verbally repeat all their details to the human agent after the transfer completes", "Send an automated email containing the session variable values to the agent's inbox just before initiating the transfer", "Store the session variables in a browser cookie that the contact center agent's desktop application will automatically read") 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.