07 · Attendants and queues

Numbers on voice apps

The number’s owner decides whether the company keeps it when a human leaves.

Room HTMLAll downloads

Learn it in 5 minutes

Put service numbers on resource accounts. Do not put the main number on a receptionist’s user object. Caller ID for the queue should be chosen, not inherited from whoever built the queue.

How you get the number depends on the connectivity option: Microsoft inventory, the Operator Connect carrier, or the Direct Routing carrier. Porting is a carrier project with a date, not a PowerShell metaphor.

Assign the company number to a resource account, and set caller ID on purpose.

Room HTML

Visual

Call queue routingCall queueLongest idleAgent 1Agent 2Agent 3Agent 4Timeout to overflow
Longest idle distribution for Numbers on voice apps. Overflow is a configured target.
Who should own the main numberResource account · YesA user · No
The resource account, not a person. Counts in this drawing are teaching order, not customers.

SVGPNGHTML

Worked example

Service numbers sit on resource accounts. Caller ID is a choice.

  1. Inventory Where the number lives
  2. Assign Resource account
  3. Identity Caller ID
  4. Port Only if you must

If it fails: The receptionist leaves and the main number is released with their user.

Checklist HTML

Quiz

A colleague reports: The schedule says five agents and three have opted out. Where do you start?

Which description of Callback is accurate?

A colleague reports: The option is on and every callback fails. Where do you start?

Flashcards

Ecosystem

Glossary

  • Auto attendant A voice app that answers, plays a greeting, and routes by schedule, menu, directory, or operator. Config: Create the attendant, attach a licensed resource account, then assign a number only if the PSTN must reach it. Fault: The menu option points at a queue that has no agents and no overflow.
  • Call queue A voice app that holds callers and offers them to agents by attendant, serial, round robin, or longest idle routing. Config: Set timeout and overflow before you publish the number. Fault: The timeout is 3 seconds and callers always overflow.
  • Conference mode A queue behavior where the caller stays in the conference while agents are tried, so the transfer is faster and the greeting is not replayed the same way. Config: Test both modes with a real agent client before you argue about delay. Fault: Callers hear silence while the queue hunts, and someone disables the queue.
  • Overflow Where the call goes when the queue is full or the timeout expires. It can be a person, another voice app, voicemail, or an external number. Config: Name the overflow in the design, then test it by making every agent busy. Fault: Overflow to a mobile fails and the queue itself is blamed.

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

The receptionist leaves and the main number is released with their user.

Cross-platform bridges

CUCM

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.

Webex

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.

UCCE

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.

Future hooks

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

BridgesEcosystem

Sources and go deeper

Opened 2026-10. A row marked confirm did not open. Wikipedia is background. The Teams blog row is the community index.

sources.json