Manage auto attendants

Publisher

Cisco Systems, Inc. (Webex Help Center)

URL

https://help.webex.com/en-us/article/nsioxoi/Manage-auto-attendants-in-Control-Hub

Published

2025-12-12

Updated

unknown

Accessed

2026-09-16

HTTP status

200

License

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

Source notes citing this source

• Custom Webex Calling auto attendant greetings must be WAV files at 8 or 16 kHz, 8 or 16 bit mono, u-law, A-law or PCM, with a maximum size of 2 MB (about 4 minutes). in context
• Webex Calling auto attendant menu keys (0-9, *, #) can play an announcement, transfer with or without prompt, transfer to operator, transfer to voicemail, dial by name, dial by extension, or exit the menu. in context
• Webex Calling auto attendant custom greetings must be 8 or 16 kHz, 8 or 16 bit mono, u-law, A-law or PCM audio, with a maximum file size of 2 MB (about 4 minutes). in context
• Webex Calling auto attendants can let callers dial an extension at any time without a dedicated menu item. in context
• Webex Calling auto attendant menu keys can be set to play an announcement, transfer with or without prompt, transfer to operator, transfer to voicemail, dial by name, dial by extension, exit menu, or Not Used. in context
• The Webex Calling auto attendant no-input timer accepts 1 to 60 seconds, and the menu can be set not to repeat or to repeat between 1 and 3 times. in context
• An auto attendant can have up to 10 alternate numbers in addition to its main number. in context
• The Control Hub calling analytics dashboard has an Auto-Attendant tab with call details for auto attendants. in context
• The auto attendant's direct line caller ID name is either its display name or a custom name of up to 128 characters. in context
• In Control Hub an auto attendant is created from Services > Calling > Features by selecting Add New on the Auto Attendant card. in context
• Auto attendants can be bulk created and updated by CSV import, with more than 1,000 records supplied as a ZIP of multiple CSV files. in context
• The auto attendant's Dial by name field accepts ASCII characters only. in context
• An auto attendant's dialing options can be set to Organization or Location scope. in context
• If the extension is left blank when a phone number is assigned, the auto attendant extension is filled with the last four digits of the phone number. in context
• An auto attendant can be set to let callers dial an extension at any time without a menu item, and this applies only to Webex Calling subscribers. in context
• Auto attendant call forwarding can be set to always forward all calls to a number or to selectively forward using rules based on schedules, calling numbers and destinations. in context
• In selective forwarding for an auto attendant, a Not to Forward rule always takes precedence over a Forward rule. in context
• A custom auto attendant greeting must be a WAV file at 8 or 16 kHz, 8 or 16 bit mono, encoded as u-law, A-law or PCM. in context
• A custom auto attendant greeting file may be at most 2 MB, about four minutes of playback. in context
• Business-hours and after-hours greetings are configured separately and each can use the default greeting or a custom recording. in context
• The after-hours menu of an auto attendant also applies during its holiday schedule; there is no separate holiday menu. in context
• Auto attendant menu keys can be assigned to play an announcement, transfer with prompt, transfer without prompt, transfer to operator, transfer to voicemail, dial by name, dial by extension or exit the menu. in context
• Auto attendant menu actions are defined per keypad key 0 through 9 plus * and #. in context
• The auto attendant's language setting determines the language of its default voice greetings and prompts. in context
• An auto attendant's location is chosen at creation and cannot be changed afterwards. in context
• When a caller gives no input the menu can be repeated not at all or one to three times, after which the call ends, a message plays and the call ends, or the call is transferred. in context
• The auto attendant no-input timer can be set from 1 to 60 seconds and defaults to 10 seconds. in context
• An auto attendant requires at least one of a phone number or an extension. in context
• Transfer to operator redirects the caller to the configured operator number when the assigned key is pressed. in context
• During auto attendant creation the administrator assigns an existing business hours schedule and holiday schedule or creates new ones. in context
• A single auto attendant shared by several locations applies one business-hours schedule, one holiday schedule and one time zone to every caller it answers. inferred in context
• Each auto attendant has its own Time Zone setting that can be viewed or edited in its general settings. in context
• Transfer with prompt routes the caller to an entered phone number or extension after a prompt telling them they are being transferred, while transfer without prompt does the same with no prompt. in context
• An auto attendant key can send callers to a call queue or hunt group by using a transfer action whose destination is the queue's or hunt group's number or extension. inferred in context
• As of its 2025-12-12 update, the auto attendant article listed exposing the bulk CSV operations as external APIs as coming soon. in context
• Webex Calling auto attendants are bulk managed by CSV from Services > Calling > Features > Auto Attendant through the bulk editor. Import status and errors appear under View Import history/Tasks. in context
• As of the article's 2025-12-12 update, the auto attendant bulk CSV could not delete whole auto attendants, create, modify or delete call forwarding rules, or create new schedules. The article lists these as coming soon. in context
• Creating a new auto attendant by CSV requires, among others, Name, Phone Number or Extension, Location, Business Schedule, Holiday Schedule, the business-hours and after-hours no-input settings and actions, and at least one key-press entry for each of the two menus. in context
• The auto attendant bulk import section carries a 1000-record export threshold and no larger figure; 10000 does not occur in the article. in context
• A 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. in context
• The 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 report in context
• 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. in context
• The auto attendant article does not mention call recording, a call detail record or reporting. in context
• Of 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. in context
• The article's opening gives 2 different lists of what an auto attendant routes a caller to in consecutive sentences. disputed in context

Cite this source record

APA

WarmTransfer. (2025, December 12). Manage auto attendants. WarmTransfer. https://warmtransfer.net/knowledge/sources/cisco-help-nsioxoi-webex-calling-auto-attendants

BibTeX

@misc{warmtransfer-cisco-help-nsioxoi-webex-calling-auto-attendants,
  title  = {Manage auto attendants},
  author = {{WarmTransfer}},
  year   = {2025},
  url    = {https://warmtransfer.net/knowledge/sources/cisco-help-nsioxoi-webex-calling-auto-attendants},
  note   = {Cisco Systems, Inc. (Webex Help Center), accessed 2026-09-16}
}