Cyngor Gwynedd (Wales) retires 16-server phone system for Webex Calling and Contact Center, reports 175,000 calls a month at 76% answer rate, and begins exploring AI agents (vendor case study)

Cyngor Gwynedd (Gwynedd Council), with Cisco and partners Boxxe and Gamma · Local government (UK county council): citizen contact, social care, highways, education services · Gwynedd, north-west Wales, United Kingdom; U.S. transferability limited

Cisco

Publisher: Webex Blog (Cisco)
Original publication: November 9, 2026
Source retrieved: 2026-11-10

Read original source

What happened

Cisco reports that Gwynedd Council replaced a decade-old, 16-server on-premises telephony system with Webex Calling, Webex Contact Center, Cisco devices and Control Hub, integrated Cisco Call for Microsoft Teams for 1,700 users, and localized the Webex app, Control Hub and desk phones in Welsh. It now manages 175,000 calls a month at a 76% answer rate. AI is at an early stage: the council is exploring AI-driven agents and citizen self-service through workshops with 50 employees across education, social care, highways and other departments.

Why it matters

A concrete local-government example of the cloud contact-center foundation that precedes AI agents, including mobile field staff (social workers, highways crews) and language access. For U.S. counties and cities, the relevant lesson is sequencing (platform consolidation and live contact-center data before AI self-service) and language-access design; there is no AI outcome evidence yet.

Evidence and measured results

Vendor case study with council quotes. Reported metrics: 175,000 calls/month, 76% answer rate, 16 servers retired, 1,700 Teams-integrated users. No pre-migration answer rate, cost, staffing or resident satisfaction baseline is provided; AI work is exploratory.

Limitations and uncertainty

Vendor-authored marketing; no baseline for the 76% answer rate; UK procurement and regulatory context; AI agents not yet deployed, so no AI benefit claims are supported.

Put this evidence to work

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

Sales

Role takeaway

Customer problem: Rural or dispersed local governments miss resident calls to mobile staff, run fragmented legacy telephony, and must serve residents in more than one language.
Stakeholders: County/city CIO
Contact-center or 311 manager
Social services and public works directors
Language access coordinator
Finance
Discovery questions: What is your current answer rate and how is it measured?
How many legacy telephony servers or sites do you maintain?
Which languages must your phone and digital channels support?
Are field staff reachable from their desk numbers today?
Which departments want AI self-service first?
Value hypothesis: Consolidating telephony and contact center into one cloud platform could reduce maintenance effort and improve reachability, creating the data foundation for later AI agents.
Potential engagement: A contact-center modernization and AI-readiness assessment, including baseline metrics and a language-access review.
Unsupported claims: Any AI-driven improvement (none deployed yet)
A specific answer-rate improvement (no baseline given)
Cost savings figures

Pre-sales engineering

Role takeaway

Fit: Fits local governments on aging on-prem telephony with Microsoft Teams in use and mobile field workforces.
Architecture and integration: Webex Calling and Contact Center integrated with Microsoft Teams via Cisco Call; devices and admin in Control Hub; mobile app for field staff.
Prerequisites: Telephony inventory and number porting plan
Teams licensing
Language localization requirements
Contact-center KPI baseline
Constraints: UK case; U.S. carrier, E911 and procurement rules differ
Localization availability varies by language
No AI components deployed yet
Security: Protect call recordings and transcripts containing social care and education data; define retention and access controls before AI analytics.
Proof of value: Measure answer rate and missed calls for field staff before and after migration
Test localized interfaces with native-speaker staff
Confirm live contact-center dashboards drive staffing decisions within a pilot period

Delivery

Role takeaway

Work: Telephony and contact-center migration, legacy server retirement, localization, and AI use-case discovery workshops.
Dependencies: Carrier and partner engagement
Teams environment
Department participation in workshops
Ownership: County/city IT infrastructure team owns platform; contact-center manager owns service metrics.
Skills and adoption: Staff adopt calling within Teams; supervisors learn live analytics; departments learn to frame AI use cases.
Governance checkpoints: Baseline metrics captured before cutover
Language-access review
AI use-case prioritization review
Acceptance criteria: Proposed: baseline and post-migration answer rate reported with consistent definition
Proposed: all legacy servers retired on schedule
Proposed: AI use cases documented with owner and data source
Risks: No baseline undermines value claims
Localization gaps
AI expectations outrun readiness

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?

Cloud calling and contact center integrated into Microsoft Teams via Cisco Call; centralized management in Control Hub; live contact-center analytics; mobile app for field staff. This is the data and channel layer AI agents would later sit on.

Governance

Who approves, reviews and stays accountable for outcomes?

Language standards (Welsh Language Standards) drove localization requirements; U.S. analogues are language-access obligations (e.g., Title VI LEP guidance) that AI self-service will also need to meet. AI use-case selection is being done through cross-department workshops.

Security and privacy

What data, permissions and controls need testing?

Contact-center recordings and transcripts for social care and education calls contain sensitive personal data; any future AI agents will need data-handling and retention controls. Not discussed in the source.

Accessibility and workforce

Who is affected, and what skills or accommodations follow?

Welsh-first localization across interfaces and mobile reachability for field staff are the central workforce and access gains; AI self-service planning includes frontline departments.

Procurement

What should contracts, pricing and exit terms secure?

Delivered through partners Boxxe and Gamma; U.S. agencies would procure via state contracts or cooperative vehicles, with language localization as an explicit requirement.

Operating model

Which teams own the service once it runs?

Shift from retrospective reports to live contact-center visibility for staffing; IT time moved from server maintenance to service improvement (self-reported).

Publication history

2026-11-09Cisco · Issue 106 resources

Read preserved resource versions (JSON)

Stable resource ID: cyngor-gwynedd-webex-calling-contact-center-welsh-first-ai-agents-exploration-20261109