Jump to: navigation, search

privilege.voice.can-use

Section: interaction-workspace
Default Value: true
Valid Values: true, false.
Changes Take Effect: When the session is started or restarted.


When the value of this option is set to true, the agent is permitted to use the Voice channel.

intercommunication.voice.make-call-caller-id-business-attribute

Section: interaction-workspace
Default Value:
Valid Values: The name of a valid Business Attribute.
Changes Take Effect: When the session is started or restarted.


The name of the Business Attribute that contains the Attribute Values that are used as outbound caller IDs. This option is only applicable for external calls.

intercommunication.<media-type>.routing-based-targets

Section: interaction-workspace
Default Value:
Valid Values: A comma-separated list of valid object types from the following list: Agent, InteractionQueue
Changes Take Effect: When the session is started or restarted.


Specifies the list of targets that are contacted through the 'routing based' mechanism for the requests that are defined in the option 'intercommunication.<media-type>.routing-based-actions'. Note: The targets 'AgentGroup' and 'Skill' are always addressed through routing; therefore, they are not affected by this option.

intercommunication.<media-type>.routing-based-actions

Section: interaction-workspace
Default Value: OneStepTransfer
Valid Values: A comma-separated list of valid operation names from the following list: OneStepTransfer.
Changes Take Effect: When the session is started or restarted.


Specifies the list of 'routing based' actions that an agent is allowed to perform.

intercommunication.<media-type>.queue

Section: interaction-workspace
Default Value:
Valid Values: Name of a valid Script object of type Interaction Queue
Changes Take Effect: When the session is started or restarted.


Specifies the name of the Interaction Queue that is used by the 'routing based' feature for a Workitem. The following attached data are added by Worskpace: IW_RoutingBasedOriginalEmployeeId,IW_RoutingBasedTargetId,IW_RoutingBasedTargetType,IW_RoutingBasedRequestType.

privilege.twitter.can-use

Section: interaction-workspace
Default Value: false
Valid Values: true, false.
Changes Take Effect: When the session is started or restarted.


The agent is permitted to use the Twitter channel.

workbin.facebook.draft

Section: interaction-workspace
Default Value:
Valid Values: The name of a valid Script object of type Interaction Workbin that is owned by Agents.
Changes Take Effect: When the session is started or restarted.


Specifies the name of the workbin to be used to store draft Facebook posts.

workbin.facebook.in-progress

Section: interaction-workspace
Default Value:
Valid Values: The name of a valid Script object of type Interaction Workbin that is owned by Agents.
Changes Take Effect: When the session is started or restarted.


Specifies the name of the workbin to be used to store inbound Facebook posts for later processing, after an agent explicitely saves the Facebook post or submitted an outbound reply.

facebook.outbound-queue

Section: interaction-workspace
Default Value: Facebook Outbound Queue
Valid Values: A valid name of a Script of type Interaction Queue.
Changes Take Effect: When the session is started or restarted.


Specifies the name of the queue in which an outbound interaction is to be placed when an agent has completed editing it.

facebook.default-queue

Section: interaction-workspace
Default Value: Facebook Outbound Queue
Valid Values: A valid name of a Script of type Interaction Queue.
Changes Take Effect: When the session is started or restarted.


Specifies the name of the queue in which outbound interactions are first created. This name must be identical to the name of the default queue in the configuration layer.

delivering-timeout

Section: settings
Default Value: 30
Valid Values: Any integer from 1 to 86,400 (24 hours)
Changes Take Effect: Immediately
Modified: 8.5.201.05

Specifies the timeout, in seconds, for an agent to accept an interaction that is being delivered to him or her. If the agent does not respond before the timeout expires, the interaction is revoked and returned to the queue from which it was taken by Universal Routing Server.

email.max-attachments-size

Section: interaction-workspace
Default Value: 0
Valid Values: A positive integer.
Changes Take Effect: When the session is started or restarted.


Specifies the maximum number of total megabytes of files that agents can attach to an external email interaction. An error message is displayed to the agent if the total number of megabytes for all attached files exceeds this value. The value 0 means that there is no restriction.

email.max-attachment-size

Section: interaction-workspace
Default Value: 0
Valid Values: A positive integer.
Changes Take Effect: When the session is started or restarted.


Specifies the maximum number of megabytes of one file that agents can attach to an external email interaction. The attachment is refused by the system and an error message is displayed to the agent if the size in megabytes of the attached file exceeds this value. The value 0 means that there is no restriction.

workbin.email.in-progress

Section: interaction-workspace
Default Value:
Valid Values: The name of a valid Script object of type Interaction Workbin that is owned by Agents.
Changes Take Effect: When the session is started or restarted.


The name of the workbin that is to be used to store inbound email for later processing, after an agent explicitly saved the email or submitted an outbound reply.

email.outbound-queue

