Configuration · guide

Setting up a Webex Calling auto attendant

Webex Calling

Verified 2026-09-30 · 52 sources · tier 2–6

For Webex Calling administrators configuring auto attendants in Control Hub.

Webex Calling auto attendants provide interactive voice response menus and call routing for business-hours, after-hours, and holiday schedules 40. The feature is included as part of standard location features and connects callers to users, queues, and hunt groups 24 25.

Before you start

  • Auto attendant is part of the standard package of location features in Webex Calling and does not require a user license 24.
  • Cisco positions the auto attendant for IVR menus and business-hours, after-hours, and holiday routing, while call queues handle caller queuing and hunt groups provide member hunting without IVR 40. See also Setting up Webex Calling call queues and hunt groups.
  • Review target locations in Control Hub under Management > Locations before beginning configuration 44. See also Setting up a Webex Calling location.

What changes by situation

Pick your answers to see only your path. Nothing is sent anywhere until you make a plan.

How should the auto attendant be deployed across locations?
What dialing scope should be used for dial by name and dial by extension?
What telephone addressing will be assigned to the auto attendant?
Where will menu greetings be sourced from?

Four questions. One permanent page you can send to your manager.

Step 1 Verify auto attendant availability in Control Hub

Do

Navigate to Services > Calling > Features in Control Hub to locate the Auto Attendant feature card 8.

Verify

Suggested check: Confirm the Auto Attendant card is visible and accessible under Features.

Step 2 Plan attendant location ownership

One auto attendant per location

Do

Select an owning location for each planned auto attendant, noting that an attendant's location is chosen at creation and cannot be changed afterwards 28. Note the required time zone for each site 48.

Verify

Suggested check: Verify that each planned auto attendant maps to an individual location and time zone.

Rollback

Suggested rollback: Adjust the planned mapping before creating the auto attendants, as attendants cannot change locations once created.

One shared auto attendant for multiple locations

Do

Designate a single home location to host the shared auto attendant, taking into account that the location cannot be modified after creation 28. WarmTransfer's reading of the sources is that a shared auto attendant applies a single time zone and schedule across all callers 48.

Verify

Suggested check: Verify that the agreed hours, location, and time zone satisfy call requirements across all participating sites.

Rollback

Suggested rollback: Select an alternate home location prior to creation.

Step 3 Configure business-hours and holiday schedules

Do

In the field, practitioners recommend building business-hours and holiday schedules before building the auto attendant 17. Navigate to Management > Locations, select the location, and click Calling > Schedules > Add Schedule 44. Create a business-hours schedule and a holiday schedule 45. For holidays, add one-time events (which may span multiple days), weekly events, or yearly events, applying the all-day option where required 45. Keep in mind that a location supports up to 1,000 schedules and each schedule supports up to 150 events 43.

Verify

Suggested check: Confirm that the configured schedules appear in the location schedule list with their assigned events.

Rollback

Delete the schedule from Calling > Schedules, ensuring it is removed from any features using it first 42.

Step 4 Provision downstream call queues and hunt groups

Do

Ensure that any destination queues or hunt groups exist and have an assigned number or extension before mapping menu options:

  • Call queues are created via Services > Calling > Features > Call Queue > Add new in the chosen location and require a phone number or extension 7.
  • Hunt groups are created via Services > Calling > Features > Hunt Group > Add New in a location that cannot later be changed and require a phone number or extension 22.

Verify

Suggested check: Dial each destination extension from a registered phone to confirm normal call treatment.

Rollback

Suggested rollback: Remove or reassign any temporary queues or hunt groups created for attendant routing.

Step 5 Create the auto attendant instance

Direct line phone number and extension

Do

Navigate to Services > Calling > Features and click Add New on the Auto Attendant card 8. Choose the designated location 28. Assign a phone number 32. If the extension is left blank, Control Hub fills it with the last 4 digits of the phone number 12. If required, configure up to 10 alternate numbers 3.

Verify

Suggested check: Check that the auto attendant displays the assigned direct number, extension, and alternate numbers in Control Hub.

