A 311 improvement squad wants to iterate FAQ language together with Copilot help. Where should they collaborate?
Select an answer to reveal the explanation.
Short Explanation
FAQ wording needs teamwork—put it on a Copilot Page so the 311 squad can co-edit with Copilot’s help. Shared page, shared language, fewer mystery versions.
Full Explanation
A 311 improvement squad iterating FAQ language needs a shared editable surface where Copilot can help and multiple editors can refine wording in one place. Collaborating on a Copilot Page where the squad co-edits FAQ language with Copilot assistance is correct because Pages are built for iterative, multi-person drafting with AI support. For municipal 311, consistent FAQ phrasing across channels reduces contradictory answers to residents about permits, bulky waste, noise, and service levels.
Working only in private one-off chats that never become a shared editable artifact fails knowledge capture; good phrasing dies in silos and new agents reinvent answers. Posting draft FAQ answers that include resident SSNs for “realism” fails privacy and is unnecessary for drafting public help text. Locking FAQ text so nobody—including supervisors—can revise wording fails continuous improvement; service policies and seasonal programs change, and supervisors must be able to correct errors.
Exam caveat: Copilot-assisted FAQ drafts still require accuracy review against current policy and fee schedules before publication to the public knowledge base. Operational check: keep the working FAQ on the shared Page, exclude personal identifiers from examples, assign a supervisor to approve final wording, and publish only after the Page content matches official program rules.