Limits, system behavior, and operational considerations

AI-generated summary

Genesys Cloud enforces specific limits and operational constraints for Opportunities to maintain system performance and prevent unintended scheduling outcomes. The system permits up to 10,000 invitations per creation action, with individual Opportunities supporting a maximum of 2,000 invitations. Per-agent enrollment is limited to eight opportunities within a single hour, while each business unit can process up to 24,000 enrollments per hour. Schedulers can create up to 25 opportunities per hour per business unit, with each split Opportunity counting toward this limit. Once approved, Opportunities are treated as external activities on agent schedules, preventing modification by standard rescheduling processes and restricting certain scheduling workflows. Shift trades are prohibited for shifts containing approved opportunity activities to prevent accidental removal or transfer of assigned time. Rescheduling actions may be blocked when an opportunity activity exists on a shift, even if the reschedule window does not overlap the opportunity timeframe. Opportunity activities must be managed exclusively through the Enrollments tab rather than the Schedule Editor, as direct removal breaks the link between the opportunity and scheduled activity, creating reporting inconsistencies. To properly remove an approved opportunity, schedulers must change the enrollment status from Approved to Denied in the Enrollments tab, which automatically removes the associated on-queue activity. The system manages opportunity removal through specific behavioral rules depending on placement within shifts: stand-alone opportunities are cleared without backfill, opportunities at shift boundaries trigger automatic shift shortening, and opportunities positioned between two activities are replaced with Unavailable time to prevent unintended split shifts. When removing one opportunity from multiple consecutive blocks, the system replaces only the removed block with Unavailable if positioned between activities, preserving overall schedule structure and reducing fragmentation. Agents can view opportunities only when a published schedule exists in their business unit for the relevant period. The system may briefly display enrollment requests as Pending during processing before updating to Approved status, even with auto-approval enabled. Manual opportunity closure by schedulers marks pending enrollments as Denied while maintaining Approved enrollments, and immediately changes opportunity status to Closed, providing controlled enrollment conclusion when business requirements change. Operational best practices require schedulers to monitor the Demand column during the Open stage for early over-subscription identification, establish enrollment deadlines sufficiently before start times for manual review, implement clearly defined on-queue activity codes for accurate reporting, and avoid direct removal of opportunity activities through the Schedule Editor.

Understand the limits and system behavior that affect how opportunities work in practice. This section highlights key rules, constraints, and considerations to help you use opportunities effectively and avoid unexpected outcomes. The system allows up to 12,000 invitations per creation action. Each opportunity can include up to 2,000 invitations.

System and enrollment limitsClick to expand

Per-agent enrollment limit:

An individual agent can enroll in up to eight opportunities within the same hour. For example, between 09:00 and 10:00. This limit applies to both automatic and manual approval. The system enforces this limit to prevent excessive enrollment within short timeframes.

Business unit enrollment throughput limit:

Each business unit can process up to 24,000 enrollments per hour. This limit represents the total number of enrollment actions processed across the Business Unit within a one-hour period (for example, between 09:00 and 10:00). It includes both manual and automatic approvals. The system enforces this throughput limit to protect performance during high-demand enrollment events.

Opportunity creation limit:

Schedulers can create up to 25 opportunities per business unit within the same hour period (for example, between 09:00 and 10:00). If you enable Split into multiple Opportunities option, the system counts each resulting opportunity toward this limit.

Schedule interaction and activity behaviorClick to expand

Opportunities treated as external activities

When the system approves an opportunity, it adds the selected on-queue activity to the schedule and treats it as an external activity.

As a result:

Rescheduling processes do not modify opportunity activities.
Certain scheduling workflows can be restricted if an opportunity exists on the shift.

This approach ensures that approved opportunities remain stable once assigned.

Shift trades

If a shift includes an approved opportunity activity, the system does not allow shift trades for that shift. This restriction prevents the accidental removal or transfer of approved opportunity time.

Rescheduling behavior

If a shift includes an opportunity activity:

The system can restrict rescheduling actions.
The system does not automatically move the opportunity activity.

Even if the reschedule window does not overlap the opportunity timeframe, the system can still block rescheduling due to the presence of an external activity.

Do not remove opportunity activities in the schedule editor

Manage opportunities through the Enrollments tab. Do not remove the opportunity activity directly in the Schedule Editor. This action:

Does not mark the enrollment as Denied.
Breaks the link between the opportunity and the scheduled activity.
Can create inconsistencies in reporting and enrollment records.

To remove an approved opportunity correctly, change the enrollment status from Approved to Denied in the Enrollments tab.

Remove an approved opportunity from the schedule

