Jump to: navigation, search

WA Configuration Examples for Independent Configuration Mode

In independent configuration mode, there are no dependencies between Workforce Advisor (WA) configuration and Contact Center Advisor (CCAdv) configuration. CCAdv and WA can operate with completely different sets of aggregated objects, applications, agent groups, and relationships amongst those. You can configure WA to be autonomous; that is, it can operate independently—even if CCAdv configuration is not present at all.

Independent mode is more generic than integrated mode. In independent mode, you can configure all of the same scenarios that you can configure in the integrated mode, but you must do more manual configuration work in the independent mode because WA does not use any of the relationships or associations from the CCAdv configuration. WA and CCAdv function based on their respective final configurations. Once configured, the configuration modes have no impact other than what you see in the Advisors administration module.

Related Information


For information about business objects (reporting regions, geographic regions, operating units, contact centers and application groups), see Advisors Business Objects.

For additional information about agent groups and contact groups, see:

For information about configuring contact centers (site or network), see Contact Centers and Configuring Contact Centers.

Correct Configuration: Simple Configuration Using Independent Mode

To correctly configure the deployment shown in the following Figure, see Configuring WA using the Independent Configuration Mode: Basic Configuration

Pma independent-simple-config 851.png

Legend:

  • AG = Application Group
  • Agent Gr = Agent Group
  • CC = Contact Center
  • GR = Geographic Region
  • OU = Operating Unit
  • RR = Reporting Region


Procedure: Configuring WA using the Independent Configuration Mode: Basic Configuration


Steps

  1. Verify that CCAdv/WA configuration is set to the Independent configuration mode.
    Pma verify-configmode-independent 851.png
  2. Activate the geographic region (GR1) if it is still inactive.
    Pma activate-gr-independent 851.png
  3. Make sure that any of the following objects that will participate in the configuration are active:
    • reporting region (RR1)
      Pma activate-rr-independent 851.png
    • operating unit (OU1)
      Pma activate-ou-independent 851.png
    • application group (AG1)
      Pma activate-ag-independent 851.png
  4. Configure a contact center (CC1), if it is not already configured, and associate it with the geographic region (GR1). The contact center (CC1) can be of any type.
    Pma assign-cc-to-gr-independent 851.png
  5. On the Rollups tab, choose a contact group (Contact Group 1) that, in the system, is associated with Application 1. Map Contact Group 1 to a contact center, a reporting region, an operating unit, and an application group. Switch to the Contact Groups – Applications tab and map Contact Group 1 to Application 1.
    Pma assign-cg1-to-app1-independent 851.png
  6. Switch to the Contact Groups – Agent Groups tab and choose a contact group (Contact Group 2) that, in the system, is associated with Agent Gr 1, Agent Gr 2, Agent Gr 3, and Agent Gr 4. Map Contact Group 2 to Agent Gr 1, Agent Gr 2, Agent Gr 3, and Agent Gr 4.
    Pma assign-cg2-to-ags-independent 851.png
  7. If Contact Group 1 is a parent of Contact Group 2 in the system, make sure that both are mapped to the same reporting region, operating unit, application group, and contact center.
    Pma verify-cgs-config-independent 851.png


Correct Configuration: Configuration With Agent Groups Divided Into Agent Group Contact Centers

To correctly configure the deployment shown in the following Figure, see Configuring WA using the Independent Configuration Mode: Agent Groups Divided Into Agent Group Contact Centers.
Pma independent-split-AGs-config 851.png

Legend:

  • AG = Application Group
  • AGCC = Agent Group Contact Center
  • Agent Gr = Agent Group
  • GR = Geographic Region
  • NCC = Network Contact Center
  • OU = Operating Unit
  • RR = Reporting Region


Procedure: Configuring WA using the Independent Configuration Mode: Agent Groups Divided Into Agent Group Contact Centers


Steps

  1. Verify that CCAdv/WA configuration is set to the Independent configuration mode.
    Pma verify-configmode-independent 851.png
  2. Activate the geographic region (GR1) if it is still inactive.
    Pma activate-gr-independent 851.png
  3. Make sure that any of the following objects that will participate in the configuration are active:
    • reporting region (RR1)
      Pma activate-rr-independent 851.png
    • operating unit (OU1)
      Pma activate-ou-independent 851.png
    • application group (AG1)
      Pma activate-ag-independent 851.png
  4. Configure a network contact center (NCC1), if it is not already configured, and associate it with a geographic region (GR1). Create agent group contact centers (AGCC1, AGCC2, and so on) within NCC1.
    Pma assign-ncc-to-gr-independent 851.png
  5. Map agent groups to AGCCs and include them in the WA configuration.
    Pma assign-agent-groups-to-agcc-independent 851.png
  6. Map contact groups that are associated with agent groups already assigned to AGCCs:
    1. Choose a contact group (Contact Group 1) that, in the system, is associated with an application (Application1) and map it to a network contact center (NCC1), reporting region (RR1), operating unit (OU1) and application group (AG1).
    2. Choose a contact group (Contact Group 2) that, in the system, is associated with the set of agent groups from AGCC1. Map Contact Group 2 to AGCC1 and to the same reporting region (RR1), the same operating unit (OU1), and the same application group (AG1) with which Contact Group 1 is associated.
    3. Choose a contact group (Contact Group 3) that, in the system, is associated with the set of agent groups from AGCC2. Map Contact Group 3 to AGCC2 and to the same reporting region (RR1), the same operating unit (OU1), and the same application group (AG1) with which Contact Group 1 is associated.
    4. And so on with any other contact groups.
  7. Pma assign-contact-groups-to-objects-independent 851.png
  8. Map Contact Group 1 to Application 1.
    Pma assign-cg1-to-app1-ag-split-independent 851.png
  9. Map Contact Group 2 to Agent Gr 1 and Agent Gr 2.
    Pma assign-cg2-to-ags-ag-split-independent 851.png
  10. Map Contact Group 3 to Agent Gr 3 and Agent Gr 4.
    Pma assign-cg3-to-ags-ag-split-independent 851.png

Incorrect Configuration: Contact Group Not Mapped To An Application

Failing to map the relevant contact group to an application results in an incomplete and incorrect configuration. If you use this configuration, the real-time WA metric operands will be absent, which results in inaccurate or missing metric values for the contact group and related aggregated objects.

Pma independent-incorrect-config-01 851.png

Incorrect Configuration: Incorrectly Mapped Contact Groups Example 1

In this example, Contact Group 1 is a parent of Contact Group 2.

Pma parent-child-contact-groups 851.png

The configuration shown in the figure below is incorrect because the parent and child contact groups are associated with different combinations of reporting region, operating unit, application group, and contact center. To be correct configuration, each related contact group must be associated with the same combination of reporting region, operating unit, application group, and contact center.

Pma independent-incorrect-config-02 851.png

Incorrect Configuration: Incorrectly Mapped Contact Groups Example 2

The configuration shown in the figure below is incorrect because the contact groups that are mapped to agent groups are associated with a different combination of reporting region, operating unit, and application group than the related contact group that is mapped to applications.

Pma independent-incorrect-config-03 851.png

Feedback

Comment on this article:

blog comments powered by Disqus
This page was last modified on July 5, 2018, at 13:40.