Get Ring Groups Summary report

Aspect	Ring Group Summary	Extension Summary
Perspective	Group-level activity	Extension-level activity
What it counts	Calls processed within the group	Calls that touched the extension
Scope	Single group boundary	Entire call journey (multi-group)
Use case	Team performance metrics	Extension usage for each agent
Transfers counted	Only if finalized in that group	Yes, all routing stages

Ring Group Summary report

What it shows: How a specific Ring Group handled the calls that reached and were processed within that group.

Think of it as: "What happened INSIDE this group?"

Key Metrics:

• Total Calls: Calls that reached the group
• Answered: Calls answered by group members.
• Missed: Calls that rang but were not answered in this group.
• Abandoned: Calls ended by the caller while in this group.
• Voicemail: Calls sent to group voicemail.

Use this report to:

• Measure group responsiveness
• Track answered vs. missed rates
• Monitor abandonment trends

Extension Summary report

What it shows: A complete view of all interactions at the extension level, for both Ring Groups and individual users

Think of it as: "Which calls TOUCHED this extension?"

What it includes:

• Direct calls to the extension
• Routed calls through a Ring Group the extension is part of.
• Arrived from another Ring Group or Auto Attendant (AAAuto Attendant is an automated receptionist service that directs callers to the desired destination.)
• Auto-forwarded or redirected when unanswered.
• Transferred (warm or cold), either within or outside the same Ring Group.
• Calls routed back to the same group after other routing attempts.

Use this report to:

• Track agent activity in complex flows
• Audit call involvement
• Analyze call volume across routing paths

Even when analyzing the same call, totals may vary between reports. That is expected and both reports are accurate and complementary. Because they look at calls from different angles — one focusing on group activity, the other on the whole call path — their totals and results will often be different.

	Ring Group Summary	Extension Summary
What it reflects	What happened inside the group	All interactions with the extension
Focus	Inside the group	Full call journey across entities
What it counts	Each group-level call entry	Each unique call that touched extension
Lens	Group performance	Call journey

Common Scenarios: Why totals may differ

Scenario 1: Transferred Between Groups

A call may appear in both reports, but with different outcomes:

• Ring Group 1: Missed - the call was not answered in RG1
• Ring Group 2: Answered - the call was transferred and completed in RG2

Scenario 2: Auto-Forward Without Handling

The Ring Group forwarded calls automatically and didn't handle the call directly.

• Ring Group 1: No data - no processing occurred in RG1.
• Ring Group 2: Missed=1 - the call passed through that extension.
• Ring Group SummaryNot appear in the report - no processing occurred.
• Extension Summary Still appears in the report - the call passed through that extension.

When Total Calls ≠ Sum of Outcomes

In simple call flows (direct call answered or abandoned in one group), metrics usually align perfectly.

However, in scenarios involving forwards, auto-forwards, or transfers, differences may occur.

When Total Calls > Answered + Missed

Abandoned calls are a form of missed calls and should not be counted towards the total.

The group received the call, but the final action (answered or abandoned) occurred in another entity.

Scenario example:

Caller → RG1 → [no answer -> Forward] → RG2 → Agent answers

• RG1 Summary:

  • Total Calls = 1
  • Answered = 0
  • Missed = 1
  • Call left the group before completion.

• RG2 Summary:

  • Total Calls = 1
  • Answered = 1
• Why? RG1 processed the call initially, but RG2 completed it.

When Total Calls < Answered + Missed

One incoming call triggered multiple events within the same group (like repeated offers, warm transfers, or re-routing).

Scenario example:

Caller → RGRing Group is a group of extensions grouped together to share distribution of incoming calls. → Agent 1 Answers → [Cold transfers back to RG] → Agent 2 → Answers

• RG1 Summary:

  • Total Calls = 1 (one incoming call)
  • Answered = 2 (by Agent 1 initially and by Agent 2 after transfer)
• The single call generated multiple internal "call legs" (offer events) as it was handled and transferred within the group.

Call Legs Defined

A call leg is a discrete routing event within the phone system. A single incoming call can generate multiple legs:

• Initial offer to Ring Group
• Offer to Agent 1
• Transfer to Agent 2
• Forward to voicemail

Ring Group Summary: Counts events at the group level.

Extension Summary: Counts calls at the extension level, collapsing multiple legs into a single call journey.

Certain routing configurations may produce unexpected-looking results across reports. These are not errors, they accurately reflect how calls are processed by the system.

Exception 1: Auto-forward scenario

Call flow:

Caller → RG1 (auto-forward configured) → RG2 → Agent1/2 → Abandoned

Reports:

• Ring Group Summary:

  • RG1: No final metrics shown - The call auto-forwarded with no processing.

  • RG2:

    • Total Calls = 1
    • Missed/Abandoned = 1

• Extension Summary:

  • Both RG1 and RG2 are shown - The call passed through RG1's extension and was finalized in RG2.

Why the difference?:

Since RG1 auto-forwarded the call without processing it (no ringing or agent offer), it has nothing to report in the Ring Group Summary. However, Extension Summary captures all entities the call touched, including RG1’s extension number.

Exception 2: Ring Group Summary shows more calls than Extension Summary.

Call flow: (A call loops back to the same Ring Group):

Caller → RG1-> Agent of RG1 Answers -> Transfer cold to RG2 -> Agent of RG2 Answers -> Transfer cold to RG1 -> Agent of RG1 Answers

Reports:

• RG1 Summary:

  • Total Calls = 1
  • Answers = 2

• Extension Summary for RG1:

  • Total = 2
  • Answered = 2

Why?:

• Ring Group Summary logs every entry into the group as a unique event.
• Extension Summary tracks the entire call journey involving the extension, collapsing repeated entries into one call per journey.

Scenario example:

If the same call loops through RG1 three times , you may see:

