Plan for the call surge.
Prepare approved updates and clear escalation paths. Test capacity against representative demand before deployment.
Help water, power and public works teams answer outage questions, collect service requests and route customers to the right people using your approved updates and response procedures.
Illustrative workflows. Configure and validate with your organization.
Share the approved update. Capture what the customer is reporting. Send the question and its context to the people who can act.
Use the utility’s published bulletin. Do not fill in an unconfirmed restoration time.
Placeholder for an approved outage bulletin, including its issue time and latest reviewed wording. No real outage is represented.
Explore three sample requests. The next step changes with the customer’s need.
Hazard reports take a separate path.
Follow your utility’s approved urgent-response procedure. This mock does not accept reports.
A reported service issue, an example location and the original description are kept together.
Review the issue and location before deciding the appropriate field response.
Example routing only. No live outage feed, work order or emergency-service connection.
Bring service records, correspondence and timestamps together. Let your reporting requirements determine what is captured and retained.
Prepare approved updates and clear escalation paths. Test capacity against representative demand before deployment.
Agree on what a dispatch integration can read or update. Keep the reported issue, location and follow-up associated.
Retain the customer-facing information and supporting service records your reporting and disclosure processes require.