From the Utility Management edition of November 4, 2026
Plumas-Sierra Rural Electric Cooperative says it will not use AI for customer service
Plumas-Sierra Rural Electric Cooperative (PSREC) · Electric cooperative · Northeastern California and Nevada (US)
- Publisher
- Plumas-Sierra Rural Electric Cooperative
- Original publication
- PSREC Manager's Message, November 2026
- Source retrieved
- 2026-11-05
What happened
In its November 2026 manager's message, PSREC says it and peer utilities are watching AI uses such as reviewing aerial photographs for line maintenance, but states it is not interested in using AI for customer service, because members are best served when they can quickly reach a human, day or after hours.
Why it matters
A member-owned co-op publicly ruling out AI in customer service is a direct counterpoint to municipal and co-op chatbot and voice-agent rollouts. It shows member expectations and governance can limit AI scope regardless of technical readiness.
Evidence and measured results
Policy statement by the utility's management in a member newsletter. No data, survey or cost analysis is offered. The day of publication within November is not stated; 1 Nov is used as the month start.
Limitations and uncertainty
Single small co-op; position statement, not evaluation. No details on what AI uses it is pursuing.
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
- Co-op leadership wants AI benefits without weakening human member service.
- Stakeholders
- General manager
- Board of directors
- Member services manager
- Operations/engineering
- Discovery questions
- Which AI uses are acceptable to members?
- Is aerial inspection imagery available?
- Is there a written AI use policy?
- Value hypothesis
- Back-office AI such as image review may save engineering time without changing member service.
- Potential engagement
- AI use-boundary workshop and policy draft, then one back-office pilot.
- Unsupported claims
- Members reject all AI
- Any savings figure
- Customer-service AI is unsuitable for all co-ops
Pre-sales engineering
Role takeaway
- Fit
- Back-office and asset analysis only, per the co-op's statement.
- Architecture and integration
- Standalone analysis of imagery and GIS outside member systems.
- Prerequisites
- Inspection imagery
- GIS asset data
- Written AI policy
- Constraints
- No member-facing AI
- Small co-op staff capacity
- No published AI plans
- Security
- Keep pilots off member account systems; govern vendor access to imagery.
- Proof of value
- Compare AI flags on historical imagery with inspector findings
- Measure review time per mile
Delivery
Role takeaway
- Work
- Document AI boundaries, communicate to members, select one back-office pilot.
- Dependencies
- Board approval
- Imagery data
- Vendor selection
- Ownership
- General manager with board oversight.
- Skills and adoption
- Brief staff on allowed and disallowed AI use.
- Governance checkpoints
- Board adoption of AI boundary
- Pilot review before expansion
- Acceptance criteria
- Proposed: published AI use boundary
- Proposed: pilot findings reviewed against inspector results
- Risks
- Scope creep into member service
- Unclear staff guidance
- Member trust if boundary changes
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?
Confines AI candidates to back-office and asset uses (e.g. aerial image review) rather than member-facing channels.
Governance
Who approves, reviews and stays accountable for outcomes?
A stated, public boundary on AI use set by co-op management for members; useful model for documenting where AI will not be used.
Security and privacy
What data, permissions and controls need testing?
Not discussed; avoiding member-facing AI also avoids account-data exposure through AI channels.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Keeps human agents as the access path for all members, including after hours.
Procurement
What should contracts, pricing and exit terms secure?
Rules out procurement of member-facing AI service tools for now.
Operating model
Which teams own the service once it runs?
Human-first service model retained; AI considered only for system analysis.
Publication history
- 2026-11-04Utility Management · Issue 073 resources
Stable resource ID: psrec-declines-ai-for-member-customer-service-2026