Voice routing application

• Overview

Inbound routing

The Business Edition Premise voice routing application provides essential inbound call center functions using built-in strategies:

• Entry handling based on contact center status
• Auto-attendant (Interactive Voice Response) menus
• Call distribution based on agent availability and call priority

Entry handling

The application receives the incoming call, retrieves the dialed number (DNIS), and applies status conditions to the call. Is the contact center closed, and if so, why?

• Is it a holiday? If so, the caller hears the Special Day announcement.
• Did the call come in outside of normal operating hours? If so, the caller hears the Closed announcement.
• Is an emergency underway? If so, the caller hears the Emergency announcement.

If the contact center is open, the caller hears an announcement or the auto-attendant menu (if one exists), or the call passes directly to an agent.

Auto-attendant menus

If you have given the caller a menu of options (“Press 1 for Sales,” and so on), the call passes to the Auto-attendant menu (DTMF) workflow, which specifies the action to be taken depending on the caller’s menu choice. The Auto-attendant flow can cycle up to three times, to accommodate three layers of routing. The Auto-Attendant Menus (DTMF) workflow, diagrammed below, acts as an Interactive Voice Response tree to the customer. It plays a menu announcement configured in the Inbound Template, and assigns a Distribution Parameter Group or an Inbound Parameter Group based on the digit (touch tones) collected. For example: The announcement gives the customer three choices (Press 1 for Customer Service, 2 for Sales, and 3 for Technical Support):

• Touch tone 1 = Customer Service (Distribution Template)
• Touch tone 2 = Sales (Distribution Template)
• Touch tone 3 = Tech Support at Route Point 6001 (the Inbound Template that matches the DNIS for the Technical Support Route Point)

The auto-attendant flow can accommodate up to three cycles during a call. In the example above, Touch tone 2 (Sales) might give the caller a second set of options: for Product A, press 1; for product B, press 2, and so on. To learn how to build your menus, see the Configuration tab.

Call distribution

The Distribution call flow distributes the call to an agent:

1. It collects statistics to determine what agents are logged in and available to take the call.
2. It routes the call to an agent from a target agent group: it first tries an agent from Target 1, then, in sequence, tries Targets 2, 3, and 4 if it does not find an agent within the timeout set for that target. Finally, if it does not find an agent from Targets 1-4 within the allotted time, it sends the call to the overflow target, which can be a standard telephone number (such as 415-555-1212) or a routing point (such as 6001). Note that Targets 2-4 are optional; routing skips any undefined targets.

The application plays queue music in a loop until the call is distributed to an agent or abandoned.

Redirect On No Answer (RONA): if the call has already been distributed to an agent who does not answer, the Distribution flow distributes the call as if it had not been previously distributed, and sets to Not Ready the status of the agent who did not answer.

Important

The voice routing application is deployed automatically during BEP installation. You can, however, use these procedures to make a test call using the existing deployment.

[+] Add Trusted Sites to Internet Explorer

To use Internet Explorer 10 to access Genesys Administrator Extension or Genesys Administrator, you must add the following to the IE Trusted Sites:

• http://your UI VM domain
• about:blank

[+] Make a test call to the routing point

1. In GA, set the SIPS TServer enable-unknown-gateway option to true. The deployment is successful if the call connects and you hear an announcement (during closed hours) or queue music (during open hours).

Important

After completing the verification process, restore the value of the enable-unknown-gateway option to false. This secures the SIP Server so that it only accepts calls from configured Trunk DNs within the configuration environment.

Business Edition Premise routing configuration occurs at two levels:

• Initial configuration, which involves the setup of auto-attendant menus, business rules, and other configuration objects, requires a basic understanding of Genesys software, particularly Genesys Administrator, SIP Server, and, for email, eServices Knowledge Manager.
• Administrative configuration, such as setting open hours and switching among auto-attendant menu trees, is a subset of the initial configuration tasks and takes place entirely within Genesys Administrator Extension (GAX). It requires no advanced knowledge of Genesys software.

You can configure different values for a number of routing parameters, such as open hours and call priority. To handle different call flow and email scenarios, you use GAX to create parameter groups based on the default parameter group templates supplied in Business Edition Premise.

Voice solution definitions (SPDs)

Installation of the solution definitions (SPDs) automatically creates several objects. Configuration Server objects created by previous voice or email installations are not overwritten. [+] Show more info

The Voice SPD creates these objects:

• Default personality
• Audio resources
• Parameters
• Parameter group templates
• Parameter groups

The Voice SPD also creates these samples (object name in parentheses):

