Difference between revisions of "ATC/Current/AdminGuide/Route"

From Genesys Documentation
Jump to: navigation, search
(Published)
(Published)
Line 2: Line 2:
 
|Standalone=No
 
|Standalone=No
 
|DisplayName=Route an action map to a target
 
|DisplayName=Route an action map to a target
|TocName=Route
+
|TocName=Route an action map
 
|Context=Learn how to route an action map to an agent queue for chat offers.
 
|Context=Learn how to route an action map to an agent queue for chat offers.
 
|ComingSoon=No
 
|ComingSoon=No
Line 25: Line 25:
 
{{MintyDocsProduct}} also manages chat routing to ensure that agents aren't overwhelmed with chats. {{MintyDocsProduct}} uses one of the following, depending on your configuration:
 
{{MintyDocsProduct}} also manages chat routing to ensure that agents aren't overwhelmed with chats. {{MintyDocsProduct}} uses one of the following, depending on your configuration:
  
*For most customers, {{MintyDocsProduct}} uses an estimated wait time (EWT) of approximately 20 seconds. If an agent won't be available within 20 seconds, the visitor doesn't receive a chat offer.<br />If you use EWT, and you have a predefined Service Level Agreement that includes a queue throttling provision, {{MintyDocsProduct}} follows those configuration guidelines.
+
*For most customers, {{MintyDocsProduct}} uses an estimated wait time (EWT) of approximately 20 seconds. If an agent won't be available within 20 seconds, the visitor doesn't receive a chat offer.<br />If you use EWT, and you have a predefined Service Level Agreement that includes a queue {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=How_throttling_works|display text=throttling}} provision, {{MintyDocsProduct}} follows those configuration guidelines.
 
*For Genesys Engage Premises customers only, the [[ATC/Current/PacingServiceDeployment|Agent Pacing Service]] determines agent availability.
 
*For Genesys Engage Premises customers only, the [[ATC/Current/PacingServiceDeployment|Agent Pacing Service]] determines agent availability.
  

Revision as of 15:55, October 30, 2020

Learn how to route an action map to an agent queue for chat offers.

Prerequisites

About targets for action maps

When Genesys Predictive Engagement presents an offer to chat to a visitor, that offer can include an invitation to speak directly with a live person, such as an agent or salesperson. The agent or salesperson is part of a team that has a corresponding queue in your contact center. Multiple action maps can route to the same target queue.

Genesys Predictive Engagement offers chats to users only when both of the following occur:

  • User agrees to speak to an agent; and
  • Agent is available to respond to the visitor

Genesys Predictive Engagement also manages chat routing to ensure that agents aren't overwhelmed with chats. Genesys Predictive Engagement uses one of the following, depending on your configuration:

  • For most customers, Genesys Predictive Engagement uses an estimated wait time (EWT) of approximately 20 seconds. If an agent won't be available within 20 seconds, the visitor doesn't receive a chat offer.
    If you use EWT, and you have a predefined Service Level Agreement that includes a queue throttling provision, Genesys Predictive Engagement follows those configuration guidelines.
  • For Genesys Engage Premises customers only, the Agent Pacing Service determines agent availability.

To configure a target for an action map, create an action map and use the Route to target section to select the team who should talk to the users that the action map engages.

For more information about creating queues in Genesys Cloud, see Queue administration.

Route to a target

  1. Click the queue to receive engagements from this action map. You can select any queue that is available in your contact center. For more information about unavailable targets, see Unavailable or unselected targets.
  2. To ensure that Genesys Predictive Engagement presents the engagement only when agents are available to engage with the visitor and only when you are not using chatbots, turn on the Route if agents available option.
Important
 
  • If you do not turn on the Route if agents available option, Genesys Predictive Engagement sends the engagement to the queue that you specify regardless of whether an agent in the queue is available.
  • If chatbots are handling interactions, do not turn on the Route if agents available option.
Tip
For more information about advanced routing, see: Genesys Predictive Engagement with advanced chat routing.

Unavailable or unselected targets

  • Deleted or removed queues aren't available for selection.
  • If a target that you selected previously becomes unavailable, a warning appears next to the Route to a target list box.
  • If you do not select a target and you configured a default or general queue, Genesys Predictive Engagement sends all engagements from this action map to the configured queue. Genesys Predictive Engagement doesn't make routing decisions; they are platform dependent.
Retrieved from "https://all.docs.genesys.com/ATC/Current/AdminGuide/Route (2024-10-07 00:24:02)"
Comments or questions about this documentation? Contact us for support!