Jump to: navigation, search

Customizing the Chat Routing Strategy

When you create your Web Engagement application, Genesys Web Engagement also creates default Engagement Logic and Chat Routing SCXML strategies in the \apps\application_name\resources\_composer-projects\ folder. Orchestration Server (ORS) uses these strategies to decide whether and when to make a proactive offer and which channels to offer (chat or web callback).

The default Chat Routing strategy delivers chat interactions that are initiated in Genesys Web Engagement to a specific target. Although this strategy is included as part of the Web Engagement installation, it is possible to use your own existing strategy for routing. For example, a URS-based chat routing strategy; however, in this scenario you will need to adjust the Web Engagement solution to support the pacing algorithm functionality.

You can modify the Chat Routing SCXML by importing the Composer project into Composer. The project is located here: \apps\application name\resources\_composer-projects\WebEngagement_ChatRouting\. Refer to the sections below for details about the Chat Routing strategy and how it can be modified.

Main Interaction Workflow

The default entry point to the GWE Chat Routing strategy is the Interaction Queue specified in the webengagementChatQueue option on the Web Engagement Cluster application.

The Interaction Queue.

The interaction process pulls interactions from this queue and sends them through the chat workflow:

The chat workflow
Important
If you decide to change the value of queueWebengagement, make sure to also adjust the name of the queue in the Chat Routing strategy.

The default Chat Routing strategy is straightforward and includes the following highlights in the workflow:

  1. Obtain information from the User Data of the chat interaction that is being routed. See the AssignCategory block in the Chat Routing Strategy for details.
  2. Send messages to the chat session from the routing strategy. See Sending Messages from the Chat Routing Strategy into the Chat Session for details.
  3. Branch the workflow based on categories obtained from the chat interaction User Data. See the BranchingByCategory block for details.
  4. Route to skill-based Virtual Groups. See the RouteCustomerServer and RouteCustomerCare blocks for details.
  5. Route to a static Agent Group. See Routing to a Static Agent Group for details.

Routing to a Static Agent Group

When you plan to route an interaction to a static Agent Group, you should specify the name of this group and the name of the Stat Server in the Target property of the RouteInteractionDefault block.

The Target property of the RouteInteractionDefault block.

In the image above, the Stat Server name is specified through the Variable(_data.StatServerName) variable. You can define this variable, or others like it, in Composer and Genesys Administrator.

Specifying Variables in Composer

Start

  1. Double click the interaction process - in this case, webme_chat.ixnprocess.
  2. Make sure that there are no elements selected in the opened interaction process.
  3. Access the interaction process variables by clicking "Access Project Variables", marked with a red square in the image below:

    Access the project variables
    In the image above, the StatServerName variable is used in the default Chat Routing strategy.

End

Specifying Variables in Genesys Administrator

The StatServerName parameter is set automatically by the Provisioning Tool when you install Genesys Web Engagement, but it can be changed manually.

Start

  1. Navigate to Provisioning > Environment > Scripts and find the script with the entry-point Interaction Queue. In this case, the script is Webengagement_Chat.Routing.
  2. In the Configuration tab, open the Orchestration section.
  3. Now you can see a list of parameters that are passed into the Chat Routing strategy, including StatServerName.

    The StatServerName parameter.

End

Sending Messages from the Chat Routing Strategy into the Chat Session

There are times when you might need to send messages into the chat session directly from the routing strategy. For example, this could be additional information messages, advertising messages, and so on.

The default Chat Routing strategy contains an External Service block that provides this functionality:

The External Services block lets you send message from the routing strategy.
Important
The External Service block is disabled by default.

Feedback

Comment on this article:

blog comments powered by Disqus
This page was last modified on October 30, 2015, at 10:03.