Saudi HRSD reports in-house Webex Suite/Calling migration to 11,000+ users with custom device monitoring and Virtual Branch citizen services

Cisco Webex / Saudi Ministry of Human Resources and Social Development (HRSD) · National government workforce and social services collaboration modernization (international) · Saudi Arabia (international); transferability caveats for U.S. SLED

Cisco

Publisher: Webex Blog
Original publication: November 5, 2026
Source retrieved: 2026-11-07

Read original source

What happened

Webex’s Nov. 5 customer story says Saudi Arabia’s HRSD migrated calling, meetings and messaging from on-prem to Webex Suite and Webex Calling for 11,000+ users (~28% growth from ~8,600), with 662,900 meetings and 20.8M meeting minutes (Sep 2025–Sep 2026) and 400,000+ calls/month. HRSD’s in-house team executed the migration without an external implementer and built a custom API monitoring/backup engine for Cisco collaboration devices. Virtual Branch extends Webex to remote beneficiary services. AI Assistant transcription/translation is under cybersecurity review; Webex Contact Center is being tested pending local availability. Story won a 2026 Webex Customer Award (Bold Explorer: Government & Public Sector).

Why it matters

Illustrates government collaboration cloud migration, citizen-facing virtual services and in-house delivery capacity. U.S. SLED applicability is limited by jurisdiction (FedRAMP/Webex for Government, records retention, accessibility and procurement differ). Treat metrics as vendor-reported international evidence with transferability caveats, not U.S. agency results.

Evidence and measured results

Vendor blog with attributed HRSD quotes (Rashed Alzannan) and quantitative usage claims; no independent audit of uptime, cost savings or citizen outcomes.

Limitations and uncertainty

International vendor story; cost predictability claims lack dollar figures; AI and Contact Center still evaluative; not a U.S. SLED deployment.

Put this evidence to work

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

Sales

Role takeaway

Customer problem: Government collaboration stacks are siloed on aging on-prem systems that block hybrid work and citizen digital services.
Stakeholders: CIO
collaboration/network lead
citizen services owner
cybersecurity
procurement
Discovery questions: Is Webex for Government already authorized in your environment?
Who must approve AI transcription/translation?
Do you need partner delivery or can in-house teams lead?
Value hypothesis: A unified cloud suite plus device monitoring may improve continuity and citizen reach; HRSD metrics are vendor-reported and non-U.S.
Potential engagement: A government collaboration migration readiness workshop scoped to one agency unit and compliance boundary.
Unsupported claims: U.S. SLED cost savings matching HRSD
Guaranteed 28% adoption lift
AI features cleared for production

Pre-sales engineering

Role takeaway

Fit: Fit for agencies standardizing on Webex cloud calling/meetings; Saudi architecture details are incomplete for direct copy.
Architecture and integration: Webex Suite, Webex Calling, Cisco collaboration devices, Control Hub, customer-built API monitoring/backup; AI Assistant and Contact Center evaluative.
Prerequisites: Authorized government cloud tenancy
Identity and dial-plan design
Device inventory and PoE/network readiness
Cyber review path for AI features
Constraints: International reference only
No independent verification
Contact Center local availability pending in story
Records/e-discovery rules differ by jurisdiction
Security: Story emphasizes cyber review before AI features; U.S. deployments must satisfy FedRAMP and agency privacy overlays separately.
Proof of value: Pilot user experience scores
MTTD for device issues via monitoring API
Meeting/call quality metrics vs baseline
Documented cyber decision on AI features

Delivery

Role takeaway

Work: Migrate a defined user cohort to Webex cloud, deploy devices and stand up proactive monitoring.
Dependencies: Carrier/numbering
Endpoint staging
Training and change sponsorship
Cybersecurity approvals
Ownership: Ministry/agency collaboration operations owns platform; cyber owns AI feature gates; citizen services owns Virtual Branch processes.
Skills and adoption: Build in-house Webex administration and API automation skills; avoid sole reliance on external implementers if capacity exists.
Governance checkpoints: Security ATO/delta
Records retention for recordings
Accessibility review
Citizen-services privacy assessment
Acceptance criteria: Cutover complete for pilot org unit
Monitoring alerts before user tickets
Adoption targets with training evidence
Written AI feature go/no-go
Risks: Transferability overclaim to U.S. SLED
Underestimated compliance
Device configuration drift without monitoring
AI features delayed by security

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?

Unified Webex cloud plus collaboration devices and Control Hub, extended by customer-built API monitoring; AI features gated by security review.

Governance

Who approves, reviews and stays accountable for outcomes?

Recorded meetings growth (>80%) and analytics (Verint) support governance/review; AI transcription/translation awaiting cyber approval—model for SLED change control.

Security and privacy

What data, permissions and controls need testing?

National security/regulatory review of AI features is acknowledged; U.S. agencies must map to FedRAMP Webex for Government and privacy/records rules separately.

Accessibility and workforce

Who is affected, and what skills or accommodations follow?

Virtual Branch and planned translation aim to reduce barriers for beneficiaries and hybrid staff; no formal accessibility audit is presented.

Procurement

What should contracts, pricing and exit terms secure?

In-house migration without a partner may not match U.S. SLED staffing or contract vehicles; confirm Webex for Government SKUs and device lifecycle funding.

Operating model

Which teams own the service once it runs?

Shifts CapEx refresh cycles toward cloud OpEx and frees IT from on-prem PBX maintenance toward platform engineering and custom monitoring.

Publication history

2026-11-06Cisco · Issue 095 resources

Read preserved resource versions (JSON)

Stable resource ID: webex-saudi-hrsd-cloud-migration-virtual-branch-20261105