You are here:
Create a Workload History
A workload history aggregates all the historical channel data that you specify. When you create an intelligent forecast later, it makes predictions based on data in a workload history.
Required Editions
Example
Note Workforce Engagement is scheduled for retirement. See Workforce Engagement Retirement.
| View supported editions. |
| User Permissions Needed | |
|---|---|
| To view, create, and adjust a workload history: | Workforce Engagement Analyst |
When you create a workload history, keep these considerations in mind.
- There’s a one-to-one mapping between each forecast and its workload history.
- If Machine Learning is selected as the forecasting algorithm in your org, your workload history must be at least three times as long as the forecast that you want to create. For example, use a workload history that’s 60 weeks to create a 20-week forecast.
- The workload history creation flow is optimized for customers who use Omni-Channel queue-based routing. Customers who don't use Omni-Channel queue-based routing follow a different set of steps.
For Omni-Channel queue-based routing workflows:
- Click App Launcher | Intelligent Forecasts | New.
- Select Omni Workload History.
- Select a queue from the Queue Name dropdown menu.
- In the Dashboard Filter Name column, enter a name for your queue as you’d like it to appear in the filter dropdown menu.
- Click + Add Queue Mapping to map additional queues to dashboard filter names. If you map more than one queue to a dashboard filter name, the dashboard filter dropdown menu lets you filter by your various support queues.
- Click Next.
- Select to use all history, or filter the data you’re bringing in.
- Select a service territory. This service territory sets the time zone in data views for this workload history and its related intelligent forecast and capacity plan.
- Select the option to add to a workload history or to create a new one. You can add to an existing workload history if it hasn't been used in an intelligent forecast.
- Click Next.
- Enter an end date and duration for your workload history, and name it. The maximum duration is 260 weeks or five years.
- Click Save, and click Done.
- Check the Status column in the Intelligent Forecasts list view to see when your workload history’s aggregation is complete.
For customers who don't use Omni-Channel queue-based routing:
- Click App Launcher | Intelligent Forecasts | New.
- Select the Select my own channel radio button to create a workload history from your available channels.
- Select a channel to view history for. Each workload history is based on one channel.
- Select to use all history, or filter the data you’re bringing in.
- Select a service territory. This service territory sets the time zone in data views for this workload history and its related intelligent forecast and capacity plan.
- Tell your channel if it’s filterable by Skill, Region, or Custom. Map these filter names to the custom fields you or your admin created in the configuration pre-work.
- If you want to include average handle time data, check the Calculate Average Handle Time box.
- Click Next.
- Click each object, Region, Skill, and Custom, and then map Picklist Value to Dashboard Filter Value. The total number of slices across Region, Skill, and Custom can’t exceed 198.
- Select the option to add to a workload history or create a new one. You can add to an existing workload history if it hasn't been used in an intelligent forecast.
- Click Next.
- Enter an end date and duration for your workload history, and name it. The maximum duration is 260 weeks or 5 years.
- Save your changes and click Done.
- Check the Status column in the Intelligent Forecasts list view to see when your workload history’s aggregation is complete.
- Adjust Your Workload History Data
Want to clean up your workload history to produce a more accurate intelligent forecast? Change, replace, or remove workload history data with an adjustment. - Export a Workload History
Export your workload history as a CSV file.
Did this article solve your issue?
Let us know so we can improve!