Rollback

Suggested rollback: Edit the auto attendant settings to modify or unassign the phone numbers.

Extension only

Do

Navigate to Services > Calling > Features and click Add New on the Auto Attendant card 8. Select the designated location 28. Enter an extension and leave the phone number empty 32.

Verify

Suggested check: Confirm the attendant appears in the feature list with its assigned extension and no phone number.

Rollback

Suggested rollback: Edit the attendant settings to alter the extension or supply a direct phone number.

Step 6 Configure identity, language, time zone, and schedule bindings

Do

Set the direct line caller ID name to either the display name or a custom name of up to 128 characters 6. If entering a Dial by name entry, use ASCII characters only 10. Select the language, which establishes the language for default voice greetings and prompts 27. Set the auto attendant Time Zone in general settings 48. Assign the business-hours and holiday schedules created earlier 41.

Verify

Suggested check: Open the attendant's general settings to verify the caller ID name, language, time zone, and assigned schedule bindings.

Rollback

Suggested rollback: Adjust the identity, language, time zone, or schedule bindings within the auto attendant general settings.

Step 7 Configure greeting audio

Built-in system default greetings

Do

Leave both business-hours and after-hours greetings set to Default, which will play prompt audio in the attendant's selected language 21 27.

Verify

Suggested check: Place a call to the attendant during business hours and after hours to confirm default system greeting playback.

Announcement repository audio file or text-to-speech

Do

Prepare audio files matching the required format: WAV files at 8 or 16 kHz, 8 or 16 bit mono, encoded as u-law, A-law, or PCM, up to 2 MB (about 4 minutes) 19 20. Alternatively, generate text-to-speech announcements up to 3,000 characters, respecting the limit of 150 TTS announcements created or updated per organization per day 38. Upload audio files under Services > Calling > Features > Announcements, adhering to the 1 GB total storage limit 36 37. Store files at the organization level if they need to be usable across multiple locations, or at the location level for single-site use 35. In the auto attendant settings, select the custom recording for the business-hours greeting and the after-hours greeting 21.

Verify

Suggested check: Call the attendant during business and after-hours periods to verify custom announcement playback.

Rollback

Revert the greeting selection back to Default 21. Files in active use cannot be deleted directly from the repository, though they can be replaced 34.

Step 8 Build the business-hours menu

Do

Assign routing actions to keys 0 through 9, *, and # 26. Available menu actions include 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 25. Transfer with prompt notifies the caller before transferring, whereas transfer without prompt connects without an intermediate message 49. In the field, practitioners commonly map auto attendant keys to transfer callers to hunt groups or call queues 16. If configuring an operator key, select transfer to operator and specify the operator destination number 33. Configure the no-input timer between 1 and 60 seconds (defaults to 10 seconds) 31. When a caller gives no input the menu can be repeated not at all or 1 to 3 times, after which the call ends, a message plays and the call ends, or the call is transferred 29.

Verify

Suggested check: Dial the attendant during business hours, press each configured key to confirm call routing, and allow the timer to expire to verify no-input call handling.

Rollback

Suggested rollback: Clear or reassign the key mappings and reset the no-input handling parameters in the business-hours menu.

Step 9 Build the after-hours and holiday menu

Do

Configure after-hours key treatments using the available menu actions 25. Note that the after-hours menu also applies during the holiday schedule, as there is no separate holiday menu 23.

Verify

Suggested check: Place a test call outside business hours and during a configured holiday schedule event to verify that the after-hours menu plays.

Rollback

Suggested rollback: Adjust or clear the after-hours menu key definitions.

Step 10 Set dialing scope options

One auto attendant per location + Whole organization

Do

Set dialing options to Organization scope 11. Optionally enable extension dialing without requiring a menu item, which applies only to Webex Calling subscribers 13.

Verify

Suggested check: Test extension dialing from the menu to an extension located at a different site to verify cross-location reach.

Rollback

Suggested rollback: Switch the dialing option setting to Location scope.

