This page was last edited on January 10, 2020, at 18:53.
Comments or questions about this documentation? Contact us for support!
In the Column List:
Introduced: 8.5.006
In partitioned databases, this table is not partitioned.
This aggregate table provides a rollup of agent participation in Voice and Chat interactions that include Co-browse sessions. This table is used to produce the Co-browse Summary Report.
Column | Data Type | P | M | F | DV |
---|---|---|---|---|---|
AGR_SET_KEY | NUMBER(38,0) | X | X | ||
DATE_TIME_KEY | NUMBER(38,0) | X | X | -1 | |
TENANT_KEY | NUMBER(38,0) | X | X | -1 | |
MEDIA_TYPE_KEY | NUMBER(38,0) | X | X | -1 | |
AGENT_RESOURCE_KEY | NUMBER(38,0) | X | X | -1 | |
ENTERED | NUMBER(38,0) | X | |||
INTERACTIONS | NUMBER(38,0) | X | |||
SESSIONS | NUMBER(38,0) | X | |||
RW_SESSIONS | NUMBER(38,0) | X | |||
FIRST_WAIT_TIME | NUMBER(38,0) | X | |||
HANDLE_TIME | NUMBER(38,0) | X |
[INTERNAL] The surrogate key that is used to join this aggregate table to the AGR_SET table.
The surrogate key that is used to join this aggregate table to the DATE_TIME dimension table to identify the calendar date and 15-minute interval during which the caller's participation in the interaction began.
The surrogate key that is used to join this aggregate table to the TENANT view to identify a specific tenant.
The surrogate key that is used to join this aggregate table to the MEDIA_TYPE dimension table.
The surrogate key that is used to join this aggregate table to the RESOURCE_ dimension table to get information such as the Agent Name, Agent ID.
The total number of Voice or Chat interactions that were accepted by the agent, regardless of whether Co-browse sessions were part of the interaction.
The total number of Voice or Chat interactions that were accepted by the agent, and that included one or more Co-browse sessions.
The total number of Co-browse sessions with WRITE mode. In WRITE mode sessions, the customer enables the agent to remote control the customer browser.
The total amount of time (in seconds) that elapses after the interaction starts before the first Co-browse session is initiated. For example: In a scenario where an interaction starts at 10:00 and the customer later requests help with Co-browse, and a Co-browse session is initiated at 10:07, the FIRST_WAIT_TIME is calculated as seven minutes (420 seconds).
The total amount of time (in seconds) that this agent spent handling Co-browse sessions.
No subject area information available.