Webex Calling auto attendants
Verified 2026-09-16 · 9 sources · tier 2 · 1 disputed
Also known as Dial by name, auto attendant.
An auto attendant menu key takes one of 9 actions: not used, play an announcement, transfer with a prompt, transfer without a prompt, transfer to an operator, transfer to voicemail, dial by name, dial by extension, or exit the menu 4. A hunt group is named once in the opening prose of the auto attendant documentation and never appears as a selectable menu action, while a call queue does not appear in the documentation at all 2.
Routing destinations and menu actions
Sources disagree on what destinations an auto attendant routes a caller to, as the documentation gives 2 different lists in consecutive sentences in its opening prose 7.
The auto attendant menu provides 9 specific key actions: not used, play an announcement, transfer with a prompt, transfer without a prompt, transfer to an operator, transfer to voicemail, dial by name, dial by extension, and exit the menu 4. Although a hunt group is mentioned once in the documentation's opening prose, it is never listed as a selectable menu action, and a call queue is not mentioned anywhere in the article 2.
Configuration bounds and bulk management
Of 11 numeric bounds in the auto attendant documentation, 1 publishes a default, and that default appears only in the bulk import reference rather than in the step-by-step text for the same field 6. The bulk import section specifies a 1000-record export threshold and no larger figure, with 10000 not appearing in the documentation 1.
In the field, the auto attendant documentation carries its own inherited errors: a bulk step instructs the reader to add a first and last name for a feature whose import schema contains only a name, and an after-hours procedure is labeled with a heading for the business hours menu 3.
The documentation does not mention call recording, call detail records, or reporting 5.
See also
See also Webex Calling hunt groups. See also A documentation template and the defects it carries.
Applicability
Applies to: Cisco Webex Calling. Sources checked 2026-09-05.
What remains uncertain
Whether call records distinguish an auto attendant transfer from a blind transfer is not covered by the sources below. Whether a menu key can reach a hunt group or call queue by dialing its number is not covered by the sources below. The defaults for the other auto attendant bounds are not covered by the sources below.
See also
Related to
- A documentation template and the defects it carries — A bulk section without the contradiction which bounds the finding
- A documentation template and the defects it carriesstub — A bulk section without the contradiction which bounds the finding
- Webex Calling hunt groups — Promised as a destination in prose and not selectable
Sources
- 1The auto attendant bulk import section carries a 1000-record export threshold and no larger figure; 10000 does not occur in the article.Manage auto attendants · Manage auto attendants, bulk management section, counted against the rendered article · Checked 2026-09-05
- 2A hunt group is named once in the article's opening prose and never appears as a selectable menu action, and a call queue does not appear in the article at all.Manage auto attendants · Manage auto attendants, opening prose against the menu action list, counted against the rendered article · Checked 2026-09-05
- 3The auto attendant article carries its own inherited errors: a bulk step tells the reader to add a first and last name for a feature whose import schema has only a name, and an after-hours procedure is headed as the business hours menu.field reportManage auto attendants · Manage auto attendants, bulk management and after hours menu · Checked 2026-09-05
- 5The auto attendant article does not mention call recording, a call detail record or reporting.Manage auto attendants · Manage auto attendants, counted against the rendered article · Checked 2026-09-05
- 6Of 11 numeric bounds in the auto attendant article, one publishes a default, and that default appears only in the bulk import reference and not in the step-by-step text for the same field.Manage auto attendants · Manage auto attendants, limits and the bulk import field table · Checked 2026-09-05
- 7The article's opening gives 2 different lists of what an auto attendant routes a caller to in consecutive sentences.disputedManage auto attendants · Manage auto attendants, opening prose · Checked 2026-09-05
- 8Cisco states that the Location Default ECBN and the Assigned Number from the user's location must be directed to a live answering point such as a receptionist or other person within the location, and cannot be an auto attendant, interactive voice response or other service.Emergency Callback Number (ECBN) in Control Hub · Options for ECBN configuration, opening paragraph · Checked 2026-09-16
- 9Changing a location's time zone does not update the time zones of features associated with that location, and Cisco names auto attendant, hunt group and call queue as features whose time zone must be edited in each feature's own general settings.Configure Webex Calling for your organization · Update an existing location, note at the end of step 7 · Checked 2026-09-15
Documents
Configure Webex Calling for your organization
Emergency Callback Number (ECBN) in Control Hub
Manage auto attendants
Cite this page
APA
WarmTransfer. (2026, September 16). Webex Calling auto attendants. WarmTransfer. https://warmtransfer.net/knowledge/webex-calling-auto-attendant
BibTeX
@misc{warmtransfer-webex-calling-auto-attendant,
title = {Webex Calling auto attendants},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/webex-calling-auto-attendant},
note = {Verified 2026-09-16}
}