A utilities lead has an existing outage-incident report and needs a customer email draft. Which Copilot action fits best?

Utilities customer communications during outages must stay faithful to the operational record. When a lead already has an outage-incident report, the appropriate Copilot action is to generate a customer email draft from that existing report so restoration status, affected areas, and safety guidance reflect what operations actually documented. Grounding the draft in the incident write-up reduces rumor, supports consistent messaging across channels, and illustrates the skill of turning an internal municipal document into an external customer-ready message without inventing an all-clear.

Emailing every account’s full meter ID and account balance pulled into the prompt fails privacy and least-privilege rules: billing identifiers and balances are not needed for a general outage notice and should not be injected into generative prompts. Asking Copilot to claim restoration is complete when the report says otherwise fails truthfulness—false all-clear messaging can put residents at risk and destroy trust. Deleting the incident report so Copilot has no operational source fails the grounding pattern entirely and forces unsupported drafting.

Exam caveat: for customer-facing outage mail, choose generate-from-existing-report over fabricating status, oversharing account data, or discarding the source. Stems that mention an existing incident report are pointing you at grounded drafting.

Operational check: feed the current incident report (or an approved excerpt), draft the customer email from reported facts only, omit meter IDs and balances, have the utilities lead confirm restoration language against SCADA/field status, then send from the official channel with a timestamped source reference.