Jump to: navigation, search

teamcommunicator.routing-point-presence-metrics

Section: interaction-workspace
Default Value: routing-point-presence
Valid Values: A string that contains a comma separated list of routing point presence options section names.
Changes Take Effect: When the application is started or restarted.
Introduced: 8.5.102.06

Specifies a list of routing point presence sections. Each of these sections contain a valid statistic name related to the routing point, the text to be displayed in Team Communicator, a warning level value, an error level value, and a list of object ids that apply to this presence statistic.

teamcommunicator.request-start-timer

Section: interaction-workspace
Default Value: 300
Valid Values: An integer value from 1 through 5000.
Changes Take Effect: When the application is started or restarted.


Request start timer wait interval, in milliseconds, between the last key pressed and the beginning of the search through the contact database.

teamcommunicator.recent-max-records

Section: interaction-workspace
Default Value: 10
Valid Values: An integer value from 1 through 50.
Changes Take Effect: When the application is started or restarted.


Specifies the maximum number of internal entries (for example, agent and groups) and the maximum number of external entries (customer contacts) to be displayed in the Team Communicator suggestion list while an agent is entering a contact or target name. For example, if 10 is specified, up to 10 internal targets and up to 10 contacts may be displayed.

teamcommunicator.queue-presence-metrics

Section: interaction-workspace
Default Value: queue-presence
Valid Values: A string that contains a comma separated list of queue presence options section names.
Changes Take Effect: When the application is started or restarted.


Specifies a list of queue presence sections. Each of these sections contain a valid statistic name related to the queue, the text displayed in Team Communicator, a warning level value, an error level value, and a list of object ids that apply to this presence statistic.

teamcommunicator.max-suggestion-size

Section: interaction-workspace
Default Value: 10
Valid Values: An integer value from 1 through 50.
Changes Take Effect: When the application is started or restarted.


Specifies the maximum number of internal entries (agent, agent groups and so on) and maximum number of external entries (customer contacts) to be displayed in the Team Communicator suggestion list while an agent is entering a contact or target name.
For example, if 10 is specified, up to 10 internal targets and up to 10 contacts may be displayed.

teamcommunicator.max-favorites-size

Section: interaction-workspace
Default Value: 50
Valid Values: Any positive integer value.
Changes Take Effect: When the application is started or restarted.


Specifies the maximum number of entries in the list of favorites that is displayed while an agent is entering a contact or target name in the favorites view.

Note: High values (100+) will impact the performance of the workstation and application.

teamcommunicator.load-at-startup

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


Provides performance protection if you have a large number of agents that all login at the same time. Specifies whether all the configuration elements (Agents, Agent Groups, Queues, Routing Points, Skills) that are required by the Team Communicator are loaded at login. If this option is set to false, the elements are not loaded at login; instead, they are loaded when the Team Communicator is used for the first time in the session.

teamcommunicator.list-status-reachable

Section: interaction-workspace
Default Value: NotReady
Valid Values: A comma-separated list of agent status from the following list: NotReady, LoggedOff, Busy
Changes Take Effect: When the application is started or restarted.


Specifies the list of statuses, excepting Ready, for which a target agent can be contacted for consultation, transfer, and conference, requests. If the status of the target agent is neither Ready nor in the list of allowed statuses, the target agent will not be listed as available for consultation, transfer, and conference requests.

Note: The value LoggedOff typically applies to off-line media types such as Email.

teamcommunicator.list-filter-showing

Section: interaction-workspace
Default Value: Agent,AgentGroup,Skill,RoutingPoint,Queue,InteractionQueue,Contact,CustomContact
Valid Values: A comma-separated list of values from the following list: Agent, AgentGroup, Skill, RoutingPoint, Queue, Contact, InteractionQueue, CustomContact
Changes Take Effect: When the application is started or restarted.


Specifies the list of filters that an agent can use to search for contacts and internal targets by using the team communicator. The object types are presented in the specified order.

teamcommunicator.internal-favorite-fields

Section: interaction-workspace
Default Value: Category,DisplayName
Valid Values: A comma-separated value list of values from the following list: Category, DisplayName.
Changes Take Effect: When the application is started or restarted.


