Modernizing voice infrastructure is a priority for many state and local government agencies. For departments running Cisco Unified Contact Center Express (UCCX), migrating to Webex Calling Customer Assist is an attractive step toward cloud flexibility, simplified operations, and long-term sustainability.
From a call-handling perspective, these migrations are often straightforward. But many agencies discover an issue immediately after cutover:
Be mindful of reporting gaps when migrating from Cisco UCCX to Webex Calling
The familiar UCCX CUIC reports—especially those tied to Contact Service Queues (CSQs)—are no longer available in the same form in Webex Calling.
For supervisors and leadership teams who rely on those reports for service-level oversight, staffing discussions, and accountability, this can feel like a step backward.
This post looks at why that gap exists, why it matters, and how agencies can plan for reporting continuity when moving to Webex Calling Customer Assist.
Why UCCX Reporting Becomes Institutional Memory
Cisco Unified Contact Center Express (UCCX) reporting is accessed through Cisco Unified Intelligence Center (CUIC), which Cisco describes as an end-to-end reporting solution for Unified CCX with access to Historical and Live Data reports. CUIC further supports operational reporting workflows such as dashboard creation and scheduled report execution.
Over time, CSQ-based reports become embedded in weekly and monthly workflows:
- How many calls were answered vs. abandoned by queue?
- Are we meeting service-level expectations?
- Where are callers waiting the longest?
- How is agent workload distributed throughout the day?
Supervisors, finance teams, and executives often build staffing models, performance scorecards, and budget narratives around these definitions. When an agency migrates away from UCCX, those expectations do not disappear just because the platform changes.
Cisco’s own CUIC reporting includes CSQ-focused live and historical reporting concepts, such as agent CSQ statistics and CSQ activity reporting.
What Changes with Webex Calling Customer Assist
Webex Calling Customer Assist modernizes call handling by shifting queues and agent workflows into a cloud-managed model. Cisco positions Customer Assist as a way to add contact-center capabilities such as queue management, analytics, and reports. Agents and supervisors access Customer Assist features in the Webex App, with several real-time/historical and supervisor capabilities delivered primarily through the Webex App desktop client.
However, the reporting model and report set in Customer Assist differ from CUIC-based UCCX reporting. Because CUIC’s stock reports are specific to UCCX (for example, CSQ Activity and Agent CSQ Statistics), agencies should expect the report set and metric presentation in Customer Assist to be different. Customer Assist provides its own built-in reports (such as call queue status, agent status, wrap-up reason, and real-time/historical agent/queue views).
As a result:
- CSQ-centric reporting conventions don’t automatically carry forward
- Metric names and drill-through depth may differ from CUIC expectations
- Leadership still expects the same service-level answers they had before
This creates a common post-migration pattern: the migration is technically successful, but reporting questions immediately flow back to Voice teams, IT, and partners.
- Plan reporting upfront, not after go-live.
What Carries Forward When Moving to Webex Calling Customer Assist
For agencies familiar with UCCX, Customer Assist retains many of the operational constructs teams rely on—while simplifying administration in a cloud model.
- Call queues and routing patterns are supported in Customer Assist, including overflow/timeout, business hours, and holidays.
- Agent participation remains a core part of the workflow in the Customer Assist model, accessible in the Webex App.
- Supervisor functions such as monitoring workflows exist within the intended scope of Customer Assist.
The net effect: many agencies keep familiar operational motions (queues, auto attendants, agent participation), but with fewer moving parts than a full contact center stack.
Where Reporting Expectations Diverge Between UCCX and Webex Customer Assist
The friction typically appears in reporting continuity and depth between UCCX to Webex Customer Assist. CUIC became institutional memory for many public sector teams: shared scorecards, CSQ-centric views, and the ability to self-serve routine operational questions.
Customer Assist provides basic visibility, including real-time and historical data views for agents and queues.
But agencies should validate early how those views map to existing CUIC-based expectations:
- Queue-level KPI mapping: how queue metrics align to the CSQ-centric reporting teams are used to
- Drill-through depth: how easily managers can move from summary KPIs to supporting detail
- Reporting windows: how historical access aligns with leadership review cycles (monthly, quarterly, fiscal-year)
These differences don’t diminish Customer Assist’s strengths; instead, they highlight the importance of treating reporting continuity as part of the migration plan rather than a post‑cutover cleanup project.
Call Reporting Features You’ll Keep, Gain, and Should Plan For
The table below summarizes common expectations agencies bring into a migration and how those expectations typically shift when moving from CUCM/UCCX to Webex Calling Customer Assist.
(Cisco: Call Queue vs Customer Assist Feature Comparison;
UCCX Live Data Reports)
| Area | CUCM (basic routing only)* | CUCM + UCCX (with CUIC) | Webex Calling Customer Assist | Notes for Migration Planning |
|---|---|---|---|---|
| Call Routing Basics | Hunt groups, basic routing | Advanced routing via UCCX | Cloud queues; overflow/timeout; business hours; holidays | Operational constructs remain familiar; scripting complexity is reduced. |
| Auto Attendants (IVR) | Varies (depends on adjunct IVR/AA tools; CUCM-native routing is limited) | Robust via UCCX | Native auto attendant features with common patterns | Most public sector patterns are supported without custom code. |
| Agent Participation / Status | Limited | Robust | Supported (cloud model) | Map existing workflows and status conventions during cutover. |
| Supervisor Monitoring | Possible (call monitoring/barge features vary by deployment; not queue-aware like UCCX) | Available in UCCX | Supported within Customer Assist scope | Validate features and policies early to avoid surprises. |
| Queue-Level (CSQ-Style) KPIs | No | Yes (CSQ) | Partial; not CUIC one-for-one | Expect differences in metric definitions and drill-down depth. |
| Historical Analytics / Trends | Limited | Strong via CUIC | Essential historical views available | Validate how historical access aligns to monthly/quarterly/fiscal-year needs. |
| Role-Based Dashboards | No | Common in CUIC | Basic agent/supervisor views | Determine who needs which view and whether native roles suffice. |
| Ad-Hoc Call Journey Search | Not built-in for queue journeys | Often possible via CUIC/custom | Limited | Confirm needs for end-to-end journeys (AA → Queue → Agent → Transfer). |
| Compliance / Audit Support | Varies | Often addressed via CUIC + policy | Requires policy alignment | Ensure reporting windows and audit needs are addressed during planning. |
| Operational Overhead | On-prem maintenance | Higher (contact center stack) | Lower (cloud-managed) | One key benefit is reduced infrastructure complexity. |
*Capabilities vary based on adjunct applications and licensing.
Key changes to understand:
- Keep: Similar operational motions (queues/auto attendants/agent participation) with a simpler admin model.
- Gain: Cloud management, lower overhead, and fewer moving parts.
- Change: CUIC-level depth and CSQ-centric conventions may differ unless specifically planned for.
Why Call Reporting Gaps Create Real Risk for Agencies
For state and local agencies, reporting gaps are more than an inconvenience. They can impact:
- Service-level accountability
- Staffing justification and workforce planning
- Leadership confidence in operational data
- IT and Voice teams, who become ad hoc reporting resources
When reporting isn’t addressed upfront, agencies are often forced into difficult choices: accept reduced visibility, invest in custom reporting, or deploy a full contact center platform solely to regain insights they previously had.
“When agencies migrate platforms, call handling is only half the story. The real continuity challenge is reporting. If supervisors can’t answer the same operational questions the day after go-live, the migration never feels complete. Planning for reporting upfront eliminates that risk.”
— Chris Welch, VP Sales & Strategic Alliances, ISI Analytics
ISI Analytics offers a fourth option — purpose-built queue reporting for Webex Calling environments that closes the visibility gap without the cost or complexity of a full contact center deployment.
Planning for Reporting Continuity from Webex (Without Turning It Into a Full Contact Center)
A practical approach is to treat reporting continuity as a first-class requirement alongside call flows and cutover logistics.
- Inventory your “day after” questions. Which CUIC/CSQ views are essential for supervisors and leadership?
- Define retention and audit windows. Quarterly reviews? Fiscal-year trends? Public records requests?
- Map Customer Assist capabilities to those needs. Identify where the fit is strong and where it differs.(Cisco: Customer Assist for Supervisors)
- Validate early in a pilot/parallel period. Align terminology and expectations before go-live.
Bridging the Reporting Gap with ISI Analytics
Many agencies moving from UCCX to Customer Assist find that native reporting covers the essentials — but falls short of the CSQ-level depth, historical retention windows, and role-based dashboards their supervisors and leadership teams rely on.
ISI Analytics is designed specifically for this scenario. Built for Webex Calling environments, ISI extends Customer Assist with queue-level reporting, cradle-to-grave call journey visibility, unlimited data retention, and scheduled report delivery — without requiring a full contact center deployment.
For public sector agencies, that means supervisors can answer the same operational questions the day after go-live that they were answering the day before. Finance teams keep their trend data. Leadership keeps their scorecards. IT stops fielding one-off reporting requests.
[ Explore ISI Analytics for Webex Calling ]
Note: Customer Assist documentation indicates public APIs are not supported in the current phase, which limits certain custom integration approaches. ISI’s cloud-based connection model works within Webex’s existing data access framework, so this doesn’t affect ISI’s ability to collect and report on your queue data.
Designed for Government Operating Models
Many state and local agencies operate departmental contact centers often ranging from dozens to a few hundred agents, where simplicity and accountability matter more than advanced omnichannel features. A Customer Assist-based approach supports that reality by:
- Preserving familiar call-handling constructs without UCCX dependencies
- Avoiding heavy custom report development
- Reducing operational overhead for Voice and IT teams
- Avoiding the need to deploy a full contact center platform solely for reporting
The result is continuity: supervisors retain the visibility they rely on, leadership maintains confidence in service-level data, and IT avoids becoming a reporting bottleneck.
Making the Migration Count
Migration success isn’t just measured at cutover — it’s measured by whether supervisors and leadership can answer the same operational questions the day after.
Webex Calling Customer Assist modernizes call handling in a lightweight package. But reporting continuity doesn’t happen automatically. Agencies that plan for it upfront avoid the common post-migration pattern of IT fielding one-off reporting requests while leadership loses confidence in service-level data.
ISI Analytics is built for exactly this moment — extending Webex Calling with the queue-level depth, historical retention, and role-based reporting your teams already rely on.
Ready to talk through your reporting requirements before go-live? Contact ISI →
(Cisco: Webex Calling Customer Assist)