When a scheduler changes an approved opportunity to Denied, the system removes the associated on-queue activity from the agent’s schedule. How the schedule adjusts depends on the opportunity’s position within the shift.

Opportunity between two activities

If the opportunity sits between two scheduled activities, for example:

Activity A
Opportunity (30 minutes)
Activity B

When the system removes the opportunity, it fills the gap with Unavailable time.

For example:

09:00–09:30 Activity A.
09:30–10:00 Opportunity.
10:00–10:30 Activity B.

After removal:

09:00–09:30 Activity A.
09:30–10:00 Unavailable.
10:00–10:30 Activity B.

This prevents unintended split shifts and maintains schedule continuity.

Opportunity at the start or end of a shift

The opportunity is at the beginning or end of a shift:

The system shortens the shift when it removes the opportunity.
- If the opportunity exists as a stand-alone block outside a shift:
  - Removing it clears the time from the schedule.
  - No backfill occurs.
- If the opportunity is at the beginning or end of a shift:
  - The system shortens the shift when it removes the opportunity.
  - The system does not backfill the time with Unavailable.

Multiple consecutive opportunities

If an agent has multiple consecutive opportunities and the system removes one in the middle:

The system replaces only the removed block with Unavailable (if it is between two activities).
The system does not change the remaining opportunity blocks.

This behavior reduces fragmentation while preserving the overall schedule structure.

Visibility and eligibility rulesClick to expand

Enrollment behavior and space managementClick to expand

Temporary Pending status with auto-approval

When auto-approval is enabled:

The system automatically processes eligible agent submissions
Requests may briefly appear as Pending, but typically remain in a Processing state while the system evaluates and completes the request
Once processing completes, the system updates the status to Approved or Denied, depending on eligibility and available capacity
The system continues processing requests until all spaces are filled

This behavior is expected.

Manual/automatic closure behavior

When a scheduler closes an opportunity manually or automatically:

Approved enrollments remain Approved.
The system marks pending enrollments as Denied.
The system immediately changes the opportunity status to Closed.

This approach provides a controlled way to conclude enrollment activity when business needs change.

Operational considerations

Schedulers must:

Monitor the Demand column during the Open stage to identify over-subscription early.
Set enrollment deadlines early enough to allow manual review before the start time.
Use clearly defined on-queue activity codes for accurate reporting.
Avoid removing opportunity activities directly in the Schedule Editor.

Work plan hours and opportunity impact

The system treats approved opportunities as scheduled time once it adds them to an agent’s schedule.

Opportunities are not subject to work plan limits at the time of request or approval. An agent can request and receive approval for an opportunity even if it causes them to exceed minimum or maximum hour thresholds. However, once the system adds an approved opportunity to the schedule, it includes those hours in standard scheduling and planning calculations.

Planning period hour balancing

When you use work plans with minimum or maximum hours per day, week, or planning period, the system includes approved opportunity hours in those totals, just like any other scheduled activity.

When generating a schedule, the system considers:

All previously scheduled hours in the planning period, including approved opportunities.
The total required or allowed hours defined by the work plan.

Example:

If an agent’s work plan requires 80 hours over a two-week planning period and Week 1 already includes 50 scheduled hours (including approved opportunities), the system schedules approximately 30 additional hours in Week 2 to meet the total.

This approach ensures accurate hour calculations across the entire planning period, regardless of whether the hours come from base scheduling or opportunities.

Planning guidance

Schedulers should publish the next schedule period before approving opportunities. This ensures that the base schedule meets work plan requirements without including opportunity time. You can then add opportunities after publishing. When you use planning periods with minimum or maximum hour targets, follow this recommendation:

Generate and publish the next schedule before you approve or publish opportunities for the current period.

.This approach helps ensure that:

The system completes planning period calculations first.
Opportunity time does not reduce hours allocated in a future schedule generation.
Work plan balancing remains predictable across the full planning period.

Schedule editor warnings

Because the system treats approved opportunity hours as standard scheduled time, it includes them in Schedule Editor validations. As a result, the system may show warnings, such as paid time violations.

These warnings can appear after opportunities are approved, even if the original schedule did not trigger them. This behavior is expected because the opportunity time contributes to total scheduled hours.

Opportunities and work plan limits

Opportunities:

Do not prevent agents from exceeding work plan limits at the time of request.
Do not modify or reconfigure an agent’s work plan.
Become standard scheduled hours once the system approves them.

The system performs hour-limit validation during standard schedule calculations and warnings, not during the opportunity enrollment process.

[NEXT] Was this article helpful?

Get user feedback about articles.