# The Webex Calling Attendant Console

Canonical: https://warmtransfer.net/knowledge/webex-calling-attendant-console

Last verified: 2026-09-15

The Webex Calling Attendant Console names 5 transfer actions: blind transfer, attended transfer, fast transfer, one-click transfer, and transfer to voicemail[^3]. The console also provides call queue monitoring, contact directory presence indicators, administrator-gated recording controls, and an interface-capped call history[^10][^6][^14][^1].

## Call handling and transfers

The console enumerates 3 transfer types consisting of blind, attended, and fast transfer, describing fast transfer as executed through a blind or consultative transfer to a frequent destination[^13]. In the field, 2 transfer paths sit outside that initial enumeration: transfer to voicemail, and a one-click transfer to a contact's primary extension[^15]. Across all transfer actions, the console identifies 5 named options: blind transfer, attended transfer, fast transfer, one-click transfer, and transfer to voicemail[^3]. The attendant console documentation states no busy, no-answer, or failure behaviour for any transfer path, providing only a general operational error message[^8].

For call history, the console keeps at most 60 call history records in total and at most 20 of each call type[^1][^2]. The word report occurs 0 times in the attendant console documentation[^2]. 

The console documents 3 recording modes with an administrator-gated permission and an in-call indicator[^14]. The console documentation says nothing about where a recording is stored, how long it is kept, or how it is played back[^14].

## Directory and presence

The console shows a presence status for a person[^6]. Phone and rich presence are not available for resources such as call queues, hunt groups, auto attendants, workspaces, and virtual lines[^6]. The console describes a current presence status for a contact but names no presence values[^4]. 

The console documentation does not use the words supervisor, role, or barge[^7]. Its 2 uses of the word monitor concern which contacts a receptionist watches in their directory[^7].

## Call queue monitoring

The console queue panel shows 3 aggregate queue figures named Subscribed Queues, Current Waiting Calls, and Maximum Wait Time, alongside per-queue Average Handling Time and Average Waiting Time[^10]. The queue panel also includes an expandable list of a queue's current calls whose columns are not named[^10].

The console ties no per-call action to a call waiting in a queue[^5]. In the console documentation, retrieve occurs 3 times and reorder once and none of the 4 is about a queued call[^5]. An operator cannot change agent status or unsubscribe from a queue inside the console and must use the Webex App to stop receiving calls from a queue[^9].

## Licensing and transitions

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[^12]. 

After the Attendant Console is purchased, the Receptionist Client disappears from Control Hub[^11]. It remains reachable at a hardcoded external address until the end of feature support, with no loss of configuration data[^11].

## See also

