From the Local Government edition of October 22, 2026
Civic Marketplace case study says Prince William County's Citibot assistant handled nearly 40,000 of about 90,000 PWC311 interactions in its first year
Prince William County, Virginia (PWC311); Citibot; Civic Marketplace · County 311 resident services · Prince William County, Virginia, United States
- Publisher
- Civic Marketplace
- Original publication
- 21 October 2026 (Civic Marketplace Team)
- Source retrieved
- 2026-10-23
What happened
A Civic Marketplace case study published 21 October 2026 says Prince William County's Citibot assistant, Will, deployed across PWC311 phone, text and web in May 2025, handled nearly 40,000 of roughly 90,000 resident interactions in its first year. It reports more than 95% completion of nearly 7,000 service requests and about 13-second live-agent answer times, with tax administration and real estate as leading topics. The piece promotes cooperative-contract access to Citibot and cites Denver's Sunny as a model, a week after Denver's council rejected Sunny's extension over accuracy and measurement concerns.
Why it matters
Vendor-side volume claims are being marketed through cooperative contracts at the same moment a peer council has rejected the same vendor's assistant for weak accuracy evidence, so buyers need independent measures.
Evidence and measured results
Vendor-marketplace figures: ~90,000 interactions, ~40,000 handled by Will, >95% of ~7,000 service requests completed, ~13 s live-agent answer. No accuracy, containment, satisfaction or cost data; no pre-deployment baseline.
Limitations and uncertainty
Marketing content. The 95% completion rate covers all channels, not Will alone. Figures differ in framing from an archived county release reporting 64,000-plus interactions; neither source explains the difference.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-10-22; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- High volumes of routine 311 questions on tax and real estate compete with complex cases for staff time.
- Stakeholders
- County 311 director
- Finance and tax administration
- Real estate assessments
- County data and AI engineering
- Procurement (cooperative contracts)
- Board of County Supervisors
- Discovery questions
- How will accuracy be measured and reported to the board?
- What share of AI-handled conversations end without escalation?
- Which cooperative contract terms cover data use and exit?
- What happened to staffing and wait times before and after launch?
- Value hypothesis
- Bounded: an assistant may absorb a substantial share of routine contacts, but the share that is resolved correctly is unknown from this source.
- Potential engagement
- An independent evaluation plan for a 311 assistant: accuracy sampling, escalation analysis and satisfaction survey before renewal.
- Unsupported claims
- Staff time or cost savings
- Answer accuracy
- That results replicate in other jurisdictions
- Causal link between Will and 13-second answer times
Pre-sales engineering
Role takeaway
- Fit
- Counties with an established multichannel 311 operation and high-volume informational queries.
- Architecture and integration
- Assistant embedded in existing phone, text and web channels with service request creation in the 311 case system (integration details not given).
- Prerequisites
- Maintained 311 knowledge base
- Service request system integration
- Live-agent handoff path
- Conversation logging
- Constraints
- No accuracy or containment data
- Cooperative-contract terms not reviewed
- Integration method undisclosed
- Security
- Tax and property queries may involve personal data; logging, retention and vendor data-use terms must be verified.
- Proof of value
- Sample 200 AI conversations for answer correctness
- Trace escalation reasons by channel
- Compare service request quality from AI versus agents
Delivery
Role takeaway
- Work
- Operate and improve a 311 assistant across channels, with knowledge upkeep and quality reporting.
- Dependencies
- 311 knowledge base owners
- Vendor configuration
- Case system integration
- Board reporting cycle
- Ownership
- County 311 (PWC311) with county data and AI engineering.
- Skills and adoption
- 311 agents shift to complex cases; staff need skills in conversation review and knowledge-base editing.
- Governance checkpoints
- Accuracy report before renewal
- Data-use review of cooperative contract terms
- Board briefing on outcomes beyond volume
- Acceptance criteria
- Proposed: at least 90% correct answers in sampled conversations
- Proposed: escalation reasons logged for every handoff
- Proposed: satisfaction measured per channel quarterly
- Risks
- Inaccurate answers on tax or assessment questions
- Renewal decided on volume rather than outcomes
- Vendor lock-in through cooperative contract
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?
Assistant integrated into existing 311 phone, text and web channels rather than a new app; service request completion implies integration with the county's 311 case system, though not described.
Governance
Who approves, reviews and stays accountable for outcomes?
Cooperative contracts (AFI, TXShare) let agencies buy without a standalone solicitation, which shortens procurement but also removes a point where councils typically ask for accuracy and outcome evidence.
Security and privacy
What data, permissions and controls need testing?
Not addressed in the source; tax and real-estate queries may involve personal data, so data handling terms need checking.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Multichannel and 24/7 access may help residents outside office hours; live agents remain for complex cases. No language-access or staffing data given.
Procurement
What should contracts, pricing and exit terms secure?
Promoted via AFI and TXShare cooperative contracts that avoid standalone solicitations; tiered monthly SaaS pricing not disclosed.
Operating model
Which teams own the service once it runs?
AI absorbs routine 311 contacts while agents handle complex needs; requires ongoing knowledge upkeep and quality review.
Publication history
- 2026-10-22Local Government · Issue 475 resources
Stable resource ID: prince-william-county-va-citibot-will-first-year-civic-marketplace-case-study-20261021