A permitting desk wants a reusable helper that always answers from the city's zoning FAQ and fee schedule. What does that need primarily justify?
Select an answer to reveal the explanation.
Short Explanation
When the same zoning FAQ and fee schedule questions keep walking up to the counter, you don't want a brand-new blank chat every time—you want a reusable agent grounded on that knowledge.
Full Explanation
Repeated tasks that must stay bound to approved knowledge sources—such as a city's zoning FAQ and fee schedule—are a classic reason to create your own Copilot agent. A permitting desk that wants a reusable helper always answering from those sources needs persistence, instructions, and knowledge grounding that disposable chats do not reliably provide. The need primarily justifies creating an own agent for repeated, knowledge-bound municipal tasks.
Deleting the zoning FAQ so Copilot invents fees freely fails because removing authoritative sources invites hallucinated fees and policy errors. Using only one disposable chat and never saving guidance fails the reuse requirement; the desk would re-explain context every time. Training a new public large language model from scratch on every permit fails as an extreme, inappropriate response to a business-user agent use case.
Exam caveat: Grounding on the FAQ and fee schedule only helps if those documents are current. Stale fee PDFs in the knowledge source will produce confidently wrong answers at the counter.
Operational check: Build the agent against the official zoning FAQ and fee schedule libraries, restrict edit rights on those sources, test sample permit fee questions against the published schedule, and re-test whenever fees or zoning interpretations change.