One auto attendant per location + Attendant location only

Do

Set dialing options to Location scope 11. Optionally enable extension dialing without requiring a menu item for Webex Calling subscribers 13.

Verify

Suggested check: Test dialing an extension within the local site and confirm an extension at another site is unreachable.

Rollback

Suggested rollback: Change the dialing options back to Organization scope.

One shared auto attendant for multiple locations + Whole organization

Do

Set dialing options to Organization scope so that the shared front door can reach subscribers across the organization 11. If desired, enable extension dialing without requiring a menu item, which applies to Webex Calling subscribers 13.

Verify

Suggested check: From the auto attendant, dial extensions located in different sites to verify organization-wide routing.

Rollback

Suggested rollback: Switch the dialing option setting to Location scope.

One shared auto attendant for multiple locations + Attendant location only

Do

Set dialing options to Location scope 11. If desired, configure extension dialing without requiring a menu item for Webex Calling subscribers 13.

Verify

Suggested check: Confirm that callers can reach extensions in the home location but cannot dial extensions outside it.

Rollback

Suggested rollback: Revert dialing options to Organization scope.

Step 11 Validate call forwarding settings

Do

Confirm that "Always forward" is disabled unless unconditional redirection is desired, as it diverts all calls 14. If configuring selective forwarding rules based on schedules, calling numbers, and destinations, remember that a Not to Forward rule always takes precedence over a Forward rule 14 15.

Verify

Suggested check: Call the auto attendant and confirm that the call presents the menu rather than unexpected forwarding.

Rollback

Suggested rollback: Reconfigure or disable selective or unconditional call forwarding rules.

Step 12 Test and review reports

Do

Review the Auto-Attendant tab within Control Hub calling analytics 4. See also Webex Calling analytics in Control Hub. Access Monitoring > Reports to run the Auto-attendant stats summary, business hours key details, or after-hours key details reports, which display the keys pressed and their destinations 1. Note that in these reports, calls transferred to call services are counted as answered 39.

Verify

Suggested check: Place end-to-end test calls across business hours, after hours, and holiday schedules, verifying key actions, extension dialing, and no-input actions. Suggested check: Verify that key presses appear with their corresponding destinations in the key details report.

Applicability

Applies to: Cisco Webex Calling. Deployments: multi-tenant. Sources checked 2026-09-30. The ability to specify call routing when a caller does not respond to menu prompts was added in Cisco's 22 September 2025 Webex Calling release 30. Cisco AI Receptionist was introduced on 18 June 2026 with intent-based routing and received multi-language support on 29 July 2026 2. Bulk imports support CSV files, and imports exceeding 1,000 records require a ZIP archive containing multiple CSV files 9.

What remains uncertain

Recording greetings via the voice portal is not covered by the sources below. The complete deletion procedure for an auto attendant in Control Hub is not covered by the sources below. Building multi-level submenus natively without chaining auto attendants is not covered by the sources below. The maximum number of auto attendants supported per location or organization is not covered by the sources below.

See also

Depends on

Referenced by

