Utility field technicians work in a canvas app. An agent can suggest a replacement part, but the technician must accept it, and the app must remain the system they use. Which design fits?
Select an answer to reveal the explanation.
Short Explanation
The technician's hands stay on the work order, and the suggestion waits for a yes. You show the part in the canvas app and record the acceptance there before anything is ordered. A chat that replaces the app takes the job out of the system the crew already uses.
Full Explanation
The canvas app is the system of work, and the agent is a step inside it. The design should show the suggested part in that app and record the technician's acceptance before an order is placed, so the person still decides and the job stays where the crew already works. A standalone chat that replaces the canvas app and orders the part with no accept step removes both the system of work and the human decision. A background job that posts the part to truck stock as soon as the agent names it skips the acceptance the utility required. A nightly note read outside the app leaves the suggestion where the technician is not working, so the decision no longer happens in the system of record. The accept action belongs on the work order the technician already completes, and the parts order is created only after that field is set. A suggestion in the app is useful, and it is not permission for the agent to drain truck stock on its own. Exam caveat: acceptance on the canvas screen is the control, and it is different from chatting about parts in a side channel. Operational check: run a test job, confirm the suggestion appears in the canvas app, and confirm no order is created until the technician accepts it.