From the Utility Management edition of November 4, 2026
Oshawa Power upgrades AI virtual assistant Watt to handle moves, balances and bill due dates
Oshawa Power (municipally owned local distribution company) · Municipal electric utility, billing and customer service · Oshawa, Ontario (Canada)
- Publisher
- Durham Radio News
- Original publication
- Durham Radio News, 4 Nov 2026
- Source retrieved
- 2026-11-05
What happened
Oshawa Power launched an upgraded virtual assistant, Watt, that uses AI to understand questions and complete tasks 24/7, including starting or stopping service for moves and checking balances or bill due dates. The utility says move requests and balance inquiries are more than 25% of customer service calls, and Watt uses multi-factor verification before account updates or sharing account information. Human agents remain available.
Why it matters
A municipally owned utility moving AI from FAQ answers to account transactions is directly transferable to US municipal electric and water billing offices, though Ontario's regulatory and privacy context differs.
Evidence and measured results
Local news report based on the utility's announcement. The 25% figure is the utility's share of call volume for these request types, not a measured deflection result. No accuracy, containment or satisfaction data. The utility's own pages returned HTTP 403 to our fetch.
Limitations and uncertainty
No results yet; vendor and model not named; utility site not accessible to verify directly.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-11-04; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Routine move and balance calls consume a large share of service capacity.
- Stakeholders
- Customer service manager
- Billing/CIS lead
- IT security
- Utility executive
- Discovery questions
- What share of calls are moves and balance checks?
- Does the CIS expose move-order APIs?
- How are callers verified today?
- Value hypothesis
- Verified self-service for routine requests may reduce call load; must be measured locally.
- Potential engagement
- Call-mix analysis and a read-only-first self-service pilot.
- Unsupported claims
- A specific call reduction
- Customer satisfaction gains
- Safe automation of all account changes
Pre-sales engineering
Role takeaway
- Fit
- Municipal utilities with an API-capable CIS and digital identity channels.
- Architecture and integration
- Chat assistant calling CIS/billing APIs after multi-factor verification, with handoff to agents.
- Prerequisites
- CIS APIs
- MFA channel (SMS/email)
- Audit logging
- Constraints
- Ontario context
- No published results
- Vendor unnamed
- Security
- Verify identity before any disclosure; log all AI-initiated account changes; monitor for takeover attempts.
- Proof of value
- Test move-order accuracy against CIS
- Attempt disclosure without verification
- Measure handoff success
Delivery
Role takeaway
- Work
- Map routine requests, integrate CIS, enable MFA, pilot read-only then transactional tasks.
- Dependencies
- CIS vendor
- Identity channel
- Contact-centre staff
- Ownership
- Customer service manager with billing IT.
- Skills and adoption
- Train agents to handle escalations and review AI-created orders.
- Governance checkpoints
- Approve automatable transaction list
- Security review of verification flow
- Post-launch accuracy audit
- Acceptance criteria
- Proposed: move-order error rate below agreed threshold
- Proposed: no disclosures before verification in testing
- Proposed: human handoff available at all times
- Risks
- Incorrect move dates or billing
- Account takeover
- Customers unable to reach staff
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
Chat assistant integrated with customer information and billing systems to read balances and write move orders, gated by multi-factor verification.
Governance
Who approves, reviews and stays accountable for outcomes?
Transactional AI needs rules on which account changes may be automated and how they are audited; the utility says more capabilities will follow on request.
Security and privacy
What data, permissions and controls need testing?
Multi-factor verification before account disclosure or updates is the stated control; identity proofing and logging details are not given.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
24/7 self-service; staff redirected to customers needing extra help; humans remain available.
Procurement
What should contracts, pricing and exit terms secure?
Requires CIS/billing integration capability from the assistant vendor; scope expansion is planned.
Operating model
Which teams own the service once it runs?
Routine move and balance requests shift to self-service, freeing representatives for complex cases.
Publication history
- 2026-11-04Utility Management · Issue 073 resources
Stable resource ID: oshawa-power-watt-ai-virtual-assistant-account-tasks-2026