Sources

  1. 1
    Control Hub offers Auto-attendant stats summary, business hours key details and after-hours key details report templates under Monitoring > Reports, and the key details reports show the key pressed and its destination.
    Reports for Your Cloud Collaboration Portfolio · Webex Calling reports, Auto-attendant report sections · Checked 2026-09-30
  2. 2
    Cisco introduced AI Receptionist for Webex Calling on 18 June 2026 with intent-based routing, and added multi-language support on 29 July 2026.
    What's new in Webex Calling · June 18, 2026 and July 29, 2026 entries · Checked 2026-09-30
  3. 3
    An auto attendant can have up to 10 alternate numbers in addition to its main number.
    Manage auto attendants · Edit auto attendant settings, Alternate numbers · Checked 2026-09-30
  4. 4
    The Control Hub calling analytics dashboard has an Auto-Attendant tab with call details for auto attendants.
    Manage auto attendants · Analytics and reports section · Checked 2026-09-30
  5. 5
    In the auto attendant API model, extensionDialing and nameDialing each take ENTERPRISE (organization level) or GROUP (location level) and default to ENTERPRISE when not set.
    wxc_sdk.telephony.autoattendant module · AutoAttendant model fields extension_dialing and name_dialing; Dialing enum · Checked 2026-09-30
  6. 6
    The auto attendant's direct line caller ID name is either its display name or a custom name of up to 128 characters.
    Manage auto attendants · Create an auto attendant, Basics, Direct line caller ID name · Checked 2026-09-30
  7. 7
    A call queue is created from Services > Calling > Features > Call Queue > Add new, in a chosen location, and must have a phone number or an extension.
    Configure call queues · Create a call queue, Basics · Checked 2026-09-30
  8. 8
    In Control Hub an auto attendant is created from Services > Calling > Features by selecting Add New on the Auto Attendant card.
    Manage auto attendants · Create an auto attendant, step 1 · Checked 2026-09-30
  9. 9
    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.
    Manage auto attendants · Bulk manage auto attendants · Checked 2026-09-30
  10. 10
    The auto attendant's Dial by name field accepts ASCII characters only.
    Manage auto attendants · Create an auto attendant, Basics, Dial by name · Checked 2026-09-30
  11. 11
    An auto attendant's dialing options can be set to Organization or Location scope.
    Manage auto attendants · Dialing options · Checked 2026-09-30
  12. 12
    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.
    Manage auto attendants · Create an auto attendant, Basics, Phone number and extension · Checked 2026-09-30
  13. 13
    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.
    Manage auto attendants · Business hours menu, Enable extension dialing without requiring a menu item · Checked 2026-09-30
  14. 14
    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.
    Manage auto attendants · Call forwarding section · Checked 2026-09-30
  15. 15
    In selective forwarding for an auto attendant, a Not to Forward rule always takes precedence over a Forward rule.
    Manage auto attendants · Call forwarding, selectively forward calls, rule ordering · Checked 2026-09-30
  16. 16
    Practitioners commonly map auto attendant keys to transfer callers to hunt groups or call queues.field report
    Cisco WebEx Calling Features: Auto Attendant vs Queue vs Hunt Group · Auto Attendant section, key mapping paragraph · Checked 2026-09-30
  17. 17
    Practitioners recommend building business-hours and holiday schedules before building the auto attendant.field report
    Cisco WebEx Calling Features: Auto Attendant vs Queue vs Hunt Group · Schedules paragraph · Checked 2026-09-30
  18. 18
    In at least one service provider's portal a second-level menu is built by sending a key to another auto attendant, because one attendant only offers keys 0-9, * and #.field report
    Enterprise Portal: Auto Attendant · Menu options, submenu note · Checked 2026-09-30
  19. 19
    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.
    Manage auto attendants · Business hours greeting, custom greeting requirements · Checked 2026-09-30
  20. 20
    A custom auto attendant greeting file may be at most 2 MB, about four minutes of playback.
    Manage auto attendants · Business hours greeting, custom greeting requirements · Checked 2026-09-30
  21. 21
    Business-hours and after-hours greetings are configured separately and each can use the default greeting or a custom recording.
    Manage auto attendants · Business hours greeting; After hours greeting · Checked 2026-09-30
  22. 22
    A hunt group is created from Services > Calling > Features > Hunt Group > Add New, in a location that cannot later be changed, and must have a phone number or an extension.
    Manage hunt groups in Control Hub · Create a hunt group, Basics · Checked 2026-09-30
  23. 23
    The after-hours menu of an auto attendant also applies during its holiday schedule; there is no separate holiday menu.
    Manage auto attendants · After hours menu, introductory note · Checked 2026-09-30
  24. 24
    Auto attendant is part of the standard package of location features in Webex Calling and does not need a user license.
    Webex Calling features by license type · Location features section · Checked 2026-09-30
  25. 25
    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.
    Manage auto attendants · Business hours menu, dialing menu options · Checked 2026-09-30
  26. 26
    Auto attendant menu actions are defined per keypad key 0 through 9 plus * and #.
    Manage auto attendants · Bulk manage auto attendants, CSV field reference, key actions · Checked 2026-09-30
  27. 27
    The auto attendant's language setting determines the language of its default voice greetings and prompts.
    Manage auto attendants · Create an auto attendant, Basics, Language · Checked 2026-09-30
  28. 28
    An auto attendant's location is chosen at creation and cannot be changed afterwards.
    Manage auto attendants · Create an auto attendant, Basics, Location field · Checked 2026-09-30
  29. 29
    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.
    Manage auto attendants · Business hours menu, call treatment when no input · Checked 2026-09-30
  30. 30
    Cisco's 22 September 2025 Webex Calling release added the ability to specify call routing when a caller does not respond to the auto attendant menu prompt.
    What's new in Webex Calling · September 22, 2025 entry: Auto Attendant enhancement for call handling · Checked 2026-09-30
  31. 31
    The auto attendant no-input timer can be set from 1 to 60 seconds and defaults to 10 seconds.
    Manage auto attendants · Business hours menu, call treatment when no input · Checked 2026-09-30
  32. 32
    An auto attendant requires at least one of a phone number or an extension.
    Manage auto attendants · Create an auto attendant, Basics, Phone number and extension · Checked 2026-09-30
  33. 33
    Transfer to operator redirects the caller to the configured operator number when the assigned key is pressed.
    Manage auto attendants · Business hours menu, Transfer to operator · Checked 2026-09-30
  34. 34
    An announcement file that a feature is currently using cannot be deleted, though it can be replaced.
    Manage announcement repository · Delete or replace announcement section · Checked 2026-09-30
  35. 35
    Announcements can be stored at organization level, usable across the organization, or at location level, usable only at that location.
    Manage announcement repository · Overview, organization and location level · Checked 2026-09-30
  36. 36
    The announcement repository is managed from Services > Calling > Features > Announcements in Control Hub and holds audio used for auto attendant greetings, call queue announcements and music on hold.
    Manage announcement repository · Manage announcement repository, navigation steps and overview · Checked 2026-09-30
  37. 37
    The announcement repository has a 1 GB storage limit across all levels.
    Manage announcement repository · Overview, storage limit · Checked 2026-09-30
  38. 38
    The announcement repository can generate text-to-speech announcements of up to 3000 characters, with up to 150 TTS announcements created or updated per organization per day.
    Manage announcement repository · Text-to-speech section · Checked 2026-09-30
  39. 39
    In the auto attendant reports, calls transferred to call services are counted as answered.
    Reports for Your Cloud Collaboration Portfolio · Auto-attendant stats summary, Answered column · Checked 2026-09-30
  40. 40
    Cisco positions the auto attendant for IVR menus and business-hours, after-hours and holiday routing, the call queue for queuing callers, and the hunt group for simple member hunting without IVR.
    Comparison of call routing methods · Auto attendant, Call queue and Hunt group comparison rows · Checked 2026-09-30
  41. 41
    During auto attendant creation the administrator assigns an existing business hours schedule and holiday schedule or creates new ones.
    Manage auto attendants · Create an auto attendant, Business hours schedule and Holiday schedule · Checked 2026-09-30
  42. 42
    A location schedule must be removed from every feature using it before it can be deleted.
    Create schedules in Control Hub · Delete a location schedule · Checked 2026-09-30
  43. 43
    A location can have at most 1,000 schedules and each schedule at most 150 events.
    Create schedules in Control Hub · Limits · Checked 2026-09-30
  44. 44
    Location schedules are created from Management > Locations, selecting the location, then Calling > Schedules > Add Schedule.
    Create schedules in Control Hub · Create a location schedule · Checked 2026-09-30
  45. 45
    Location schedules are either business hours schedules or holiday schedules, and holiday events can be one-time (optionally multi-day), weekly or yearly, with an all-day option.
    Create schedules in Control Hub · Create a location schedule, schedule type and event recurrence · Checked 2026-09-30
  46. 46
    With organization (Enterprise) scope callers who dial by name or extension can reach users at any location, while location (Group) scope limits them to users at the auto attendant's own location.inferred
    Enterprise Portal: Auto Attendant · Dialing scope, Enterprise and Site descriptions · Checked 2026-09-30
  47. 47
    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
    Manage auto attendants · Create an auto attendant, schedule fields; General settings, Time Zone · Checked 2026-09-30
  48. 48
    Each auto attendant has its own Time Zone setting that can be viewed or edited in its general settings.
    Manage auto attendants · Edit auto attendant settings, General settings, Time Zone · Checked 2026-09-30
  49. 49
    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.
    Manage auto attendants · Business hours menu, Transfer with prompt and Transfer without prompt · Checked 2026-09-30
  50. 50
    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
    Manage auto attendants · Business hours menu, Transfer with prompt and Transfer without prompt · Checked 2026-09-30
  51. 51
    When a location has more than one auto attendant, the voice portal asks for the auto attendant number before recording a greeting.
    Record an Auto Attendant Greeting on a Phone for Webex Calling · Procedure, note after step 5 · Checked 2026-09-30
  52. 52
    An administrator can record business-hours or after-hours auto attendant greetings by phone through the location's voice portal using the voice portal admin passcode, pressing 1 for auto attendant greetings then 1 for business hours or 2 for after hours.
    Record an Auto Attendant Greeting on a Phone for Webex Calling · Prerequisites; Procedure steps 1 to 6 · Checked 2026-09-30

