The Analyzer field names that must not be quoted alone
Verified 2026-09-15 · 9 claims · sources tier 2
Also known as Abandoned Type, Activity Span, Channel Type, Handle Type.
In Cisco Webex Contact Center Analyzer appendix tables, Twelve Analyzer field names are about a different subject or state incompatible things across tables 9. These Twelve Analyzer field names include Abandoned Type, Activity Span, Channel Type, Current State, Handle Type, Is Within Service Level, Number of Opt-outs, Reason, Transfer Count, Second Team ID, Second Team Name, and Agent Skills 9.
Conflicting definitions across repositories
Across the appendix tables, several fields change their underlying calculation, units, actor, or valid values depending on the repository queried 65341.
Is Within Service Level is stated to be calculated on the first queue in the Customer Session Repository and on the last queue in the Queue Record 6. Handle Type takes 3 values in the Customer Session Repository, including short, and 5 values in the Queue Record, which do not include short 5. Channel Type is described as the number of media channels agents are logged in to in the Customer Session Repository, but as the media type of the contact in 3 other tables 3.
Other fields switch between describing a contact and describing an agent 41. Current State and Reason describe the contact in the Customer Session Repository and the Queue Record, but describe the agent in the Agent Session Repository 4. Activity Span is defined as milliseconds of customer engagement in the Customer Session Repository, but as seconds of agent engagement in the other 4 tables 1.
Name counts and census patterns
Field reports suggest that Second Team ID and Second Team Name each appear in 2 appendix tables, placing the swapped pair inside the shared-name census rather than outside it 7.
In the field, a reproducible recount finds 12 names in the subject and contradiction classes where the corpus recorded 16, and the 16 cannot be checked because its members were never listed 8. Additionally, field reports suggest that a recount matching the whole first cell finds 137 field names in more than 1 appendix table and 86 with differing descriptions where the corpus holds 136 and 87 2.
See also
See also How much the Analyzer field name collisions matter.
Applicability
Across the claims in this article, the evidence covers Cisco Webex Contact Center, verified as of 2026-09-15. The deployment model is not covered by any claim in this article.
What remains uncertain
Which service level figure Cisco reports when a call passes through more than 1 queue is not covered by any claim in this article. The members of the 16 unquotable names the corpus recorded in tranche 020 is not covered by any claim in this article. How many names carry identical descriptions and different data types is not covered by any claim in this article.
See also
Part of
- How much the Analyzer field name collisions matter — The members of the count that classification produced
Related to
- What the Customer Session Record carries — Where the service level disagreement sits
- Which record type each Analyzer report draws on — The names that make an unattributed figure dangerous
Claims
| # | Claim | Status | Confidence | Verified |
|---|---|---|---|---|
| 1 | Activity Span is milliseconds of customer engagement in the Customer Session Repository and seconds of agent engagement in the other 4 tables. Cisco Webex Contact Center Analyzer User Guide · Appendix, Activity Span across all 5 tables | fact | 0.90 | 2026-09-15 |
| 2 | A recount matching the whole first cell finds 137 field names in more than one appendix table and 86 with differing descriptions where the corpus holds 136 and 87. Cisco Webex Contact Center Analyzer User Guide · Appendix, the 5 tables compared by exact field name across 603 rows | field-pattern | 0.90 | 2026-09-15 |
| 3 | Channel Type is described as the number of media channels agents are logged in to in the Customer Session Repository and as the media type of the contact in 3 other tables. Cisco Webex Contact Center Analyzer User Guide · Appendix, Customer Session Repository against the Agent Session Agent Activity and Queue tables, Channel Type | fact | 0.90 | 2026-09-15 |
| 4 | Current State and Reason describe the contact in the Customer Session Repository and the Queue Record and the agent in the Agent Session Repository. Cisco Webex Contact Center Analyzer User Guide · Appendix, Current State and Reason across the Customer Session Agent Session and Queue tables | fact | 0.90 | 2026-09-15 |
| 5 | Handle Type takes 3 values in the Customer Session Repository including short and 5 in the Queue Record which do not include short. Cisco Webex Contact Center Analyzer User Guide · Appendix, Customer Session Repository and Queue Record, Handle Type | fact | 0.90 | 2026-09-15 |
| 6 | Is Within Service Level is stated to be calculated on the first queue in the Customer Session Repository and on the last queue in the Queue Record. Cisco Webex Contact Center Analyzer User Guide · Appendix, Customer Session Repository and Queue Record, Is Within Service Level | fact | 0.90 | 2026-09-15 |
| 7 | Second Team ID and Second Team Name each appear in 2 appendix tables so the swapped pair is inside the shared-name census rather than outside it. Cisco Webex Contact Center Analyzer User Guide · Appendix, Customer Activity Repository and Queue Record, Second Team ID and Second Team Name | field-pattern | 0.90 | 2026-09-15 |
| 8 | A reproducible recount finds 12 names in the subject and contradiction classes where the corpus recorded 16; the 16 cannot be checked because its members were never listed. Cisco Webex Contact Center Analyzer User Guide · The tranche 020 classification against the tranche 023 recount | field-pattern | 0.90 | 2026-09-15 |
| 9 | Twelve Analyzer field names are about a different subject or state incompatible things in different appendix tables: Abandoned Type Activity Span Channel Type Current State Handle Type Is Within Service Level Number of Opt-outs Reason Transfer Count Second Team ID Second Team Name and Agent Skills. Cisco Webex Contact Center Analyzer User Guide · Appendix, the 5 tables the guide introduces as the Customer Session Customer Activity Agent Session Agent Activity and Queue repositories | fact | 0.90 | 2026-09-15 |
Sources
Cisco Webex Contact Center Analyzer User Guide
Cite this page
APA
WarmTransfer. (2026, September 15). The Analyzer field names that must not be quoted alone. WarmTransfer. https://warmtransfer.net/knowledge/wxcc-analyzer-unquotable-field-names
BibTeX
@misc{warmtransfer-wxcc-analyzer-unquotable-field-names,
title = {The Analyzer field names that must not be quoted alone},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/wxcc-analyzer-unquotable-field-names},
note = {Verified 2026-09-15}
}