From the State Government edition of September 25, 2026
Nevada CIO cites executive-branch Copilot, AI call centers, and AI-enhanced cyber as top impacts
Nevada Office of the CIO / Timothy Galluzi · State enterprise IT / shared services / contact centers · Nevada, United States
- Publisher
- Government Technology — Digital States 2026 ‘A’ State Interview: Timothy Galluzi, Nevada
- Original publication
- 2026-09-23
- Source retrieved
- 2026-09-26
- Event date
- 2026-09-23
What happened
Why now: 2026-09-23 Digital States A-state interview complements the prior day’s Digital States infrastructure narrative with Nevada-specific deployment claims. CIO Timothy Galluzi says the state launched Copilot across the executive branch and highlights AI tools supporting call centers plus AI enhancements to cybersecurity platforms and code review as the highest-impact AI work—arguing defenders must use AI because attackers do. He also ties IT priorities to 2025 special-session legislation enabling whole-of-state cybersecurity collaboration beyond the executive branch.
Why it matters
State shared-services Copilot and contact-center AI claims from an A-grade CIO, useful for workforce-productivity and resident-service channel discussions, with explicit linkage to whole-of-state cyber operating models.
Evidence and measured results
GovTech Digital States Q&A; qualitative self-report without seat counts, deflection, or time-saved KPIs in the opened interview.
Limitations and uncertainty
No quantitative Copilot adoption or call-center outcome metrics in this interview; “amazing results” is qualitative. Distinct from Utah Gemini hours-saved piece archived 2026-09-24.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-09-25; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- States launching enterprise copilots and contact-center AI need credible metrics and cyber guardrails before scaling spend.
- Stakeholders
- State CIO
- Contact-center / digital services leads
- CISO / cyber command
- Agency business owners
- Discovery questions
- How many Copilot seats are active vs licensed?
- What call-center KPIs changed after AI assist?
- Which data classes are blocked from Copilot?
- How is AI code-review gated before production?
- Value hypothesis
- A bounded Copilot and contact-center measurement engagement can turn qualitative Digital States claims into decision-grade KPIs.
- Potential engagement
- 4–6 week Copilot/contact-center KPI and data-class policy review.
- Unsupported claims
- Proven call-center deflection
- Enterprise-wide hours saved
- AI cyber tooling as complete defense
Pre-sales engineering
Role takeaway
- Fit
- Fit for executive productivity Copilot and assisted contact-center knowledge; cyber AI as augmentation only.
- Architecture and integration
- M365/Copilot enterprise; contact-center AI assist; AI-enhanced SIEM/code-review tools; whole-of-state service adjacency.
- Prerequisites
- Data classification and DLP
- Contact-center knowledge grounding
- Secure SDLC review gates
- Identity baselines
- Constraints
- Qualitative evidence only in source
- Nevada-specific whole-of-state statute context
- Security
- Treat AI cyber claims as assistive; require independent validation and change control for AI-suggested code fixes.
- Proof of value
- Seat utilization and blocked-prompt rates
- Contact-center QA sample
- Code-review false-positive/negative sampling
Delivery
Role takeaway
- Work
- Enablement curriculum, data-class enforcement, contact-center content ops, cyber tool playbooks.
- Dependencies
- CIO office
- Agency contact centers
- Cyber team
- Identity/DLP platform owners
- Ownership
- State CIO organization with agency operational owners for call centers.
- Skills and adoption
- Staff need Copilot prompt discipline; analysts need AI-assisted triage literacy.
- Governance checkpoints
- Data-class approval
- Monthly Copilot misuse review
- Cyber AI detection efficacy review
- Acceptance criteria
- Published Copilot usage dashboard
- Call-center quality baseline
- Documented AI code-review gate
- Risks
- Shadow AI with sensitive data
- Contact-center hallucination to residents
- Over-reliance on AI cyber alerts
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?
Enterprise Copilot for executive-branch users; AI assist in call-center stacks; AI-enhanced cyber tooling and code review; potential service expansion to non-executive governmental entities.
Governance
Who approves, reviews and stays accountable for outcomes?
Whole-of-state cyber collaboration authority from 2025 special session; CIO framing of AI as defensive necessity alongside productivity tools.
Security and privacy
What data, permissions and controls need testing?
AI for cyber defense and code review emphasized; data-classification burden reduction flagged as GenAI opportunity; detailed control baselines not published here.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Enterprise Copilot framed as day-to-day staff leverage; accessibility not quantified here. Workforce implication is broad enablement plus cyber/code-review skills, not headcount replacement claims.
Procurement
What should contracts, pricing and exit terms secure?
Copilot implies Microsoft ecosystem; call-center and cyber AI vendors unnamed—confirm contract vehicles and data-processing addenda.
Operating model
Which teams own the service once it runs?
Executive-branch-first Copilot with optional expansion of cyber services to non-executive entities under whole-of-state strategy.
Publication history
- 2026-09-25State Government · Issue 204 resources
Stable resource ID: nevada-digital-states-2026-galluzi-copilot-callcenters-20260923