These are the prerequisites for enabling Intraday OT/VTO features. During the beta, Aspect will verify the items marked “Aspect” in the Who Verifies (For Beta Only) column of the internal tables below on the customer’s behalf.

Amazon Connect WFM Customers: Intraday Pre-Requisites

• Aspect Public Cloud WFM in use with Amazon Connect as the ACD
• WFM configured and operational with Amazon Connect, generating the required IDP metrics (e.g., Net Staffing)
• WFM integrated with Amazon Connect and receiving the required real-time data
• WFM integrated with Amazon Connect and receiving the required historical data
• WFX deployed
• WFX regular user login for each participant
• WFX Admin/Agent login available for testing the admin/agent portion of the experience
• Amazon Connect API access configuration for the Intraday Automation feature completed using the steps provided by Aspect
• Required Amazon Connect access parameters (ARN and unique identifier(s)) for the Intraday Automation feature provided to Aspect

Items 8–9 are specific to the Intraday Automation feature.

Non-Amazon Connect ACD/CCaaS WFM Customers: Intraday Pre-Requisites

• Aspect Public Cloud WFM in use
• WFM configured and operational with the existing ACD/CCaaS platform
• WFM able to generate the required IDP metrics
• WFX deployed
• WFX regular user login for each participant
• WFX Admin/Agent login available for testing the admin/agent portion of the experience

The tables in the document reflect the planned Aspect Cloud Workforce (the New Experience) changes for August 2026.

In the tables, the Feature Audience column designates the availability for that feature. A designation of All Customers indicates that all Aspect customers will receive the feature. A designation of Selected Customers indicates that only specific customers are receiving the feature. Other designations indicate specific component distribution for the feature.

The Enablement Method column in the tables describes the method by which the designated feature will be deployed. In many cases, features are automatically delivered. In some cases, customers will engage with the Aspect account team to enable the feature in their Aspect platform. Documentation related to the feature, if available, is found in the Documentation column. In some limited cases, documentation may follow the feature being released in as much as two weeks.

Note: This is a living document and subject to change. Customer features may be added or removed prior to official rollout.

To view the complete document, click the PDF attachment.

The tables in the document reflect the planned Aspect Developer Portal changes for August 2026.

In the tables, the Feature Audience column designates the availability for that feature. A designation of All Customers indicates that all Aspect customers will receive the feature. A designation of Selected Customers indicates that only specific customers are receiving the feature. Other designations indicate specific component distribution for the feature.

The Enablement Method column in the tables describes the method by which the designated feature will be deployed. In many cases, features are automatically delivered. In some cases, customers will engage with the Aspect account team to enable the feature in their Aspect platform. Documentation related to the feature, if available, is found in the Documentation column. In some limited cases, documentation may follow the feature being released by as much as two weeks.

Note: This is a living document and subject to change. Customer features may be added or removed prior to official rollout.

To view the complete document, click the PDF attachment.

1. A stop on agents being able to work 7 consecutive days.

2. A forced minimum 12 hour gap between shifts.

Has anyone else had similar restrictions and how did you go about implementing?

This document contains detailed instructions on how to install and configure Aspect Workforce™, Aspect Quality™, and Aspect Performance™ with Aspect Workforce Engagement Management™.

For information about Training, Technical Support, commenting on the documentation, and a list of additional documentation, see the appropriate product Release Notes document on the Aspect documentation portal.

To view the complete guide, click the PDF attachment.

Audience

The Aspect Workforce Engagement Management Installation Guide is for IT personnel and Aspect Administrators who set up the system. Contact center managers may also want to review this manual to obtain familiarity with what is involved in the system installation.

Specifically, this guide is intended for use by anyone who participates in the installation and configuration of Aspect Workforce Engagement Management™, Aspect Workforce™, Aspect Performance™, and Aspect Quality™.

Knowledge of third-party applications including Microsoft Windows Server and Microsoft Internet Information Services (IIS) is a prerequisite for installation and deployment.

Organization of this Guide

This guide includes the following sections with corresponding beginning page numbers:

• (9) Chapter 1, Overview - provides information on what prerequisites need to be performed prior to installing and configuring the software.
• (14) Chapter 2, Pre-Installation Tasks - provides pre-installation tasks that you must perform prior to installing and configuring Aspect Workforce Engagement Management.
• (18) Chapter 3, Installing Aspect Workforce Engagement Management - provides procedures on how to install and configure Aspect Workforce Engagement Management.
• (24) Chapter 4, Configure Workforce Engagement Management - provides information on how to configure Workforce Engagement Management, once you have the components installed.
• (35) Chapter 5, Configure Aspect Workforce - provides procedures on how to install and configure Aspect Workforce with Aspect Workforce Engagement Management.
• (45) Chapter 6, Configure Aspect Quality - provides procedures on how to install and configure Aspect Quality with Aspect Workforce Engagement Management.
• (77) Chapter 7, Configure Aspect Performance - provides procedures on how to install and configure Aspect Performance with Aspect Workforce Engagement Management.
• (81) Chapter 8, Verifying the Installation - provides procedures on how to verify that the installation of Aspect Quality, Aspect Performance, and Workforce Management are properly installed and configured with Workforce Engagement Management.
• (85) Chapter 9, Dashboard Configuration - provides information on how to configure a dashboard in Workforce Engagement Management if you prefer not to use the default dashboard.
• (94) Appendix A, Troubleshooting - provides troubleshooting guide for issues related to Aspect Workforce, Aspect Quality, and Aspect Performance, based on their integration with Aspect Workforce Engagement Management.
• (98) Appendix B, Notes on the IIS Role Services for Windows - contains a table that you can use to identify which IIS Role Services you can disable when you are using Server Manager to configure role services for IIS.
• (101) Appendix C, Security and Authentication - contains information on how to configure authentication with Workforce Engagement Management and Workforce, Quality, and Performance.

The guide is organized into sections based on user roles and common tasks, with expandable toggles that allow you to quickly navigate to the specific information you need.

Whether you're registering your account for the first time, managing user invitations as an admin, or adjusting your personal settings, you'll find clear guidance throughout this documentation.

Review the audience and organization sections below for more details.

To view the complete guide, click the PDF attachment.

Audience

This guide is designed for Aspect Cloud Workforce (the New Experience) users, including both administrators and employees. It provides comprehensive instructions for getting started, managing accounts, and utilizing key features of the platform.

Organization of this Guide

This guide covers an overview of Aspect Workforce, the tasks involved in using it, and how the user interface works, configuration and administration tasks, forecasting, scheduling, and tracking.

The guide includes the following sections:

• Introduction
• Admin Management
• Employee Schedule Management
• Notification Management
• FAQ
• Troubleshooting

The guide begins with an Introduction section covering account registration, login procedures, and an overview of the portal's key features. It then provides dedicated sections on Apps (creating and managing applications with credentials), the API Catalog (exploring available APIs and their documentation), Integrations (HRIS Data Connect), and Usage (monitoring API activity and performance).

Whether you're a developer integrating workforce data for the first time or an admin managing multiple applications, this guide provides step-by-step instructions tailored to your role and objectives.

Review the audience and organization sections below for more details.

To view the complete guide, click the PDF attachment.

Audience

This guide is designed to help Aspect Developer Portal users quickly find the information they need to get started and make the most of the portal.

Organization of this Guide

The guide includes the following sections:

• Introduction
• Apps
• API Catalog
• Integrations
• Usage
• FAQ
• Contact Support

I'm thinking about creating a set of 'no selection' trial schedules to include in the bid and making that the top selection in the bid. That way, if an agent doesn't complete the bid, they don't occupy one of the other schedules where someone has actually selected their rankings. I would have enough of these 'no selection' schedules to potentially allow everyone in the bid to be awarded one.

Has anyone tried something like this before? Any words of caution in such an approach? I would share that information with them when letting them know the bid is open and to indicate that when they make their selection the 'no selection' option should be their lowest ranked (highest numerical) option.