Section: interaction-workspace
Default Value:
Valid Values: A valid name of a Script of type Interaction Queue.
Changes Take Effect: When the session is started or restarted.


Specifies the Interaction Queue in which outbound emails are placed when agents click Send or Send Interim. This options is used only when Interaction Workflow does not set Queue for New Interactions when it is routing inbound email interactions to agents.

email.default-queue

Section: interaction-workspace
Default Value:
Valid Values: A valid name of a Script of type Interaction Queue.
Changes Take Effect: When the session is started or restarted.


Specifies the Interaction queue in which new or reply outbound emails are submitted.

teamcommunicator.max-size

Section: interaction-workspace
Default Value: 50
Valid Values: An integer value from 0 through 100.
Changes Take Effect: When the session is started or restarted.
Related Options: teamcommunicator.show-all-internal-targets

Specifies the maximum size of the default list when the value of teamcommunicator.show-all-internal-targets is set to true.

teamcommunicator.corporate-favorites

Section: interaction-workspace
Default Value:
Valid Values: A comma-separated list of favorite names (section names) that are defined in the Workspace application.
Changes Take Effect: When the session is started or restarted.


Specifies the list of corporate favorites (quick dial favorites) that are configured in the Configuration Server for an Agent, Agent Group, Skill, Routing Point, or Custom Contact. See the Procedure: Creating Corporate Favorites for information about creating Corporate Favorite objects in the configuration layer. This option can be overridden by a routing strategy as described in this Deployment Guide.

intercommunication.email.routing-based-targets

Section: interaction-workspace
Default Value:
Valid Values: A comma-separated list of valid object types from the following list: Agent, InteractionQueue
Changes Take Effect: When the session is started or restarted.
Dependencies: intercommunication.email.routing-based-actions

Specifies the list of targets that are contacted through the routing based mechanism for the requests that are defined by the intercommunication.email.routing-based-actions option. Note: The targets 'AgentGroup' and 'Skill' are always addressed through routing; therefore, they are not affected by this option.

intercommunication.chat.routing-based-targets

Section: interaction-workspace
Default Value:
Valid Values: A comma-separated list of valid object types from the following list: Agent, InteractionQueue
Changes Take Effect: When the session is started or restarted.
Dependencies: intercommunication.chat.routing-based-actions

Defines the list of targets that are contacted through the routing based mechanism for the requests that are defined by the intercommunication.chat.routing-based-actions option. Note: The targets 'AgentGroup' and 'Skill' are always addressed through routing; therefore, they are not affected by this option.

intercommunication.chat.queue

Section: interaction-workspace
Default Value:
Valid Values: Name of a valid Script object of type Interaction Queue
Changes Take Effect: When the session is started or restarted.


Specifies the name of the Interaction Queue that is used by the 'routing based' feature for Chat. The following attached data are added by Worskpace: IW_RoutingBasedOriginalEmployeeId,IW_RoutingBasedTargetId,IW_RoutingBasedTargetType,IW_RoutingBasedRequestType.

intercommunication.email.queue

Section: interaction-workspace
Default Value:
Valid Values: Name of a valid Script object of type Interaction Queue
Changes Take Effect: When the session is started or restarted.


Specifies the name of the Interaction Queue that is used by the routing based feature for email. The following attached data are added by Worskpace: IW_RoutingBasedOriginalEmployeeId,IW_RoutingBasedTargetId,IW_RoutingBasedTargetType,IW_RoutingBasedRequestType.

intercommunication.voice.single-step-transfer-enabled

Section: interaction-workspace
Default Value: Agent, AgentGroup, RoutingPoint, Contact, TypeDestination, Skill
Valid Values: A comma-separated list of valid object types from the following list: Agent, AgentGroup, RoutingPoint, Contact, TypeDestination, Skill.
Changes Take Effect: When the session is started or restarted.


Specifies the list of targets enabled in Team Communication for a single step transfer.

intercommunication.voice.single-step-conference-enabled

Section: interaction-workspace
Default Value: Agent, AgentGroup, RoutingPoint, Contact, TypeDestination, Skill
Valid Values: A comma-separated list of valid object types from the following list: Agent, AgentGroup, RoutingPoint, Contact, TypeDestination, Skill.
Changes Take Effect: When the session is started or restarted.


Specifies the list of targets enabled in Team Communication for a single step conference.

intercommunication.voice.make-call-enabled

Section: interaction-workspace
Default Value: Agent, AgentGroup, RoutingPoint, Contact, TypeDestination, Skill
Valid Values: A comma-separated list of valid object types from the following list: Agent, AgentGroup, RoutingPoint, Contact, TypeDestination, Skill.
Changes Take Effect: When the session is started or restarted.


Specifies the list of targets enabled in Team Communication for making call.

intercommunication.voice.consultation-enabled