• ACD Queues (9000)
• Action codes (Admin Work, Locked, Lunch, Meeting, Pause, RONA, Training)
• Agent groups (AG_Voice_Sample, AG_Voice_Skill_Sample)
• Agent Logins (1000)
• Business attributes
• DN Groups (All_ACDQueues, All_RoutePoints, All_VirtualQueues)
• Extensions (8000)
• Place Groups (All_Places)
• Places (Place_SIP_8000)
• Route Point (selected during SPD installation)
• Skill (Skill_Sample)
• Virtual queue (VQ_Default_sample)

Initial configuration

Initial configuration of the voice routing application depends on the needs of the customer. Typically, the defaults supplied in the solution definition are sufficient. You can adjust voice routing parameters in either of two ways:

• To set new default values to be used in all new parameter groups that use the parameter, open Genesys Administrator Extension, navigate to Operations > Parameters, and adjust values as desired. Do not change Key Names.
• To set a new value that applies only to a specific parameter group, open Genesys Administrator Extension, navigate to Operations > Parameter groups, and adjust values as desired.

[+] Step 1. Define the auto-attendant menus

You can use parameter groups to build multiple sets of up to three cascading auto-attendant menus. Keep in mind that you must record corresponding Auto attendant menu announcements for each set you build.

To create a single set of three cascading menus:

1. Plan your menu set, because it is most efficient to begin by creating the third tier and its touch-tone selections, then the second tier, then the first. Your plan will look something like the following (the parameter group type is in parentheses):

 8000 (Inbound)
  1: Customer Service (Distribution)
     1: Wondrous Product Line (Distribution)
     2: Stupendous Product Line (Distribution)
  2: Sales (Distribution)
     1: North America (Distribution)
     2: EMEA (Distribution)
  3: Technical Support at routing point 6001 (Inbound)
     1: Printers (Distribution)
     2: Monitors (Distribution)
     3: Mice (Distribution)

A customer having difficulty with their mouse calls the number that corresponds to routing point 8000, then presses 3 for Technical Support and 3 again for Mice. In this example, you create 11 parameter groups: 2 Inbound and 9 Distribution.

2. Deploy the third-tier parameter groups (in the example, Wondrous Product Line, Mice, and the other 5). See below for help in setting the individual parameters.

3. Deploy the second-tier parameter groups. Add the third-tier groups as values for the Touch tone parameters. In the example, you deploy the Sales parameter group, then assign the North America group to Touch tone 1, and EMEA to Touch tone 2.

Important

When you create an Inbound parameter group, the name of the parameter group must be the same as the routing point that you want to handle these incoming calls (in the example, the Technical Support group must be named 6001).

4. Deploy a parameter group based on the Inbound parameter group template. Add the second-tier groups as values for the Touch tone parameters. In the example, you deploy the 8000 parameter group, then assign the Customer Service group to Touch tone 1, Sales to Touch tone 2, and 6001 to Touch tone 3.

[+] Step 2. Upload audio resources

Note: To use Internet Explorer 10 to access Genesys Administrator Extension or Genesys Administrator, you must add the following to the IE Trusted Sites:

• http://your UI VM domain
• about:blank

In GAX, for each audio resource, upload the corresponding audio (WAV) files:

Resource name	Description
Announcement-Auto attendant menu	Played when the auto attendant is enabled
Announcement-Closed	Played when the service is closed
Announcement-Emergency	Played when Emergency declared is activated
Announcement-Greeting 1	Played when Greeting 1 is enabled
Announcement-Greeting 2	Played after Greeting 1 when Greeting 2 is enabled
Announcement-Special day	Played for a Special day
Music File	Music played while the caller is in the queue

[+] Step 3. Customize business attributes

Your customer might require different Disposition Codes, which are the codes agents can select to specify the outcome of an interaction. The default disposition codes are:

• Cross Sell
• Not Right Skill
• Terminated
• Transferred
• Up Sell

To modify these samples or create your own codes, in Genesys Administrator, navigate to Provisioning > Routing > eServices > Business Attributes, and open the existing Disposition Code Business Attribute.

Your customer might also require different reporting categories. The five default business parameters (Service, Segment, Product, Department, and Flow) represent reporting categories and are completely customizable to your business model. You can assign different combinations of these parameters to each of your Inbound and Distribution parameter groups, to distinguish them in reporting and enable you to identify the unique properties of the parameter group.

[+] Step 4. Set open hours and special days

The parameter Open hours sets the standard hours that your office is open during the week. Use the Special day parameter to set:

• The dates or days of the week on which your office is closed for the entire day.
• The dates or days of the week on which your office is closed for only part of the day. In these cases, you use the Time Ranges field in GAX to set the hours that you will be open on that date.

