Callback Administrator's Guide
From Genesys Documentation
Search the table of all articles in this guide, listed in alphabetical order, to find the article you need.
|Callback scenarios||This article summarizes the scenarios that Genesys Callback supports. In addition to the traditional Immediate and Scheduled callback scenarios, Callback also supports Click-To-Call-In scenarios, allowing consumers to initiate a call to your contact center by tapping a Click-To-Call button in your mobile app.|
|Configuring Capacity rules||You want to manage the number of scheduled callbacks that are allowed during specific time intervals. To do that, you'll create a Capacity rule in Genesys Callback and assign it to a callback queue. We'll walk you through the process and explain the implications of using a Capacity rule in relation to Designer. We'll also tell you about a shortcut method for entering values in your Capacity rule (JSON-format capacity statements).|
|Configuring Click-To-Call-In Groups||As a Callback administrator, you are setting up the Click-To-Call-In groups that you require for the Click-To-Call-In scenario. We'll tell you how to add your DNIS numbers to a group and how to enable the use of an access code for consumer call-ins. If you are migrating groups from an earlier version of Callback, be sure to read the note related to this activity.|
|Configuring Country and Number Validation rules||As a Callback administrator, you want the added security of blocking callbacks to certain numbers and countries. To do that, you'll configure a Country and Number Validation rule in Genesys Callback and assign it to at least one callback queue. You can test your rules before assigning them to a queue or when troubleshooting. You can also edit and delete existing rules, as required.|
|Configuring Region Affinity rules||Genesys has regional names for the locations at which there are nodes (servers with relevant applications) that manage the interactions for callback virtual queues. You use a Region Affinity rule to specify the regional nodes that you prefer to use and to control the order in which Callback attempts to connect to the available nodes. Region Affinity rules configuration is an advanced feature; you must consult with your Genesys representative before using this feature.|
|Controlling user access||You can limit user access within the Callback UI to what is appropriate for each user's role. This article describes the predefined Access Groups and Callback Roles to which you can assign users and includes information about how to restrict user access to callback information based on your lines of business. If you are migrating Roles and Access Groups from an earlier version of Callback, be sure to read the note related to this activity.|
|Genesys Multicloud CX REST APIs and tutorials for Callback||Depending on your role, you might work with the APIs that are available for Genesys Engagement Services (GES)/Callback. This article provides links to documentation and tutorials for the GES REST APIs and tells you what is required to access Callback APIs from web or mobile applications.|
|Getting started with Callback||Genesys Callback, available from the Genesys portal, provides traditional callback services, user-originated Click-To-Call scenarios, and supports the integration of Push Notifications and CAPTCHA widgets. This article includes information about where to begin if you are new to Callback and what steps are required to get started using the Callback UI.|
|Managing callbacks||The Callback tab in the Callback UI displays the list of callback records. If you have sufficient user privileges, you can create, recreate, schedule, edit or cancel callbacks on this tab. Use the Advanced Options dialog to customize the display of data.|
|Monitor callback queues||Use the Callback Queues page in the Callback UI to find information about each configured queue and to add capacity or country and number validation rules to queues.
|Provisioning Callback in Designer||Callback is provisioned with Designer. To create and configure Callback services, Designer includes a set of blocks dedicated to Callback. This article provides information about how to provision a basic callback scenario in Designer. For information about the supported callback scenarios, see Callback Scenarios. For information about provisioning the Click-To-Call-In scenario in Designer, see Provisioning the Click-to-Call-In scenario.|
|Provisioning CAPTCHA||If you have a website that includes a callback feature, then you can provision and use a CAPTCHA widget to verify that a human is requesting the callback. Currently, Callback supports integration with only one CAPTCHA widget: Google reCAPTCHA. This page describes how to enable the use of reCAPTCHA with Callback.|
|Provisioning Push Notifications||The Push Notification page in the Callback UI helps you to integrate Push Notification support into your apps. In the Callback UI, you implement Push Notifications on the Developer > Credential Management > Push Notification tab.|
|Provisioning the Click-to-Call-In scenario||This article describes how to provision Callback's Click-To-Call-In feature, which lets consumers initiate a call to your contact center directly from your mobile app.|
|Registering for access to statistics||Register your credentials to use Callback's Statistics API.|
|Troubleshooting and validating functionality||The Callback UI includes a number of troubleshooting and validation tools, available as menu options under the Developer and Tools tabs. This page describes those tools and also describes some features for which you might need to investigate the existing configuration as part of your troubleshooting effort.|
|Viewing Click-To-Call-In records||If you use the Click-To-Call-In feature with Callback, use the Call-In tab in the Callback UI to view the Click-To-Call-In records.|
Comments or questions about this documentation? Contact us for support!