Forecast, capacity, and schedule

Learn it in 5 minutes

The forecasting overview says a forecast estimates volume and average handle time by channel and queue. Volume excludes conversations that AI agents handle with no representative joining. Forecasting is the first stage. Capacity planning uses the default forecast snapshot to calculate staffing requirements. Scheduling turns those requirements into shifts.

A short-term scenario is 15-minute intervals for a horizon of up to six weeks, which the page also states as 42 days, using a linear trend on internal or external data. A long-term scenario is daily, for up to three years, stated as 1,096 days. Weighted average is marked preview, uses external data, and refreshes manually. The page says not to use the feature for employment decisions. It also says forecasts might not account for unexpected trends. This room does not copy a shrinkage percentage. The Erlang calculator elsewhere in this campus stays a teaching model.

Forecasting estimates volume and average handle time. Short-term is 15-minute intervals up to 42 days. Long-term is daily, up to 1,096 days.

Room HTML

Visual

SVGPNGHTML

Worked example

Forecast volume and handle time, then capacity, then shifts. The short-term horizon on the page is up to 42 days.

1. Forecast Volume and AHT
2. Capacity Default snapshot
3. Schedule Shifts
4. Limit Not an employment decision

If it fails: A daily three-year scenario is used to staff a 15-minute interval this afternoon.

Checklist HTML

Quiz

Flashcards

Ecosystem

Glossary

• Least active assignment The assignment-methods page says least active is available for voice and messaging only, and is the default selection when you create a voice or messaging queue. Config: The page says the last-capacity-release data is in msdyn_agentchannelstate. It also says not to use the feature for employment decisions. Fault: Least active is promised on a record queue.
• Quality evaluation plan The quality and coaching page, which applies to Dynamics 365 Contact Center only, says an evaluation plan sets the criteria, the conversations, the timing, and the actions. Config: The page names the Omnichannel Administrator role, plus consumption-based billing and capacity. It says not to use the feature for employment decisions. Fault: A plan is activated before any indicator exists in the quality library.
• Quality guardrail On the quality and coaching page, a guardrail defines a required or prohibited behavior. Guardrails are evaluated for violations rather than assigned numeric scores, and each has a priority. Config: Set priority and optional nudge text, then activate the guardrail before you add it to a plan. Fault: A prohibited behavior is given a numeric score because the indicator form was copied.
• Short-term forecast The forecasting overview says a short-term scenario predicts volume and average handle time in 15-minute intervals for a horizon of up to six weeks (42 days), using a linear trend on internal or external data. Config: The same page says a long-term scenario is daily, up to three years (1,096 days). Weighted average is marked preview. Fault: A six-week forecast is read as a daily three-year plan.

Sister technologies

Around the call: compliance recording, workforce management, emergency location, analytics, CRM screen pop, and an agent with a human escape. Each one has its own failure.

Config and troubleshooting

A daily three-year scenario is used to staff a 15-minute interval this afternoon.

Cross-platform bridges

Future hooks

Copilot Studio, Azure Communication Services, and Graph are later tracks in this lab. Treat any uncited limit as confirm before relying.

BridgesEcosystem