17 · Ecosystem
A queue without a staffing model is a guess. Teams user reports will not staff next Tuesday.
Workforce management consumes offered, answered, abandoned, and handle time from the contact center or the queue, in the same interval the schedule uses. Erlang C is a teaching model of how many people must be available. Shrinkage is the fraction of paid time that is not available. Roster is larger than the Erlang number. Occupancy is handle time over handle time plus ready time. Very high occupancy burns people and raises abandons.
Troubleshooting: if WFM says you were overstaffed while the queue overflowed, check whether overflow removed calls from this queue’s offered count, whether the interval was a day instead of 30 minutes, and whether handle time forgot after-call work. Agents set to available in Teams while still writing a case will poison both tools.
WFM eats queue intervals. Erlang C plus shrinkage is the teaching math. Do not feed it from a user’s call history.
I staff from queue intervals, Erlang C, and an explicit shrinkage. I do not staff from Call Analytics.
If it fails: The forecast is ten times too high because the interval was a whole day.
Which description of Shrinkage is accurate?
The fraction of paid time that is not available for contacts: leave, training, meetings, breaks. Erlang C tells you how many people must be on the phone. Shrinkage tells you how many to roster. Source: https://learn.microsoft.com/en-us/dynamics365/contact-center/ accessed 2026-10-14.
A colleague reports: The schedule staffs the Erlang number and half the team is in training. Where do you start?
The schedule staffs the Erlang number and half the team is in training. Publish the assumption. A 30 percent guess should be labeled as a guess. Source: https://learn.microsoft.com/en-us/dynamics365/contact-center/ accessed 2026-10-14.
Which description of Occupancy is accurate?
Handle time divided by handle time plus available time. High occupancy feels efficient and burns people out. WFM and quality fight here. Source: https://learn.microsoft.com/en-us/dynamics365/contact-center/ accessed 2026-10-14.
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.
The forecast is ten times too high because the interval was a whole day.
Cisco CUBE is one of the SBC families named in this lab’s certification lesson. A certified release can be the Direct Routing SBC between Unified CM and Teams.
The tenant still needs a verified domain on the SBC FQDN, and the user still needs Teams Phone. The studio translator does not open a live AXL session. Confirm the current certified release before you build.
Teams Phone and Webex Calling are separate clouds. This lab does not describe a feature that registers a Webex Calling user into a Teams tenant.
A number move is usually a carrier port, a certified SBC, or a meetings interop product. Confirm before relying.
Unified CCE stays the ACD until you migrate it. Microsoft’s contact-center articles name Connect, Extend, and Unify. They do not name a UCCE connector in the notes this lab cites.
Voice into Teams is still Direct Routing or Operator Connect. The routing script stays on the contact-center product you bought. Confirm the vendor’s current model. Source: https://learn.microsoft.com/en-us/microsoftteams/teams-contact-center.
Copilot Studio, Azure Communication Services, and Graph are later tracks in this lab. Treat any uncited limit as confirm before relying.
Opened 2026-10. A row marked confirm did not open. Wikipedia is background. The Teams blog row is the community index.
