Utilities revises the outage-communications playbook that a Copilot agent uses. What should staff do to keep answers current?
Select an answer to reveal the explanation.
Short Explanation
When the outage playbook changes, you’ll want to refresh the agent’s knowledge so its guidance stays current. Think of it as keeping the agent’s checklist in step with the one your crews use.
Full Explanation
Agent knowledge must be maintained when municipal source documents change. After Utilities revises the outage-communications playbook, staff should update the agent’s knowledge set to reflect the revised playbook so answers stay current. Knowledge is not a one-time setup; operational Copilot agents need the same document-update discipline cities apply to SOPs and call-center scripts. Leaving the agent pointed at the obsolete playbook indefinitely fails currency and can broadcast outdated outage steps to staff or residents. Deleting the agent entirely whenever any source document changes slightly is disproportionate: document updates usually call for a knowledge refresh, not agent destruction. Hiding the revised playbook from knowledge so the agent keeps citing old outage steps preserves outdated grounding and defeats the purpose of the revision. Exam caveat: updating knowledge should include removing or superseding the obsolete version, not merely adding the revised file alongside it; competing playbook versions can produce mixed guidance. Practical check: replace or update the outage-communications knowledge source with the revised playbook, remove obsolete versions, test representative outage-message prompts, and record the update date and owner in the agent’s maintenance notes.