CDR Plus Disposition Extended Report

Required permissions: Data Download

The CDR Plus Disposition Extended report provides the most comprehensive interaction dataset available in the Data Download suite. It includes every field found in the CDR Plus Disposition Expanded Report, supplemented by high-priority metrics for custom variables, agent refusals, and interaction flow.

By consolidating data that previously required cross-referencing multiple reports (such as the 501 Report for Variables and the Agent Refusal Report), the Extended report serves as a single, unified source for deep-dive contact analysis.

Key Enhancements

In addition to all standard Expanded metrics, this report includes:

  • Consolidated Custom Data: Surfaces Studio script variables directly within the contact record.

  • Detailed Refusal Analytics: Provides the specific reasons and timestamps for agent refusals.

  • Interaction Metadata: Includes the handling script name and system-level cause codes.

  • Transfer Tracking: A dedicated indicator to identify transferred interactions at a glance.

Select Report Option

You need to configure a Date Range, Start/End Time, and Export Format when you run a data download report.

Columns

This report contains all columns found in the CDR Plus Disposition Expanded Report, plus some additional fields:

Contact_ID

The unique, system-generated ID of the contact.

Master_Contact_ID

The unique, system-generated ID of the master or parent of the contact interaction. The master contact IDClosed A unique numerical identifier assigned to each contact. can be parent to many contact IDs. A new master contact ID will be assigned if a contact has been transferred two or more times.

There is a parent child relationship on all contacts that are created from the original contact. The masterId of the contact is the parent that created it, meaning for subsequent transfers from the original contact, the masterId will be the transferred contact that created it.

Contact_Code

The unique, system-generated ID of the point of contact.

Media_Name

The media type or channelClosed Various voice and digital communication mediums that facilitate customer interactions in a contact center. of the contact.

Contact_Name

The point of contact value or description, such as the phone number or email address the contact used to connect with an agent.

Contact_Type

The delivery mode of the contact, if the contact requires compliance. If ComplianceRecord is TRUE, it is one of the following:

  • None: The system does not deliver the contact because it requires compliance.
  • ClickToCall: The agent must click a button to dial contacts that require compliance.
  • ManualDialWithKeypad: The agent must manually dial contacts that require compliance.
  • ManualDialWithKeypadAutoCorrect: The agent must manually dial contacts that require compliance, but the system automatically corrects the number if the agent enters it incorrectly.
  • DialOutsideNICEinContactNetwork: The agent must call contacts that require compliance outside the platform.

Direction


The direction of the contact: Inbound or Outbound.

ANI_DIALNUM

The name of the contact, or the phone number associated with the contact.

Skill_No

The unique, system-generated ID of the skillClosed Used to automate delivery of interactions based on agent skills, abilities, and knowledge. the contact entered. This is the skill associated with the point of contact.

Skill_Name

The name of the skillClosed Used to automate delivery of interactions based on agent skills, abilities, and knowledge. that handled the interaction.

Campaign_No

The unique, system-generated ID of the campaign the skill that handled the contact belongs to.

Campaign_Name

The name of the campaignClosed A grouping of skills used to run reports. the skill that handled the contact belongs to.

Agent_No

The unique, system-generated ID of the agent who handled the interaction. If more than one agent handled the contact, it is the ID of the last agent to handle the contact.

Agent_Name

The first and last name of the agent who handled the interaction, based on the OriginalAgentID, as displayed in the agent's NiCE CXone user profile. If more than one agent handled the interaction, it is the OriginalAgentID name, who handled the interaction.

Team_No

The unique, system-generated ID of the team the agent who handled the contact belongs to.

Team_Name

The name of the team the agent who handled the contact belongs to.

SLA

A code indicating whether the contact was handled within the required SLA. It is one of the following codes:

  • -1: The contact was short abandoned and not counted toward SLA, or it never effectively entered SLA evaluation.

  • 0: An agent handled the contact within the required service level.

  • 1: An agent did not handle the contact within the required service level. This can include calls answered after SLA threshold, calls never answered, calls abandoned after short abandon threshold, and calls short abandoned and counted (if enabled).

Start_Date

The date within the specified time period on which the contact entered the system or had valid activity. It has a format of MM/DD/YYYY.

Start_Time

The time on the Start_Date at which the contact entered the system. It has a format of HH:MM:SS.