• RG1 Summary: Total Calls = 3
• Extension Summary (RG1): Total Inbound = 1

Same call entered RG1 three times during complex routing.

Exception 3: Warm vs. cold transfers

• Cold Transfer: The transferring agent disconnects immediately. The call moves from one destination to another.
• Warm Transfer: The transferring agent consults with the receiving agent before completing the transfer. This creates additional call legs.

• Impact on reporting:

  • Warm transfers generate more call leg events (consultation, hold, transfer completion).
  • This may result in higher event counts in the Ring Group Summary compared to the Extension Summary.

Example 1: Simple call (Metrics align)

Call flow:

Caller → RG1 → Agent1 (answered)

Reports:

• RG1 Summary:

  • Total Calls = 1
  • Answered = 1
  • Missed = 0
  • Abandoned = 0

• Extension Summary: (Agent1, RG1)

  • Single call displayed
  • Status = Answered

Interpretation:

Metrics align perfectly across both reports: simple, single-destination call.

Example 2: Cold transfer between groups

Call flow:

Caller → RG1 → [Transfer] → RG2 → Agent2 (answered)

Visual:

Reports:

• RG1 Summary:

  • Total Calls = =1
  • Answered = =0
  • Missed = 1
  • Abandoned = 0

• RG2 Summary :

  • Total Calls = 1
  • Answered = 1

• Extension Summary: (RG1, RG2, Agent2)

  • All three extensions are recorded,

  • Call shows as transferred from RG1 to RG2,

  • Final status: Answered (in RG2)

Insight:

Metrics differ because the call was initiated but not answered in RG1 (and marked as Missed) but successfully answered and completed after transfer in RG2.

Example 3: Auto-forward exception

Call flow:

Caller → RG1 (auto-forward) → RG2 → Agent1/2 → Abandoned

Visual flow:

Reports:

• Ring Group Summary:

  • RG1 No final metrics displayed (auto-forward only)

  • RG2:

    • Total Calls = 1
    • Missed/Abandoned = 1

• Extension Summary:

  • Both RG1 and RG2 appear

  • Call path shows: RG1 → RG2

  • Final status: Abandoned in RG2

This difference is expected. Since Ring Group 1 (RG1) immediately forwarded the call, it had no group-level activity to record in the Ring Groups Summary Report. However, the Extension Summary tracks the call "touching" RG1's extension during the routing process.

Q1: Which report should I use for KPIs and performance metrics?

It depends on what you're measuring:

• For team or group performance: Use Ring Group Summary.

  • Example: How many calls did the Sales team answer?

• For individual agent activity: Use Extension Summary.

  • Example: How many calls did Agent Smith handle, including transfers?

• For complete call tracking: Use Call Detail Records (Legs).

  • Example: Where did this call go before it was answered?

Q2: Why don't the “Total Calls” match between reports?

Because each report tracks calls from a different perspective:

• Ring Group Summary counts the calls processed within that group.Each inbound call is counted only once when it initially enters the Ring Group, regardless of whether it rings multiple members or cycles back into the group multiple times.
• Extension Summary tracks all interactions with the extension.—even if the extension only touched the call briefly (e.g., a missed call, transfer, or forward).

Both reports are correct—they just reflect different scopes.

Q3: Can I reconcile the numbers between both reports?

Only in simple call flows.

In complex scenarios (such as transfers, forwards, loops), the numbers will differ. This is expected and reflects real routing behavior.

Best practice:

• Use Ring Group Summary for group performance.
• Use Extension Summary for individual activity and full call journey analysis.
• Don’t try to force alignment between the two—they’re complementary, not identical.

Q4: What’s the difference between warm and cold transfers?

Cold transfer	Warm transfer
Transferring agent disconnects immediately	Transferring agent consults first
Call moves directly to new destination	Creates consultation call leg
Fewer call leg events	More call leg events (consultation, hold, completion)
Simpler to track	Can create higher event counts in reports

Q5: Can I export both reports and merge them?

Yes, you can export both, but merging requires understanding:

• Call IDs (to match the same call across reports)
• The different perspectives each report represents
• That some calls will appear in one report but not the other (by design)

Use Call Detail Records (CDRCall Detail Record includes call details such as point of origin,end point, call direction, call duration, and more.) for granular, leg-by-leg call data.

Core principle

The Ring Group Summary and Extension Summary reports provide two valid but different perspectives on call activity:

• Ring Group Summary → How calls were handled within the group
• Extension Summary → How calls touched individual extensions, regardless of routing path

These reports may reference the same extension number but represent distinct reporting layers.

Remember the differences

Perspective	Ring Group Summary	Extension Summary
Focus	What happened inside the group	Which calls touched the extension
Lens	Group performance	Call journey / agent interaction
Best for	Team KPIs	Complete call tracking

Why numbers might differ

When call totals don't match, it's usually because:

• Calls were transferred between groups - Each group logs its own handling.
• Auto-forwards were used - Originating group may not record processing.
• Warm transfers occurred - Multiple call legs = multiple events.
• Calls looped back to the same group - Ring Group Summary counts each entry.
• Complex routing paths - Different logging points across reports.

Best practices

Use Ring Group Summary to:

• Evaluate team performance
• Measure service levels per group
• Monitor answered vs. missed within a group

Use Extension Summary to:

• Follow the complete call journey
• Track individual agent activity
• Audit all calls that involved a specific extension

Use both together to:

• Get a 360° view of call handling
• Understand both team and individual performance
• Troubleshoot complex routing behavior

If call data looks unexpected or doesn't fit known patterns:

• Reach out to your 8x8 Analytics administrator

Or

• Contact the 8x8 support team

Reminder:

• Different numbers ≠ incorrect numbers
• They reflect different, valid perspectives on the same call flow.