During an interruption, customers mostly want to know what is happening and when the next update is due. Drafting updates from the operations log, with a supervisor approving each one, gets consistent answers out sooner without the assistant ever guessing at safety or restoration times. These four steps start with planned work and keep operations in charge of the facts.

Step 1 — Agree the templates

Goal: Decide what a good update says.

  1. Write short templates for planned work, interruptions and restoration.
  2. Agree who approves updates on each shift.
  3. Decide which channels updates go to.
  4. Start with planned work in one area.

You finish with: Approved templates, approvers and channels.

Step 2 — Connect the operations log

Goal: Read status from the source of truth.

  1. Read planned work and interruption status from the existing log or work order system.
  2. Map each record to the affected area or customer group.
  3. Keep customer contact details in approved systems only.
  4. Time a few recent updates as a baseline.

You finish with: Status changes flowing into draft updates.

Step 3 — Draft, approve and answer

Goal: Publish consistent updates quickly.

  1. Draft each update in the approved template with the next update time.
  2. Have the duty supervisor approve every update before it is published.
  3. Answer customer questions only from the latest approved update.
  4. Pass safety concerns and anything unclear to a person immediately.

You finish with: Approved updates and consistent answers across channels.

Step 4 — Measure and refine

Goal: Show fewer repeat contacts.

  1. Track time from status change to approved update.
  2. Track repeat contacts per interruption.
  3. Review questions the assistant could not answer.
  4. Add unplanned interruptions only after planned work runs smoothly.

You finish with: Measured update speed and fewer repeat contacts.

Common pitfalls

  • Letting the assistant estimate restoration times on its own.
  • Publishing updates without a supervisor approving them.
  • Giving different answers on different channels.
  • Starting with unplanned emergencies before the process works on planned work.

Read as Markdown Automate the repeatable