Section: interaction-workspace
Default Value: Agent, AgentGroup, RoutingPoint, Contact, TypeDestination, Skill
Valid Values: A comma-separated list of valid object types from the following list: Agent, AgentGroup, RoutingPoint, Contact, TypeDestination, Skill.
Changes Take Effect: When the session is started or restarted.


Specifies the list of targets enabled in Team Communication for a consultation.

intercommunication.voice.routing-points

Section: interaction-workspace
Default Value:
Valid Values: The call number names of the routing point in the following format: $dn_name@switch$
Changes Take Effect: When the session is started or restarted.


Specifies the call number that is used by the Routing Base feature for outbound calls. The following attached data are added by Workspace: IW_RoutingBasedOriginalEmployeeId,IW_RoutingBasedTargetId,IW_RoutingBasedTargetType,IW_RoutingBasedRequestType.

intercommunication.voice.routing-based-actions

Section: interaction-workspace
Default Value: MakeCall,OneStepConference,InitConference,OneStepTransfer,InitTransfer
Valid Values: A comma-separated list of valid operation names from the following list: MakeCall, OneStepTransfer, InitTransfer, InitConference, OneStepConference.
Changes Take Effect: When the session is started or restarted.
Related Options: intercommunication.voice.routing-based-targets

Specifies the list of Routing Based Actions that an agent may perform.

intercommunication.voice.routing-based-targets

Section: interaction-workspace
Default Value:
Valid Values: A comma-separated list of valid object types from the following list: Agent, RoutingPoint, TypeDestination, OutboundRecord, Contact
Changes Take Effect: When the session is started or restarted.
Dependencies: intercommunication.voice.routing-based-actions

Specifies the list of targets that are contacted through the routing based mechanism for the requests that are defined by the intercommunication.voice.routing-based-actions option. Note: The targets AgentGroup and Skill are always addressed through routing; therefore, they are not affected by this option.

intercommunication.voice.routing-points

Section: interaction-workspace
Default Value:
Valid Values: The call number names of the routing point in the following format: $dn_name@switch$
Changes Take Effect: When the session is started or restarted.


Specifies the call number that is used by the Routing Base feature for outbound calls. The following attached data are added by Workspace: IW_RoutingBasedOriginalEmployeeId,IW_RoutingBasedTargetId,IW_RoutingBasedTargetType,IW_RoutingBasedRequestType.

teamcommunicator.max-size

Section: interaction-workspace
Default Value: 50
Valid Values: An integer value from 0 through 100.
Changes Take Effect: When the session is started or restarted.
Related Options: teamcommunicator.show-all-internal-targets

Specifies the maximum size of the default list when the value of teamcommunicator.show-all-internal-targets is set to true.

teamcommunicator.show-all-internal-targets

Section: interaction-workspace
Default Value: false
Valid Values: true, false.
Changes Take Effect: When the session is started or restarted.


Specify whether all internal targets are displayed by default in the Team Communicator when an agent is searching for a transfer or conference target, including all Agents, Agent Groups, Skills, and Routing Points.

privilege.teamcommunicator.display-agent-groups-availability

Section: interaction-workspace
Default Value: true
Valid Values: true, false.
Changes Take Effect: When the session is started or restarted.


Allows an agent to view the number of agents ready in agent groups in Team Communicator. Depends on 'Team Communicator - Can Use' and 'Team Communicator - Can View Favorites'.

presence.evaluate-presence

Section: interaction-workspace
Default Value: true
Valid Values: true, false.
Changes Take Effect: When the session is started or restarted.


When this option is set to true, the presence (availability) of an agent or agent group (when configured) is shown in Team Communicator in the search results.

privilege.voice.can-use

Section: interaction-workspace
Default Value: true
Valid Values: true, false.
Changes Take Effect: When the session is started or restarted.


When the value of this option is set to true, the agent is permitted to use the Voice channel.

teamcommunicator.permissions.agent.exclude-from-agent-groups

Section: interaction-workspace
Default Value: No default value
Valid Values: A comma-separated list of Agent Groups; empty means Workspace doesn't exclude any agent groups.
Changes Take Effect: When the session is started or restarted.
Introduced: 8.5.202.04
Related Options: teamcommunicator.permissions.agent.restrict-to-agent-groups