Specific dates set in Open hours are treated as special days. Hours set for the same date in Special day override those set in Open hours; for example, if Open hours specifies that you are open from 9AM to noon on December 31, and Special day sets the hours of 11AM-2PM for the same date, callers who call at 10AM on that date hear the Closed announcement. Similarly, in both parameters, date patterns higher in the list take precedence over those lower in the list.

[+] Step 5. Set targets and target timeouts

Assign at least one target agent group for each parameter group. Change the timeout for each group as needed (default is 300 seconds, or 5 minutes). You should also assign a Target overflow, which serves as the "last resort" number to which a call is transferred when none of the other target agent groups answers within their timeout.

[+] Step 6. Tune priorities

You can adjust the priority of calls using the four priority tuning options. Over time, unanswered calls receive higher and higher priority, ensuring that calls do not remain in the queue for excessive lengths of time.

• Priority start sets the initial call priority; you typically have little reason to change the default of 1.
• Priority interval sets the number of seconds between priority increments. If you set the priority interval to 60 seconds, for example, and the priority increment is 1, then after 5 minutes of wait time, the call would have a priority level of 6, pushing it ahead of calls with priority values of 1-5.
• Priority Increment sets the number to add to the priority value each time the priority interval is exceeded. As the priority levels are relative, a setting of 1 typically works.
• Priority limit sets the upper limit for priority increments; all calls at the maximum priority level receive equal treatment.

[+] Step 7. Verify call routing

To verify that Business Edition Premise is correctly receiving and routing calls, make a test call to an agent:

1. Ensure that you have:
   • A soft phone, such as SJPhone
   • A sound-enabled Windows PC that can connect to the Core server
2. In GA, set the SIPS TServer option enable-unknown-gateway to true.

   Important: After completing the verification process, restore this value to false.

3. In GA, ensure that the user TestAgent belongs to the agent group AG_Voice_Sample.
4. In GAX, for parameter group 6000, ensure that:
   • Greetings activated is True.
   • Target 1 is AG_Voice_Sample.
   • Open Hours includes the current time (or the call will not route to the agent).
5. Install the Interaction Workspace (IWS) client by navigating to http://UI VM name or IP address/InteractionWorkspace/publish.htm and selecting Install or Launch.
6. Open IWS and log in using these credentials:
   • User name: TestAgent
   • Password: (none)
   • Place: Place_1000
   • Queue: 1004@SIP_Switch

   Ensure that the agent can log in and set their status to ready.

7. Open a soft phone as any user. For Domain, enter the FQDN of the SIP Server. Uncheck Register with domain.
8. Dial 6000. If the installation was successful, the call appears in IWS.

[+] Step 8. Verify call reporting

To verify reporting, run a report in Interactive Insights (GI2).

VIDEO: To watch a short demonstration of running a report, click the Genesys icon below:

Generating a Report	Generating a Report using Pre-Set Values

1. In a browser, log into GI2 at http://UI VM name or IP address:9080/CmcApp/logon.faces
   • User: administrator
   • Password: G3n35y5
2. Go to Folders > Interactive Insights > 8.1.1 > Agents.
3. Run the report Agent Group Interaction Handling Report.
4. In the report list, click Refresh until status = success.
5. Open the report and click Instance Time. If the installation was successful, the call appears in the report.
6. In GA, reset the TServer option enable-unknown-gateway to false.

[+] Step 9. Configure UCS database pruning

Genesys recommends that you configure automatic pruning of the Universal Contact Server (UCS) database to prevent it from growing too large in size.

Important

Changes made to the UCS database maintenance settings will apply to all deployed media strategies (Voice, Email, Chat, and Outbound).

1. On the UI host, log in to Universal Contact Server Manager.
2. Select the Scheduled task on Main DB tab.
3. Configure the Main DB maintenance settings as desired.
4. Click Save.

For each parameter group, enter a description in the Description field.

Audio and Announcements

For instructions on setting these parameters, see the Configuration tab.

Parameter	Values (default in bold)	Mandatory?	Description
Announcement-Closed	Closed Annc, any valid audio resource	Yes	Audio Resource played when the service is closed
Announcement-Auto attendant menu	Auto-attendant Menu 1, any valid audio resource	Yes	Audio Resource played when the auto attendant is enabled
Announcement-Emergency	Emergency Annc, any valid audio resource	Yes	Audio Resource played when Emergency declared is True
Announcement-Greeting 1	Greeting 1, any valid audio resource	Yes	Audio Resource played when Greeting 1 is enabled
Announcement-Greeting 2	Greeting 2, any valid audio resource	No	Audio Resource played after Greeting 1 when Greeting 2 is enabled
Announcement-Special day	Special Day Annc, any valid audio resource	Yes	Audio Resource played for a special day
Greetings activated	False, True	Yes	Activates the Greeting 1 and, if enabled, Greeting 2 announcements
Music File	Music In Queue, any valid audio resource	Yes	Audio Resource for music played while the caller is in the queue
Personality	Default Personality, other personality defined in GAX	Yes	The voice used in the announcements

