From the Local Government edition of November 5, 2026
Beroun, Czech Republic ends its Chetty virtual voice assistant after nine months of resident complaints about delays and wrong transfers
Městský úřad Beroun · Municipal government · Beroun, Central Bohemian Region, Czech Republic
- Publisher
- Berounský deník
- Original publication
- 4 November 2026
- Source retrieved
- 2026-11-06
- Event date
- 2026-11-03
What happened
City of Beroun (Berounsko), Czech Republic: Berounský deník (4 November 2026) reports that after nine months the municipal office permanently ended the Chetty virtual voice assistant on the main information line 311 654 111. Spokesperson Jitka Soukupová said the technology was meant to modernize and speed call handling but did not meet expectations. During the trial residents frequently complained about lengthy call handling, misunderstandings with the automated system and incorrect transfers to departments. From Tuesday 3 November the line is again answered by mail-room staff. The city thanked residents for feedback during the test. No quantitative complaint counts, cost figures or vendor name beyond Chetty are reported.
Why it matters
Why now: service ended 3 November 2026, reported 4 November. A concrete local failure of a municipal voice assistant after resident complaints is scarce measured-operations evidence for contact-center AI.
Evidence and measured results
Local newspaper quoting the city spokesperson; complaint themes named but not quantified; no cost or vendor corporate detail beyond the Chetty product name.
Limitations and uncertainty
Single local report; no complaint counts, costs or technical root-cause analysis.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-11-06; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Municipalities automate info lines to speed service but risk resident frustration when routing fails.
- Stakeholders
- Municipal office leadership
- Mail-room / podatelna staff
- Residents
- Telephony or AI vendor
- Discovery questions
- What is the transfer-success rate today?
- How are complaints logged by theme?
- What is the human fallback path?
- What exit criteria were set at launch?
- Value hypothesis
- Bounded: restoring humans may cut wrong transfers; no post-rollback metrics reported.
- Potential engagement
- Post-incident review: complaint coding, routing metrics and rollback playbook for future pilots.
- Unsupported claims
- Any cost savings from Chetty
- Technical root cause
- That all voice AI fails
Pre-sales engineering
Role takeaway
- Fit
- Cities piloting voice assistants on general information lines.
- Architecture and integration
- IVR/voice-AI with explicit human transfer and department routing analytics.
- Prerequisites
- Complaint taxonomy
- Baseline handle-time and transfer metrics
- Rollback authority
- Constraints
- Czech language and local department structure
- Vendor/stack unknown
- Single news source
- Security
- Not addressed in the report.
- Proof of value
- Track wrong-transfer rate weekly
- Mystery-shop common intents
- Confirm human answer SLA
Delivery
Role takeaway
- Work
- Document failure modes; rebuild human coverage; set future pilot gates.
- Dependencies
- Staffing for human coverage
- Vendor offboarding
- Public communications
- Ownership
- Municipal office (podatelna) owns the info line after rollback.
- Skills and adoption
- Front-line staff need clear scripts after the assistant is removed.
- Governance checkpoints
- Human coverage confirmed on the published number
- Complaint themes re-checked after rollback
- Acceptance criteria
- Proposed: wrong-transfer complaints fall after rollback
- Proposed: published number always reaches a person within a set number of rings
- Proposed: any future voice AI has written exit criteria before launch
- Risks
- Staffing strain after rollback
- Loss of vendor lessons if offboarding is abrupt
- Repeating the pilot without metrics
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 IVR/assistant on the main info line replaced by human agents; telephony integration details not given.
Governance
Who approves, reviews and stays accountable for outcomes?
City prioritized understandable communication and reversed the pilot after feedback; no formal audit cited.
Security and privacy
What data, permissions and controls need testing?
Not discussed.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Mail-room staff resumed answering; resident experience issues (misunderstandings, wrong transfers) drove the rollback.
Procurement
What should contracts, pricing and exit terms secure?
Nine-month trial ended; procurement or contract terms not described.
Operating model
Which teams own the service once it runs?
Return to human front-door for the main information line after failed automation.
Publication history
- 2026-11-05Local Government · Issue 614 resources
Stable resource ID: beroun-cz-chetty-voice-assistant-discontinued-20261103