Team Management
The "Team" tab in the Configurator allows to configure and manage ("activate / deactivate") teams that were acquired from Active Directory by by CIC component.
Teams are divided in Organization Units. An additional tenant layer is possible to be added to team organization, but requires deactivation of the AD sync in favor of manual user provisioning. More about this in the CIC component configuration chapter.
Preconditions
In order to operate, TM relies on other data entities to be define beforehand. The following graphic illustrates the data dependencies configured in each tab of the Configurator:
- A configured Topology with running TM System Components
- Services (will be created automatically when you create a new team)
- Workflows Structures which are used to generate Instances with Placeholders and Service Parameters that can be uniquely modified per team
- Agents
Good to know:
- Service Endpoints get created once a team is "enabled" (= set to "Active" in the Frontend).
- Disabled Teams are automatically created when synchronized with Active Directory via the CIC component. Read more below.
Creating a Team
Teams can be created and configured via the Frontend if the user has the corresponding System Level admin rights. Tenant and Team Administrators can operate within their given activated teams only. By default a newly created team is " inactive " to allow for backend configuration until the team is ready for operation. This mode of operation can be changed at any time, e.g. to put a service offline temporarily without the need to reconfigure Opening Hours .
For Team Creation Refer to the following chapter for Frontend UI handling:
Basic Team Configuration
To explain the following sections we use Configurator Backend to explain and show all properties and types of teams. The Frontend UI may only show a reduced set. Team properties can be altered within both Frontend and Backend, however the Configurator uses the term "Enabled / Disabled" teams synonymous with "Activated / Deactivated" in the Frontend. A property change of any team is immediately reflected on both sides.
The Configurator " Team " tab consists of two sub-tabs:
- Disabled Teams sub-tab - which sync with your confured AD directory. Disabling teams in the Activated Teams Page will also make the appear in this tab.
- Enabled Teams sub-tab - which are also visible in the Activated Teams Page in the Frontend
Types of Teams
TM distinguishes by three types of Teams which are differing in operation mode:
Team Type Name | Description | When to choose this type |
---|---|---|
TeamServiceOnly | Corresponds to the classical call distribution configuration for TM. A call service and trusted application endpoint are created for the team, which can be called via SfB. This endpoint distributes calls within team members. | Choose when team should only be represented as one public-facing SfB contact which can be called directly. |
TeamCallGroupOnly | Team configuration for which no SfB endpoint is created. Instead, TM manages the SfB team call group for each team member. | Choose when direct calls to team members should be possible and distributed among the whole team member list. Other team members will be notified and can accept calls instead of the original target. |
TeamService&CallGroup | Combines both aforementioned versions. A call service and trusted application endpoint are created for the team. TM manages the SfB team call group for each team member. | Choose when you want individual team members as well as public-facing SfB contact which can be called directly. Other team members will be notified and can accept calls instead of the original target. |
Disabled / Inactive Teams
Good to know
The "Disabled teams" sub-tab contains a list of all teams that were found in Active Directory by the path defined in CIC component's 'TeamAdOuFilter' key.
When the "Disabled Teams" tab is empty the CIC property " EnableAdTeamSyncActivatedTeamsOnly " is set to " true", so only activated Teams get AD-synched.
Please note that "Disabled" and "Inactive" Teams used in the Frontend Activated Teams Page in this context is synonymous
By default two sections common for all team types are shown on the tab TM Configurator -> Team -> Disabled Teams.
Upon selecting a team, detailed information appears. The set of sections differs depending on team type.
Inactive "TeamServiceOnly" Configuration
The team creation can be handled in the Frontend via the Add Teams Page. To configure a service team:
Set "TeamServiceOnly" type in "Team Type" combobox for the selected team.
To activate a service team fill in all mandatory fields and press "activate " button.
→ After the team was activated, it appears on "Enabled Teams " sub-tab.
→ A service, an organization unit, traits and team members are created by the system and inherit the team's name.
After the creation, configure the team using the following call service settings table:
Field Name | Description |
---|---|
Name | Shows a unique name of a team in Active Directory Domain Services. |
SID | Shows a security identifier (SID) that allows to identify an Active Directory team. |
Team member BusyOnBusy in a call enabled |
|
Team member is busy selectable | Set to "true" to let a team member with "Busy" SfB state receive calls. |
Team member is busy in a meeting selectable |
The flag is enabled if "Team member is busy selectable" is set to "true" otherwise it is disabled and its value could not be changed. |
Team Name | Define a сustom name for a team in TM. A service created on the basis of this command inherits this name. |
Branch ID | Define"Branch ID" value to group teams by their affiliation to a branch. It serves as an additional identifier for searching and more usable team administration. |
Trusted Application | Select with which trusted application the service will work. |
SIP URI | A unique identifier that allows to reach a service using SIP devices such as Skype for Business. The SIP address must use the sip: prefix as well as a valid SIP domain; |
Telephone URI | Enter a global telephone number that will be assigned to the service. |
Tel SIP URI | Enter a local telephone sip uri that will be assigned to the service. |
Workflow Instance | Select the workflow instance which the service will use. |
Culture | Select culture to define in which language the announcements will be made. |
Service FWD SipUri1 | Define a forward target that will be used by a service during a workflow instance execution.
|
Service FWD SipUri2 | Define an additional forward target that will be used by a service during a workflow instance execution. The following formats are supported:
To configure the workflow instance go to TM Configurator -> Workflow ->" "Workflow Instance" and use "Forward" or "Blind Transfer" workflow elements. |
Service FWD SipUri3 | Define an additional forward target that will be used by a service during a workflow instance execution. The following formats are supported:
|
Direct Selectable | Select the SfB state the service will have if at least one team member is selectable.
|
No One Available | Select SfB state the service will have if all agents are offline. |
In Time Selectable | Select SfB state the service will have if all agents are busy or away. |
Team Choice Enabled | Set to "true" to allow team members of the team change their responsibility for the team service upon clicking on "Active/Inactive" button on TM FE "Team Choice" page. |
Create Team Member as Default | Set to "Active" to activate a team with already active new team members . |
Set/Remove VoicePolicy (User Level) | Shows a list with user voice policies that are available on the SfB Server. |
Set/Remove ExternalAccessPolicy (User Level) | Shows a list with external access policies that are available on the SfB Server. |
Set/Remove OpeningHour Box | Select a mailbox from which the calendar events will be used. |
Set/Remove Service Voicemail: | Select a preconfigured recording definition and mailbox which will send recorded messages. Works along with a specific workflow instance. |
Use Recording Definition From Incoming Service: | Defines if for a call transferred to another service a recorded voicemail will be sent on behalf of initial or the last service name. |
Voicemail To | Enter the "To" address for voicemail. The recorded data will be sent to this email account. |
Voicemail Cc | Enter the "Cc" address for voicemail. The recorded data will be sent as a carbon copy to this email account. |
Use Display Name in subject for Non Pstn Call | Set to "true" to make the agent see the name of the customer during the conversation. |
Publish as Automation | Set to "false" to make the service selectable as a Forward target in the SfB client. |
Simultaneous ring on DECT Endpoint (pager) | Set to "true" to allow agents get an audio call on secondary phone (pager) simultaneously with the main one when agents is not at the desk. |
Tenant ID | A globally unique identifier (GUID) that is different than your tenant name or domain. E.g. 00000000-0000-0000-0000-000000000000 Required when the team is registed with an O365 / Azure tenant. |
Inactive "TeamCallGroupOnly" Configuration
The team creation can be handled in the Frontend via the Add new team dialogue. To configure a service team
Set "TeamCallGroupOnly" type in "Team Type" combobox for the selected team.
To activate a service team fill in all mandatory fields and press "activate " button.
→ After the team was activated, it appears on "Enabled Teams " sub-tab.
→ A service, an organization unit, traits and team members are created by the system and inherit the team's name.
After the creation, configure the team using the following settings:
Field Name | Description |
---|---|
Name | Shows a unique name of a team in Active Directory Domain Services. |
SID | Shows a security identifier (SID) that allows to identify an Active Directory team. |
Team member BusyOnBusy in a call enabled | Set to "true" to make incoming callers hear a busy signal if team members are already on another call. The phone will not ring on a receiver's end and the receiver will not be alerted . |
Team Name | Define a unique name for a team in TM. A service created on the basis of this command inherits this name. |
Branch ID | Define "Branch ID" value to group teams by their affiliation to a branch. |
CallGroup Default Delay | Set the delay in seconds after which a call starts ringing all other team members. |
Fwd Default Delay | Set the delay in seconds after which a call will be forwarded to another number or to another contact. |
Fwd SipUri | Define a number or a contact to which an unanswered call will be forwarded. |
Enabled / Active Teams
Good to know
The "Disabled teams" sub- tab contains a list of all the teams existing in Active Directory and already activated in TM.
- Please note that "Enabled" and "Inactive" as term used on the Frontend Activated Teams Page in this context is synonymous
- Compared to a "disabled" Team more properties are shown on an enabled team. The set of sections differs depending on Team Type
Also refer to the "Types of Teams" chapter above and the following chapter for details.
Enabled / Active: "TeamService&CallGroup" Configuration
TeamService&CallGroup team type combines the configurations for both types: TeamCallGroupOnly and TeamServiceOnly team types, so their properties match accordingly.
The team creation can be handled in the Frontend via the Add new team dialogue. To configure a service team
Set "TeamService&CallGroup" type in "Team Type" combobox for the selected team.
To activate a service team fill in all mandatory fields and press "activate " button.
→ After the team was activated, it appears on "Enabled Teams " sub-tab.
→ A service, an organization unit, traits and team members are created by the system and inherit the team's name.
Enabled / Active: "TeamServiceOnly" and "TeamService&CallGroup" Configuration
Comparing to "Disabled Teams" two new sections for " TeamServiceOnly" and "TeamService&CallGroup" type teams:
- Placeholders
- Team Members
Placeholders
The "Placeholders" section shows default and custom values of placeholders that are used in the Workflow Instance assigned to the team.
Placeholders are configured in TM Configurator -> Workflow -> Placeholders
Field Name | Description |
---|---|
Name | Shows a name of a placeholder used in Workflow Instance. |
Value | Define a custom value for the selected placeholder. The value is changed only within the team and doesn't affect other teams with the same Workflow Instance. |
Default Value | Shows default value for the selected placeholder. |
Use Default | Set to "true" to use default values in Workflow Instance. |
Team Members
The 'Team members " section shows the users that exist in Active Directory and belong to the team. All changes that are made in Active Directory will be reflected in the section.
Detailed information about team members is available in TM Configurator -> Users -> Users sub-tab.
Users can be added can be performed in the Frontend via Users Page - User Provisioning
Field Name | Description |
---|---|
First Name | Shows a user's first name acquired from Active Directory and used in TM system. |
Last Name | Shows a user's last name acquired from Active Directory and used in TM system. |
Is Team Administrator | Team Administrator is a user that has Team Administrator permissions and as a result is able to perform the following actions:
|
Private Line URI |
|
Enabled / Active: "TeamCallGroupOnly" Configuration
Comparing to "Disabled Teams" one new section for " TeamCallGroupOnly" type teams:
- Team Members
The configuration of Team Members is identical to the chapter described above