A manufacturer turns on Copilot for Sales for its dealers, but the dealer price list is not connected, so quotes ignore contracted prices. What is the right configuration?
Select an answer to reveal the explanation.
Short Explanation
A price book that is still in the warehouse cannot show up on the quote. You connect the dealer price list to Copilot for Sales before dealers rely on it. Turning the copilot on, with no data connection, is a switch, not a configuration.
Full Explanation
Copilot for Sales quotes from the data it can reach. The contracted dealer price lives on the price list, and that list is not connected, so the copilot cannot see the price the dealer is allowed to offer. Connecting the price list is the configuration. Without that connection a dealer can still chat with the copilot and receive a confident number at the wrong price, which is the miss the manufacturer is already seeing. Leaving it disconnected and treating the copilot as configured because it is turned on confuses a license switch with a data path. Turning the copilot off and on so it discovers contracted prices without a data connection restarts an app that still has nothing to read. Sending dealers to Copilot for Service and asking it to quote from a case that has no price list moves a sales quote onto the service copilot and still omits the list. Exam caveat: a connected price list has to be the dealer's contracted list, not a generic catalog with the same product names. Operational check: quote a known dealer SKU, confirm the copilot returns the contracted price from the connected list, and confirm a dealer without that contract does not receive it.