Mary.hachey@genesys.com: Published

2021-10-21T13:27:42Z

Published

Show changes

WikiSysop: Text replacement - "\|Platform=([^\|])GenesysEngage-onpremises([\|])" to "|Platform=$1GenesysEngage-cloud$2"

2020-07-25T02:31:13Z

Text replacement - "\|Platform=([^\|]*)GenesysEngage-onpremises([\|]*)" to "|Platform=$1GenesysEngage-cloud$2"

WikiSysop: Text replacement - "\|Platforms?=([^\|])PureEngage([\|])" to "|Platform=$1GenesysEngage-onpremises$2"

2020-07-15T11:46:11Z

Text replacement - "\|Platforms?=([^\|]*)PureEngage([\|]*)" to "|Platform=$1GenesysEngage-onpremises$2"

Bgrenon: Published

2020-06-08T15:21:11Z

Published

New page

{{Article
|Standalone=No
|DisplayName=Configuration objects
|TocName=Configuration objects
|Context=Learn about how WFM's Configuration objects can be used to effectively plan, organize, and manage your contact center requirements.
|ComingSoon=No
|Platform=PureEngage
|Prereq=
|Section={{Section
|sectionHeading=
|anchor=
|alignment=Vertical
|Media=
|image=
|structuredtext=The '''Configuration''' module in the WFM Web for Supervisors application enables you to configure a number of object types that provide structure and set parameters that will simplify various tasks. The following sections briefly describe each object type and highlight some things to consider when planning your workforce configuration.

{{NoteFormat|The following sections provide only brief introductions to these objects and focus on aspects relevant to deployment planning. For a full description, see ''{{Link-AnywhereElse|product=PEC-WFM|version=Current|manual=Supervisor|topic=CfgtnMdl|display text=Workforce Management Web for Supervisors (Classic) Help}}''.|2}}
|structuredtextwide=
|FAQHeading=
|Status=No
}}{{Section
|sectionHeading=Agents
|anchor=Agnts
|alignment=Vertical
|Media=
|image=
|structuredtext=Using Agent objects, you can plan for, manage, and make changes to the contact information, agent IDs, and profiles for all agents in the various sites within the enterprise. WFM Web provides many configuration views and categories in which to manage agents effectively. For detailed information about agent configuration, see the '''Configuration > Agents''' view in the ''{{Link-AnywhereElse|product=PEC-WFM|version=Current|manual=Supervisor|topic=CfgAgts|display text=Workforce Management Web for Supervisors (Classic) Help}}''.
|structuredtextwide=
|FAQHeading=
|Status=No
}}{{Section
|sectionHeading=Organization
|anchor=Org
|alignment=Vertical
|Media=
|image=
|structuredtext=Use the '''Organization''' module to configure sites, business units, and time zones, and determine which sites belong to each business unit. Decide on the site properties, the maximum seats, how you will collect statistics, and so on. Collect information about agent team and site associations, as well as agent settings, such as rotating pattern (if any), contracts, and rules for the accrual of time off.

Keep in mind that there are many WFM configuration objects that are associated with a site, including rotating patterns, contracts, activities, time-off types and rules, exception types, and more. When you move an agent from one site to another, you must reassign that agent to a new contract, time-off rules, and rotating patterns, if these were previously assigned. Take this action to correctly schedule agents whenever they are moved to a new site.

{{AnchorDiv|OrgBU}}
===Business Units===
At times, you might need to create and configure new business units. To do so, see '''Configuration > Organization > Business Units > Creating Business Units''' in the ''{{Link-AnywhereElse|product=PEC-WFM|version=Current|manual=Supervisor|topic=CrtBUs|display text=Workforce Management Web for Supervisors (Classic) Help}}''.

{{AnchorDiv|Sts}}
===Sites===
Sites can be equivalent to switches, which are defined in Genesys Administrator and imported into WFM. You can also create sites in WFM that are unrelated to a switch. This is appropriate when switches do not correlate with your company's organization. For example, a single location could be divided into multiple entities to reflect divisions along business unit lines. To configure sites in your enterprise, see the WFM Web for Supervisors '''Configuration > Organization''' module.

====Teams====
Within new or existing sites, you can create and add agents to teams. Creating teams enables you to group agents to meet scheduling and business requirements. You can organize teams by agent skill sets, schedule, sales targets, achievements, geographies, or any other factor. For example, to email agents, start a sales drive, or initiate platinum customer care. An agent can belong to only one team at a time. To create teams, use the '''Sites > Properties''' view in Web for Supervisors.

{{AnchorDiv|TmeZns}}
===Time Zones===
''Time zones'' are set up in Genesys Administrator and imported into WFM during synchronization. You can assign time zones to business units only. For efficiency in configuring new objects, you can configure a default time zone, or a user time zone that can be used as the alternative time zone in the '''Performance''' views. Newly created sites and business units use the default time zone unless specified otherwise.

To learn how to configure and work with time zones, see '''Configuration > Time Zones''' in the ''{{Link-AnywhereElse|product=PEC-WFM|version=Current|manual=Supervisor|topic=OrgTmZns|display text=Workforce Management Web for Supervisors (Classic) Help}}''.
|structuredtextwide=
|FAQHeading=
|Status=No
}}{{Section
|sectionHeading=Schedule-State Groups
|anchor=SSG
|alignment=Vertical
|Media=
|image=
|structuredtext=A ''schedule-state group'' is a collection of schedule states that is linked to a site. These include breaks, meals, exceptions, activities, time off, and so on. You can group these, and then associate the group with one or more Genesys states.

Additionally, you can configure an adherence threshold for the schedule state group, which defines when an agent should be considered non-adherent to the schedule states contained in the group.

To configure schedule-state groups, determine what schedule states you are using, what are the most logical groupings, and which Genesys state(s) best corresponds to each group.

To learn how to configure schedule state groups and adherence rules for them, see '''Configuration > Schedule State Groups''' in the ''{{Link-AnywhereElse|product=PEC-WFM|version=Current|manual=Supervisor|topic=SchStGrps|display text=Workforce Management Web for Supervisors (Classic) Help}}''.
|structuredtextwide=
|FAQHeading=
|Status=No
}}{{Section
|sectionHeading=Activities
|anchor=Actv
|alignment=Vertical
|Media=
|image=
|structuredtext=''Activities'' are defined as different categories of work that comprise the total workload for a contact center. Workload and staffing forecasts are created for each activity. Each site configures its own activities, to take the local conditions into account. All agent work that is forecast and schedule must be assigned to an activity.

Activities can take various forms. They might describe types of work, such as inbound calls or email; groups of customers served, such as preferred customer care; or work times, such as overnight. You can also use activities for non-CTI work. Each activity is then associated with one or more preconfigured skills. Because activities are a fundamental unit for forecasts and schedules, it is critical that you configure them accurately.

====Maximum simultaneous users for activities====
The Maximum Simultaneous Users feature limits the number of agents that can be scheduled for an activity, even if the workload requires more. This feature can be used as a way to prevent excessive staffing for some activities so that the agents can be moved to more important activities, even if it leaves some less-important activities understaffed. This feature is best used when the contact center is understaffed as a whole. When the '''Maximum Simultaneous Users''' value is reached, agents are then assigned to other activities.

{{NoteFormat|The Maximum Simultaneous Users feature is used only in multi-skilled environments.|2}}

{{AnchorDiv|ActSets}}
===Activity Sets===
The '''Activities''' module enables you to set activity open hours and staffing constraints. You can also use it to create activity sets.

Activity sets provide a means to combine activities into groups for multi-skilled scheduling. Activity sets are associated with sites. Any agent can work on an activity set if that agent has the skills required for the activities included in the activity set. When performing activity set work, agents must perform only the activities included in the set for a specified period of time. When planning your deployment, consider which activities could logically be grouped into activity sets.

{{AnchorDiv|MSActv}}
===Multi-site Activities===
Multi-site activities are performed at multiple physical sites. They enable you to view several local activities as a single WFM object. The performance information is split among the sites that perform the activity. You can build interaction volume forecasts, staffing forecasts, and view contact center performance for multi-site activities.

For more information about activities, activity sets, and multi-site activities, see '''Configuration > Activities''' in the ''{{Link-AnywhereElse|product=PEC-WFM|version=Current|manual=Supervisor|topic=CfgActvs|display text=Workforce Management Web for Supervisors (Classic) Help}}''.

{{AnchorDiv|ActStats}}
===Activities Statistics===
Administrators and supervisors can associate statistics with activities and multi-site activities in WFM Web. WFM tracks four statistical categories: Interaction Volume (IV), Abandonment Percentage, Quality of Service, and Handle Time. These statistics are written to the WFM database, providing the historical data necessary for WFM forecasting, scheduling, and performance and adherence monitoring.

In WFM Web you associate statistics with activities. These statistics may be ''out-of-the-box'' or customized statistics.

For example, you can sum up values from any set of statistics you want, such as <tt>totalTalkTime</tt> + <tt>totalHoldTime</tt> + <tt>totalAfterCallWorkTime</tt>. This type of flexible configuration overcomes the limitations of some reports and integration, enabling you to choose the statistics that best represent the work associated with servicing each customer interaction.

For more information about statistics, see '''Configuration > Statistics''' in the ''{{Link-AnywhereElse|product=PEC-WFM|version=Current|manual=Supervisor|topic=CfgActvs|display text=Workforce Management Web for Supervisors (Classic) Help}}'' and {{Link-SomewhereInThisVersion|manual=Administrator|topic=RecStats}} in this guide.
|structuredtextwide=
|FAQHeading=
|Status=No
}}{{Section
|sectionHeading=Skills
|anchor=Skl
|alignment=Vertical
|Media=
|image=
|structuredtext=You can configure interactions to be routed to specific agents within a contact center, based on skill definitions.

For example, you may want to have incoming interactions go first to an agent at the highest level of a certain skill. If no agent with that skill level for that activity is available, then the interaction can be routed to an agent with the next highest level of that skill. If no agent is available at that level, then the interaction can be routed to the next available agent, regardless of the agent’s skill level for the activity.

The contact center manager can decide whether to staff for the higher skill levels, or whether to staff so that any agent can handle the interaction.

Skills are defined and assigned to agents in Genesys Administrator, then imported into WFM automatically during synchronization. In WFM, skills are assigned to business units. A skill can be assigned to one business unit only and can be assigned only to activities and profiles under this business unit. To assign skills to business units, see '''Configuration > Configuring Skills for Activities''' in the ''{{Link-AnywhereElse|product=PEC-WFM|version=Current|manual=Supervisor|topic=SklsForAct|display text=Workforce Management Web for Supervisors (Classic) Help}}''.

===Matching Skills and Activities===
Activities often correspond to skills but may also correspond to agent skill levels. Choosing an appropriate strategy for a contact center’s activities allows for improved staffing decisions.

For example, in a simple scenario, the relationship between the queue, skills, and activities is a 1-1-1 correspondence. As things get more complex, the relationships get more complex. Activities consist of multiple skills, and each site has many activities associated with it. The goal is to find the best combination of relationships to meet staffing requirements.
|structuredtextwide=
|FAQHeading=
|Status=No
}}{{Section
|sectionHeading=Users
|anchor=Users
|alignment=Vertical
|Media=
|image=
|structuredtext=''Users'' are supervisors and other persons who are not agents. They are divided into two groups:

*Users who have been imported into WFM (WFM users).
*Users who are configured in Genesys but not selected as WFM users (Genesys Users).

In WFM Web you can create a list of existing WFM users or import Genesys users from Genesys Administrator. You can configure user properties, and assign security roles and privileges to them, enabling access to specific business units, sites, and teams within the enterprise.

Before you import Genesys users into WFM, ensure you understand the how the user's security rights and privileges are impacted by the move. Be sure to read the topics {{Link-SomewhereInThisManual|topic=AboutCfg|anchor=SecRls|display text=Roles}} and {{Link-SomewhereInThisManual|topic=UserSec|anchor=GenCfgMgrObj|display text=Genesys Administrator Objects Imported to WFM}}.

Users are configured in the '''Configuration > Users''' view. See the ''{{Link-AnywhereElse|product=PEC-WFM|version=Current|manual=Supervisor|topic=CfgUsrs|display text=Workforce Management Web for Supervisors (Classic) Help}}''.
|structuredtextwide=
|FAQHeading=
|Status=No
}}{{Section
|sectionHeading=Roles
|anchor=SecRls
|alignment=Vertical
|Media=
|image=
|structuredtext=WFM uses roles and privileges to manage user access to WFM functionality. WFM has its own security/access rights system that defines the objects and modules that each WFM supervisor user can access in WFM. In addition, WFM implements tenant security for the objects that are shared with Genesys Administrator.

WFM implements security/access as follows:

*If the user belongs to '''Enterprise''' in Genesys Administrator, all objects are accessible to the user in WFM, if the appropriate WFM access rights are assigned.
*If the user belongs to a '''tenant''', the WFM user has access to object under that tenant only, even if the WFM access rights are assigned for related objects.

{{NoteFormat|WFM follows tenant access rights only (and no other Genesys Administrator access rights).}}

User security roles are configured in the '''Configuration > Roles''' view, enabling you to configure security settings for all supervisors (that is, all non-agents who use WFM). It groups role privileges into the following categories: General, Configuration, Policies, Calendar, Forecast, Schedule, Trading, Performance, Adherence, Reports, and Notifications. Under each category are various options.

For example, '''Notifications''' is an option under the '''Configuration''' category. If a user is assigned the '''Notifications''' privilege, that user can then access the '''Notifications''' view in WFM Web. Users without this permission cannot access and therefore cannot modify the configuration of email notifications.

{{NoteFormat|There is a distinction between the '''Notifications''' category and the '''Notifications''' privilege under the '''Configuration''' category. For further clarification, see '''Configuration > Roles''' in the ''{{Link-AnywhereElse|product=PEC-WFM|version=Current|manual=Supervisor|topic=CfgRols|display text=Workforce Management Web for Supervisors (Classic) Help}}''.|2}}

User security settings allow for a great deal of flexibility. You can specify which sites and business units, teams, and so on, the user can access. You can configure calendar, forecast, and schedule access; read-only access; or full access.

In addition, you can enable users to make only pending schedule changes—that is, schedule changes that require approval from a qualified user before they are incorporated into the Master Schedule.

To configure user security settings efficiently, determine the access levels appropriate for all users. You can change settings at any time, as necessary. You can also use security roles to more easily configure security settings for users, by creating a security role, assigning privileges to it, and then assigning one or more WFM users to that security role.

When importing users, administrators will configure a security role. All new users added to the WFM system will be assigned to this security role and will be limited to its access permissions. Roles can be changed at any time. See '''Configuration > Roles > Creating Roles''' in the ''{{Link-AnywhereElse|product=PEC-WFM|version=Current|manual=Supervisor|topic=RolsCrtNw|display text=Workforce Management Web for Supervisors (Classic) Help}}''.

Some configuration is required to assign roles and privileges for individual agents or groups of agents in Genesys Administrator. Ask your Genesys Professional Service representative for assistance with this.
|structuredtextwide=
|FAQHeading=
|Status=No
}}
}}

@@ Line 5: / Line 5: @@
 |Context=Learn about how WFM's Configuration objects can be used to effectively plan, organize, and manage your contact center requirements.
 |ComingSoon=No
-|Platform=GenesysEngage-onpremises
+|Platform=GenesysEngage-cloud
 |Prereq=
 |Section={{Section

PEC-WFM/Current/Administrator/AboutCfg - Revision history

Mary.hachey@genesys.com: Published

WikiSysop: Text replacement - "\|Platform=([^\|]*)GenesysEngage-onpremises([\|]*)" to "|Platform=$1GenesysEngage-cloud$2"

WikiSysop: Text replacement - "\|Platforms?=([^\|]*)PureEngage([\|]*)" to "|Platform=$1GenesysEngage-onpremises$2"

Bgrenon: Published

WikiSysop: Text replacement - "\|Platform=([^\|])GenesysEngage-onpremises([\|])" to "|Platform=$1GenesysEngage-cloud$2"

WikiSysop: Text replacement - "\|Platforms?=([^\|])PureEngage([\|])" to "|Platform=$1GenesysEngage-onpremises$2"