m (Text replacement - "Genesys PureEngage" to "PureEngage") |
(Modified comment string __NOINDEX__ Category:V:PSAAS:Public with Category:V:PSAAS:Public) |
||
| (3 intermediate revisions by 2 users not shown) | |||
| Line 7: | Line 7: | ||
{{BEC_Head | {{BEC_Head | ||
|context= | |context= | ||
| − | Given that Harry is new to | + | Given that Harry is new to Genesys Engage cloud products, Alex, a Genesys Administrator, will take care of the first step – routing configuration. }} |
Using '''Platform Administrator''' Alex will create and configure the Routing Point DN, the Virtual Queue DN, and the Agent Group, and then assign agents to the group. | Using '''Platform Administrator''' Alex will create and configure the Routing Point DN, the Virtual Queue DN, and the Agent Group, and then assign agents to the group. | ||
Latest revision as of 12:23, October 2, 2020
Stage 1: Configuring Outbound routing
Given that Harry is new to Genesys Engage cloud products, Alex, a Genesys Administrator, will take care of the first step – routing configuration.
Using Platform Administrator Alex will create and configure the Routing Point DN, the Virtual Queue DN, and the Agent Group, and then assign agents to the group.
Then he’ll build the IVR using Designer. He’ll drag and drop blocks from the Palette into one of the four Application Flow phases that define the IVR. Then he’ll hand it off to Harry.
Scenario: A week later, the contact center hired five new agents and asked Harry to add them and assign them to the Outbound campaign.
Solution: Even though Alex assigned the agents to an Agent Group in Platform Administrator, Harry can sign into the application and add or remove agents as needed.
