If you manage call queues in Microsoft Teams or Webex, you probably know how a call starts. What’s harder to see—yet far more important—is what happens next.
How many times was it transferred? Did it bounce between queues? Was it forwarded externally? Was it ultimately answered, abandoned, or redirected? For many organizations, that full journey remains invisible. That’s where cradle-to-grave visibility changes everything.
The blind spot in native queue reporting
Native queue reporting tools provide useful metrics — calls answered, calls abandoned, average wait time, talk time — but they’re snapshots of a small part of the story.
What they don’t reliably show is the complete journey from start to finish:
- How a caller moved between queues, attendants, and agents
- Whether a transfer loop occurred
- If the call was forwarded — and where
- Where the call actually ended (final action, final destination)
Until recently, teams had to piece these patterns together manually using fragmented logs and screenshots. That’s time-consuming and unreliable — especially in mission-critical, high-volume environments.
Transfer Path visibility in ISI Queue Analytics
With Transfer Path now available for both Microsoft Teams and Webex Customer Assist and Customer Assist Queues, administrators can see a call’s complete journey — from origination to resolution — without manual tracing. As noted in the recent release notes, the Microsoft Teams Queue Dashboard now supports drilling into a single call’s details to view “all existing information and the full call transfer path,” enabling better operational insight and faster root-cause analysis.
The workflow is straightforward. From the queue activity view, administrators can drill into a single call and follow its full lifecycle—from entry point to final resolution. The screenshots below illustrate how this investigation unfolds.
How it works in practice
In the Queue Detail preview, each call appears as a row in an on-screen preview. Clicking the drill-down icon opens a detailed “Call Details” panel, organized into three sections:
- Each call in the queue activity view can be opened to reveal detailed call-level insight
Call Origination
- Original start time
- Call direction
- Caller phone number and ID
- Original destination (e.g., auto attendant or routing point)
Leg Details
This is where the operational story unfolds — showing how the call progressed through the system:
- Start time, source, and destination
- Wait time and disposition
- Handling action and handled by
- Answer time, talk time
- Final action and final destination
Call Completion
A compact summary confirms how the call ended — final interaction time, transfer depth, final action, final destination, and releasing party.
- The Call Details panel provides immediate visibility into call origination, queue interaction, and how the call ultimately concluded.
Transfer Path — see the complete journey
The Transfer Path tab presents each transfer step in sequence, including:
- Transfer Path reveals every step of the caller’s journey—from initial entry through each transfer until the call is completed.
- Source and destination
- Wait time
- Handling action
- Handled by
- Talk time
- Final action and final destination
If a call was transferred twice, you see both transfers.
If it looped between queues, that pattern is visible.
If wait time occurred after initial answer, you see it.
There is no manual tracing required.
Case Study: Regional Hospital System
A large regional hospital system began receiving complaints from patients and families who said they were being transferred multiple times before reaching the right department.
Supervisors could see high-level metrics — but they couldn’t explain what was happening during transfers.
Leadership asked:
“Are callers waiting too long in the queue — or are they being transferred after they reach someone?”
What Transfer Path Visibility Revealed
By drilling into full call journeys, the team discovered:
- Transfer loops between the main auto attendant and scheduling
- Hidden wait time occurring after initial queue answer
- Outdated routing logic misdirecting specific call types
- Certain specialties consistently requiring multiple handoffs
Operational Improvements
Using these insights, the hospital system:
- Updated auto attendant routing logic
- Reduced unnecessary inter-department transfers
- Lowered average handling time
- Improved first-touch resolution
- Gained documented insight into caller experience
Within three months of refining routing based on Transfer Path analysis, the organization reduced multi-transfer calls by 22% and decreased average handling time by 14% in affected departments.
Instead of relying on anecdotal complaints, supervisors could validate exactly what happened to each call.
The result was not just improved metrics — but a smoother patient experience.
Why Transfer Path visibility matters operationally
- Faster root-cause analysis: Validate caller experiences in minutes, not hours.
- Routing optimization: Identify and eliminate unnecessary handoffs.
- Staffing insight: Understand where calls are actually resolved.
- Audit and compliance support: Documented call journeys reduce reporting friction.
- Cross-platform consistency: Standardize queue intelligence across Microsoft Teams and Webex Customer Assist.
This is more than reporting.
It is operational clarity.
Beyond metrics: true queue intelligence
Queue reporting shouldn’t just tell you how many calls were answered. It should tell you what happened — from entry to resolution. That’s the purpose of cradle-to-grave visibility: transparency, accountability, and faster operational improvement without manual detective work.
To explore the latest product updates, visit the ISI Analytics release notes.