A retail service desk wants help with password resets and order-status questions. A prebuilt service copilot already matches that work. The sponsor wants to start by training a custom model on old chats. What should the architect propose?
Select an answer to reveal the explanation.
Short Explanation
When the counter already has someone trained for password resets and order status, you start there. You propose the prebuilt service copilot for that work and you leave the custom model unfunded. Old chat logs are not a reason to skip the copilot that already matches the job.
Full Explanation
A prebuilt copilot that already matches the job comes before a custom model. Password resets and order-status questions are the work this service copilot matches, so the architect proposes that copilot and does not start with a custom model. A custom model trained on old chat logs before the prebuilt service copilot is even configured for the desk spends the project on training and does not try the copilot that fits. Computer Use on the password screens, with the prebuilt service copilot left unused on this desk, drives a user interface for a job the prebuilt copilot already covers and adds a screen path the desk does not need. A foundation model whose job is to invent a new password policy for each caller at the desk replaces a reset procedure with a newly invented policy, which is not the request. Custom work waits until the prebuilt copilot has a gap this desk has actually hit. Exam caveat: the service copilot still has to be connected to this retailer's password and order systems. Prebuilt does not mean unconfigured. Operational check: a test caller completes a password reset and an order-status question through the service copilot, with no custom model in the path.