The list of fields that are displayed to an agent when adding or editing a favorite that is created from a named resource.

teamcommunicator.interaction-queue-presence-metrics

Section: interaction-workspace
Default Value: interaction-queue-presence
Valid Values: A string that contains a comma separated list of interaction queue presence options section names.
Changes Take Effect: When the application is started or restarted.
Introduced: 8.5.102.06

Specifies a list of interaction queue presence sections. Each of these sections contain a valid statistic name related to the interaction queue, the text to be displayed in Team Communicator, a warning level value, an error level value, and a list of object ids that apply to this presence statistic.

teamcommunicator.custom-favorite-fields

Section: interaction-workspace
Default Value: Category,FirstName,LastName,PhoneNumber,EmailAddress
Valid Values: A comma-separated list of values from the following list: Category, FirstName, LastName, PhoneNumber, EmailAddress.
Changes Take Effect: When the application is started or restarted.


The list of fields that are displayed to an agent when adding or editing a favorite that is created from a typed phone number or email address.

teamcommunicator.corporate-favorites-file

Section: interaction-workspace
Default Value:
Valid Values: File path or HTTP/HTTPS URL.
Changes Take Effect: When the application is started or restarted.
Modified: 8.5.152.02
Related Options: teamcommunicator.corporate-favorites

Specifies the name and the path to your corporate favorites definition file. The path can be relative to the Workspace working directory (for example: Favorites\CorporateFavorites.txt) or an absolute path (for example: C:\PathToFavorites\CorporateFavorites.txt) or a location of the file using an HTTP/HTTPS URL (Proxy and Authentication are not supported). The file must be in XML format. For information about how to use this option with the teamcommunicator.corporate-favorites option and transaction overrides see Creating Corporate Favorites.

teamcommunicator.corporate-favorites

Section: interaction-workspace
Default Value:
Valid Values: A comma-separated list of favorite names (section names) defined in the Workspace application.
Changes Take Effect: When the application is started or restarted.
Modified: 8.5.141.04 (behavior description clarified)
Related Options: teamcommunicator.corporate-favorites-file

The list of corporate favorites (quick dial favorites) that are configured in Configuration Server for an Agent, Agent Group, Skill, Routing Point, Queue, Interaction Queue, or Custom Contact in the same tenant as the agent. See the Procedure: Creating Corporate Favorites for information about creating Corporate Favorite objects in the configuration layer. For operations such as transfer and conference from the Interaction Window Team Communicator, this option can be overridden by a routing strategy, as described in Overriding Options by Using a Routing Strategy, but not for the Main Window Team Communicator.

teamcommunicator.contact-favorite-fields

Section: interaction-workspace
Default Value: Category,FirstName,LastName,PhoneNumber,EmailAddress
Valid Values: A comma-separated list of values from the following list: Category, FirstName, LastName, PhoneNumber, EmailAddress.
Changes Take Effect: When the application is started or restarted.


The list of fields that are displayed to an agent when adding or editing a favorite that is created from a Contact.

teamcommunicator.always-clear-textbox-on-new-interaction

Section: interaction-workspace
Default Value: true
Valid Values: true, false
Changes Take Effect: Immediately.


When this option is set to true, Workspace clears the teamcommunicator search textbox when the interaction is initiated by pressing "Enter" or by clicking on one of the medias of teamcommunicator results. When it is set to false, this option clears the teamcommunicator search textbox only when the interaction is initiated by pressing "Enter"

teamcommunicator.add-recent-filters.voice

Section: interaction-workspace
Default Value:
Valid Values: A comma-separated list of interaction types taken from the following values: internal, external, consultation.
Changes Take Effect: At next interaction event.


Specifies whether to store incoming interactions into the "Recent" buffer. By default, the Recent buffer stores only the actions of the agent, such as recent outbound voice calls. If one or more of the valid values is specified, then recent inbound interactions of that type are also stored in the Recent buffer. This enables agents to see a record of missed calls of the specified type(s).

Team Communicator options

Tip
For the most up to date Workspace Desktop Edition configuration options, see the Genesys Configuration Option Database.

Related Resources

The following topics discuss the implementation of these options:

This page was last edited on July 23, 2020, at 12:41.
Comments or questions about this documentation? Contact us for support!