A clerk wants an agent that already includes a structure for suggested prompts covering common counter questions. Why create from a template?
Select an answer to reveal the explanation.
Short Explanation
Templates often bring a starter pack of suggested prompts—handy for common counter questions. Less blank-page panic at the permitting counter.
Full Explanation
One concrete benefit of template-based Copilot agent creation is inherited structure such as suggested prompts for common counter questions. Clerks should create from a template when they want that scaffolding already present, because it speeds setup versus inventing every prompt from scratch at a busy municipal counter. Suggested-prompt structure helps standardize frequent resident questions while still allowing later review and adjustment.
The claim that templates remove all suggested prompts fails factually and conceptually—the value cited in the stem is that templates can include that structure. The claim that templates permanently lock agents so prompts can never be reviewed fails governance reality and product intent: templates start configuration; they should not be treated as forever-frozen. The claim that templates exist only for Azure developers and cannot help Microsoft 365 Copilot business users fails audience scope—business users creating Copilot agents are exactly who templates assist.
Exam caveat: inherited suggested prompts are starters. Clerks still must validate wording against city policy and remove prompts that do not match local procedures or legal constraints.
Operational check: create the agent from a template, review the suggested-prompt list against top counter questions, edit or add prompts as needed, and confirm frontline clerks see the intended starters when they open the agent.