Get started with the Attendant Console

Publisher

Cisco Systems

URL

https://help.webex.com/en-us/article/4xgekbb/Get-started-with-the-Attendant-Console

Published

2026-07-23

Updated

unknown

Accessed

2026-09-05

HTTP status

200

License

Cisco proprietary documentation; all rights reserved; no-redistribution; short excerpts and locators only

Source notes citing this source

• Cisco documentation read for this packet describes Webex Attendant Console provisioning only for Webex Calling multi-tenant. Treating it as a like-for-like CUAC replacement on on-prem UCM or Dedicated Instance is not supported by that documentation. inferred in context
• Webex Attendant Console lists Windows 10 or later and macOS 13 or later, with at least 4 GB RAM and 5 GB disk space. in context
• Administrators provision Webex Attendant Console in Control Hub under Services > Calling > Features > Attendant Console by assigning users. in context
• Webex Attendant Console contact sources include colleagues, favourites, resources (call queues, hunt groups, auto attendants), personal contacts, and external contacts from LDAP, BroadWorks or Cisco Unified Communications Manager. in context
• Webex Attendant Console needs its own licence, ordered in CCW as an add-on to a Webex Calling or Webex Suite order, and the user also needs a Webex Calling Professional licence. in context
• Webex Attendant Console shows subscribed queues with current waiting calls, maximum wait time and average handling time. in context
• Webex Attendant Console is a web-based tool that pairs the Webex Calling service, Webex App or a desk phone with a desktop interface for handling calls. in context
• A user needs a Webex Calling Professional licence to use Webex Attendant Console, which has its own add-on licence. in context
• Attendant Console licences are ordered through Cisco Commerce with a Flex 3 purchase order, with a new Webex Calling subscription order, or as a change order on an existing Webex Calling subscription. in context
• The Attendant Console license is an add-on ordered with a Flex-3 purchase order, with a new Webex Calling subscription order, or as a change order against an existing Webex Calling subscription. in context
• Attendant Console is enabled per user in Control Hub under the user's Calling settings at User Call Experience > Attendant Console. in context
• A user must hold a Webex Calling Professional license to access the Attendant Console. in context
• The console keeps 60 call history records in total and 20 of each type. in context
• The console's call history holds at most 60 records with at most 20 per call type and the word report occurs 0 times in the article. in context
• The console names 5 transfer actions: blind transfer attended transfer fast transfer one-click transfer and transfer to voicemail. in context
• The console describes a current presence status for a contact and names no presence values. in context
• The Attendant Console article ties no per-call action to a call waiting in a queue: retrieve occurs 3 times and reorder once and none of the 4 is about a queued call. in context
• The console shows a presence status for a person and states that phone and rich presence are not available for resources such as call queues, hunt groups, auto attendants, workspaces and virtual lines. in context
• The attendant console article does not use the words supervisor, role or barge, and its 2 uses of monitor concern which contacts a receptionist watches in their directory. in context
• The attendant console article states no busy, no-answer or failure behaviour for any transfer path; its only error language is a general operational error message. in context
• An operator cannot change agent status or unsubscribe from a queue inside the Attendant Console and must use the Webex App to stop receiving calls from a queue. in context
• The console shows 3 aggregate queue figures named Subscribed Queues Current Waiting Calls and Maximum Wait Time plus per-queue Average Handling Time and Average Waiting Time and an expandable list of a queue's current calls whose columns are not named. in context
• After the Attendant Console is purchased the Receptionist Client disappears from Control Hub and remains reachable at a hardcoded external address until the end of feature support with no loss of configuration data. in context
• Selecting the Attendant Console for an organisation without a Webex Calling Professional licence also selects that licence together with Cisco Calling Plans and Webex Go. in context
• The attendant console names 3 transfer types: blind, attended, and fast transfer, and describes fast transfer as executed through a blind or consultative transfer to a frequent destination. in context
• The console documents 3 recording modes with an administrator-gated permission and an in-call indicator, and says nothing about where a recording is stored, how long it is kept, or how it is played back. in context
• Two transfer paths sit outside the article's own enumeration: transfer to voicemail, and a one-click transfer to a contact's primary extension. field report in context
• Once an organisation holds the Attendant Console licence, the Receptionist Client options disappear from the Control Hub user call experience settings. in context

Cite this source record

APA

WarmTransfer. (2026, July 23). Get started with the Attendant Console. WarmTransfer. https://warmtransfer.net/knowledge/sources/cisco-help-4xgekbb-attendant-console

BibTeX

@misc{warmtransfer-cisco-help-4xgekbb-attendant-console,
  title  = {Get started with the Attendant Console},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/sources/cisco-help-4xgekbb-attendant-console},
  note   = {Cisco Systems, accessed 2026-09-05}
}