A 311 lead wants a reusable standard reply document for sidewalk-complaint triage. Which action creates it?
Select an answer to reveal the explanation.
Short Explanation
Need a standard sidewalk-complaint reply? Prompt Copilot to generate a new document that captures the triage pattern. Sticky notes aren’t a reusable city artifact.
Full Explanation
Generating a new standard reply document with Copilot from a prompt describing triage needs creates the reusable sidewalk-complaint artifact a 311 lead wants. Drafting business communications includes producing a new document that captures standard reply patterns—acknowledgment, information to collect, escalation criteria, and expected timelines—so counter staff reuse one governed file instead of improvising each time.
Storing triage replies only as unlabeled sticky notes with no document created fails because sticky notes are not reusable, searchable, or shareable municipal standards. They vanish with the desk and cannot be versioned.
Asking Copilot to merge sidewalk replies into sealed personnel files automatically fails by concept and privacy: personnel files are the wrong container for public-facing triage language and must not be auto-merged with 311 reply text.
Deleting the knowledge base used by counter staff before drafting any reply document fails as a destructive precondition. Knowledge deletion harms other counter helpers and is unrelated to creating a standard reply document.
Exam caveat: AB-730 new-document skills expect a prompt that describes the municipal communication need, then a reviewable document—not sticky-note chaos or attacks on unrelated knowledge bases.
Operational check: Prompt Copilot with sidewalk-complaint triage requirements, save the new standard reply document to the 311 SharePoint location, and pilot it with two clerks before making it the desk default.