Revision as of 16:24, December 24, 2018 by Mwest (talk | contribs)
Jump to: navigation, search

contact.lookup.<media-type>.enable

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

Specifies that the Workspace features that rely on Universal Contact Server (UCS) for contact lookup when an interaction of the given media type is presented to the Agent are activated. This option can be overridden by a routing strategy as described in the Configuration Guide. Note: This option overwrites the contact.lookup.enable option. It is not taken into account when the attached data IdentifyCreateContact is set in the interaction. Use the voice-campaign media-type to define the lookup behavior in the context of outbound campaign interactions.

contact.last-called-agent.enable

Section: interaction-workspace
Default Value: false
Valid Values: true, false.
Changes Take Effect: When the session is started or restarted.
Dependencies: contact.last-called-agent.<media-type>.enable

Specifies if the last called agent properties are set in the contact when an interaction is presented to the agent. This option is taken into account only when the contact.last-called-agent.<media-type>.enable option is not defined for the applicable media type

contact.history.media-filters

Section: interaction-workspace
Default Value: $AllMedia$,voice,email,chat,twitter,facebook,$OtherMedia$
Valid Values: A comma-separated value of valid media type names or $AllMedia$ or $OtherMedia$.
Changes Take Effect: When the session is started or restarted.


Specifies the list of media types that can be used to filter the Contact History(depends on privilege.contact.can-filter-contact-history), My History(depends on privilege.contact.can-filter-my-history), and the result list of Interaction Search(depends on privilege.contact.can-filter-all-interactions). $AllMedia$ allows to add the filter to return any media. $OtherMedia$ allows to add the filter returning any media not listed in this option.

contact.date-search-types

Section: interaction-workspace
Default Value: On,OnOrAfter,Before,Between
Valid Values: A comma-separated list of the following options: On, OnOrAfter, OnOrBefore, Before, Between
Changes Take Effect: When the session is started or restarted.
Related Options: contact.default-directory-page-size

Specifies the list of search types that are available for the agent to use to search the contact database by date.

contact.history-search-attributes

Section: interaction-workspace
Default Value: Status,StartDate,EndDate,Subject
Valid Values: A comma-separated value list of Interaction attributes.
Changes Take Effect: When the session is started or restarted.


Specifies the list of interaction attributes that an agent can use in Advanced Search mode of the Contact History, My History and Interaction Search views. You can also use custom interaction attributes.

privilege.contact.can-filter-my-history

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


Enables agents to filter interactions within the My history view.

privilege.contact.can-advanced-search-my-history

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


Enables agents to do advanced searches within My History.

privilege.contact.can-search-my-history

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


Enables agents to search for interactions in the My History view.

contact.myhistory-displayed-columns

Section: interaction-workspace
Default Value: Status,Subject,StartDate,EndDate
Valid Values: A comma-separated value list of Contact History items to display in the interaction view MyHistory. For example: Status, Subject, StartDate, EndDate, MediaType
Changes Take Effect: When the session is started or restarted.
Modified: 8.5.202.94

Specifies the list of Contact History items that are displayed in the MyHistory view.

contact.history-displayed-columns

Section: interaction-workspace
Default Value: Status,Subject,StartDate,EndDate,OwnerId
Valid Values: A comma-separated value list of Contact History items to display in the interaction view, for example: Status, Subject, StartDate ,EndDate, OwnerId, MediaType.
Changes Take Effect: When the session is started or restarted.
Modified: 8.5.202.94

Specifies the list of Contact History items that are displayed in the interaction view.

contact.displayed-attributes

Section: interaction-workspace
Default Value: Title,FirstName,LastName,PhoneNumber,EmailAddress
Valid Values: A comma-separated value list of Attribute Value names that correspond to contact field names.
Changes Take Effect: When the session is started or restarted.


Specifies the list of contact fields that are displayed when a Contact record is displayed.

contact.directory-search-attributes

Section: interaction-workspace
Default Value: LastName,FirstName,PhoneNumber,EmailAddress
Valid Values: A comma-separated value list of Attribute Value names that correspond to contact field names that can be used as search parameters.
Changes Take Effect: When the session is started or restarted.


Specifies the list of Contact fields that can be used as search parameters.

contact.directory-enabled-modes

Section: interaction-workspace
Default Value: ListView,GridView
Valid Values: A comma-separated value list of views from the following list: ListView, GridView.
Changes Take Effect: When the session is started or restarted.


Specifies which view of the Contact Directory can be selected.

  • ListView: Quicker search performance and tokenized search items, but no sort on the result. This view can be enabled only if the 'Contact' index is activated in Universal Contact Server.
  • GridView: Results are sortable, but the search is less powerful, and the search items are non-tokenized.

contact.directory-displayed-columns