Times are shown in the time zone selected in the user's settings.

InboundPending


Either Y (yes) or N (no)

This indicates whether the agent was identified as inbound pending. Inbound pending is when the agent is waiting for an inbound call to connect.

OutboundPending


Either Y (yes) or N (no)

This indicates whether the agent was identified as outbound pending. Outbound pending is when the agent is waiting for a dialed call to connect to a contact.

PreQueue

The amount of time in seconds the contact spent in the prequeue state.

InQueue

The amount of time in seconds the contact spent in the queue.

Wait_Time


The amount of time in seconds the agent spent connected to the call waiting for the contact to answer.

Preview_Time


The amount of time in seconds the agent spent viewing preview messages prior to accepting or rejecting a contact. Only applies to preview skills.

Agent_Time

The amount of time in seconds the contact spent conversing with an agent.

Active_Talk_Time


The amount of time in seconds the contact spent conversing with the primary agent. Does not include hold time or conference time.

Conference_Time


The amount of time in seconds the contact spent in a conference.

PostQueue

The amount of time in seconds the contact spent on the line after the agent hung up.

End_Time


The time the contact ended. Follows this format: HH:MM:SS.

ACW_Time

The amount of time in seconds the agent spent doing after contact work (ACWClosed State that allows an agent to complete work requirements after finishing an interaction.)  after conversing with the contact.

Abandon_Time

The amount of time in seconds the contact spent in the system before abandoning the call. The value is 0 unless the value in the Abandon column is Y.

Total_Time_Plus_Disposition

The total amount of time in seconds the contact spent in the NiCE CXone system on the date specified. It is calculated by adding the times associated with all contact states for every contact entering the IVR plus the ACWClosed State that allows an agent to complete work requirements after finishing an interaction. time.

Routing_Time

The amount of time in seconds it took to route the contact to an agent. This count is included in the Inqueue time.

Abandon

Whether or not the contact abandoned the call before its completion. Y means the contact abandoned the call and N means the contact did not abandon the call.

Refused


Whether or not the agent refused the contact. Y means the agent refused the contact. N means the agent answered the contact.

Refused_Time

The date and time when the agent refused the contact. It follows the format MM/DD/YYYY HH:MM, 24-hour time in seconds.

Callback_Time

The amount of time in seconds the contact spent in the callbackClosed Holds a customer's place in queue and automatically calls the customer when they move to the front of the queue. state.

Callback_Number

The phone number at which the contact requested the agent call back.

ContactEndReason


The reason the contact ended, such as Agent Abandon, Contact Refused, or Contact Completed.

Logged

Whether or not the call was logged. It is one of the following values:

  • Y: The call was logged
  • N: The call was not logged

Hold_Time

The amount of time in seconds the contact spent on hold.

Disp_Code

The unique ID associated with the dispositionClosed Result assigned by the agent or system at the end of a voice (disposition) or digital (status) interaction. assigned to the contact. For a list of system disposition codes and their associated dispositions, see System Disposition Values.

Disp_Name

The name of the dispositionClosed Result assigned by the agent or system at the end of a voice (disposition) or digital (status) interaction. assigned to the contact.

Tags

A comma-delimited list of tags the agent attached to the contact.

Data_Name_Data_Value The custom variables associated with the contact. Data is formatted as Data_Name:Data_Value. If multiple variables exist for a single contact, they are separated by a semicolon (;).
RefusalReason_AgentNumber_RefusalTime The details for agent refusal events. Data is formatted as Reason:agent_no:refuse_time. If multiple refusal events occurred for the contact, they are separated by a semicolon (;).
Script Name The name of the CXone script that handled the interaction.
Cause Code The system-generated code indicating the reason the contact ended.
Transferred Indicates whether the contact was transferred during the interaction.

Note:
The data_name_data_value and RefusalReason_AgentNumber_RefusalTime columns are unique because they can contain multiple pieces of information within a single cell. This concatenation ensures that the report maintains one row per contact, which keeps the total time and volume metrics accurate
• This formatting applies only to the two columns mentioned above. All other columns in this report contain a single value per contact.
• Related data points are joined by a colon (:) and multiple entries for the same contact are separated by a semicolon (;).
Example: Variable1:ValueA; Variable2:ValueB