Lighthouse AdvisorySLED AI Adoption Intelligence
← Back to results

From the Local Government edition of October 18, 2026

Government evaluationEmergingNew this fortnight

Bergisch Gladbach runs a 12–25 October 2026 livetest of Mähnfred voice-bot on the switchboard and waste hotline, with phase-one calls fully bot-handled and no staff transfer

Stadt Bergisch Gladbach (North Rhine-Westphalia) · Municipal telephone citizen service and waste utilities · Bergisch Gladbach, North Rhine-Westphalia, Germany

Publisher
Stadt Bergisch Gladbach
Original publication
12 October 2026
Source retrieved
2026-10-19
Event date
2026-10-12
Read original source

What happened

On 12 October Bergisch Gladbach announced a two-week livetest (12–25 October 2026) giving its existing website chatbot Mähnfred a voice on the main switchboard (02202 14-0) and the Abfallwirtschaftsbetrieb leaf-and-brush hotline. Phase one (12–20 Oct) routes all switchboard calls to the voice-bot with the desk unstaffed and explicitly no transfer to employees; from 21 October a staffer answers in hours and the bot covers out of hours. The AWB line keeps human transfer on request in hours and can take out-of-hours leaf/brush registrations for email handoff to staff. Multilingual support (100+ languages) is an explicit test objective. The test is labelled open-ended; personal contact is to be complemented, not replaced. Feedback via end-of-call prompt or email. Why now: on the 18 October edition date the city is mid-test (phase-one no-transfer window still active through 20 Oct), and the source is new to the archive.

Why it matters

Documents an unusually explicit experimental design—full bot takeover of a city switchboard with no human transfer for nine days—plus a utilities line that keeps transfer, offering a rare controlled contrast for voice-bot risk appetite.

Evidence and measured results

Municipal news page opened in full via curl and read in German. No interim metrics published; results promised after 25 October.

Limitations and uncertainty

Pre-results press release; phase-one design intentionally removes human transfer, raising accessibility risk for complex or urgent needs during 12–20 Oct. No accuracy metrics yet.

Put this evidence to work

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

Sales

Role takeaway
Customer problem
Cities want after-hours and multilingual phone access without staffing every line continuously.
Stakeholders
  • Digitalisation lead
  • IT
  • Switchboard manager
  • Waste utility operations
  • Communications
  • Elected members
Discovery questions
  • Is a temporary no-transfer window acceptable?
  • Which lines must always allow human escape?
  • What seasonal spikes (e.g., leaf collection) justify a voice pilot?
  • How will success be measured before permanence?
Value hypothesis
Voice-bot may raise after-hours containment on FAQ and seasonal utility questions; no results published yet.
Potential engagement
Two-week voice pilot on one utility hotline with mandatory transfer-on-request and published metrics.
Unsupported claims
  • Improved reachability as a proven outcome
  • Multilingual accuracy
  • That personal contact is preserved during phase one

Pre-sales engineering

Role takeaway
Fit
FAQ and structured seasonal intake where the web chatbot knowledge base is already trusted.
Architecture and integration
PBX routing to voice-bot; shared knowledge base; email handoff for registrations; feedback capture.
Prerequisites
  • Stable web chatbot content
  • Call-recording / consent policy
  • Feedback channel staffing
Constraints
  • Phase-one no human transfer
  • Telephony ASR/TTS quality
  • German accessibility expectations
Security
Define retention of voice audio and transcripts; limit PII in registration capture.
Proof of value
  • Containment and transfer rates by phase
  • Complaint volume during no-transfer window
  • Multilingual sample tests

Delivery

Role takeaway
Work
Execute livetest, monitor, collect feedback, evaluate permanence after 25 October.
Dependencies
  • Digitalisation office
  • IT/PBX
  • Switchboard staffing plan
  • AWB operations
Ownership
Joint: digitalisation office, municipal IT, switchboard and AWB.
Skills and adoption
Supervisors reviewing transcripts and updating knowledge base from feedback.
Governance checkpoints
  • Pre-test public notice of no-transfer window
  • Mid-test check on 21 October phase change
  • Post-test permanence decision with metrics
Acceptance criteria
  • Proposed: phase metrics published before permanence
  • Proposed: accessibility review of stranded-call risk
  • Proposed: AWB transfer-on-request verified in hours
Risks
  • Stranded callers in phase one
  • Multilingual failures
  • Unclear recording consent
  • Decision to permanent without evidence

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?

Same knowledge base as the web chatbot powering a telephony voice-bot via the existing phone plant; AWB registrations captured by voice then emailed to staff.

Governance

Who approves, reviews and stays accountable for outcomes?

Digitalisation office, IT, switchboard and AWB jointly run an open-ended test with public feedback before any permanence decision.

Security and privacy

What data, permissions and controls need testing?

Voice capture of leaf/brush registrations and general questions; retention and recording policy not stated on the page.

Accessibility and workforce

Who is affected, and what skills or accommodations follow?

Tests out-of-hours and multilingual access; phase-one switchboard users cannot reach a person—material accessibility constraint during the test window.

Procurement

What should contracts, pricing and exit terms secure?

Extension of an existing chatbot capability to voice; vendor and cost not named.

Operating model

Which teams own the service once it runs?

Two contrasting operating modes (no-transfer vs transfer-on-request) in parallel on different numbers for the same two-week window.

Publication history

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

Stable resource ID: bergisch-gladbach-de-maehnfred-voicebot-livetest-20261012