Section: interaction-workspace
Default Value: LastName,FirstName,PhoneNumber,EmailAddress
Valid Values: A comma-separated value list of Attribute Value names that correspond to contact field names. For example: LastName,FirstName,PhoneNumber,EmailAddress.
Changes Take Effect: When the session is started or restarted.


Specifies the list of contact fields that are displayed when the results of a contact search are displayed.

contact.directory-default-mode

Section: interaction-workspace
Default Value: ListView
Valid Values: A value from the following list: ListView, GridView
Changes Take Effect: When the session is started or restarted.


Specifies which view of the Contact Directory is displayed by default.

  • ListView: Quicker search performance and tokenized search items, but no sort on the result.
  • GridView: Results are sortable result, but the search is less powerful, and the search items are non-tokenized.

contact.default-directory-page-size

Section: interaction-workspace
Default Value: 10
Valid Values: An integer from 1 through 50.
Changes Take Effect: When the session is started or restarted.
Dependencies: contact.available-directory-page-size

Specifies the default value for the number of rows per page in the contact directory search result view. The value must be defined in the option contact.available-directory-page-size.

contact.cache-timeout-delay

Section: interaction-workspace
Default Value: 600
Valid Values: An integer from 1 through 3600.
Changes Take Effect: When the session is started or restarted.


Specifies the delay, in seconds, before the cache of the result of a Universal Contact Server request is cleared.

contact.available-directory-page-sizes

Section: interaction-workspace
Default Value: 5,10,25,50
Valid Values: A comma-separated list of numbers that define the number of rows per result page from which the agent can make selections.
Changes Take Effect: When the session is started or restarted.


Specifies the possible values for the number of rows per page in the contact directory search result view.

Enabling Agents To Manage Contacts

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 Extension (GAX).
  • 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.

Procedure: Enabling agents to manage contacts

Purpose: To enable an agent to view and manage contact information.

Prerequisites

  • A working knowledge of Genesys Administrator Extension (GAX).
  • The WS_Cluster application object exists in the Configuration Database.
  • The WS_Cluster application has a connection to Universal Contact Server.
  • The WS_Cluster application has a connection to Interaction Server.
  • The agent object is configured to use one or more of the following media channels:

Start

  1. In the feature-definition.json file, enable the api-multimedia feature.
  2. Configure the Contact options in the interaction-workspace section of the WS_Cluster application object.

End

Procedure: Enabling the Contact Directory, Contact History, and My History

Purpose: To enable an agent to use the Contact Directory, Contact History, and My History views.

This functionality enables agents to search the contact data base, create new contacts, and delete existing contacts.

The Contact Directory supports two views, a grid and a list.

Prerequisites

  • 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.

Start

  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.
      • annex—Used in the Agent interface. Include a settings section with these options:
        • is-sortable = true
        • is-searchable = true
  2. Configure the following Interaction options in the interaction-workspace section of the WS_Cluster object:
    • Interaction option...
  3. For the Contact Directory view, configure the Contact options in the interaction-workspace section:
  4. For the Contact History view, configure the Contact options in the interaction-workspace section:
  5. For the My History view, configure the Contact options in the interaction-workspace section:
  6. Enable My History Search. You can enable basic and advanced searching in the My History tab in the Connect group for agents in your contact center and specify which advanced search options are displayed in Workspace Agent Desktop. With advanced searching enabled, agents can search their own interaction history by date range, interaction type, and specific default and custom attributes. The search returns a maximum of 100 results.
    1. Activate the basic search privilege. See privilege.contact.can-search-my-history.
    2. Enable advanced searching. See privilege.contact.can-advanced-search-my-history.
    3. Enable the filtering of interactions in the Contact History view. See privilege.contact.can-filter-my-history.
    4. Define the list of attributes displayed on the Advanced Search window. See contact.history-search-attributes.
    5. Define the list of date search options on the Advanced Search window. See contact.date-search-types.
    6. Specify which interaction types (channels) are included in the My History view list of interactions. See contact.history.media-filters.

End

Procedure: Enabling Last Routed Agent

Purpose: To enable the last routed agent feature, which saves information about the last agent who handled interactions from that contact in the Contact Profile. That information can then be used during the routing of subsequent interactions from this contact. When an agent actively handles an interaction of a given media type from a contact, the following keys are set in the Contact Profile:

  • LastCalledAgent_EmployeeID
  • LastCalledAgent_TimeStamp
  • LCA_EmplID_<MediaType>
  • LCA_TimeStamp_<MediaType>

Where <MediaType> corresponds to the media of the interaction.

Refer to the eServices and Routing documentation for more information about this feature.

Start

  1. You can activate this feature by setting the following options in the interaction-workspace section:

End

Comments or questions about this documentation? Contact us for support!