(Replaced content with "=Genesys Task Routing= {{ClosedProductNote}} Genesys Task Routing allows you to submit workitems to Genesys from an external source, such as Salesforce or NetSuite. Once...") |
(Update with the copy of version: Closed) |
||
Line 1: | Line 1: | ||
=Genesys Task Routing= | =Genesys Task Routing= | ||
+ | This page provides a high-level overview of Genesys Task Routing and the steps you must complete to implement it for your contact center. | ||
− | + | Genesys Task Routing allows you to submit workitems to Genesys from an external source, such as Salesforce or NetSuite. Once these external workitems are entered in the Genesys system, you can treat them like other Genesys interactions. For example, you can route workitems to the best-skilled agent using a [[Documentation:PSAAS:Administrator:Designer:Public|Designer]] application. You can also get interactions that were processed by an agent in [[Documentation:PSAAS:Agent:AD|Agent Desktop]], including automated third-party application screen pop-ups. Reporting is also available through [[Documentation:PSAAS:RPRT:HRCXI:Public|Genesys CX Insights]]. | |
− | Genesys Task Routing | + | Genesys Task Routing is integrated with other Genesys solutions and it can support blended agents handling chat, email, voice and so on, at the same time they manage workitems. |
− | + | At a high level, you'll need to complete the following steps to implement Genesys Task Routing: | |
+ | * Use the {{#Widget:ExtLink|link=https://developer.genesyscloud.com/|displaytext=Genesys Task Routing API}} to submit workitems to Genesys. You can also use this API to get, update and stop submitted workitems. | ||
+ | * Contact your Genesys representative to create a Capture Point. | ||
+ | * Define the routing application in Designer. | ||
+ | * Associate the Capture Point and routing application in Designer. '''Note:''' You can associate more than one Capture Point with the same routing application. | ||
+ | Complete the steps below to implement Genesys Task Routing for your contact center. | ||
+ | |||
+ | {{NoteFormat|You should be able to complete most of the steps on your own, but sometimes you'll need help from Genesys. We'll let you know when a task requires extra help from a Genesys representative.}} | ||
+ | |||
+ | {{AnchorDiv|DefineAgents}} | ||
+ | == 1. Define agents and agent groups == | ||
+ | Use Agent Setup to define [[Documentation:PSAAS:Administrator:UserMan:Public|agents]] and [[Documentation:PSAAS:Administrator:umgrAgentGroups:Public|agent groups]]<!--, and make sure to enable the [[Documentation:PSAAS:Administrator:umgrChannels:Public|Open Media channel]] for the agents-->. | ||
+ | |||
+ | Next, work with your Genesys representative to enable an Open Media channel and define a capacity rule, then [[Documentation:PSAAS:Administrator:UserMan:Public|assign]] it in Agent Setup. | ||
+ | |||
+ | {{AnchorDiv|ConfigureAD}} | ||
+ | |||
+ | == 2. Configure Agent Desktop == | ||
+ | You should go through the normal process to configure any necessary [[Documentation:PSAAS:Administrator:umgrDesktopOptions:Public|desktop options]] for the agents in your contact center. You'll also need help from your Genesys representative to set a few options related to Open Media. | ||
+ | |||
+ | <!--Pay special attention to the following options: | ||
+ | * If you want to prevent agents from declining incoming workitems, [[Documentation:PSAAS:Administrator:ASOpenMedia:Public|disable the Decline option for Open Media]]. | ||
+ | * Genesys recommends [[Documentation:PSAAS:Administrator:ASOpenMedia:Public|disabling the Mark Done button]] to ensure the task is completed only from the third-party application.--> | ||
+ | |||
+ | {{AnchorDiv|CreateCP}} | ||
+ | |||
+ | == 3. Create a Capture Point == | ||
+ | Contact your Genesys representative to create a Capture Point. | ||
+ | <!-- Create a [[Documentation:PSAAS:Administrator:DigServiceAdmin:Public|Capture Point]] (also called a service) in Agent Setup. '''Note''': You'll need your API key and Genesys Task Routing API endpoint to use Genesys Task Routing. This information is displayed by Agent Setup for each Capture Point.--> | ||
+ | |||
+ | {{AnchorDiv|CreateRouting}} | ||
+ | == 4. Create a routing application == | ||
+ | Genesys Task Routing includes a sample Designer application to show one of the possible scenarios. Check out the [[GTRSampleDesignerApp|sample application]] for more information. | ||
+ | |||
+ | For more details about creating a new routing application in Designer, see the [[Documentation:PSAAS:Administrator:ApplicationsBar:Public|documentation]]. | ||
+ | |||
+ | Once you have a routing application, use Designer to [[Documentation:PSAAS:Administrator:ApplicationsBar:Public#manage_om_endpoint|link it to the Capture Point]] created in step 3. | ||
+ | |||
+ | {{AnchorDiv|Integrate}} | ||
+ | == 5. Integrate third-party applications == | ||
+ | A third-party application can interact with Genesys Task Routing through the {{#Widget:ExtLink|link=https://developer.genesyscloud.com/|displaytext=Genesys Task Routing API}} and the [[Documentation:PSAAS:Administrator:ServiceClientAPI:Public|Service Client API]]. | ||
+ | |||
+ | You'll need to develop a third-party system adapter that can create and stop workitems using the Genesys Task Routing API. It should also update and retrieve information about a workitem, if needed. | ||
+ | |||
+ | The typical workflow is as follows: | ||
+ | |||
+ | # The third-party application creates a workitem through the Genesys Task Routing API. | ||
+ | # The third-party application updates and/or retrieves the interaction through the Genesys Task Routing API (if needed). | ||
+ | # The third-party application stops the interaction. | ||
+ | |||
+ | There are two ways for the third-party application to stop an interaction: | ||
+ | * Implicit (recommended) — stop by invoking Mark Done using the Service Client API. For this method, complete the following steps: | ||
+ | *# [[Documentation:PSAAS:Administrator:ASServiceClient:Public|Set up Agent Desktop to use the API.]] | ||
+ | *# Disable the Mark Done button in Agent Desktop (as mentioned earlier in [[#ConfigureAD|Configuring Agent Desktop]]) and instead [[Documentation:PSAAS:Administrator:InteractionNamespace:Public#markdone|invoke Mark Done through the Service Client API]]. | ||
+ | *# You can also use the Service Client API to [[Documentation:PSAAS:Administrator:InteractionNamespace:Public#setUserData|set the Disposition Code]]. | ||
+ | * Explicit — stop by using the Genesys Task Routing API. This requires additional configuration from your Genesys representative. | ||
+ | |||
+ | A sample application that demonstrates using the Genesys Task Routing API and the Service Client API is also available through your Genesys representative. | ||
+ | |||
+ | {{AnchorDiv|Configure3rdParty}} | ||
+ | ===Configure third-party application screen pop-up === | ||
+ | You can configure Genesys Task Routing to enable a third-party application screen pop-up inside Agent Desktop when an agent accepts a task. There are two ways to do it: | ||
+ | |||
+ | # Pop-up a third-party application screen for all media types. This approach works well when an agent is handling only workitems. See the [[Documentation:PSAAS:Administrator:DesktopSettings:Public#External_URLs|Agent Setup documentation]] for details. | ||
+ | # Pop-up a third-party application screen for only workitems. This approach works well when an agent handles multiple media types and the third-party pop-up should only happen for workitems. You'll need to work with your Genesys representative to configure this approach. | ||
[[Category:V:PSAAS:Public]] | [[Category:V:PSAAS:Public]] |
Revision as of 18:52, April 18, 2019
Contents
Genesys Task Routing
This page provides a high-level overview of Genesys Task Routing and the steps you must complete to implement it for your contact center.
Genesys Task Routing allows you to submit workitems to Genesys from an external source, such as Salesforce or NetSuite. Once these external workitems are entered in the Genesys system, you can treat them like other Genesys interactions. For example, you can route workitems to the best-skilled agent using a Designer application. You can also get interactions that were processed by an agent in Agent Desktop, including automated third-party application screen pop-ups. Reporting is also available through Genesys CX Insights.
Genesys Task Routing is integrated with other Genesys solutions and it can support blended agents handling chat, email, voice and so on, at the same time they manage workitems.
At a high level, you'll need to complete the following steps to implement Genesys Task Routing:
- Use the Genesys Task Routing API to submit workitems to Genesys. You can also use this API to get, update and stop submitted workitems.
- Contact your Genesys representative to create a Capture Point.
- Define the routing application in Designer.
- Associate the Capture Point and routing application in Designer. Note: You can associate more than one Capture Point with the same routing application.
Complete the steps below to implement Genesys Task Routing for your contact center.
1. Define agents and agent groups
Use Agent Setup to define agents and agent groups.
Next, work with your Genesys representative to enable an Open Media channel and define a capacity rule, then assign it in Agent Setup.
2. Configure Agent Desktop
You should go through the normal process to configure any necessary desktop options for the agents in your contact center. You'll also need help from your Genesys representative to set a few options related to Open Media.
3. Create a Capture Point
Contact your Genesys representative to create a Capture Point.
4. Create a routing application
Genesys Task Routing includes a sample Designer application to show one of the possible scenarios. Check out the sample application for more information.
For more details about creating a new routing application in Designer, see the documentation.
Once you have a routing application, use Designer to link it to the Capture Point created in step 3.
5. Integrate third-party applications
A third-party application can interact with Genesys Task Routing through the Genesys Task Routing API and the Service Client API.
You'll need to develop a third-party system adapter that can create and stop workitems using the Genesys Task Routing API. It should also update and retrieve information about a workitem, if needed.
The typical workflow is as follows:
- The third-party application creates a workitem through the Genesys Task Routing API.
- The third-party application updates and/or retrieves the interaction through the Genesys Task Routing API (if needed).
- The third-party application stops the interaction.
There are two ways for the third-party application to stop an interaction:
- Implicit (recommended) — stop by invoking Mark Done using the Service Client API. For this method, complete the following steps:
- Set up Agent Desktop to use the API.
- Disable the Mark Done button in Agent Desktop (as mentioned earlier in Configuring Agent Desktop) and instead invoke Mark Done through the Service Client API.
- You can also use the Service Client API to set the Disposition Code.
- Explicit — stop by using the Genesys Task Routing API. This requires additional configuration from your Genesys representative.
A sample application that demonstrates using the Genesys Task Routing API and the Service Client API is also available through your Genesys representative.
Configure third-party application screen pop-up
You can configure Genesys Task Routing to enable a third-party application screen pop-up inside Agent Desktop when an agent accepts a task. There are two ways to do it:
- Pop-up a third-party application screen for all media types. This approach works well when an agent is handling only workitems. See the Agent Setup documentation for details.
- Pop-up a third-party application screen for only workitems. This approach works well when an agent handles multiple media types and the third-party pop-up should only happen for workitems. You'll need to work with your Genesys representative to configure this approach.