Campaign settings

When creating a campaign Collection of scheduling periods in WFM, which are defined time periods where specific employees target specific workloads., you need to complete fields that define the campaign.

Field	Description
Name	Defines the name of the campaign.
Description	Optional: Describes the campaign.
Time Zone	Sets the time zone of the campaign.
Week Start Day	Specifies the day of the week on which the campaign starts its work week.
Periodicity	Specifies the time period of the scheduling periods defined for the campaign: Weekly: Campaign includes weekly scheduling periods. Monthly: Campaign includes monthly scheduling Optional licensed feature in WFM that allows generating schedules that cover a time period from the first to the last day of a calendar month, instead of one or multiple weeks. periods.
Month Start Day
NOTE: The Periodicity and Month Start Day fields only appear if the Monthly scheduling feature is enabled by activating the Monthly Forecast Feature in WFM used to estimate the required resources for a specific scheduling period based on historical data. The data in a forecast includes interaction and work volume, and Average Handling Time (AHT). and Rules license.
Day Boundary	Specifies the time at which one day is considered to end and the next to begin. Day boundaries that are set at 30 mins past the hour are not always compatible when working with Scheduling Periods that overlap DST periods. We recommend you use day boundaries that are set on the hour.
Distributed Campaign	Indicates whether a campaign is a distributed campaign Type of campaign in WFM where workload is allocated among the sites regardless of employee availability. A pre-determined percentage of interactions is routed to each site in each interval.. Distributed campaigns are campaigns that include distributed work queues. Distributed work queues are used in multi-site scheduling, where workload is allocated among the sites, regardless of employee availability. A predetermined percentage of interactions is routed to each site in each interval.

The calendar uses Time Zone and Day Boundary to determine to which day shifts belong. When user and campaign time zones are different, shifts appear to belong to the wrong day when viewing them in user time zone.