Hospital billing wants a plain-language collections explanation from invoice data Dynamics 365 Finance already holds. A proposal builds an agent that retypes each invoice into a chat before any finance copilot is tried. What should the architect choose first?
Select an answer to reveal the explanation.
Short Explanation
The invoice is already on the desk the finance copilot can read. You use that copilot for the collections explanation before anyone builds an agent that retypes the same invoice into a chat. Retyping copies the record instead of using it.
Full Explanation
When a prebuilt copilot already sits on the finance data, the architect uses it before funding a custom agent that copies the same rows. Hospital billing wants a collections explanation from invoices Dynamics 365 Finance already holds, so the finance copilot comes before an agent that retypes invoices into chat. A custom agent that retypes each invoice into chat before the finance copilot is given the question skips the copilot and creates a second, pasted copy of the invoice. A small language model that memorizes one collections letter and does not read the invoice tables can recite a template and cannot explain this account. A public paste form where clerks retype each invoice while the finance tables stay disconnected moves the same retyping onto a website and leaves Finance unread. The finance copilot is the prebuilt that already has the invoice context. Exam caveat: using that copilot comes before a custom build. It does not by itself approve a new model. Operational check: open one overdue account in a finance test company and confirm the copilot's explanation matches that account's invoices without a clerk pasting them.