The ININ_DIALER_40.CallHistory table holds call-completion information for every campaign call placed. The Outbound Dialer Server populates the CallHistory table as it progresses through the contact list during the course of a campaign. This table indicates who was called and the completion result of the call. No customer maintenance is required. The CallHistory table is in the CIC database. It is shared by multiple campaigns.
Column | Data Type (Size) | Is Nullable | Contains PII | Description | Last Change Version | Last Change Reason | CX Insights Name | CX Insights Type | CX Insights Folder Name | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
campaignname | varchar (255) | False | Unknown | The name of the Campaign. |
4.0.106.453 | 4.0 Release | |||||||||||||||||||
siteid | varchar (80) | False | Unknown | Name of the Outbound Dialer server that will call back the party. |
4.0.106.453 | 4.0 Release | |||||||||||||||||||
i3_identity | bigint | True | Unknown |
An integer value that uniquely identifies each row in the contact list. This field is managed for the customer by Dialer. Customers may continue to insert records that contain I3_ROWID, but they should not populate I3_IDENTITY fields. When using the Follow Up Call feature, you'll see the same integer value in multiple rows - one for each additional call. To help you track each additional call, the phone numbers will appear in the corresponding phonenumber column. The label assigned to the phone in the contact record will appear in the corresponding phonenumbertype column. |
4.0.106.453 | 4.0 Release | |||||||||||||||||||
i3_rowid | varchar (80) | True | Unknown | i3_rowid is a customer-managed field used to uniquely identify a row. i3_rowid is no longer a required field, since it was superseded by i3_identity, a Dialer-managed field. However, i3_rowid is supported in the contact list and is propagated to the CallRecordSchedule and CallHistory tables. i3_rowid is also available in Scripter and in policies for backwards compatibility. |
4.0.106.453 | 4.0 Release | |||||||||||||||||||
callid | char (11) | True | Unknown | The callid number of this call attempt. For more information, see the discussion of callid in the Reporting Data Dictionary. |
4.0.106.453 | 4.0 Release | |||||||||||||||||||
callidkey | char (18) | True | Unknown | This internal, site-unique key identifies a call in the system. It is an 18 character alphanumeric strings whose format may change from release to release, though the values will always be unique. This field is not referenced in any report, but can be used by customers to cross-reference Dialer calls with the standard call data stored in the CIC database. For more information, see the discussion of callidkey in the Reporting Data Dictionary. |
4.0.106.453 | 4.0 Release | |||||||||||||||||||
wrapupcategory | varchar (80) | False | Unknown |
A code that generally identifies the completion status of the call. Used to provide standardized reporting across multiple campaigns. See the Dialer Manager Help guide for more information. If you create a custom wrap-up category, this column will contain a GUID that is associated with the display name of the custom wrap-up category. To match the GUID to the display name for reporting purposes, you will have to use the WrapupCategory lookup table. See WrapupCategory Table |
4.0.106.453 | 4.0 Release | |||||||||||||||||||
wrapupcode | varchar (80) | False | Unknown |
A code that more specifically indicates the outcome of the call. Wrap-up codes add granularity to reporting, while wrap-up Categories provide for standardized reporting across multiple campaigns. See the Dialer Manager Help guide for more information. If you create a custom wrap-up code, this column will contain a GUID that is associated with the display name of the custom wrap-up category. To match the GUID to the display name for reporting purposes, you will have to use the WrapupCode lookup table. See WrapupCode Table |
4.0.106.453 | 4.0 Release | |||||||||||||||||||
callingmode | tinyint | True | Unknown |
|
4.0.106.453 | 4.0 Release | |||||||||||||||||||
phonenumber | varchar (50) | True | Unknown | The telephone number dialed for this attempt. |
4.0.106.453 | 4.0 Release | |||||||||||||||||||
phonenumbertype | varchar (80) | True | Unknown |
The customer-defined phone number type associated with the phone number dialed. This is used for reporting purposes. When using the Follow Up Call feature, you will find the term 'NULL' in the phonenumbertype column if this was an ad-hoc call where the number was manually entered. |
4.0.106.453 | 4.0 Release | |||||||||||||||||||
agentid | varchar (80) | True | Unknown | The CIC User ID of the Agent who processed the call, as it is defined in Interaction Administrator. |
4.0.106.453 | 4.0 Release | |||||||||||||||||||
calledpartyoffset | int | True | Unknown | Offset in seconds used to adjust UTC times based on the called party's time zone. |
4.0.106.453 | 4.0 Release | |||||||||||||||||||
odsoffset | int | False | Unknown | Offset in seconds used to adjust UTC times based on ODS's time zone. |
4.0.106.453 | 4.0 Release | |||||||||||||||||||
previewpoptimeUTC | datetime | True | Unknown | In Preview mode, the time when the call record popped for the Agent to review. This is the time that Preview call data was presented to an Agent (not the actual call time.) |
4.0.106.453 | 4.0 Release | |||||||||||||||||||
callplacedtimeUTC | datetime | True | Unknown | The time when the call was placed by Telephony Services. |
4.0.106.453 | 4.0 Release | |||||||||||||||||||
callansweredtimeUTC | datetime | True | Unknown | The time when the call was answered by the remote party or a device. |
4.0.106.453 | 4.0 Release | |||||||||||||||||||
messageplaytimeUTC | datetime | True | Unknown | The time that a message was played to the contact, due to the campaign type or due to the absence of available agents. |
4.0.106.453 | 4.0 Release | |||||||||||||||||||
callconnectedtimeUTC | datetime | True | Unknown | The time that the call was connected to the Agent. |
4.0.106.453 | 4.0 Release | |||||||||||||||||||
calldisconnectedtimeUTC | datetime | False | Unknown | The time when Dialer stopped tracking the call. This can occur when the call is disconnected or the call is completed upon a disposition being received from either by an agent or the system. |
4.0.106.453 | 4.0 Release | |||||||||||||||||||
length | int | True | Unknown | Length of the call in seconds. The length column in the Call History table does not always match the call duration. The callplacedtimeUTC and calldisconnectedtimeUTC accumulators are tracked internally by Dialer and may not match Interaction Summary information for the call. The length field is calculated from the Completed time minus the Start time. The completed time is set when the call is completed and the wrapup code is written. That happens after policy evaluations and agent finalization. The start time occurs when the call is placed. The length field can match the (Disconnected - Placed) time when the disconnect was a result of the wrapup and finalization of the interaction. This can occur if you disposition an interaction while the call is still live. |
4.0.106.453 | 4.0 Release | |||||||||||||||||||
caresult | tinyint | True | Unknown |
|
4.0.106.453 | 4.0 Release | |||||||||||||||||||
cadetail | varchar (255) | True | Unknown |
Call Analysis results for each call are written to the CallHistory table along with the other information about the call, such as Wrap-up Codes and Categories, call id, and so forth. This allows reporting to be done not just on disposition, but also on call analysis results. This is important for customers whose call analysis is performed by Media Servers. Two columns in CallHistory table facilitate this:
The cadetail (call analysis detail) column is text field up to 255 characters in length that contains extra information that supplements the caresult value. For example, if caresult is 2 (SIT), cadetail would contain a description of the SIT tone/message. For a caresult of 5 (ISDN Cause Code) cadetail would contain a description of the ISDN cause code. For caresult 6 (Failure) cadetail would contain a description of the error returned from MakeCall. Null values are allowed, since some caresult codes do not generate detail information. |
4.0.106.453 | 4.0 Release | |||||||||||||||||||
isabandoned | bit | True | Unknown | This flag indicates whether the call was abandoned (1=Yes, 0=No). This value can be set by Dialer or by a script. See Interaction Scripter Developer Guide for details. |
4.0.106.453 | 4.0 Release | |||||||||||||||||||
iscontact | bit | True | Unknown | This flag indicates whether the call reached a live contact (1=Yes, 0=No). Contacts are defined in the Dialer configuration. Specifically, the 'Interaction Connected to an Actual Person' checkbox in Wrap Up Categories affects the 'iscontact' field. |
4.0.106.453 | 4.0 Release | |||||||||||||||||||
isdetect | bit | True | Unknown | Signifies whether call analysis detected that the call was answered by a person. If call analysis is turned off, the value will always be 1 (true) since those calls are treated as live voice. |
4.0.106.453 | 4.0 Release | |||||||||||||||||||
isrpc | bit | True | Unknown | Signifies whether the call was a right party contact. |
4.0.106.453 | 4.0 Release | |||||||||||||||||||
issuccess | bit | True | Unknown | Signifies whether the campaign result was achieved, governed by the 'interaction was successful' setting on the wrap-up Category. |
4.0.106.453 | 4.0 Release | |||||||||||||||||||
successresult | float | True | Unknown |
This column is populated with the value of the successresult column on the contact. Successresult is a customer-managed column in both the ContactList and CallHistory tables. Customers can use successresult to maintain running counters, such as a money counter for example. The value of 'successresult' can be NULL when records are added or updated. The value of successresult in a CallHistory row will contain whatever was in the successresult column of the associated contact at the time the history row was written (when the record was dispositioned). |
4.0.106.453 | 4.0 Release | |||||||||||||||||||
customdata1 | varchar (255) | True | Unknown | Provided for customer use. Not used by Dialer. |
4.0.106.453 | 4.0 Release | |||||||||||||||||||
customdata2 | varchar (255) | True | Unknown | Provided for customer use. Not used by Dialer. |
4.0.106.453 | 4.0 Release | |||||||||||||||||||
campaignfilterid | smallint | True | Unknown | The ID assigned to the filter that is applied to the campaign. |
4.0.106.453 | 4.0 Release | |||||||||||||||||||
previewtimerinit | bit | True | Unknown |
This flag indicates whether a Preview call was initiated manually or automatically through a campaign configured preview timer.
|
4.0.106.453 | 4.0 Release | |||||||||||||||||||
rulegroupid | smallint | True | Unknown | The ID assigned to the Rule Group that was set. You can find more details about the RuleGroupID, such as the name of the Rule Group, in the CallHistory_RuleGroup table. |
15.3.0.384 | Added for reporting on a campaign with context information from the rule group. | |||||||||||||||||||
callscheduletime | datetime | True | Unknown |
When a scheduled callback occurs, this field will show the date and time that the call was scheduled. (Based on CCS time) More specifically, when a call results in a scheduled callback, a record is added the CallHistory table for that call and both the wrapupcategory and wrapupcode entries will contain the word Scheduled. The callscheduletime entry will be set to NULL at this point. When the scheduled callback actually occurs, a second record will added to the CallHistory table for that call; only this time the callscheduletime entry will show the date and time when the call was scheduled and the wrapupcategory and wrapupcode entries will contain appropriate values. Keep in mind that the callscheduletime entry will NOT indicate when the actual call occurred - just the time that the call was scheduled to occur. If you wish to determine the elapsed time between when the call was scheduled and when the call was actually made, you will need to check the callplacedtimeUTC entry in the record. |
4.0.106.453 | 4.0 Release | |||||||||||||||||||
isAdditionalCall | bit | True | Unknown |
This flag indicates whether the call is one of the additional calls made to the same contact using the Follow Up Call feature or an standard call.
|
4.0.106.453 | 4.0 Release | |||||||||||||||||||
agentoverride | smallint | True | Unknown | If the agent chose an override option while using the Follow Up Call feature, there will be a code number in this column that indicates what type of override that occurred. To find out what type of override the code number indicates, you'll need to check the AgentComplianceOverrides table. By performing an SQL join of the CallHistory table and the AgentComplianceOverrides table, a database administrator can extract the pertinent data. |
4.0.106.453 | 4.0 Release | |||||||||||||||||||
callhistory_id | bigint | False | Unknown | Correlates this record with a row in the CallHistory table |
18.4.0.000 | Added column for joining the record to the Call History Details table. |
Primary Key Name | Type | Column Name (sort order) |
---|---|---|
PK_CALLHISTORY_ID | Non-clustered | callhistory_id (Ascending) |
Index Name | Type | Column Name (sort order) |
---|---|---|
IX_CallHistory_CampAgtPlaced | Non-clustered | campaignname (Ascending) agentid (Ascending) callplacedtimeUTC (Ascending) |
IX_CallHistory_Campaign_Date | Non-clustered | campaignname (Ascending) callconnectedtimeUTC (Ascending) |
IX_CallHistory_CampPlaced | Non-clustered | campaignname (Ascending) callplacedtimeUTC (Ascending) |
IX_CallHistory_Date | Clustered | callconnectedtimeUTC (Ascending) |
UX_CallHistory | Unique non-clustered | calldisconnectedtimeUTC (Ascending) callidkey (Ascending) campaignname (Ascending) i3_identity (Ascending) |
Column | Data Type (Size) | Is Nullable | Contains PII | Description | Last Change Version | Last Change Reason | CX Insights Name | CX Insights Type | CX Insights Folder Name |
---|---|---|---|---|---|---|---|---|---|
callhistory_id | bigint | False | Unknown | Correlates this record with a row in the CallHistory table |
18.4.0.000 | Added for reporting on key events of a dialer interaction. | |||
callidkey | char (18) | True | Unknown | Alphanumeric string set by Queue Manager that uniquely identifies an interaction, guaranteed to be unique across related sites and over time. Useful to correlate this table with other data tables. |
18.4.0.000 | Added for reporting on key events of a dialer interaction. | |||
call_requested | datetime | True | Unknown | Time when Dialer sent a request to place the call to Telephony Services. The call has not been placed yet. |
18.4.0.000 | Added for reporting on key events of a dialer interaction. | |||
line_connect | datetime | True | Unknown | Time when the call connected to the remote station and audio is detected. This occurs when the call connected to the station begins ringing and Telephony Services detects that someone or something picked up the call. At this point, audio is detected, but is not identified by Call Analysis. Dialer does not know exactly when the call is answered, only when a person or machine responded to a connected call. |
18.4.0.000 | Added for reporting on key events of a dialer interaction. | |||
ca_requested | datetime | True | Unknown | Time when Telephony Services requests for Call Analysis to begin. |
18.4.0.000 | Added for reporting on key events of a dialer interaction. | |||
ca_begin | datetime | True | Unknown | Time when Telephony Services started to send audio to Media Server. At this moment, TS begins Call Analysis to detect whether a person or machine answered. This is typically the moment when a contact said hello, or a machine said something. |
18.4.0.000 | Added for reporting on key events of a dialer interaction. | |||
ca_end | datetime | True | Unknown |
Time when Media Server determined whether a person or machine answered. At this time, TS completed call analysis. Put another way, ca_end indicates when call analysis had high enough confidence in its result to stop analyzing the audio stream. Call analysis is longer or shorter based on the audio it receives. It is most efficient when it hears audio followed by a period of silence. For example, when someone answers and says hello, call analysis waits another half second for the silence that follows. Live party detection generally takes 1 second. Call analysis will take longer if it is sent music, or if a person or machine speaks without leaving a gap of silence in the audio stream. Until call analysis has high confidence in the accuracy of its result, it will continue analyzing audio until it eventually times out. |
18.4.0.000 | Added for reporting on key events of a dialer interaction. | |||
acd_routed | datetime | True | Unknown | Time when Dialer started to route to an agent or workgroup, by asking TS to route the call to an agent or workgroup. |
18.4.0.000 | Added for reporting on key events of a dialer interaction. | |||
agent_connected | datetime | True | Unknown |
Time when the audio stream between the called party and the agent is started. The agent may not have spoken yet. Agent Connected occurs when the call is connected to the agent's queue. If the agent has a persistent connection, he will respond sooner than when the agent must make a connection to pick up the call. For this reason, persistent connections are highly recommended. During this phase, calls transition from an Offering state (when the call goes to an agent's station) to an Alerting state when ringing begins, and to a Connected state when the agent presses a button or picks up a handset. The time recorded for Agent Connected corresponds to the Connected state. This column is set to NULL for agentless campaigns. |
18.4.0.000 | Added for reporting on key events of a dialer interaction. | |||
playback_requested | datetime | True | Unknown | When playing a recording or sending a call to an Attendant profile, the time when Dialer requests TS to play a Pre-recorded message, where applicable. Simply put, the time when Dialer requested to play back a wave file. |
18.4.0.000 | Added for reporting on key events of a dialer interaction. | |||
insert_time | datetime | True | Unknown | Time when this record was inserted into the database. |
18.4.0.000 | Added for reporting on key events of a dialer interaction. |
The ININ_DIALER_40.CallHistory_RuleGroup table contains details of the RuleGroupID that appears in the CallHistory and CampaignStat tables. More specifically, it contains the name of the Rule Group associated with the ID. In addition, the CallHistory RuleGroup table contains the RuleSetID. You can find more details about the RuleSetID, such as the name of the Rule Set, in the CallHistory RuleSet table.
The CallHistory RuleGroup table contains details of the RuleGroupID that appears in the CallHistory and CampaignStats tables.
Column | Data Type (Size) | Is Nullable | Contains PII | Description | Last Change Version | Last Change Reason | CX Insights Name | CX Insights Type | CX Insights Folder Name |
---|---|---|---|---|---|---|---|---|---|
RuleGroupId | smallint | False | Unknown | The identification number assigned to the Rule Group for tracking purposes. |
15.3.0.384 | Added for reporting on a campaign with context information from the rule group. | |||
RuleSetId | uniqueidentifier | False | Unknown | The identification number assigned to the Rule Set for tracking purposes. The name of the Rule Set can be found in the CallHistory Rule Set Table. |
15.3.0.384 | Added for reporting on a campaign with context information from the rule group. | |||
ActiveRuleGroupName | nvarchar (80) | False | Unknown | The actual name assigned to the Rule Group. |
15.3.0.384 | Added for reporting on a campaign with context information from the rule group. |
Primary Key Name | Type | Column Name (sort order) |
---|---|---|
PK_CallHistory_RuleGroup | Clustered | RuleGroupId (Ascending) |
Foreign Key Name | Column | Reference Table | Reference Column | Indexed |
---|---|---|---|---|
FK_CallHistory_RuleGroup | RuleSetId | CallHistory_RuleSet | RuleSetId | Yes |
The ININ_DIALER_40.CallHistory_RuleSet table contains details of the RuleSetID, such as the name of the Rule Set, which appears in the CallHistory RuleGroup table.
The CallHistory RuleSet table contains details of the RuleSetID that appears in the CallHistory RuleGroup table.
Column | Data Type (Size) | Is Nullable | Contains PII | Description | Last Change Version | Last Change Reason | CX Insights Name | CX Insights Type | CX Insights Folder Name |
---|---|---|---|---|---|---|---|---|---|
RuleSetId | uniqueidentifier | False | Unknown | The identification number assigned to the Rule Set for tracking purposes. |
15.3.0.384 | Added for reporting on a campaign with context information from the rule group. | |||
RuleSetName | nvarchar (80) | False | Unknown | The actual name assigned to the Rule Set. |
15.3.0.384 | Added for reporting on a campaign with context information from the rule group. |
Primary Key Name | Type | Column Name (sort order) |
---|---|---|
PK_CallHistory_RuleSet | Clustered | RuleSetId (Ascending) |
If an agent chooses an override option while using the Follow Up Call feature, there will be a code number in the agentoverride column in the CallHistory table that indicates what type of override occurred. This table is used to identify those code numbers.
By performing an SQL join of the CallHistory table and the AgentComplianceOverrides table, a database administrator can extract the pertinent data.
NOTE: In addition to identifying overrides from the Follow Up Call feature, this table also identifies overrides from the use of custom Icelib Manual call overrides.
Column | Data Type (Size) | Is Nullable | Contains PII | Description | Last Change Version | Last Change Reason | CX Insights Name | CX Insights Type | CX Insights Folder Name |
---|---|---|---|---|---|---|---|---|---|
id | smallint | False | Unknown | Code number from the agentoverride column in the CallHistory table. |
4.0.106.453 | 4.0 Release | |||
Filter | bit | True | Unknown |
This flag indicates whether Filter was overridden. This only applies to custom Icelib Manual Call overrides. If it is a 1, Filter was overridden. If it is a 0, Filter was not a factor. |
4.0.106.453 | 4.0 Release | |||
QueryTimeFilter | bit | True | Unknown |
This flag indicates whether QueryTimeFilter was overridden. This only applies to custom Icelib Manual Call overrides. If it is a 1, QueryTimeFilter was overridden. If it is a 0, QueryTimeFilter was not a factor. |
4.0.106.453 | 4.0 Release | |||
ZoneBlocking | bit | True | Unknown |
This flag indicates whether ZoneBlocking was overridden to make the call while using the Follow Up Call feature. If it is a 1, ZoneBlocking was overridden. If it is a 0, ZoneBlocking was not a factor. |
4.0.106.453 | 4.0 Release | |||
Skills | bit | True | Unknown |
This flag indicates whether Skills was overridden to make the call while using the Follow Up Call feature. If it is a 1, Skills was overridden. If it is a 0, Skills was not a factor. |
4.0.106.453 | 4.0 Release | |||
DailyLimit | bit | True | Unknown |
This flag indicates whether DailyLimit was overridden to make the call while using the Follow Up Call feature. If it is a 1, DailyLimit was overridden. If it is a 0, DailyLimit was not a factor. |
4.0.106.453 | 4.0 Release | |||
MinimumSpacing | bit | True | Unknown |
This flag indicates whether MinimumSpacing was overridden. This only applies to custom Icelib Manual Call overrides. If it is a 1, MinimumSpacing was overridden. If it is a 0, MinimumSpacing was not a factor. |
4.0.106.453 | 4.0 Release | |||
PNDStatus | bit | True | Unknown |
This flag indicates whether PNDStatus was overridden. This only applies to custom Icelib Manual Call overrides. If it is a 1, PNDStatus was overridden. If it is a 0, PNDStatus was not a factor. |
4.0.106.453 | 4.0 Release | |||
DNCScrub | bit | True | Unknown |
This flag indicates whether DNC was overridden to make the call while using the Follow Up Call feature. If it is a 1, DNC was overridden. If it is a 0, DNC was not a factor. |
4.0.106.453 | 4.0 Release | |||
CampaignOwnership | bit | True | Unknown |
This flag indicates whether CampaignOwnership was overridden. This only applies to custom Icelib Manual Call overrides. If it is a 1, CampaignOwnership was overridden. If it is a 0, CampaignOwnership was not a factor. |
4.0.106.453 | 4.0 Release |
The ININ_DIALER_40.AgentStats table keeps track of agent performance. This table is shared by multiple Campaigns. It is in the CIC database, not the Dialer database.
Specifically, AgentStats stores the amount of time that agents spend in "Idle", "Connected", "Wrap Up" and "Do Not Disturb" states. "Connected" time is further broken into stages so that the time an agent spends in each stage of the call is recorded. The stage information in this table is updated when an agent transitions from one stage of a call to another.
The Outbound Dialer Server populates this table as it progresses through the contact list during the course of a campaign.
Column | Data Type (Size) | Is Nullable | Contains PII | Description | Last Change Version | Last Change Reason | CX Insights Name | CX Insights Type | CX Insights Folder Name | ||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
campaignname | varchar (255) | True | Unknown | The name of the Campaign as defined in Dialer Manager. |
4.0.106.453 | 4.0 Release | |||||||||||||||||||||||||||||||||||||||
siteid | varchar (80) | False | Unknown | The name of the Outbound Dialer server that the agent was logged on to. |
4.0.106.453 | 4.0 Release | |||||||||||||||||||||||||||||||||||||||
odsoffset | int | False | Unknown | The offset of the ODS's time zone from UTC in seconds. This is used to translate the agenttimeUTC field to local time. |
4.0.106.453 | 4.0 Release | |||||||||||||||||||||||||||||||||||||||
agenttimeUTC | datetime | False | Unknown | The time when the action described by this record happened. |
4.0.106.453 | 4.0 Release | |||||||||||||||||||||||||||||||||||||||
agentid | varchar (80) | False | Unknown | The CIC User ID of the agent who processed the call, as it is defined in Interaction Administrator. |
4.0.106.453 | 4.0 Release | |||||||||||||||||||||||||||||||||||||||
stageid | varchar (10) | True | Unknown | Dialer uses this column to categorize non-Dialer call time as inbound or outbound (manually dialed). It populates the stageid column with the identifier 'ND-IN' for inbound non-Dialer calls or the identifier 'ND-MO' for manually-dialed outbound non-Dialer calls. This information is used by the Agent Utilization Summary report to summarize non-Dialer call time by inbound and outbound categories. |
4.0.106.453 | 4.0 Release | |||||||||||||||||||||||||||||||||||||||
callid | varchar (11) | True | Unknown | Numeric ID of this call object. For more information, see the discussion of callid in the Reporting Data Dictionary. |
4.0.106.453 | 4.0 Release | |||||||||||||||||||||||||||||||||||||||
callidkey | varchar (18) | True | Unknown | This internal, site-unique key identifies a call in the system. It is an 18 character alphanumeric strings whose format may change from release to release, though the values will always be unique. This field is not referenced in any report, but can be used by customers to cross-reference Dialer calls with the standard call data stored in the CIC database. For more information, see the discussion of callidkey in the Reporting Data Dictionary. |
4.0.106.453 | 4.0 Release | |||||||||||||||||||||||||||||||||||||||
propertyname | varchar (255) | False | Unknown |
A name that identifies the type of statistic that the record contains. The supported property values are:
|
4.0.106.453 | 4.0 Release | |||||||||||||||||||||||||||||||||||||||
propertyvalue | varchar (255) | True | Unknown | The value of the statistic. All time-based values are expressed in seconds. |
4.0.106.453 | 4.0 Release | |||||||||||||||||||||||||||||||||||||||
agentstats_id | bigint | False | Unknown | The identification number assigned to the agent statistic. |
18.4.0.000 | Added id columns to agentstats and campaignstats. |
Primary Key Name | Type | Column Name (sort order) |
---|---|---|
PK_AGENTSTATS_ID | Non-clustered | agentstats_id (Ascending) |
Index Name | Type | Column Name (sort order) |
---|---|---|
IX_AgentStats_Date | Clustered | agenttimeUTC (Ascending) |
UX_AgentStats | Unique non-clustered | campaignname (Ascending) agenttimeUTC (Ascending) agentid (Ascending) propertyname (Ascending) |
The ININ_DIALER_40.CampaignStats table contains summary statistics for each campaign running in Dialer. Each row will contain a set of statistics averaged over a configurable sample period. The default sample period is 60 seconds, but the user can change the sample period under the campaign configuration using the 'Statistics sample period' control. Columns that do not allow NULL values must have a value when records are added or inserted.
Column | Data Type (Size) | Is Nullable | Contains PII | Description | Last Change Version | Last Change Reason | CX Insights Name | CX Insights Type | CX Insights Folder Name |
---|---|---|---|---|---|---|---|---|---|
periodstarttimeUTC | datetime | False | Unknown | Timestamp for the start of the sample period |
4.0.106.453 | 4.0 Release | |||
periodendtimeUTC | datetime | False | Unknown | Timestamp for the end of the sample period |
4.0.106.453 | 4.0 Release | |||
odsoffset | int | False | Unknown | The UTC offset of the ODS in seconds |
4.0.106.453 | 4.0 Release | |||
campaignname | varchar (255) | False | Unknown | The name of the campaign |
4.0.106.453 | 4.0 Release | |||
siteid | varchar (80) | False | Unknown | The site name of the ODS for this row |
4.0.106.453 | 4.0 Release | |||
event | varchar (20) | True | Unknown | Records significant campaign events that occurred during the sample period. Valid values: 'recycle', 'reset', 'NewActive Group'' |
4.0.106.453 | 4.0 Release | |||
campaignstate | varchar (20) | False | Unknown | The state of the campaign at the end of the sample period. Valid values: 'on', 'off', 'paused', 'scheduledonly' |
4.0.106.453 | 4.0 Release | |||
dialingmode | varchar (10) | False | Unknown | The dialing mode of the campaign at the end of the sample period. Valid values: 'preview', 'predictive', 'power', 'agentless' |
4.0.106.453 | 4.0 Release | |||
filtersize | int | False | Unknown | The filter size at the start of the sample period |
4.0.106.453 | 4.0 Release | |||
recyclesize | int | False | Unknown | The recycle size at the start of the sample period |
4.0.106.453 | 4.0 Release | |||
totalagents | int | False | Unknown | The total number of agents that are active in the campaign |
4.0.106.453 | 4.0 Release | |||
effectivetotalagents | float | False | Unknown | The total number of agents that are active in the campaign minus average non-Dialer agents (agents in this campaign that are currently on non-Dialer calls (). |
4.0.106.453 | 4.0 Release | |||
idleagents | int | False | Unknown | The number of agents that are in an idle or finishing state in the campaign |
4.0.106.453 | 4.0 Release | |||
effectiveidleagents | float | False | Unknown | The number of idle agents minus average non-Dialer agents |
4.0.106.453 | 4.0 Release | |||
nondialeragents | int | False | Unknown | The number of agents that are on non-dialer calls in the campaign |
4.0.106.453 | 4.0 Release | |||
dndagents | int | False | Unknown | The number of agents in a DND state in the campaign |
4.0.106.453 | 4.0 Release | |||
totaldialercalls | int | False | Unknown | The total number of active calls in the campaign (pending + outstanding + connected) |
4.0.106.453 | 4.0 Release | |||
pace | int | True | Unknown | The current pace value for the campaign |
4.0.106.453 | 4.0 Release | |||
cpa | float | True | Unknown | The current calls per agent being used by the campaign (for example: 1/ConnectRate) |
4.0.106.453 | 4.0 Release | |||
adjcpa | float | True | Unknown | The adjusted calls per agent being used by the campaign (for example the CPA adjusted by pace.) |
4.0.106.453 | 4.0 Release | |||
abandonrate | float | True | Unknown | The current abandon rate of the campaign |
4.0.106.453 | 4.0 Release | |||
priority | tinyint | False | Unknown | The campaign's priority among all running campaigns |
4.0.106.453 | 4.0 Release | |||
rulegroupid | smallint | True | Unknown | The ID assigned to the Rule Group that was set. (When an entry appears in the RuleGroupID column, an entry titled NewAcive Group will appear in Event column.) |
15.3.0.384 | Added for reporting on a campaign with context information from the rule group. | |||
campaignstats_id | bigint | False | Unknown | The identification number assigned to the campaign statistic. |
18.4.0.000 | Added id columns to agentstats and campaignstats. |
The analytics table is written to via the DialerTranServer process server. It is treated like a log table to implement data retention. The table will be named Dialer.CampaignStats. Rows are written to the table only if the data in the row is different from the previous row. Rows are written to the table only if any of the following values are non-zero: calls placed, dispositions, abandons, detections, contacts, rpcs, or if a significant event occurs.
Primary Key Name | Type | Column Name (sort order) |
---|---|---|
PK_CAMPAIGNSTATS_ID | Non-clustered | campaignstats_id (Ascending) |
Index Name | Type | Column Name (sort order) |
---|---|---|
IX_CampaignStats_Date | Clustered | periodstarttimeUTC (Ascending) |
UX_CampaignStats | Unique non-clustered | campaignname (Ascending) periodstarttimeUTC (Ascending) periodendtimeUTC (Ascending) siteid (Ascending) event (Ascending) |
The ININ_DIALER_40.DigitalHistory table tracks email interactions initiated by Dialer.
Column | Data Type (Size) | Is Nullable | Contains PII | Description | Last Change Version | Last Change Reason | CX Insights Name | CX Insights Type | CX Insights Folder Name | ||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
interactionid | char (19) | False | Unknown | Interaction Id of the email initiated by Dialer. |
18.4.0.000 | Added for reporting on the various digital interactions initiated by dialer campaigns. | |||||||||
associated_callid | char (19) | True | Unknown | Interaction Id of the Dialer call that initiated the email. |
18.4.0.000 | Added for reporting on the various digital interactions initiated by dialer campaigns. | |||||||||
time_queued_utc | datetime2 | True | Unknown | The time when Dialer sent the request to the PostOffice subsystem to send an email. |
18.4.0.000 | Added for reporting on the various digital interactions initiated by dialer campaigns. | |||||||||
sender | nvarchar (255) | True | Unknown | The sender's email address. |
18.4.0.000 | Added for reporting on the various digital interactions initiated by dialer campaigns. | |||||||||
recipient | nvarchar (255) | True | Unknown | The recipient's email address. |
18.4.0.000 | Added for reporting on the various digital interactions initiated by dialer campaigns. | |||||||||
email_subject | nvarchar (MAX) | True | Unknown | Text of the email's subject field. |
18.4.0.000 | Added for reporting on the various digital interactions initiated by dialer campaigns. | |||||||||
policy_behavior_name | nvarchar (30) | True | Unknown | Name of the policy behavior that initiated the email, as defined in Interaction Administrator. |
18.4.0.000 | Added for reporting on the various digital interactions initiated by dialer campaigns. | |||||||||
digital_type | tinyint | True | Unknown |
An integer indicating the type of digital interaction.
|
18.4.0.000 | Added for reporting on the various digital interactions initiated by dialer campaigns. |