Auto-attendant menus

For instructions on setting these parameters, see the Configuration tab.

Parameter	Values (default in bold)	Mandatory?	Description
Auto attendant menu activated	False, True	Yes	Activates an auto-attendant menu (such as Press 1 for Sales) for this parameter group
Touch tone 0	[none], target parameter group	No	Distribution or Inbound parameter group selected when the caller selects 0
Touch tone 1	[none], target parameter group	No	Distribution or Inbound parameter group selected when the caller selects 1
Touch tone 2	[none], target parameter group	No	Distribution or Inbound parameter group selected when the caller selects 2
Touch tone 3	[none], target parameter group	No	Distribution or Inbound parameter group selected when the caller selects 3
Touch tone 4	[none], target parameter group	No	Distribution or Inbound parameter group selected when the caller selects 4
Touch tone 5	[none], target parameter group	No	Distribution or Inbound parameter group selected when the caller selects 5
Touch tone 6	[none], target parameter group	No	Distribution or Inbound parameter group selected when the caller selects 6
Touch tone 7	[none], target parameter group	No	Distribution or Inbound parameter group selected when the caller selects 7
Touch tone 8	[none], target parameter group	No	Distribution or Inbound parameter group selected when the caller selects 8
Touch tone 9	[none], target parameter group	No	Distribution or Inbound parameter group selected when the caller selects 9

Business (reporting)

For instructions on setting these parameters, see the Configuration tab.

Parameter	Values (default in bold)	Mandatory?	Description
Department	[none], an item from the Department custom list for the parameter group	No	A business organization used as a category in reporting
Flow	[none], an item from the Flow custom list for the parameter group	No	A business flow used as a category in reporting
Product	[none], an item from the Product custom list for the parameter group	No	A product or product group used as a category for reporting
Segment	[none], an item from the Segment custom list for the parameter group	No	A customer category used as a category for reporting
Service	[none], an item from the Service custom list for the parameter group	No	Business categories typically used as the top level of the auto-attendant menu choices
Target virtual queue	[none], a target virtual queue set in GA	No	A reporting entity set up in Genesys Administrator

Contact center status

For instructions on setting these parameters, see the Configuration tab.

Parameter	Values (default in bold)	Mandatory?	Description
Emergency declared	False, True	Yes	Activates the emergency announcement, overriding any other announcement
Open Hours	From Monday to Friday, 0800-2000, closed Saturday and Sunday, value set for parameter group	Yes	Sets the hours that you are open and accepting calls; to specify open hours on specific dates, you must place the date above all day-of-week entries
Special day	December 25, January 1, any dates	No	A list of exceptions to the regular open hours, for a holiday or other reason.

Distribution

For instructions on setting these parameters, see the Configuration tab.

Parameter	Values (default in bold)	Mandatory?	Description
Default distribution parameter group	[none], parameter group	No	The distribution parameter group that provides the default and overflow target for this parameter group; if you do not set this parameter, the call flow uses the originally defined list of targets and timeouts
Target 1	[none], agent group	No	The first agent group to which the call is routed
Target 2	[none], agent group	No	The second agent group to which the call is routed
Target 3	[none], agent group	No	The third agent group to which the call is routed
Target 4	[none], agent group	No	The fourth agent group to which the call is routed
Target 1 timeout	300, integer between 0 and 99999	No	The timeout, in seconds, after which the call is routed to the next target agent group
Target 2 timeout	1, integer between 0 and 99999	No	The timeout, in seconds, after which the call is routed to the next target agent group
Target 3 timeout	1, integer between 0 and 99999	No	The timeout, in seconds, after which the call is routed to the next target agent group
Target 4 timeout	1, integer between 0 and 99999	No	The timeout, in seconds, after which the call is routed to the next target agent group
Target overflow	[none], a standard telephone number, such as 8005551212	No	The phone number to which a call is routed if the final Target timeout is exceeded or if no target agent group is specified. Important: you cannot use a routing point as this number.

Priority tuning

For instructions on setting these parameters, see the Configuration tab.

Parameter	Values (default in bold)	Mandatory?	Description
Priority Increment	0, integer between 0 and 99999	No	Sets the number to add to the priority value each time the priority interval is exceeded
Priority Interval	0, integer between 0 and 99999	No	The time interval (in seconds) between priority increments
Priority Limit	0, integer between 0 and 99999	No	Sets the upper limit for priority increments; all calls at the maximum priority level receive equal treatment
Priority Start	1, integer between 1 and 99999	Yes	The initial priority assigned to each incoming call