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

From Genesys Documentation
Jump to: navigation, search
m (Text replacement - "https://help.mypurecloud.com/articles/altocloud-permissions-overview" to "https://help.mypurecloud.com/articles/?p=195191")
(Published)
Line 16: Line 16:
 
|sectionHeading=About targets for action maps
 
|sectionHeading=About targets for action maps
 
|alignment=Vertical
 
|alignment=Vertical
−
|structuredtext=When {{MintyDocsProduct}} presents an [[ATC/Current/AdminGuide/Chat offers|offer to chat]] to a visitor, that offer can include an invitation to speak directly with a live agent assigned to the queue to which the action map routes. Multiple action maps can route to the same target queue.{{NoteFormat|Genesys Predictive Engagement can offer web actions, such as web chats and content offers, every 10 seconds. Visitors may experience a delay in receiving these types of offers.|}}{{MintyDocsProduct}} allows chat offers when the following criteria are met:
+
|structuredtext=When {{MintyDocsProduct}} presents an [[ATC/Current/AdminGuide/Chat offers|offer to chat]] to a visitor, that offer can include an invitation to speak directly with a live agent assigned to the queue to which the action map routes. Multiple action maps can route to the same target queue.{{NoteFormat| 
 +
*Genesys Predictive Engagement can offer web actions, such as web chats and content offers, every 10 seconds. Visitors may experience a delay in receiving these types of offers.
 +
*Only use the '''Route if agents available''' option for web chat engagements that you don't intend to route to a bot.
 +
*Multiple action maps can route to the same target queue.|}}{{MintyDocsProduct}} allows chat offers when the following criteria are met:
  
 
*Action map conditions are met.
 
*Action map conditions are met.
Line 23: Line 26:
 
**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.
 
*Agents are on queue.
 
*Agents are on queue.
−
*Chat is within scheduled hours.
+
*Chat is within {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Schedules|display text=scheduled}} hours.
  
 
{{MintyDocsProduct}} calculates the [https://help.mypurecloud.com/glossary/service-level/ service level] based on the queue's configuration in Genesys Cloud.  
 
{{MintyDocsProduct}} calculates the [https://help.mypurecloud.com/glossary/service-level/ service level] based on the queue's configuration in Genesys Cloud.  
Line 37: Line 40:
 
|image=RouteToTeamEWT.png
 
|image=RouteToTeamEWT.png
 
|structuredtext=#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 {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Route|anchor=unavailableTargets|display text=Unavailable or unselected targets}}.
 
|structuredtext=#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 {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Route|anchor=unavailableTargets|display text=Unavailable or unselected targets}}.
−
#To ensure that {{MINTYDOCSPRODUCT}} presents the engagement ''only'' when agents are available to engage with the visitor and ''only'' when you are not {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Route|anchor=ChatbotConsiderations|display text=using chatbots}}, turn on the '''Route if agents available''' option.
+
#To ensure that {{MINTYDOCSPRODUCT}} presents the chat engagement ''only'' when agents are available to engage with the visitor and ''only'' when you are not {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Route|anchor=ChatbotConsiderations|display text=using chatbots}}, turn on the '''Route if agents available''' option.
 
{{NoteFormat| 
 
{{NoteFormat| 
 
*If you do not turn on the '''Route if agents available''' option, {{MINTYDOCSPRODUCT}} sends the engagement to the queue that you specify regardless of whether an agent in the queue is available.
 
*If you do not turn on the '''Route if agents available''' option, {{MINTYDOCSPRODUCT}} 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.|}}{{NoteFormat|For more information about advanced routing, see: {{#mintydocs_link:topic=Solution/ChatSolutions|standalone}}.|2}}
+
*If chatbots are handling interactions, do not turn on the '''Route if agents available''' option.|}}{{NoteFormat|For more information about advanced routing, see {{#mintydocs_link:topic=Solution/ChatSolutions|standalone}}.|2}}
 
|Status=No
 
|Status=No
 
}}{{Section
 
}}{{Section

Revision as of 13:30, November 19, 2020

This topic is part of the manual Genesys Predictive Engagement Administrator's Guide for version Current of Genesys Predictive Engagement.

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 agent assigned to the queue to which the action map routes. Multiple action maps can route to the same target queue.
Important
 
  • Genesys Predictive Engagement can offer web actions, such as web chats and content offers, every 10 seconds. Visitors may experience a delay in receiving these types of offers.
  • Only use the Route if agents available option for web chat engagements that you don't intend to route to a bot.
  • Multiple action maps can route to the same target queue.
Genesys Predictive Engagement allows chat offers when the following criteria are met:
  • Action map conditions are met.
  • URL conditions are verified.
  • Throttling allows the chat. By default, throttling aims to have 80% of chats answered within 20 seconds.
  • Agents are on queue.
  • Chat is within scheduled hours.

Genesys Predictive Engagement calculates the service level based on the queue's configuration in Genesys Cloud.

To specify a target queue for an action map, create an action map and then specify the queue to which to route the chat offer. 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 chat 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:26:59)"
Comments or questions about this documentation? Contact us for support!