As of Friday October 16th, access to restricted content on this site now requires you to log in with your Genesys account. If you don't have an account, you can request one at these locations: Request MyPartner Portal Account or Request My Support Account.
Jump to: navigation, search

Chat Attributes

The Chat folder contains numerous attributes that you can use to build chat-related reports.

Note the following:

  • When creating attributes, any forms you create must have a one-is-to-one mapping relationship. For example, an attribute that represents the name of a customer can have only one phone number form associated with it.
Important
Objects in each folder or subfolder are designed to be used together to create reports. Avoid mixing attributes and metrics from multiple folders into your reports. One exception to this rule is objects in the Time folder; Time attributes can be used in any report, and most reports include at least one attribute from the Time folder.


The following Attributes are available in this folder and are described on this page.

Chat

Chat > Agent

Chat > Async

  • There are no attributes in this folder

Chat > Thread


Folder: Chat

Attribute name: End Reason


Introduced: 9.0.011

Folder: Chat
Description: Enables data to be organized based on the reason why the chat ended.
Database table: CHAT_SESSION_DIM.ENDED_REASON
>> Back to list
Attribute name: Ended By


Introduced: 9.0.011

Folder: Chat
Description: Enables data to be organized based on what party ended the interaction (agent, customer, or timeout).
Database table: CHAT_SESSION_DIM.ENDED_BY
>> Back to list
Attribute name: Language Name


Introduced: 9.0.011

Folder: Chat
Description: Enables data to be organized based on the language used in the chat interaction.
Database table: CHAT_SESSION_DIM.LANGUAGE_NAME
>> Back to list
Attribute name: Media Origin


Introduced: 9.0.011

Folder: Chat
Description: Enables data to be organized by where the chat session originated—for example, CHAT, Facebook, Twitter, or SMS.
Database table: CHAT_SESSION_DIM.MEDIA_ORIGIN
>> Back to list
Attribute name: Mode


Introduced: 9.0.011

Folder: Chat
Description: Enables data to be organized by the mode (Regular or Async).
Database table: CHAT_SESSION_DIM.ASYNC_MODE
>> Back to list


Folder: Chat > Agent

Attribute name: Agent Group
Folder: Chat > Agent
Description: Enables data within the reporting interval to be organized by the groups to which agents belong. An agent can belong to more than one agent group.
Database table: GROUP_A.GROUP_NAME (WHERE GROUP_.GROUP_TYPE_CODE in ('AGENT', 'UNKNOWN','NO_VALUE'))
>> Back to list
Attribute name: Agent Name
Folder: Chat > Agent
Description: Enables data to be organized by certain attributes of the agent who is associated with the interaction.
Database table: RESOURCE_A.AGENT_NAME
Form(s): User Name, Last Name, First Name, Employee ID
Forms in this attribute:
Form: Employee ID

Table.Column: RESOURCE_A.EMPLOYEE_ID
Data type: Text

Description: Enables data to be organized by the Employee ID of the agent who is associated with the interaction.
Form: First Name

Table.Column: RESOURCE_A.AGENT_FIRST_NAME
Data type: Text

Description: Enables data to be organized by the first name of the agent who is associated with the interaction.
Form: Last Name

Table.Column: RESOURCE_A.AGENT_LAST_NAME
Data type: Text

Description: Enables data to be organized by the last name of the agent who is associated with the interaction.
Form: User Name

Table.Column: RESOURCE_A.RESOURCE_NAME
Data type: Text

Description: Enables data to be organized by the user name of the agent who is associated with the interaction.
>> Back to list


Folder: Chat > Async

There are no attributes in this folder

Folder: Chat > Thread

Attribute name: Media Origin


Introduced: 9.0.011

Folder: Chat > Thread
Description: Enables data to be organized by where the chat session originated—for example, CHAT, Facebook, Twitter, or SMS.
Database table: MEDIA_ORIGIN.MEDIA_ORIGIN
>> Back to list
This page was last edited on June 10, 2020, at 18:16.

Feedback

Comment on this article:

blog comments powered by Disqus