Schedules

From Genesys Documentation
Revision as of 02:34, July 25, 2020 by WikiSysop (talk | contribs) (Text replacement - "\|Platform=([^\|]*)GenesysEngage-onpremises([\|]*)" to "|Platform=$1GenesysEngage-cloud$2")
Jump to: navigation, search
This topic is part of the manual Outbound (CX Contact) CX Contact Help for version Current of Outbound (CX Contact).

Learn about Schedules.

CX Contact (CXC) Schedules is a powerful tool that enables you to execute one or more Campaign Groups automatically and periodically using a predefined schedule. Each Schedule can include one or more Campaign Groups that are not necessarily associated with the same campaign, group and so on. Multiple schedules can be configured and active in the same Outbound Contact Server (OCS) instance.

Schedules simplifies configuration by enabling you to define the activation and deactivation time for all the Campaign Groups that operate frequently and have recurring usage (for example, every weekday at 8 am).

While numerous Campaign Groups can be configured to be active/inactive at the same time, each Campaign Group within the schedule can be individually configured for activation/deactivation.

Important
In the future CX Contact will include Sequence Campaign Groups that support Time in State and Statistical Value. With these conditions you will be able to define that when one campaign group achieves a 90% penetration status Campaign Group 2 begins.

Key Features

  • Schedule a Campaign Group to start/finish.
  • Schedule a Campaign Group to run for a specified period of time or until a specific statistic is achieved.
  • Sequence Campaign Groups. For example, it can be defined that when one campaign group achieves a 90% penetration status Campaign Group 2 begins.

Work with Schedules

Important
You can access and customize near-real time reporting data about Schedules from the Schedules Dashboard.

Click the Schedules menu to open the Schedules page. The following image depicts a typical Schedules page.

CXC Schedules.png

Related Topics

Comments or questions about this documentation? Contact us for support!