Specifies the list of agent groups (virtual agent groups aren't supported) used to exclude agents returned in a Team Communicator search. Agents who belong to at least one of these agent groups are excluded from the list. Note: This overrides the Template loop detected: Template:Optionslink filter where there is overlap. For example, if an agent belongs to groups A and B, and the exclude filter specifies B while the include filter specifies A, the agent is excluded from the returned list.

teamcommunicator.permissions.agent.restrict-to-agent-groups

Section: interaction-workspace
Default Value: No default value
Valid Values: A comma-separated list of Agent Groups; empty means no restriction are applied.
Changes Take Effect: When the session is started or restarted.
Introduced: 8.5.202.04

Specifies the list of agent groups (virtual agent groups aren't supported) used to restrict agents returned in a Team Communicator search. Agents who belong to at least one of these agent groups are included in the list.

privilege.teamcommunicator.can-use

Section: interaction-workspace
Default Value: true
Valid Values: true, false.
Changes Take Effect: When the session is started or restarted.


Allows access to the Team Communicator.

Enabling Internal And External Communications

The following procedures enable internal and external communication features in Workspace Web Edition.

Configuring Team Communicator

Team Communicator is a universal lookup tool. Agents use the Team Communicator to start phone calls and emails. The following procedures enable features in Team Communicator.

Enabling Team Communicator

You can enable agents to use Team Communicator to call a contact that is stored in the Universal Contact Server (UCS).

Before you begin, ensure that the following prerequisites are met:

To enable agents to use Team Communicator to call a contact:

  1. Grant the privilege.teamcommunicator.can-use privilege.
  2. Configure the Team Communicator options in the interaction-workspace section of the WS_Cluster application object.
  3. To restrict which agents can be seen in Team Communicator search results, you can specify which groups an agent can or cannot see by specifying them in these configuration options:
  4. Ensure that the UCS application to which WS_Cluster is connected is configured to support index searches in the Contact database:
    • Set the index\enabled option to true.
    • Set the index.contact\enabled option to true.

    For more details about these settings, refer to the eServices 8.1 Reference Manual.

Enabling call routing and voice call, conference, or transfer

You can enable agents to use Team Communicator to call, conference, or transfer to an agent, agent group, skill, or a routing point using a strategy. This procedure is mandatory for agent groups and skill targets.

Tip
No extra configuration is required to transfer an interaction to an agent.

Before you begin, ensure that the following prerequisites are met:

  • A working knowledge of Genesys Administrator or Configuration Manager.
  • A working knowledge of Genesys Designer.
  • A WS_Cluster application object exists in the Configuration Database.
  • To transfer to skills, you must have skills defined in the Configuration Database.
  • To transfer to agent groups, you must have agent groups defined in the Configuration Database.

To enable agents to use Team Communicator to call, conference, or transfer to an agent, agent group, skill, or a routing point:

  1. Set up your system infrastructure:
    1. In the Configuration tab of the WS_Cluster application, add connections to the following servers:
      • Stat Server
      • Universal Contact Server (Optional)
    2. In the connections, add a reference to the T-Server associated with the switch to which the agent logs in.
    3. Configure the Team Communicator options in the interaction-workspace section of the WS_Cluster application object.
  2. Set up your agents to be able to use the Team Communicator to call or transfer to other agents or other internal targets:
    1. To let your agents make voice calls, set the value of the privilege.voice.can-use option, to true.
    2. To ensure that the status of your agents is displayed in the Team Communicator of other agents who might be trying to call them, set the value of the presence.evaluate-presence option to true.
    3. To enable your agents to view the number of targets who are in Ready status in an agent group, perform the following steps:
      1. Add the following definition for the VIRTUAL_AGENT_GROUP and AGENT_GROUP object types to the statistics.yaml file: TransferAvailability_CurrentReadyAgents.
      2. Allow the privilege.teamcommunicator.display-agent-groups-availability privilege.
    4. For small contact centers, where the number of potential transfer targets is low, you can configure Workspace to display all of the possible targets in the Team Communicator search results when an agent initiates a transfer or conference by searching in the Team Communicator.
      To enable this functionality, set the value of the teamcommunicator.show-all-internal-targets option to true.
      This option is limited by the value that is specified for the teamcommunicator.max-size option.
      Important
      Genesys strongly recommends that only small contact centers use this option. Agents in large contact centers will experience system performance issues if the teamcommunicator.show-all-internal-targets option is enabled.
  3. You can choose to set up call routing to direct calls to specific agents based on strategies. To transfer to Skills and Groups, you must also create a routing point by using the intercommunication.voice.routing-points option.
    1. First determine which call flow scenarios you want handled by a routing-based mechanism based on targets, such as langauge or product skills, level of training, or availability, and types of calls, such as high priority customers, inquiries, sales, and so on.
    2. Use Genesys Designer, to create a routing strategy that uses routing targets (agents, agent groups, skills, and so on) to process routing-based actions by using the following attached data:
      • IW_RoutingBasedOriginalEmployeeId — The employee ID of the agent who is transferring the interaction.
      • IW_RoutingBasedTargetId — The ID (employee ID of another agent, AgentGroup name, Skill name, Routing Point name) of the target.
      • IW_RoutingBasedTargetType — The type of the target (Agent, AgentGroup, Skill, or RoutingPointl)
      • IW_RoutingBasedRequestType — Informs the strategy of the type of action is to be done (MakeCall,OneStepConference,InitConference,OneStepTransfer,InitTransfer)
    3. Depending on the type of target for which you want to use routing-based transfer, use Configuration Manager or Genesys Administrator to set the value of the intercommunication.voice.routing-based-targets options as follows:
      • To use T-Server to handle transfers to Agent, Routing Point, and Type Destination, and have all other transfers handled by a strategy, set the value of this option to "" (empty)
      • To use routing-based transfer for Agents, add the value Agent to this option.
      • To use routing-based transfer for Routing Point, add the value RoutingPoint to this option.
      • To use routing-based transfer for Type Destination (a dialed call), add the value TypeDestination to this option.
      • For agent groups and skills, it is not mandatory to set the routing-based target option because these target always use routing-based transfer.
    4. To specify whether a specific call type is to be handled by the routing-based mechanism, set the value of the intercommunication.voice.routing-based-actions option.
      • MakeCall: Use the routing-based mechanism for external calls.
      • OneStepTransfer: Use the routing-based mechanism for single-step transfers.
      • InitTransfer: Use the routing-based mechanism for two-step transfers.
      • InitConference: Use the routing-based mechanism for two-step conferences.
      • OneStepConference: Use the routing-based mechanism for single-step conferences.
    5. Load the routing strategy on the Routing Point that is defined by the intercommunication.voice.routing-points option.
  4. Fine-tune the settings for contacting specific targets (Agent, AgentGroup, RoutingPoint, Contact, and/or TypeDestination) that are using a routing-based mechanism by configuring action-specific options:

Enabling multimedia interaction transfer

You can enable agents to use Team Communicator to transfer a multimedia interaction (Email and Chat) to an agent, agent group, or skill by using a strategy. This procedure is mandatory to transfer to agent groups and skills.

Before you begin, ensure that the following prerequisites are met:

  • A working knowledge of Genesys Administrator or Configuration Manager.
  • A working knowledge of Genesys Designer.
  • A WS_Cluster application object exists in the Configuration Database.
  • To transfer to skills, you must have skills defined in the Configuration Database.
  • To transfer to agent groups, you must have agent groups defined in the Configuration Database.

To enable agents to use Team Communicator to transfer a multimedia interactions:

  1. By using Genesys Designer, configure a routed-based transfer workflow by using these steps:
    1. Create an Interaction Queue/Interaction View pair. The Interaction Queue is used as a part of the workflow; however, Interaction Queues are not available as transfer targets in the agent interface.
    2. Create a routing strategy to process routing-based actions. To help you write the appropriate strategy, Workspace Web Edition adds the following attached data to the interaction:
      • IW_RoutingBasedOriginalEmployeeId — The employee ID of the agent who is transferring the interaction.
      • IW_RoutingBasedTargetId — The ID (employee ID of another agent, AgentGroup name, Skill name) of the target.
      • IW_RoutingBasedTargetType — The type of the target (Agent, AgentGroup, or Skill)
      • IW_RoutingBasedRequestType — Informs the strategy of the type of action is to be done. This attached data has only one value available for this release: OneStepTransfer
    3. Link the above Queue to the strategy.
    4. Activate the strategy.
  2. By using Configuration Manager or Genesys Administrator, set the values of the following configuration options to the Queue that you created in Step 1:
  3. Depending on the type of target for which you want to use routing-based transfer, use Configuration Manager or Genesys Administrator to set the values of the intercommunication.chat.routing-based-targets and intercommunication.email.routing-based-targets configuration options as follows:
    • To use Interaction Server to handle agent-to-agent transfer and have all other transfers handled by a strategy, set the values of these options to "" (empty)
    • To use routing-based transfer for Agents, set the values of these options to Agent.
    • For agent groups and skills, it is not mandatory to set the routing-based target options because these target always use routing-based transfer.
  4. Log out agents and log them back in again.

Creating Corporate Favorites

You can enable the use of corporate favorites in the Team Communicator. Administrators must create, edit, and remove favorites by using either Configuration Manager or Genesys Administrator. You can configure the system so that each agent is assigned one or more quick dial favorites lists. You do not have to assign the same list of favorites to every agent.

Before you begin, ensure that the following prerequisites are met:

  • A working knowledge of Genesys Administrator.
  • An understanding of Configuration options
  • A WS_Cluster application object exists in the Configuration Database.

To enable the use of corporate favorites:

  1. By using either Configuration Manager or Genesys Administrator, create a new section in the appropriate object (the WS_Cluster application, Tenant, Agent Group, or Agent), and name it with the name of the Corporate Favorite that you want to create.
  2. Configure the new Corporate Favorite section to be one of the following types:
    • Agent
    • Agent Group
    • Skill
    • Routing Point
    • Custom Contact
    • Interaction Queue

Attached Data

You can have multiple instances of the same object type, such as a routing point, in corporate favorites with different attached data for each. For example:

[Fav-English] [Fav-Spanish]
type: RoutingPoint type: RoutingPoint
id: 6666@MySwitch

Note: the following characters are not supported for the id:
?|{}[]()"\,

id: 6666@MySwitch

Note: the following characters are not supported for the id:
?|{}[]()"\,

display-name: English display-name: Spanish
attached-data.lang: en attached-data.lang: es

Corporate Favorite Options by Type

The Table Corporate Favorite Options by Type defines the Corporate Favorite types and the mandatory options.</li> </ol>

Important
A corporate favorite that has Custom Contact specified as the type only appears in a Favorites search and the Recent list if the contact was previously called. Search All only searches within targets that specify the following types: Agent, Contact, Routing Point, Skill, Queue, Interaction Queue, and Agent Group.
Corporate Favorite Options by Type
Type Options Mandatory Valid values Example
Agent type Yes Agent Agent
id Yes <user name of the agent> User123

Note: the following characters are not supported for the id: ?|{}[]()"\,

category Yes <a semicolon-separated list of category names> CorporateCategory1;FavoriteAgents
display-name No <display name of the agent> Jim Brown
Agent Group type Yes AgentGroup AgentGroup
id Yes <name of the agent group> Agent Group Meridian

Note: the following characters are not supported for the id: ?|{}[]()"\,

category Yes <a semicolon-separated list of category names> CorporateCategory1;FavoriteAgents
display-name No <display name of the agent group> Meridian
Skill type Yes Skill Skill
id Yes <name of the skill> French

Note: the following characters are not supported for the id: ?|{}[]()"\,

category Yes <a semicolon-separated list of category names> French Speaking Agents;Mandarin Speaking Agents
display-name No <display name of the skill> French
Routing Point type Yes RoutingPoint RoutingPoint
id Yes The DN number in the following format: <DN number>@<switch> 123@MySwitch

Note: the following characters are not supported for the id: ?|{}[]()"\,

category Yes <a semicolon-separated list of category names> CorpRoutingPoint
display-name No <display name of the routing point> Support
attached-data.<AttachedDataKey> No <an attached data key> attached-data.lang: en
Directly Dialed type Yes CustomContact CustomContact
category Yes <a semicolon-separated list of category names> External Resources
firstname No <any string> First
lastname No <any string> External
phonenumber Yes (one or both) <a semicolon-separated list of phone numbers> +1555234567890;+555123454321
emailaddress <a semicolon-separated list of email addresses> external1@mail.dom;external2@mail.dom
display-name No <display name of the custom contact> Angie Davis
Interaction Queue type Yes InteractionQueue InteractionQueue
id Yes <script name of the interaction queue> 123

Note: the following characters are not supported for the id: ?|{}[]()"\,

category Yes <a semicolon-separated list of category names> CorporateCategory1;FavoriteAgents
display-name No <display name of the interaction queue> Quality Assurance
  1. In the configuration layer, in options of the related section (or Tenant/Agent Group/Agent annexes), configure the following options in the interaction-workspace section of agent, agent group, tenant, and/or application annexes:
    • teamcommunicator.corporate-favorites -- The list of corporate favorites (quick dial favorites) that are configured in Configuration Server for an Agent, Agent Group, Skill, Routing Point, or Custom Contact in the same tenant as the agent. Favorites that are configured at the agent level take precedence over those that are configured at the agent group level, which take precedence over the tenant level, which takes precedence over the application level.
    • teamcommunicator.max-size -- The maximum number of favorites to display to the agent in the Team Communicator drop-down view.

Assignment of Favorites

When you create corporate favorites, you assign to them a type that is based on the scope to which it is applied: agent, agent group, tenant, or application. You can create multiple favorites and assign them in a hierarchy. For example, you create four favorites: fav1, fav2, fav3, and fav4. You then make the following assignments:

  1. application—teamcommunicator.corporate-favorites="fav1,fav2"
  2. tenant—teamcommunicator.corporate-favorites="fav4"
  3. agent—teamcommunicator.corporate-favorites="fav1,fav3"

The final list of favorites that are assigned to the agent are: "fav1,fav3"

Enabling the Email channel

You can enable agents to use Email to correspond with a contact that is stored in Universal Contact Server (UCS).

Before you begin, ensure that the following prerequisites are met:

  • A working knowledge of Genesys Administrator.
  • The WS_Cluster application object exists in the Configuration Database.
  • The WS_Cluster application has a connection to Universal Contact Server and Interaction Server.
  • Procedure: Enabling agents to manage contacts.
  • A capacity rule that allows Agents to receive email interactions.

To enable agents to email contacts:

  1. Configure the Email options in the interaction-workspace section of the WS_Cluster application object.
  2. Configure the email queue options in the email section that are mandatory for basic email processing: email.default-queue and email.outbound-queue.
  3. Configure the Workbin options in the interaction-workspace section of the WS_Cluster application object, them), in particular: workbin.email.in-progress and workbin.email.draft.
  4. To control the size of an attachment that agents are allowed to attach to an external email interaction, configure the email.max-attachment-size option in the interaction-workspace section of the WS_Cluster application object.
  5. To control the total size of attachments that agents are allowed to attach to an external email interaction, configure the email.max-attachments-size option in the interaction-workspace section of the WS_Cluster application object.

Enabling the Chat channel

You can enable agents to use the Chat channel to handle inbound chat interactions from a contact that is stored in Universal Contact Server (UCS).

Before you begin, ensure that the following prerequisites are met:

  • A working knowledge of Genesys Administrator.
  • The WS_Cluster application object exists in the Configuration Database.
  • The WS_Cluster application has a connection to Universal Contact Server and Interaction Server.
  • Enabling Agents To Manage Contacts.
  • A capacity rule that allows Agents to receive chat interactions.

To enable the Chat channel:

  1. Configure the Chat options in the interaction-workspace section of the WS_Cluster application object.
  2. To enable Chat transfer without a strategy, in the Chat Media Type Object, set the value of the delivering-timeout option to 20 seconds or less.

Enabling agents to join an Outbound Campaign functionality to a contact

You can enable agents to join an Outbound Campaign call to a contact that is stored in Outbound Contact Server (OCS).

Before you begin, ensure that the following prerequisites are met:

  • A working knowledge of Genesys Administrator.
  • The Application object exists in the Configuration Database.

To enable agents to join an Outbound Campaign call to a contact:

  1. Allow the Outbound privileges (see [Outbound|Outbound Campaign configuration options]) for the role to which the agent is assigned.
    • Can Use
    • Can Reject Record
    • Can Cancel Record
    • Can Dial Alternative Chained Record
    • Can Get Next Preview Record
    • Can Mark Do Not Call
    • Can Set Call Result
    • Can Reschedule
    • Can Reschedule On New Number
  2. Configure the Outbound options in the interaction-workspace section of the Workspace Application object (refer to the Outbound configuration option reference for a list of Outbound options and a description of how to configure them).

Enabling the Facebook channel

You can enable agents to use the Facebook channel to handle inbound Facebook interactions from a contact that is stored in Universal Contact Server (UCS).

Before you begin, ensure that the following prerequisites are met:

  • A working knowledge of Genesys Administrator.
  • The WS_Cluster application object exists in the Configuration Database.
  • The WS_Cluster application has a connection to Universal Contact Server and Interaction Server.
  • Enabling Agents To Manage Contacts.
  • A capacity rule that allows Agents to receive Facebook interactions.

To enable the Facebook channel:

  1. Configure the Facebook options in the interaction-workspace section of the WS_Cluster application object.
  2. Configure the Facebook queue options in the interaction-workspace section that are mandatory for basic Facebook processing: facebook.default-queue and facebook.outbound-queue.
  3. Configure the Workbin options in the interaction-workspace section of the WS_Cluster application object, them), in particular: workbin.facebook.in-progress and workbin.facebook.draft.