Documents

tier 2 current vendor documentation

Comparison of call routing methods

Cisco Webex · 2024-08-30 · accessed 2026-09-30

tier 2 current vendor documentation

Configure call queues

Cisco Webex · 2026-07-23 · accessed 2026-09-30

tier 2 current vendor documentation

Create schedules in Control Hub

Cisco Webex · 2026-01-29 · accessed 2026-09-30

tier 2 current vendor documentation

Manage announcement repository

Cisco Webex · 2026-08-04 · accessed 2026-09-30

tier 2 current vendor documentation

Manage auto attendants

Cisco Systems, Inc. (Webex Help Center) · 2025-12-12 · accessed 2026-09-16

tier 2 current vendor documentation

Manage hunt groups in Control Hub

Cisco Systems, Inc. (Webex Help Center) · 2026-07-23 · accessed 2026-09-16

tier 2 current vendor documentation

Record an Auto Attendant Greeting on a Phone for Webex Calling

Cisco · 2022-09-06 · accessed 2026-09-30

tier 2 current vendor documentation

Reports for Your Cloud Collaboration Portfolio

Cisco Systems, Inc. (Webex Help Center) · 2026-09-15 · accessed 2026-09-16

tier 2 current vendor documentation

Webex Calling features by license type

Cisco Webex · 2026-09-28 · accessed 2026-09-30

tier 2 current vendor documentation

What's new in Webex Calling

Cisco Systems · 2026-09-05 · accessed 2026-09-05

tier 4 archived vendor documentation

Enterprise Portal: Auto Attendant

Verizon · 2026-09-30 · accessed 2026-09-30

tier 5 independent technical research

wxc_sdk.telephony.autoattendant module

wxc_sdk (open-source Python SDK for Webex Calling APIs) · 2026-09-30 · accessed 2026-09-30

tier 6 community and field reports

Cisco WebEx Calling Features: Auto Attendant vs Queue vs Hunt Group

LookingPoint · 2026-09-30 · accessed 2026-09-30

Cite this page

APA

WarmTransfer. (2026, September 30). Setting up a Webex Calling auto attendant. WarmTransfer. https://warmtransfer.net/guides/webex-calling-auto-attendant-setup

BibTeX

@misc{warmtransfer-webex-calling-auto-attendant-setup,
  title  = {Setting up a Webex Calling auto attendant},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/guides/webex-calling-auto-attendant-setup},
  note   = {Verified 2026-09-30}
}