Jump to: navigation, search

Legal Notices

[+] Genesys Chat

[+] July 20, 2021


[+] February 19, 2021


[+] May 15, 2020


[+] March 12, 2020


[+] December 19, 2019


[+] September 16, 2019


[+] May 31, 2019


[+] March 26, 2019


[+] January 11, 2019


[+] October 17, 2018


[+] September 27, 2018


[+] August 22, 2018


[+] August 23, 2017


For a complete list of new features in the 8.5.x release, please see Chat Server Release Notes.

allow-duplicated-kvp

Section: settings
Default Value: true
Valid Values: true, false
Changes Take Effect: Immediately
Introduced: 8.5.201.05

With a value of "false", Chat Server will return an error when any duplicated key-value pairs (for example, pairs with the same key name) in userdata or event attributes in chat protocol requests are provided. With a value of "true", Chat Server will ignore such conditions (and will use the value from the latest key-value pair).

Attention: While the backward compatibility default value is set to "true", it is recommended it be set to "false" for more controlled behavior.

async-idle-notices

Section: settings
Default Value: major
Valid Values: none, major, major2, typing, all
Changes Take Effect: Immediately
Introduced: 8.5.202.09 (Restricted); 8.5.301.06 (Generally Available)
Modified: 8.5.310.09

Specifies which notifications count as async chat session activity for the purpose of inactivity control.

  • all: All user notifications are included (custom, push URL, typing on/off, update nickname).
  • major: Only major notifications are included (push URL, file uploaded, file deleted).
  • major2: Extends the major value with custom notifications.
  • none: All notifications are excluded.
  • typing: Only major and "typing on" notifications are included.

async-idle-close

Section: settings
Default Value: 3600
Valid Values: Any integer from 1-1728000
Changes Take Effect: Immediately
Introduced: 8.5.202.09 (Restricted); 8.5.301.06 (Generally Available)

Specifies, in seconds, a timeout that starts after "async-idle-alert" (enabled only for async chat sessions). If any qualifying activity occurs, (see "async-idle-alert" for a description of what qualifies as activity), the timeout stops and "async-idle-alert" timer is reset. If no qualifying activity is detected during this timeout, Chat Server:

  • Sends the IDLE_CONTROL_CLOSE notice with a message specified by the value of the "message-close" option (in the section [inactivity-control]).
  • Closes the chat session.

async-idle-alert

Section: settings
Default Value: 86400
Valid Values: Any integer from 1-1728000
Changes Take Effect: Immediately
Introduced: 8.5.202.09 (Restricted); 8.5.301.06 (Generally Available)

Specifies an inactivity alert timeout (in seconds) which is enabled only for async chat sessions. The inactivity timeout is set (or reset) for a session after any of the following activities: agent joined or left, any chat participant sent a message or a notice (as defined by "async-idle-notices"). If no qualifying activity is detected during this timeout, Chat Server:

  • Sends the IDLE_CONTROL_ALERT notice with a message specified by the value of the "message-alert" option (in the section [inactivity-control]).
  • Updates the interaction properties: GCTI_Chat_AsyncStatus=3 and GCTI_Chat_AsyncCheckAt={time to check interaction at}.
  • Starts the timeout specified by the value of the "async-idle-close" option.

async-chat-enforce

Section: settings
Default Value: none
Valid Values: none, flex, basic, both
Changes Take Effect: Immediately
Introduced: 8.5.307.04

Specifies when Chat Server forces chat sessions to run in async mode.

  • none: no forcing is applied.
  • flex: chat sessions run in async mode, when started via flex chat protocol.
  • basic: chat sessions run in async mode, when started via basic chat protocol.
  • both: all chat sessions run in async mode.

async-idle-notices

Section: settings
Default Value: major
Valid Values: none, major, major2, typing, all
Changes Take Effect: Immediately
Introduced: 8.5.202.09 (Restricted); 8.5.301.06 (Generally Available)
Modified: 8.5.310.09