Enabling the Twitter channel

You can enable agents to use the Twitter channel to handle inbound Twitter interactions from a contact that is stored in Universal Contact Server (UCS).

Before you begin, ensure that the following prerequisites are met:

  • A working knowledge of Genesys Administrator.
  • The WS_Cluster application object exists in the Configuration Database.
  • The WS_Cluster application has a connection to Universal Contact Server and Interaction Server.
  • Enabling Agents To Manage Contacts.
  • A capacity rule that allows Agents to receive Twitter interactions.

To enable the Twitter channel:

  1. Configure the Twitter options in the interaction-workspace section of the WS_Cluster application object. To enable the Twitter channel, configure the privilege.twitter.can-use configuration option.

Enabling Agent Workbins

You can enable agents to use Agent Workbins to receive and/or store contact interactions for future processing.

  • A working knowledge of Genesys Administrator.
  • The WS_Cluster application object exists in the Configuration Database.
  • The WS_Cluster application has a connection to Universal Contact Server and Interaction Server.
  • Enabling Agents To Manage Contacts.

To enable Agent Workbins:

  1. Use Genesys Composer to create a Workbin.
  2. In Genesys Administrator, declare the Workbin in the interaction-workspace section of the Options tab of the WS_Cluster application object, following the generic rule: workbin.<media_type>.<workbin-nick-name>=<workbin-script-name>.
  3. Configure the following Workbin configuration options

