ACD Page: GVP Platform
Use this page if ACD is enabled for your account on the GVP Platform.
Note: If your account is enabled for ACD on the Holly platform, see ACD Page: Holly Platform. If you are unsure about which platform you are using, contact your account representative.
On the Main tab on the ACD Page specify the following:
- the administrator for the ACD for the site
- how calls are delivered to agents
- the next Voice Page to which calls are sent after the agent completes the call
Configuring the Administrator for the ACD
After you create a site and assign a phone number to it, you must create the first ACD administrator.
To create the first ACD administrator, do the following in the order specified:
- Configure a skill by going to the For an agent to be selected, they must have this skill field under the Administrator section, and selecting a variable from the drop-down menu that will contain the value used for the skill.
- If you have not already assigned a phone number to the site, right-click Site Overview, and from the left area click Assign Number. See Account Settings.
- Return to the ACD page and click Save.
- On the same ACD page, enter the administrator's first name, last name, and e-mail address in the respective fields. Note: Each agent must have a unique e-mail address.
- Click Send Login Instructions, and the administrator you just specified is sent an e-mail. When the person receives the e-mail, he or she must use it to create a password to access VCC Dashboard.
Use the Send Forgot Password Instructions, if the assigned administrator needs a reminder of the login instructions.
Note: If you have more than one ACD Page for a CX Builder site, the administrator can be the same or different for each ACD Page.[+] Password strength rules
Specifying Skill Values
Before using this routing, you need to define skill proficiencies for all your agents using VCC Dashboard. When setting up the skills for your agents, you must provide a skill proficiency between 1 and 5 for each skill that is assigned to an agent. A proficiency of 1 is the lowest rating (beginner) and 5 is the highest rating (expert).
Note: If you do not want to use skill proficiency for routing, the skill level variable can be set to 1. Otherwise, this variable should be set to 5.
For this section, you specify the value for each item using site variables that you define.
- Use the For an agent to be selected, they must have this skill option to select or create the IVR variable that the system uses to store the skill value used to route the calls. When a caller requires assisted service from the ACD queue, the caller is prompted for the type of assistance required. This type of assistance is associated with a skill, and the skill is stored in a variable. This variable is passed to the ACD queue and used in the associated routing strategy. These variables are text and should correspond to the type of agent to whom the call will target. Two examples are Sales or Support.
- Use the Agents must have skill level equal or above option to define the skill level.
- If proficiency routing is used then this variable is usually set to 5, the highest proficiency.
- If proficiencies are not used, then set this variable to 1, the lowest proficiency.
- Use If no agents available requested skill level decreases every option to define the value of the skill timeout. This value is the number of seconds the router waits until the target proficiency is lowered and the agent pool is expanded. For proficiency routing, the strategy first looks for agents with the proficiency of 5. If no agents are available with this skill and proficiency, the router waits the number of seconds defined before moving to the next target. This next target includes all agents with the selected skill and a proficiency of 4 or 5. This pattern repeats until a proficiency of 1 is reached. When the Maximum Hold Time for Callers is reached, the call is directed to another IVR destination page. The Maximum Hold Time for Callers is defined on the In Queue tab on the ACD Page.
- Use the Queue routing priority option to set the routing priority of a call. Queue priority routing allows some calls to be handled quicker than others. Any call without a priority is automatically assigned a priority value of 0 (zero). The call priority value can be any integer. As you increase the value, the call priority rises.
- Use the Transfer queue routing priority to define the routing priority of a skill transfer for inbound calls. This option applies to the transfer leg of a call, where one agent transfers a call, via the agent desktop, to another agent with a particular skill. This transfer skill could be the same skill used for the original inbound call or it could be a different skill.
- if the queue priority and the transfer priority have equal values on the ACD Page, the transferred leg of the call will be prioritized over the queued inbound calls if the original inbound call (the one being transferred to a skill) was queued before the other inbound calls for this transfer skill. If, however, the original inbound call was queued after other inbound calls for the transfer skill, the queued calls for this transfer skill will be processed in the order received.
- This option applies to direct transfers to a skill, a consult to a skill, and two-step transfers to a skill (for example, a consult to a skill and a transfer). It does not apply to outbound calls.
Specifying Call Delivery
Use the Routing Logic section on the Main tab to:
- Set the number of seconds before returning an unanswered call to the ACD queue to be rerouted in the field next to When the agent does not answer within... When the unanswered call returns to the ACD queue, the agent state can be changed to one of the following: Not Ready, Logged Out, or No Change, depending on the setting.
- If Whisper is enabled, set the When the agent does not answer within... value to total whisper greeting time + 10. If you are using the default whisper time of 20 seconds, set the value to 30 seconds.
- Make sure that the agents' phones are set up with a voicemail timeout duration that is longer than what is set on the ACD Page. Otherwise, the call might be sent to the agent's voicemail.
- The missed call (agent does not answer within xx seconds) and state change feature does not apply to outbound and consultation calls. It applies only to inbound and transfer calls.}}
- Specify the call delivery to handle situations when multiple agents are available with the same skill and proficiency. The call delivery options are:
- Round Robin — Selects an agent and then sends calls to all other agents before repeating. Unavailable agents are skipped and the next agent in the round robin is selected.
- Most Idle Agent — Sends calls to the agent that was waiting the longest (the Longest Wait Time statistic is used for this routing logic).
- Least Utilized Agent — Sends calls to the agent who has answered the fewest number of calls per time-logged-in. The statistic formula used for this routing logic is: Talk Time / Total Login Time. This statistic is reset to 0 (zero) when an agent logs in.
- Agent 1 receives a call. Within 60 minutes, another customer calls. This second call is routed to Agent 2.
- Agent 1 receives a call. After 60 minutes, another customer calls. This second call is routed to Agent 1, because the Round Robin statistic had reset after 60 minutes of inactivity.
Configuring Exit Conditions
The exit point options on the Main tab define which voice page the application is routed to when the call is returned from the ACD. Test exit points are defined in the Exit Point Options Table described below.
Exit Point Options Table
|Exit Point Name||Description||Return Code|
When the call completes, take callers to
Used when calls are successfully connected to an agent.
When no agents are available, take callers to option
When pressing 0 to exit the queue, take callers to option
Used for calls where the caller exits the queue by pressing 0. By default, this option is disabled.
For all other results, take callers to option
Used for error conditions when none of the above are met.
The return codes are:
- Max Timeout (Queue Timeout expired)
The In Queue tab specifies which audio to play while a caller is in the queue.
Using this tab, you specify the Waiting Audio and the Wait Options.
For Select first voice page for waiting loop option, select the first Waiting Message Page that a caller will hear while in the ACD queue.
Also, see Waiting Message Page.
- If you're an existing user of GVP platform, the default voice page listed is the EWT Page, as it was in the CX Builder 15.3 release.
- Click How it Works to read a pop-up titled Achieving a Great Caller Experience, which offers a summary of how to build your Voice Site and how your choices define exactly what callers will hear.
Here you decide what happens when a caller waits too long.
Maximum Hold Time for Callers
- Specify the maximum wait time. You can change the maximum wait time: default=600 seconds (10 minutes).
- Specify the voice page a caller will hear next if the maximum wait time is exceeded.
The Whisper tab functionality provides a whisper tone to the agent prior to the call being delivered to the agent.
- Click the Whisper the call information to the Agent before connecting the caller check box to enable this.
- To specify what the agent hears when the call is ringing for the incoming call, under the Prompt Agent Hears section, specify the agent prompts. If you specify more than one prompt, the agent hears only those selected and in the order they are listed on the page. For audio files, you can upload them from this page.
- Click the Record the caller's name and announce it to the Agent check box, so the IVR prompts the caller for their name, so this name is played to the agent prior to the call being answered.
- The Agent Commands section provides the CX Builder user with instructions to pass on to agents about how to accept (press 1 or say yes) or reject (press 0 or say no) a call.
- If the audio is played from the ACD queue, the Whisper Tone feature is disabled.
- The Whisper functionality is limited to the treatment being played from the IVR. If agents are using the functionality, callers cannot opt out (zero-out) of the call at the same time.
Use this page to identify voice pages visible to an agent on Agent Desktop to which the agent enable can transfer a call within the IVR.
- In each respective section, Transfer to Voice Pages (Return to agent) and Transfer to Voice Pages (Not return to agent), use the arrow keys to add voice pages from the Available Voice Page section to the Selected Voice Page section.
Once configured, the pages in the Selected Voice Pages section are available for agents to select in their Agent Desktop.
Note: When adding pages to the Transfer to Voice Pages (Return to agent) field, you can only add Message Pages and Question Pages. You cannot add an ACD Page, Call Transfer Pages, or Call Queue Pages (VCC 1.x users enabled for this feature).
Naming Convention for Voice Pages Used for IVR Transfers
When creating Message Pages and Question Pages associated with this feature, do the following:
- Use page names that identify what each accomplishes, indicates the site to which it belongs (if the agent handles calls from multiple sites) and the ACD Page from which the call originated. Since agents can see all such IVR Transfer pages in their UI, you need to ensure that they only select Transfer targets in the Team Communicator that are associated with the same site and same ACD Page.
- Alert your agents.
- About the naming convention so agents know which Transfer targets they can select in the Team Communicator and in what scenario.
- That the voice pages specified on this tab as Transfer targets cannot be used for agent consult calls.
- For VCC Dashboard users, that IVR Transfer pages appear as read-only objects in the contact list for your contact center and have the number prefix IVR (for example, IVR2030305099).
When creating a sequence of transfer pages for calls that need to return to the agent, be sure that the last destination page in the sequence, before it returns to the agent, has the Action set to End the Call. For example, a sequence might be Message Page1 > Logic Page 2 > Question Page 3 > Message Page 4 with the Action set to End the Call.
This feature would be useful in a few scenarios.
- If the agent needs the caller's credit card number. Instead of the agent taking the number, the agent can transfer the call to the voice page to prompt the caller for the information.
- If the agent needs to explain terms and conditions. Instead of the agent reading the information, the agent can transfer the caller to the voice page so the caller can hear them and then be returned to the agent to continue the call.
Skill-based transfers use the same basic routing parameters as those used for inbound calls. CX Builder takes into account that agent's proficiency, the skill timeout, or other parameters set on this ACD Page, making the user experience of transferred calls more like inbound calls.
On this tab, you specify the audio customers hears while waiting on hold during the transfer of their call where calls require a different in-queue audio than inbound calls.
Note: This tab only appears if ACD is enabled for your account.
- To enable ability, select the check box. If you do not select it, the hold music played for call transfers is the same as that specified in the In Queue tab.
- Select the first Waiting Message Page that includes the first prompt you want the caller to hear while waiting on hold during the transfer. (Note: Configure successive Waiting Message pages for additional prompts you want the caller to hear as part of the loop.) For more information, see Waiting Message Page.
Keep in mind
- The skill sought for in the agent to whom the call is transferred is the one the agent specifies when transferring the call.
- The priority of a transferred call is increased by 5. This means the caller waiting in queue for a transfer has a higher priority than other callers who have not yet spoken with an agent.
- The required skill and skill level set on the Main tab also applies to the skill/skill level required for the agent to whom the call is transferred.
- If you're an existing user of GVP platform, the default voice page listed is the Home Page, as it was in the CX Builder 15.3 release.
The Advanced Options tab allows the user to pass IVR variables to the ACD for calls, screen pops, and reporting. This tab also allows the customer to return, from the ACD, variables that are used for post-call routing or used in a transaction page.
The variables in this section of this tab are used to send data from the IVR to the ACD. Use the top section to define the Toast and Case data. Use the lower section to configure the data coming from the ACD queue that is used when the call is returned to the IVR. This data is normally used for post-call routing, such as sending the data to a customer database by using a Transaction page, or for a customer survey application.
Configuring Toast and Case Data
When an inbound call is presented to an agent, a screen popup is displayed containing information based on selected variables. These variables can be information collected from callers or information pulled from the call web services of other systems. Once the information is available in the form of variables, it can be passed to agents via a screen popup.
You can define additional variables to use for screen pop-ups (Toast and Case data). Toast and Case data is the data that an agent is provided when a call is ringing or answered, respectively.
Toast data is the data that is delivered to the Agent Desktop when a call is ringing. This data is collected within the IVR or from a back-end database lookup via the IVR. This data is used by the agent to prepare for the call prior to answering said call. You can use the Advanced Options tab to define the variables for screen pops.
- The IVR variable that is used to pass the toast data value is entered in the Queue Variables field (for example, firstNameLastName).
- The display name that is to appear in VCC Agent Desktop is entered in the Desktop Text field (for example, customer Name).
Example: An agent handles calls for multiple companies or products. The toast data provides the agent with the company or product name to which the caller wants information. This toast data might also provide the caller's name, or what action within the IVR the caller performed.
Case data is the data that is delivered to the Agent Desktop when a call is answered. This data is collected within the IVR or from a back-end database lookup via the IVR. The agent uses this data to identify the caller and to better handle the call.
- The IVR variable used to pass the case data value is entered in the Queue Variables field (for example, userAccountType).
- The display name used to appear in VCC Agent Desktop is entered in the Desktop Text field (for example, Skill).
Example: If an agent answers a call, the call controls display at the top of the main view, and the Case Information view is displayed below the call controls. The Case Information view contains the case data and provides whatever information the agent might need to handle this interaction. This information might include an account number that the caller entered, or any data a back-end database might contain regarding this contact. This data is meant to provide the agent with all of the information that they need to handle the interaction without asking the caller to repeat the information that the caller has already entered while navigating through the IVR.
Adding Toast Data, Case Data, or Both
- In the Report Settings section of the Advanced Options tab, click Add.
- Enter the IVR variable used to pass the data value in the Queue Variables field (for example, toast data of firstNameLastName).
- Enter the display name used to appear in CTI Adapter in the Desktop Text field (for example, customer Name).
- Select Toast, Case, or Both from the Toast/Case drop-down list.
- Click Save to keep the settings.
Deleting the Data
- In the Report Settings section of the Advanced Options tab:
- Check the variable that you want deleted.
- Click Delete.
- Click Save to keep the settings.
Configuring the Customer Segment Variable
The Customer Segment stored in variable is used for reporting and is an optional variable. If the contact center segments callers by using tiers, or some other method, the value of the customer can be stored here. An example of this variable might be a company that segments customers as Gold, Silver, or Bronze, or 5 year, 10 year, or Greater than 10 years. The variable that is defined in the site variables that is used to store the skill level is assigned here.
Configuring the Call Information Variables
The lower section of this tab is used to collect data from the ACD to use in the IVR Pages once the call is returned to the IVR:
- Agent Name: is the agent username that handled the call, or if more than one agent handled the call, the list of agent usernames that were included in the call.
- Agent Email: is the agent email for all agents that handled the call, or if more than one agent handled the call, the list of agent emails that were included in the call.
- Call Outcome: is a tag indicating if the call was handled by an agent or not. The return values are:
- The ACD queue returns the call status in the following cases:
- the maximum timeout is reached
- the caller zeroes out (pressing 0)
- when the caller talks to an agent and the agent releases the call
- Duration: is the amount of time that the caller spent waiting in the ACD queue plus the time spent talking with the agent. This time interval is measured in seconds.
- Wait Time: is the amount of time a caller waited in the ACD queue. This time interval is measured in seconds.
- Disposition Code: is the last Disposition Code that the agent selected for this call.