Specifies which notifications count as async chat session activity for the purpose of inactivity control.

  • all: All user notifications are included (custom, push URL, typing on/off, update nickname).
  • major: Only major notifications are included (push URL, file uploaded, file deleted).
  • major2: Extends the major value with custom notifications.
  • none: All notifications are excluded.
  • typing: Only major and "typing on" notifications are included.

include-notices

Section: inactivity-control
Default Value: major
Valid Values: none, major, major2, typing, all
Changes Take Effect: Immediately
Modified: 8.5.310.09

Specifies which notifications count as chat session activity for the purpose of inactivity control.

  • all: All user notifications are included (custom, push URL, typing on/off, update nickname).
  • major: Only major notifications are included (push URL, file uploaded, file deleted).
  • major2: Extends the major value with custom notifications.
  • none: All notifications are excluded.
  • typing: Only major and "typing on" notifications are included.

session-restore-do-purge

Section: settings
Default Value: false
Valid Values: true, false
Changes Take Effect: Immediately
Introduced: 8.5.312.10

Enables or disables sending purging requests to Chat Server which handles the chat session before it is restored in this instance.

session-restore-extend-by

Section: settings
Default Value: none
Valid Values: none, agent, esp, both
Changes Take Effect: Immediately
Introduced: 8.5.312.10
Modified: 8.5.316.02

Specifies how Chat Server enables the session restoration from agent desktop and workflow:

  • none: The functionality is disabled.
  • agent: Allows Agent Desktop to start a session restoration.
  • esp: Allows the Workflow to start a session restoration.
  • both: Allows both Agent Desktop and Workflow to start a session restoration.

allow-duplicated-kvp

Section: settings
Default Value: true
Valid Values: true, false
Changes Take Effect: Immediately
Introduced: 8.5.201.05

With a value of "false", Chat Server will return an error when any duplicated key-value pairs (for example, pairs with the same key name) in userdata or event attributes in chat protocol requests are provided. With a value of "true", Chat Server will ignore such conditions (and will use the value from the latest key-value pair).

Attention: While the backward compatibility default value is set to "true", it is recommended it be set to "false" for more controlled behavior.

async-idle-notices

Section: settings
Default Value: major
Valid Values: none, major, major2, typing, all
Changes Take Effect: Immediately
Introduced: 8.5.202.09 (Restricted); 8.5.301.06 (Generally Available)
Modified: 8.5.310.09

Specifies which notifications count as async chat session activity for the purpose of inactivity control.

  • all: All user notifications are included (custom, push URL, typing on/off, update nickname).
  • major: Only major notifications are included (push URL, file uploaded, file deleted).
  • major2: Extends the major value with custom notifications.
  • none: All notifications are excluded.
  • typing: Only major and "typing on" notifications are included.

async-idle-close

Section: settings
Default Value: 3600
Valid Values: Any integer from 1-1728000
Changes Take Effect: Immediately
Introduced: 8.5.202.09 (Restricted); 8.5.301.06 (Generally Available)

Specifies, in seconds, a timeout that starts after "async-idle-alert" (enabled only for async chat sessions). If any qualifying activity occurs, (see "async-idle-alert" for a description of what qualifies as activity), the timeout stops and "async-idle-alert" timer is reset. If no qualifying activity is detected during this timeout, Chat Server:

  • Sends the IDLE_CONTROL_CLOSE notice with a message specified by the value of the "message-close" option (in the section [inactivity-control]).
  • Closes the chat session.

async-idle-alert

Section: settings
Default Value: 86400
Valid Values: Any integer from 1-1728000
Changes Take Effect: Immediately
Introduced: 8.5.202.09 (Restricted); 8.5.301.06 (Generally Available)