- See also [The Webex Calling Receptionist Client](https://warmtransfer.net/knowledge/webex-calling-receptionist-client).
- See also [What a transferred call leaves behind across Cisco products](https://warmtransfer.net/knowledge/webex-transfer-artefacts).
- See also [Webex Calling Call Queue as a product](https://warmtransfer.net/knowledge/webex-calling-call-queue).
- See also [Webex Calling license types and entitlements](https://warmtransfer.net/knowledge/webex-calling-licensing).

## Applicability

Applies to: Cisco Webex Calling. Sources checked 2026-09-15.

## What remains uncertain

What happens when a console transfer is not answered is not covered by the sources below. Where a console recording goes and how long it is kept are not covered by the sources below. The presence values a console operator sees are not covered by the sources below. What the console shows about an individual call waiting in a queue is not covered by the sources below.

## Sources

[^1]: The console keeps 60 call history records in total and 20 of each type. Source: [Get started with the Attendant Console](https://help.webex.com/en-us/article/4xgekbb/Get-started-with-the-Attendant-Console), Get started with the Attendant Console, call history. Checked 2026-09-05.
[^2]: 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. Source: [Get started with the Attendant Console](https://help.webex.com/en-us/article/4xgekbb/Get-started-with-the-Attendant-Console), Get started with the Attendant Console, call history panel, counted against the rendered article. Checked 2026-09-15.
[^3]: The console names 5 transfer actions: blind transfer attended transfer fast transfer one-click transfer and transfer to voicemail. Source: [Get started with the Attendant Console](https://help.webex.com/en-us/article/4xgekbb/Get-started-with-the-Attendant-Console), Get started with the Attendant Console, transfer actions. Checked 2026-09-15.
[^4]: The console describes a current presence status for a contact and names no presence values. Source: [Get started with the Attendant Console](https://help.webex.com/en-us/article/4xgekbb/Get-started-with-the-Attendant-Console), Get started with the Attendant Console, contacts. Checked 2026-09-05.
[^5]: 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. Source: [Get started with the Attendant Console](https://help.webex.com/en-us/article/4xgekbb/Get-started-with-the-Attendant-Console), Get started with the Attendant Console, counted against the rendered article. Checked 2026-09-15.
[^6]: 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. Source: [Get started with the Attendant Console](https://help.webex.com/en-us/article/4xgekbb/Get-started-with-the-Attendant-Console), Get started with the Attendant Console, contacts and resources. Checked 2026-09-05.
[^7]: 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. Source: [Get started with the Attendant Console](https://help.webex.com/en-us/article/4xgekbb/Get-started-with-the-Attendant-Console), Get started with the Attendant Console, counted against the rendered article. Checked 2026-09-05.
[^8]: 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. Source: [Get started with the Attendant Console](https://help.webex.com/en-us/article/4xgekbb/Get-started-with-the-Attendant-Console), Get started with the Attendant Console, counted against the rendered article. Checked 2026-09-05.
[^9]: 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. Source: [Get started with the Attendant Console](https://help.webex.com/en-us/article/4xgekbb/Get-started-with-the-Attendant-Console), Get started with the Attendant Console, queue subscription. Checked 2026-09-15.
[^10]: 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. Source: [Get started with the Attendant Console](https://help.webex.com/en-us/article/4xgekbb/Get-started-with-the-Attendant-Console), Get started with the Attendant Console, queue panel. Checked 2026-09-15.
[^11]: 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. Source: [Get started with the Attendant Console](https://help.webex.com/en-us/article/4xgekbb/Get-started-with-the-Attendant-Console), Get started with the Attendant Console, licensing and migration. Checked 2026-09-15.
[^12]: 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. Source: [Get started with the Attendant Console](https://help.webex.com/en-us/article/4xgekbb/Get-started-with-the-Attendant-Console), Get started with the Attendant Console, licensing. Checked 2026-09-15.
[^13]: 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. Source: [Get started with the Attendant Console](https://help.webex.com/en-us/article/4xgekbb/Get-started-with-the-Attendant-Console), Get started with the Attendant Console, transfer section. Checked 2026-09-05.
[^14]: 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. Source: [Get started with the Attendant Console](https://help.webex.com/en-us/article/4xgekbb/Get-started-with-the-Attendant-Console), Get started with the Attendant Console, call recording. Checked 2026-09-05.
[^15]: 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). Source: [Get started with the Attendant Console](https://help.webex.com/en-us/article/4xgekbb/Get-started-with-the-Attendant-Console), Get started with the Attendant Console, transfer to voicemail and one-click transfer sections. Checked 2026-09-05.
[^16]: Cisco states that the Receptionist Client is retired with an end of support date of 8 July 2024, that existing users can migrate to the Webex Attendant Console, and that the client may be used until the end of the subscription term. Source: [Get started with your Receptionist Client](https://help.webex.com/en-us/article/n0lwp2o/Receptionist-Client-Monitor-Calls-in-Queue), Get started with your Receptionist Client, End of Support announcement. Checked 2026-09-15.
[^17]: Once an organisation holds the Attendant Console licence, the Receptionist Client options disappear from the Control Hub user call experience settings. Source: [Get started with the Attendant Console](https://help.webex.com/en-us/article/4xgekbb/Get-started-with-the-Attendant-Console), Get started with the Attendant Console, licensing. Checked 2026-09-15.
[^18]: A user migrating from the Receptionist Client to the Attendant Console loses the documented ability to pull a specific call out of a queue or move it to the front (inferred). Source: [Get started with your Receptionist Client](https://help.webex.com/en-us/article/n0lwp2o/Receptionist-Client-Monitor-Calls-in-Queue), Get started with your Receptionist Client against the Attendant Console article. Checked 2026-09-15.
