From the Citizen Engagement & Services edition of November 4, 2026
Nordwest-Zeitung tests Wilhelmshaven's new city chatbot and finds confident wrong answers on election results, officials and an unresolved unexploded-ordnance site
City of Wilhelmshaven, Germany (tested by Nordwest-Zeitung) · Municipal AI website assistant · Wilhelmshaven, Germany
- Publisher
- Nordwest-Zeitung (NWZ)
- Original publication
- 2026-11-04
- Source retrieved
- 2026-11-05
- Event date
- 2026-10-31
What happened
A Nordwest-Zeitung reporter tested Wilhelmshaven's new AI chatbot, launched in October with a claim of over 100 languages. Asked on Oct. 31, it did not know about a public inauguration ceremony the city had announced on its own site on Oct. 30. It treated the Sept. 13 local election as a future event, then gave a wrong 'official final result' order, and in another session said results were unpublished. It misassigned council group spokespeople, varying across sessions, and said investigations of three suspected unexploded-ordnance sites were closed when one remains open. The reporter notes it also gave several helpful answers and calls the test a sample, not a full evaluation.
Why it matters
Independent follow-up on a launch the archive covered (local-government, Oct. 19): a concrete test showing stale content and confident errors, including a safety-related one. Useful evidence for acceptance testing of U.S. city chatbots.
Evidence and measured results
Journalist's hands-on test with specific questions and checked answers; small, non-systematic sample.
Limitations and uncertainty
Single reporter, handful of questions, no systematic scoring; non-US context. City response not reported.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-11-05; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- City chatbots give confident wrong answers that residents cannot detect.
- Stakeholders
- City web and communications team
- Elections office
- Public safety office
- Vendor
- Discovery questions
- How quickly are new city pages indexed?
- Which topics are blocked or escalated?
- How are wrong answers reported and fixed?
- Value hypothesis
- Regular answer audits can catch stale or wrong answers before they spread; the test shows the risk, not a fix.
- Potential engagement
- A pre-launch and quarterly chatbot answer audit on priority topics.
- Unsupported claims
- Overall failure rate
- Vendor-wide quality
- Resident harm
Pre-sales engineering
Role takeaway
- Fit
- Applies to any city website assistant built on site content.
- Architecture and integration
- Website retrieval assistant behind a 'Moin' button; freshness and consistency are the weak points.
- Prerequisites
- Fixed test question set
- Crawl schedule
- Topic blocklist
- Constraints
- Small journalist sample
- Non-US context
- Vendor not named
- Security
- Restrict election and safety answers to verified pages or staff escalation.
- Proof of value
- Cross-session consistency replay
- Fresh-page answer test
- Safety-question escalation check
Delivery
Role takeaway
- Work
- Monitor and correct chatbot answers after launch.
- Dependencies
- Content owners by department
- Vendor indexing
- Feedback channel
- Ownership
- City web and communications team.
- Skills and adoption
- Staff need a routine for reviewing logs and correcting content.
- Governance checkpoints
- Pre-launch audit
- Election-period review
- Quarterly answer audit
- Acceptance criteria
- Proposed: new pages answerable within 24 hours
- Proposed: zero unescalated answers on safety topics in audits
- Risks
- Confident errors on safety
- Loss of public trust
- Inconsistent answers across sessions
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?
Errors suggest the bot does not reliably index the city's newest pages and answers inconsistently across sessions.
Governance
Who approves, reviews and stays accountable for outcomes?
Safety-related answers (unexploded ordnance) should be restricted or escalated; the bot presented errors with authoritative wording.
Security and privacy
What data, permissions and controls need testing?
None material in the report.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Bot is hidden behind a small 'Moin' button and not findable via site search, limiting discoverability.
Procurement
What should contracts, pricing and exit terms secure?
Supports including content-freshness and consistency tests in acceptance criteria; vendor not named in the article.
Operating model
Which teams own the service once it runs?
Shows the need for an owner who monitors answers after launch, especially on elections and safety topics.
Publication history
Read preserved resource versions (JSON)Stable resource ID: wilhelmshaven-city-chatbot-nwz-test-wrong-answers-20261104