Specifies an inactivity alert timeout (in seconds) which is enabled only for async chat sessions. The inactivity timeout is set (or reset) for a session after any of the following activities: agent joined or left, any chat participant sent a message or a notice (as defined by "async-idle-notices"). If no qualifying activity is detected during this timeout, Chat Server:

  • Sends the IDLE_CONTROL_ALERT notice with a message specified by the value of the "message-alert" option (in the section [inactivity-control]).
  • Updates the interaction properties: GCTI_Chat_AsyncStatus=3 and GCTI_Chat_AsyncCheckAt={time to check interaction at}.
  • Starts the timeout specified by the value of the "async-idle-close" option.

async-chat-enforce

Section: settings
Default Value: none
Valid Values: none, flex, basic, both
Changes Take Effect: Immediately
Introduced: 8.5.307.04

Specifies when Chat Server forces chat sessions to run in async mode.

  • none: no forcing is applied.
  • flex: chat sessions run in async mode, when started via flex chat protocol.
  • basic: chat sessions run in async mode, when started via basic chat protocol.
  • both: all chat sessions run in async mode.

async-idle-notices

Section: settings
Default Value: major
Valid Values: none, major, major2, typing, all
Changes Take Effect: Immediately
Introduced: 8.5.202.09 (Restricted); 8.5.301.06 (Generally Available)
Modified: 8.5.310.09

Specifies which notifications count as async chat session activity for the purpose of inactivity control.

  • all: All user notifications are included (custom, push URL, typing on/off, update nickname).
  • major: Only major notifications are included (push URL, file uploaded, file deleted).
  • major2: Extends the major value with custom notifications.
  • none: All notifications are excluded.
  • typing: Only major and "typing on" notifications are included.

include-notices

Section: inactivity-control
Default Value: major
Valid Values: none, major, major2, typing, all
Changes Take Effect: Immediately
Modified: 8.5.310.09

Specifies which notifications count as chat session activity for the purpose of inactivity control.

  • all: All user notifications are included (custom, push URL, typing on/off, update nickname).
  • major: Only major notifications are included (push URL, file uploaded, file deleted).
  • major2: Extends the major value with custom notifications.
  • none: All notifications are excluded.
  • typing: Only major and "typing on" notifications are included.

session-restore-do-purge

Section: settings
Default Value: false
Valid Values: true, false
Changes Take Effect: Immediately
Introduced: 8.5.312.10

Enables or disables sending purging requests to Chat Server which handles the chat session before it is restored in this instance.

session-restore-extend-by

Section: settings
Default Value: none
Valid Values: none, agent, esp, both
Changes Take Effect: Immediately
Introduced: 8.5.312.10
Modified: 8.5.316.02

Specifies how Chat Server enables the session restoration from agent desktop and workflow:

  • none: The functionality is disabled.
  • agent: Allows Agent Desktop to start a session restoration.
  • esp: Allows the Workflow to start a session restoration.
  • both: Allows both Agent Desktop and Workflow to start a session restoration.

Genesys Engage Chat

The Genesys Engage Chat channel is part of the Genesys Engage Digital (eServices) platform. It leverages the same queuing and routing engine used for all media types (voice, digital, and social) to route chats to agents based on resource skills and availability, as well as the customer's contact history. A unified agent desktop and reporting components round out the solution.

Genesys Engage Chat also has the following capabilities:

  • Mobile chat, which provides push notifications and chat for mobile apps.
  • Asynchronous chat, which enables users to connect with enterprises on their own terms and continue the conversation whenever they have free time. They can send a message when no agents are available and chat sessions will continue even when neither party is active on the session.

What's New

All 9.x products 9.x Genesys Engage Chat Release Notes
Product Component Latest Starting

Chat Server

Chat Business Process Sample

8.5.309.12

8.5.306.05

Chat Server

8.5.316.02

8.5.201.05


Documentation

Chat Server Administration Guide

Get recommendations for monitoring and adjusting your Chat Server configuration.

Chat Server Administration Supplement (Restricted)

This supplement provides additional information to the Chat Server Administration Guide

Configuration Options

Find the latest information on configuration options for selected eServices components:

More Release Information

This page was last edited on September 18, 2020, at 13:39.
Comments or questions about this documentation? Contact us for support!