Lighthouse AdvisorySLED AI Adoption Intelligence
← Back to results

From the Local Government edition of October 19, 2026

Independent reportingMixedNew this fortnight

Suisun City, California reports its Polimorphic AI phone assistant handled 11,659 finance-line calls, resolving about 70% without staff transfer, with estimated rather than budgeted savings

City of Suisun City, California · Municipal customer service and utility-billing enquiries · Suisun City, California, United States

Publisher
Cities Today
Original publication
19 October 2026 (Cities Today)
Source retrieved
2026-10-20
Event date
2025-12-01
Read original source

What happened

Cities Today reported on 19 October 2026 that Suisun City, with about 100 employees serving 30,000 residents, introduced Polimorphic's AI telephone and web assistant 'Susie' in September 2025 and a dedicated finance hotline in December 2025 for utility-billing calls, which a third-party provider handles. The finance line receives about 1,500 calls a month and resolves about 70% without staff intervention, where 'resolved' means the call did not end in a transfer to a person. Updated vendor figures show 11,659 calls since launch and an estimated 415.3 staff hours saved. The article states these are estimated staff time, not confirmed spending reductions, and measure calls handled without staff, not completed transactions. Susie uses only the city and police websites, is not connected to the Tyler Technologies billing system, and the city has no formal AI policy; the vendor reviews call logs monthly with the City Manager's Office, which has exposed gaps in published web content.

Why it matters

Rare small-city outcome data on an AI phone line, with the article itself flagging the metric definitions, which helps buyers set realistic success measures and spot the governance gap of operating without an AI policy.

Evidence and measured results

Full Cities Today article opened. Figures are attributed to Polimorphic's demand-generation specialist; no city-published dashboard or audit was found.

Limitations and uncertainty

Vendor-supplied numbers in a vendor-sourced feature; resolution metric is lenient; savings are notional capacity, not cash.

Put this evidence to work

Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-10-19; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.

Sales

Role takeaway
Customer problem
A small staff spends time redirecting routine utility-billing and service calls.
Stakeholders
  • City Manager's Office
  • Finance department
  • Police department web owners
  • Vendor (Polimorphic)
  • Billing provider (Tyler Technologies)
Discovery questions
  • How is a 'resolved' call defined and audited?
  • What share of calls are really for a third-party provider?
  • Does the city have an AI policy?
  • Which workflows would need record access next?
Value hypothesis
An AI phone line could absorb many direction-only calls; reported savings are estimated capacity, not cash.
Potential engagement
Phone-line pilot with written metric definitions and an independent monthly call sample.
Unsupported claims
  • Budget or headcount savings
  • Completed transactions
  • Answer accuracy

Pre-sales engineering

Role takeaway
Fit
Direction and FAQ calls where no account access is needed.
Architecture and integration
Voice/web assistant over public city and police websites; analytics; no billing-system connector today.
Prerequisites
  • Accurate public web content
  • Call-routing configuration
  • Interaction logging
Constraints
  • No integration with Tyler billing
  • Workflow phase needs internal-record access
  • No city AI policy
Security
Keep the assistant off internal records until access controls, logging and a policy exist.
Proof of value
  • Sample calls for correct direction, not just non-transfer
  • Track repeat callers within seven days
  • Compare staff call minutes before and after

Delivery

Role takeaway
Work
Configure assistant, route finance calls, run monthly log reviews, feed gaps into web updates.
Dependencies
  • Vendor customer success team
  • City Manager's Office reviewer
  • Website content owners
Ownership
City Manager's Office (Michael Elm named as review contact).
Skills and adoption
Staff read call analytics and turn recurring questions into page fixes.
Governance checkpoints
  • Adopt an AI use policy
  • Define metrics before scaling
  • Data-access review before workflow automation
Acceptance criteria
  • Proposed: audited correct-direction rate of at least 85% on sampled calls
  • Proposed: repeat-call rate tracked and below baseline
  • Proposed: policy adopted before any record access
Risks
  • Lenient success metric masks failures
  • Vendor-reported outcomes only
  • Governance gap as scope grows

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?

Voice and web assistant grounded on public city and police web content; no integration with Tyler billing or internal records; analytics on interactions; next phase would need system integration for workflows.

Governance

Who approves, reviews and stays accountable for outcomes?

No formal city AI policy before or after deployment; controls rely on platform safeguards, scope limits and monthly log reviews.

Security and privacy

What data, permissions and controls need testing?

Limited data exposure because no account or internal-record access; future workflow phase would add record access and new controls.

Accessibility and workforce

Who is affected, and what skills or accommodations follow?

Fewer phone interruptions for a small finance team; no staffing cuts described.

Procurement

What should contracts, pricing and exit terms secure?

Vendor deployment configured in about an hour per the vendor; contract and cost not disclosed.

Operating model

Which teams own the service once it runs?

Monthly log reviews turn repeated questions into website fixes; the city is considering AI for application workflows next.

Publication history

  1. 2026-10-19Local Government · Issue 444 resources
Read preserved resource versions (JSON)

Stable resource ID: suisun-city-ca-polimorphic-susie-finance-hotline-20261019