Receivers in a hospital supply app ask the in-app copilot how to accept a delivery, and the only answer is the generic product tour. The local receiving procedure is missing. What should the architect add?
Select an answer to reveal the explanation.
Short Explanation
A lobby map that only shows the highway will not get a truck to your dock. You add the local receiving procedure to the in-app help the supply copilot uses. Another generic tour repeats the map the receivers already have.
Full Explanation
In-app help and guidance for a finance or supply chain app starts from product documentation, and the hospital's own receiving steps are added as knowledge so the copilot can teach the local procedure. The generic product tour does not say how this dock accepts a delivery, so that procedure belongs in the supply app's in-app help. Another generic product tour on a separate site repeats public steps and still omits the local procedure. A personal prompt on one receiver's account is not the in-app help the copilot reads for everyone else on the dock. A custom model that memorizes the product tour locks in the generic path and is not given the receiving procedure the question is about. Exam caveat: local help content should describe the current receiving steps, and a procedure from a retired dock layout will be quoted as if it were current. Operational check: ask the in-app copilot how to accept a delivery and confirm the answer includes the hospital's receiving procedure, not only the generic tour. Ask from a receiver account that has no personal prompt, so the answer has to come from the in-app help.