Voice AI for field and meter-visit scheduling in utilities
Utilities field scheduling deploys cleanly on voice AI when the integration is against real engineer availability that includes drive-time and skill — the same trap as telco. The added constraint is vulnerable-customer routing: priority service register customers must be visible to the scheduling logic, not bolted on.
55–75% on schedule / reschedule intents
Integration touchpoints
- Field-service management for live engineer availability with drive-time and skill
- Meter data management for smart-meter vs traditional-meter visit logic
- Priority Services Register for vulnerable-customer flags that shape slot offering
- Outage management to suppress field bookings into impacted areas
Regulatory hooks
- Ofgem / Ofwat (UK) — vulnerability obligations under PSR and supplier licence conditions
- EU electricity and gas directives on universal service and vulnerable consumer protection
- Accessibility — TTY and equivalent obligations on the AI front door
- Industry codes on appointment standards and missed-appointment compensation
What good looks like
AI checks PSR status before offering slots — vulnerable customers see prioritised availability and assured engineer ID-card protocols. Engineers' real availability is honoured. Field bookings are suppressed into outage areas. Missed-appointment compensation rules are encoded and disclosed where applicable.
Watch-outs
- PSR customers treated like standard accounts. Regulators examine PSR handling, not aggregate metrics.
- Flat day grid scheduling. Sells slots; engineers cannot keep them; missed-appointment compensation triggers.
- No suppression during outage events. Stacks bookings the operator cannot service.
- Skipping the engineer ID-card disclosure for vulnerable customers. The protocol is regulated, not optional.
Frequently asked
How does PSR change the scheduling design?
PSR flags shape both slot offering and on-site protocol. Vulnerable customers get prioritised availability, named engineers where the supplier policy supports it, and the AI discloses the ID-card protocol the engineer will follow. None of that is optional under the supplier licence conditions.
What is the most common deployment mistake?
Treating PSR as a downstream flag rather than a scheduling input. PSR has to be visible to the slot-offer logic, not appended after the booking is made.