From the Local Government edition of October 26, 2026
Suffolk County, New York's CORA voice agent: vendor reports 45-52% autonomous resolution and live tax-due lookups
Suffolk County, New York (Department of Information Technology) · County contact center (Consumer Affairs, Comptroller) · Suffolk County, New York, United States
- Publisher
- Google Cloud
- Original publication
- Undated Google Cloud customer page, retrieved 26 October 2026; listed by a third-party use-case index with a 23 October 2026 evidence date
- Source retrieved
- 2026-10-27
What happened
Google Cloud reports that Suffolk County's CORA voice agent, built by UVS InfoTech, resolves 45-52% of Consumer Affairs calls without staff on up to 550 calls a week, using live lookups in Salesforce and Accela. In the Comptroller's Office it reads back property-tax amounts due from the 10 towns' portals, handled 874 calls in two weeks, resolved 36% directly, and is credited with a 30% drop in incoming calls during tax season. Baselines cited include waits over 30 minutes at peak. These are vendor-published figures without measurement method or error rates.
Why it matters
Why now: surfaced in late October 2026 (page undated). One of the more specific county examples of an AI agent doing live record lookups and calculations rather than FAQ answers, which raises accuracy and liability questions other counties will face.
Evidence and measured results
Vendor case study figures (resolution rate, call counts, 30% volume reduction, baselines) and county IT quotes; no independent evaluation.
Limitations and uncertainty
Vendor-published and undated; no definitions of 'resolution'; no error rate for tax figures; synthetic training data; volume drop may be seasonal or channel shift.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-10-26; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Seasonal call surges overwhelm limited county staff, producing long waits and manual escalations.
- Stakeholders
- County IT
- Comptroller or treasurer
- Consumer affairs
- Town tax receivers
- Language access office
- Discovery questions
- Which call types peak seasonally?
- Which systems would an agent need to read or write?
- How would a wrong amount quoted to a resident be handled?
- How is resolution measured today?
- Value hypothesis
- Bounded: an agent with live lookups may absorb part of routine call volume, with the share to be measured locally.
- Potential engagement
- A call-type analysis and accuracy test plan for one department before a voice-agent pilot.
- Unsupported claims
- 45-52% resolution as a typical result
- Accuracy of tax amounts
- Staff cost savings
- Resident satisfaction
Pre-sales engineering
Role takeaway
- Fit
- Counties with CRM and licensing platforms that expose APIs and high-volume routine call types.
- Architecture and integration
- Contact-center AI on existing telephony, with live reads and writes to CRM and licensing systems and lookups against external tax portals.
- Prerequisites
- System APIs or reliable portal access
- Call-type data
- Transcript handoff to staff queues
- Constraints
- Fragmented town-level systems
- Hyperscaler platform dependence
- Language quality varies
- Security
- Segment functions so the tax lookup cannot reach internal CRM, log all record access, and authenticate callers before sharing account data.
- Proof of value
- Sample calls to verify quoted tax amounts
- Define and audit 'resolution' on a call sample
- Compare call volume with the prior season
Delivery
Role takeaway
- Work
- Deploy an AI voice agent for routine county calls with measured resolution and accuracy.
- Dependencies
- Department system owners
- Telephony provider
- Systems integrator
- Ownership
- County IT, with each department owning its call content and accuracy.
- Skills and adoption
- Agents handle escalations with transcripts; IT monitors telemetry dashboards.
- Governance checkpoints
- Accuracy sign-off for calculated amounts
- Language access review
- Quarterly review of resolution definitions and repeat calls
- Acceptance criteria
- Proposed: resolution defined in writing and audited monthly on a call sample
- Proposed: quoted amounts match records in a sampled test
- Proposed: repeat-call rate tracked against baseline
- Risks
- Wrong tax amounts quoted at deadlines
- Inflated resolution metrics
- Vendor and platform lock-in
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?
Contact-center AI on a hyperscaler platform integrated with existing telephony, CRM (Salesforce), permitting/licensing (Accela) and 10 separate town tax portals; telemetry feeds a dashboard.
Governance
Who approves, reviews and stays accountable for outcomes?
An agent that reads back amounts owed including penalties needs accuracy testing, audit logs and a clear policy on reliance; none are described.
Security and privacy
What data, permissions and controls need testing?
Tax function described as ring-fenced from internal CRM; Consumer Affairs function reads and writes CRM records, so access controls and logging matter.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Seven languages aligned with the county's language access executive order; after-hours coverage; staff described as freed for complex cases, with no staffing data.
Procurement
What should contracts, pricing and exit terms secure?
Delivered by an 8(a) systems integrator on a hyperscaler platform; contract value not disclosed; planned ERP and payment expansion would deepen dependence.
Operating model
Which teams own the service once it runs?
Replaces 25-plus IVR branches with intent-based routing and transcript handoff; staff work shifts to escalations and field work.
Publication history
- 2026-10-26Local Government · Issue 517 resources
Stable resource ID: suffolk-county-ny-cora-ai-voice-agent-consumer-affairs-comptroller-2026