Because only Do not disturb, On a call and Presenting are documented as mappable, Teams states such as Busy, In a meeting or Away probably do not move the agent out of Available, so routing can continue while the agent shows those states in Teams.
inferred · Checked 2026-10-02
- Vendor
- Cisco
- Product
- Webex Contact Center
- Subsystem
- presence synchronization
- Deployment
- multi-tenant
- Region
- not restricted
- Release range
- current as of 2026-10-02
- Status
- inferred
- Checked
- 2026-10-02
Sources
- Integrate Webex Contact Center with Microsoft Teams — Cisco Systems, Inc. (Webex Help Center) · tier 2 current vendor documentation · Synchronize Microsoft Teams states with Webex Contact Center idle codes
Cite this note
APA
WarmTransfer. (2026, October 2). Troubleshooting Microsoft Teams presence sync with Webex Contact Center: source note wxcc-teams-presence-troubleshooting-inf-unmapped-states-route. WarmTransfer. https://warmtransfer.net/knowledge/claims/wxcc-teams-presence-troubleshooting-inf-unmapped-states-route
BibTeX
@misc{warmtransfer-claim-wxcc-teams-presence-troubleshooting-inf-unmapped-states-route,
title = {Troubleshooting Microsoft Teams presence sync with Webex Contact Center: source note wxcc-teams-presence-troubleshooting-inf-unmapped-states-route},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/wxcc-teams-presence-troubleshooting-inf-unmapped-states-route},
note = {Source note wxcc-teams-presence-troubleshooting-inf-unmapped-states-route, checked 2026-10-02}
}