{"resourceId":"fairfax-county-va-311-ai-agent-transactional-roadmap-it-committee-20261020","versions":[{"version":"external-4a21949dea64307ae57496afbf22f43ff0263db9384a6c42c8d50d0714f71493","resource":{"id":"fairfax-county-va-311-ai-agent-transactional-roadmap-it-committee-20261020","title":"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","organization":"Fairfax County Government, Virginia (Department of Information Technology)","sector":"County 311 and customer portal","geography":"Fairfax County, Virginia, United States","publishedAt":"20 October 2026 (Board of Supervisors IT Committee presentation)","publicationDate":"2026-10-20","eventDate":"2026-10-20","sourceName":"Fairfax County Board of Supervisors","sourceLabel":"County government committee presentation","sourceUrl":"https://www.fairfaxcounty.gov/boardofsupervisors/sites/boardofsupervisors/files/Assets/Documents/Oct-20-2026-IT-Committee-Presentation.pdf","evidenceClass":"government-evaluation","outcomeClass":"emerging","topics":["developers-agents","operating-model","data-security","infrastructure"],"finding":"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.","sledRelevance":"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":"Roadmap table and process slide in an official county presentation. Targets only; no metrics, vendor or cost.","architectureImplications":"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.","governanceImplications":"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.","securityPrivacyImplications":"Authenticated, personal-data transactions are deferred until the One County Account is in place, which will require strong identity proofing and access control.","caveats":"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.","streamIds":["local-government"],"roles":{"sales":"Framing: Fairfax is planning the step from answering questions to completing transactions. The roadmap stages a 311 AI agent into selected anonymous transactions by Q2 2027, with authenticated services waiting for a unified county account. Conversations should centre on integration, identity and phased risk, not chatbot features. No outcomes are reported, so value cases must stay hypothetical until testing results exist.","engineering":"Framing: the hard parts are integration and identity. The agent must connect to portal applications and the enterprise service platform for triage and routing, and authenticated work depends on the One County Account. Engineers should ask which transactions qualify as anonymous, how the agent writes to systems of record, how failures hand off to staff, and how the identity platform will be integrated later.","delivery":"Framing: phased transactional rollout with board checkpoints. Delivery would define the Phase 1 transaction list, test plans in Q1 2027, escalation paths and metrics for first-contact resolution. Interpretation: acceptance should include error and rollback handling for each transaction type and an independent check before moving to authenticated services."},"roleDetails":{"sales":{"customerProblem":"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"],"discoveryQuestions":["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?"],"valueHypothesis":"Bounded: completing simple anonymous transactions may reduce contact handling, but no baseline or result is published.","potentialEngagement":"Transaction-readiness and identity integration assessment ahead of a county's agentic 311 launch.","unsupportedClaims":["Faster response or higher resolution (goals only)","Any cost savings","Readiness dates as commitments"]},"engineering":{"fit":"Large counties with a customer portal and enterprise service management platform ready for agent integration.","architectureIntegration":"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.","proofOfValue":["Test each Phase 1 transaction end to end with failure injection","Measure handoff rate to staff","Audit agent write actions in logs"]},"delivery":{"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.","skillsAdoption":"Staff need to handle escalations and monitor agent actions; departments must maintain service rules the agent uses.","governanceCheckpoints":["IT Committee review before Phase 1 launch","Security review of write actions","Review before adding authenticated services"],"acceptanceCriteria":["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"]}},"retrievedAt":"2026-10-21T22:13:33-05:00","enrichedAt":"2026-10-21T22:18:42-05:00","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"No workforce or accessibility details on readable slides; the earlier Ask Fairfax assistant is multilingual.","procurementImplications":"Vendor not named on readable slides; joint county and school-system RFPs for staff augmentation and IT products are underway.","operatingModelImplications":"Moves 311 toward an agent-mediated front door integrated with service management, with staged expansion governed through the board's IT committee.","sourceVerification":{"openedUrl":"https://www.fairfaxcounty.gov/boardofsupervisors/sites/boardofsupervisors/files/Assets/Documents/Oct-20-2026-IT-Committee-Presentation.pdf","referenceExcerpt":"Service expansion, conversational transactions and unified identity advance together.","promptVersion":"sled-research-v4.0","model":null,"basis":"agent-reported inspection"}}}]}