Enabling contact history management

You can enable an agent to view and update the email and chat interaction history of a contact.

Before you begin, ensure that the following prerequisites are met:

  • A working knowledge of Genesys Administrator.
  • The WS_Cluster application object exists in the Configuration Database.
  • The WS_Cluster application has a connection to Universal Contact Server.

To enable contact history management

  1. Configure the Contact options in the interaction-workspace section of the WS_Cluster application object.
  2. Enable an index search on contacts to enable searches on contact interactions. For more information about enabling index searches, refer to the eServices 8.1 User's Guide.

Enabling disposition codes

You can enable agents to specify the outcome (disposition) of an interaction.

Before you begin, ensure that the following prerequisites are met:

  • A working knowledge of Genesys Administrator.
  • A WS_Cluster application object exists in the Configuration Database.
  • The agent object is configured to use one or more of the following media channels:

To enable disposition codes:

  1. In Genesys Administrator, create or update a Business Attribute in the tenant that contain(s) your agents.
    • The Type of the Business Attribute is Interaction Operation Attributes.
    • The Attribute values are the codes that are available for the agent:
      • name—Used in attached data.
      • display name—Used in the Agent interface.
  2. In the interaction-workspace section, set the value of the interaction.disposition.value-business-attribute option to the name of the Business Attribute that you previously configured.
  3. Configure the following Interaction options in the interaction-workspace section of the WS_Cluster object:
  • interaction.disposition.is-mandatory
  • interaction.disposition.is-read-only-on-idle
  • interaction.disposition.key-name
  • interaction.disposition.use-attached-data
  • interaction.disposition.value-business-attribute

