From the Local Government edition of October 21, 2026
Fairfax County, Virginia's IT Committee roadmap moves a 311 AI agent from information to selected anonymous transactions by Q2 2027, ahead of a unified county account
Fairfax County Government, Virginia (Department of Information Technology) · County 311 and customer portal · Fairfax County, Virginia, United States
- Publisher
- Fairfax County Board of Supervisors
- Original publication
- 20 October 2026 (Board of Supervisors IT Committee presentation)
- Source retrieved
- 2026-10-22
- Event date
- 2026-10-20
What happened
A presentation to the Fairfax County Board of Supervisors IT Committee on 20 October 2026 sets out a roadmap in which a 311 AI agent moves from an established integration foundation in October 2026 to initial transactions and testing in Q1 2027 and a Phase 1 launch of selected anonymous transactions in Q2 2027, before expanding transactional capabilities. A unified One County Account is in requirements and architecture, with implementation in Q2 2027, and the customer portal has five integrated applications. A slide on AI agents and assistants describes a flow from customer contact through AI-assisted interaction, triage and routing to integration with the county's enterprise service platform, aiming for faster response and higher first-contact resolution.
Why it matters
Shows sequencing that other counties can copy: anonymous transactions first, authenticated services only after a unified identity platform exists. It follows the county's information-only 'Ask Fairfax' assistant covered in the previous edition.
Evidence and measured results
Roadmap table and process slide in an official county presentation. Targets only; no metrics, vendor or cost.
Limitations and uncertainty
Detailed Data/AI and Customer Experience slides are images and could not be read. Roadmap dates can slip. Value statements are goals, not observed results.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-10-21; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Residents must navigate many separate county applications; the county wants an agent that can complete simple requests, not just answer questions.
- Stakeholders
- Department of Information Technology
- Chief Applications Officer
- 311 and customer experience team
- Board IT Committee
- Service-owning departments
- Discovery questions
- Which anonymous transactions are in Phase 1?
- How will first-contact resolution be measured?
- Which systems of record will the agent write to?
- What identity platform is planned for One County Account?
- Value hypothesis
- Bounded: completing simple anonymous transactions may reduce contact handling, but no baseline or result is published.
- Potential engagement
- Transaction-readiness and identity integration assessment ahead of a county's agentic 311 launch.
- Unsupported claims
- Faster response or higher resolution (goals only)
- Any cost savings
- Readiness dates as commitments
Pre-sales engineering
Role takeaway
- Fit
- Large counties with a customer portal and enterprise service management platform ready for agent integration.
- Architecture and integration
- 311 AI agent over a customer portal with five integrated applications, triage and routing into the enterprise service platform, future link to a single county identity.
- Prerequisites
- APIs to systems of record
- Service catalogue of anonymous transactions
- Enterprise service platform integration
- Identity platform for later phases
- Constraints
- Phase 1 limited to anonymous transactions
- Authenticated services wait for identity implementation
- Image-only detail slides leave design unknown
- Security
- Deferring authenticated transactions limits exposure; later phases need identity proofing and least-privilege agent permissions.
- Proof of value
- Test each Phase 1 transaction end to end with failure injection
- Measure handoff rate to staff
- Audit agent write actions in logs
Delivery
Role takeaway
- Work
- Define Phase 1 transactions, build integrations, test in Q1 2027, launch Q2 2027, then expand.
- Dependencies
- Integration foundation
- Service department sign-off
- One County Account for later phases
- Board committee oversight
- Ownership
- Department of Information Technology with customer experience leadership.
- Skills and adoption
- Staff need to handle escalations and monitor agent actions; departments must maintain service rules the agent uses.
- Governance checkpoints
- IT Committee review before Phase 1 launch
- Security review of write actions
- Review before adding authenticated services
- Acceptance criteria
- Proposed: each Phase 1 transaction completes correctly in at least 95% of test cases
- Proposed: published handoff and resolution metrics
- Proposed: rollback procedure tested
- Risks
- Schedule slip
- Incorrect transactions
- Identity platform delay
- Departmental data quality gaps
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?
Agent sits on a customer portal integrating county applications and an enterprise service management platform; authenticated transactions wait for a single identity platform. Triage and routing imply integration with case management.
Governance
Who approves, reviews and stays accountable for outcomes?
Limiting Phase 1 to anonymous transactions reduces identity and privacy exposure; the board committee is receiving staged updates, which offers a checkpoint for each phase.
Security and privacy
What data, permissions and controls need testing?
Authenticated, personal-data transactions are deferred until the One County Account is in place, which will require strong identity proofing and access control.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
No workforce or accessibility details on readable slides; the earlier Ask Fairfax assistant is multilingual.
Procurement
What should contracts, pricing and exit terms secure?
Vendor not named on readable slides; joint county and school-system RFPs for staff augmentation and IT products are underway.
Operating model
Which teams own the service once it runs?
Moves 311 toward an agent-mediated front door integrated with service management, with staged expansion governed through the board's IT committee.
Publication history
- 2026-10-21Local Government · Issue 466 resources
Stable resource ID: fairfax-county-va-311-ai-agent-transactional-roadmap-it-committee-20261020