Enabling case information editing

You can enable an agent to edit the contents of case information.

Before you begin, ensure that the following prerequisites are met:

  • A working knowledge of Genesys Administrator.
  • A WS_Cluster object exists in the Configuration Database.
  • One or more custom Case Information Business Attributes in the Configuration Layer.

To enable case information editing:

  1. In Genesys Administrator, open a Case Information Business Attribute.
  2. In the Attributes Values tab, open the attribute value that you want to enable Agent to edit.
  3. Select the Options tab.
  4. Add a new section named interaction-workspace.
  5. Configure the option according to the values in the Editing Case Information table.
  6. Save your updates.

Enabling caller ID selection

You can enable agents to select a caller ID from pre-defined list of caller IDs.

Before you begin, ensure that the following prerequisites are met:

  • A working knowledge of Genesys Administrator.
  • A WS_Cluster object exists in the Configuration Database.

To enable caller ID selection:

  1. In Genesys Administrator, create a Business Attribute that contains the possible caller ID values you want agents to be able to select. In its Business Attribute Values, the name is used to specify the actual phone number Workspace dials. If the Display Name is specified, this is the information Workspace presents to the agent (in alphabetical order).
  2. Important
    If the Business Attribute doesn't contain any Business Attribute Values, then the feature isn't enabled. Also, if the attribute contains only one value, then the adapter automatically uses that caller ID so the agent doesn't see a popup when making a call.
  3. Set the intercommunication.voice.make-call-caller-id-business-attribute option to the name of your Business Attribute. For example, if you create a Business Attribute named CallerID, then you would set intercommunication.voice.make-call-caller-id-business-attribute to CallerID.

Enabling the Instant Messaging (IM) channel

You can enable agents to use the Instant Messaging channel for internal communication and interaction consultation.

Before you begin, ensure that the following prerequisites are met:

  • A working knowledge of Genesys Administrator.
  • The WS_Cluster application object exists in the Configuration Database.
  • The WS_Cluster application has a connection to SIP Server.

To enable the Instant Messaging channel:

  1. Configure the IM options in the interaction-workspace section of the WS_Cluster application object.
  2. Ensure that the SIP DN of the Place used for Instant Messaging has the following options defined in the [TServer] section:
    • multimedia = true
    • voice = true
    • sip-signaling-chat = none
    Important
    Workspace does not support a Place that uses one DN for voice and one DN for IM.


Enabling WebRTC

You can enable agents to use WebRTC for basic call control capabilities, such as:

  • Making a call
  • Answer a call
  • Disconnect a call
  • Place call on and off hold
  • Transfer
  • Conference
  • Place a consultation call
  • Generate DTMF tones using a keypad

Workspace also allows agents to provide feedback on call quality for calls that have low scores returned by the Genesys WebRTC JavaScript API.

Before you begin, ensure that the following prerequisites are met:

  • You have configured Jetty for SSL.
  • A working knowledge of Genesys Administrator.
  • The WS_Cluster application object exists in the Configuration Database.
Important
login.voice.prompt-dn-less-phone-number is mandatory for WebRTC.

To enable WebRTC:

  1. Configure the WebRTC options in the interaction-workspace section of the WS_Cluster application object.
  2. You should also make sure that privilege.voice.can-use is set to true.

Feedback

Comment on this article:

blog comments powered by Disqus
This page was last modified on September 26, 2018, at 06:22.