# Webex Calling hunt groups

Canonical: https://warmtransfer.net/knowledge/webex-calling-hunt-groups

Last verified: 2026-09-16

A Webex Calling hunt group distributes calls across members using 1 of 5 routing policies[^10]. Member limits vary by the chosen policy, ranging from 50 to 1000 members[^11].

## Routing policies and member caps

A hunt group distributes calls using circular, top down, longest idle, weighted, or simultaneous policies[^10]. The member limit depends directly on the selected policy[^11]:

| Routing policy | Member cap |
| --- | --- |
| Circular | 1000[^11] |
| Top down | 1000[^11] |
| Longest idle | 1000[^11] |
| Weighted | 100[^11] |
| Simultaneous | 50[^11] |

WarmTransfer's reading of the sources is that every documented hunt group outcome advances, forwards, diverts, or applies busy treatment or voicemail, and no path is described as dropping the call[^12].

## Routing options and agent controls

The hunt group ring timers publish a range without default values: the option to advance after a number of rings accepts 1 to 20, and the option to forward after a number of rings accepts 1 to 99[^15]. Sources disagree about whether turning off advance after a number of rings stops calls advancing or only suppresses a notification[^7].

A hunt group agent may set a temporary calling line identity using `#80` to present the group's number and `#81` to present the default caller identity[^16].

## Bulk administration and documentation scope

Sources disagree regarding the maximum import file size for bulk edits: the hunt group documentation lists a maximum import file size of 1000 rows in its limitations section, but describes a threshold of more than 10000 rows for each file in its bulk edit procedure[^8].

In the field, the article reached for answering a hunt group call is served as a phone-model article, documents Cisco Unified Communications Manager phones, and never mentions Webex Calling or Control Hub[^14]. Furthermore, neither hunt group article mentions call recording, and neither says anything about what a hunt group leaves in a call detail record or a report[^13]. Webex Contact Center is not mentioned in either hunt group article, where the phrase occurs 0 times[^9].

## See also

See also [The Webex Calling feature access codes](https://warmtransfer.net/knowledge/webex-calling-feature-access-codes).
See also [Webex Calling call park](https://warmtransfer.net/knowledge/webex-calling-call-park-artefacts).
See also [Webex Contact Center system limits reference](https://warmtransfer.net/knowledge/webex-cc-system-limits).

## Applicability

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

## What remains uncertain

Sources disagree about whether turning off advance after a number of rings stops calls advancing or only suppresses a notification[^7]. Neither hunt group article states what a hunt group leaves in a call detail record or a report[^13]. Which other Control Hub feature articles carry the 1000 against 10000 contradiction is not covered by the sources below. The default values of the hunt group ring timers are not covered by the sources below.

## Sources

[^1]: 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. Source: [Manage auto attendants](https://help.webex.com/en-us/article/nsioxoi/Manage-auto-attendants-in-Control-Hub), Manage auto attendants, opening prose against the menu action list, counted against the rendered article. Checked 2026-09-05.
[^2]: A recall type field names a hunt group as the fallback recall destination. Source: [Reports for Your Cloud Collaboration Portfolio](https://help.webex.com/en-us/article/nmug598/Reports-for-Your-Cloud-Collaboration-Portfolio), Cloud collaboration reports, recall type field. Checked 2026-09-15.
[^3]: A call queue publishes 5 caller and agent treatments a hunt group has none of: a welcome message, an estimated wait message, a comfort message, a comfort message bypass and hold music, plus a call whisper played to the agent. Source: [Configure Call Queue](https://help.webex.com/en-us/article/nzkg083/Configure-Call-Queue), Configure Call Queue, announcements. Checked 2026-09-05.
[^4]: Neither the call queue article nor the hunt group article states how the 2 features differ, though each names the other. Source: [Configure Call Queue](https://help.webex.com/en-us/article/nzkg083/Configure-Call-Queue), Configure Call Queue and Manage hunt groups in Control Hub, counted against the rendered article. Checked 2026-09-05.
[^5]: A hunt group telephone number may be assigned as an Emergency Callback Number, and Cisco warns that the agent who called the emergency service and the agent answering the callback may be different and unaware of the emergency, and that a hunt group with Call Forwarding and Advance when busy enabled can prevent the group alerting agents about the emergency. Source: [Emergency Callback Number (ECBN) in Control Hub](https://help.webex.com/en-us/article/nzqvtyq/Emergency-Callback-Number-in-Cisco-Webex-Control-Hub), Requirements and recommendations, Assigned Number option paragraphs. Checked 2026-09-16.
[^6]: The reference names hunt groups and supervisors as row subjects, and never mentions Webex Contact Center or a queue. Source: [Feature access codes for Webex Calling](https://help.webex.com/en-us/article/0zgzwj/Feature-access-codes-for-Webex-Calling), Feature access codes for Webex Calling, whole table, counted against the rendered article. Checked 2026-09-05.
[^7]: The hunt group article's own field table and its routing options text disagree about whether turning off advance after a number of rings stops calls advancing or only suppresses a notification (disputed). Source: [Manage hunt groups in Control Hub](https://help.webex.com/en-us/article/o6rfjeb/Manage-hunt-groups-in-Control-Hub), Manage hunt groups in Control Hub, comma-separated file field table against Edit hunt group call routing options. Checked 2026-09-05.
[^8]: The hunt group article gives a maximum import file size of 1000 rows in its limitations and describes a threshold of more than 10000 rows for each file in its bulk edit step (disputed). Source: [Manage hunt groups in Control Hub](https://help.webex.com/en-us/article/o6rfjeb/Manage-hunt-groups-in-Control-Hub), Manage hunt groups in Control Hub, Known limitations against Bulk edit hunt groups. Checked 2026-09-05.
[^9]: Neither hunt group article mentions Webex Contact Center; the phrase occurs 0 times in both. Source: [Manage hunt groups in Control Hub](https://help.webex.com/en-us/article/o6rfjeb/Manage-hunt-groups-in-Control-Hub), Both hunt group articles, counted against the rendered article. Checked 2026-09-05.
[^10]: A hunt group distributes by one of 5 policies: circular, top down, longest idle, weighted or simultaneous. Source: [Manage hunt groups in Control Hub](https://help.webex.com/en-us/article/o6rfjeb/Manage-hunt-groups-in-Control-Hub), Manage hunt groups in Control Hub, call routing policies. Checked 2026-09-05.
[^11]: The member limit depends on the policy: 1000 for circular, top down and longest idle, 100 for weighted and 50 for simultaneous. Source: [Manage hunt groups in Control Hub](https://help.webex.com/en-us/article/o6rfjeb/Manage-hunt-groups-in-Control-Hub), Manage hunt groups in Control Hub, call routing policies. Checked 2026-09-05.
[^12]: Every documented hunt group outcome advances, forwards, diverts, or applies busy treatment or voicemail, and no path is described as dropping the call (inferred). Source: [Manage hunt groups in Control Hub](https://help.webex.com/en-us/article/o6rfjeb/Manage-hunt-groups-in-Control-Hub), Manage hunt groups in Control Hub, routing and unreachable settings. Checked 2026-09-05.
[^13]: Neither hunt group article mentions call recording, and neither says anything about what a hunt group leaves in a call detail record or a report. Source: [Manage hunt groups in Control Hub](https://help.webex.com/en-us/article/o6rfjeb/Manage-hunt-groups-in-Control-Hub), Both hunt group articles, counted against the rendered article. Checked 2026-09-05.
[^14]: The article reached as answering a hunt group call is served as a phone-model article, documents Cisco Unified Communications Manager phones, and never mentions Webex Calling or Control Hub (field report). Source: [Work with hunt group calls on 9800/8875](https://help.webex.com/en-us/article/hclqecb/Answer-a-call-for-your-hunt-group), Work with hunt group calls on 9800 and 8875, whole article. Checked 2026-09-05.
[^15]: The hunt group ring timers publish a range and no default: advance after a number of rings accepts 1 to 20 and forward after a number of rings accepts 1 to 99. Source: [Manage hunt groups in Control Hub](https://help.webex.com/en-us/article/o6rfjeb/Manage-hunt-groups-in-Control-Hub), Manage hunt groups in Control Hub, call routing options. Checked 2026-09-05.
[^16]: A hunt group agent may set a temporary calling line identity with hash 80 to present the group's number and hash 81 to present the default caller identity. Source: [Manage hunt groups in Control Hub](https://help.webex.com/en-us/article/o6rfjeb/Manage-hunt-groups-in-Control-Hub), Manage hunt groups in Control Hub, temporary calling line identity. Checked 2026-09-05.
[^17]: Changing 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. Source: [Configure Webex Calling for your organization](https://help.webex.com/en-us/article/njvdjf2/Configure-Webex-Calling-for-your-organization), Update an existing location, note at the end of step 7. Checked 2026-09-15.
[^18]: In Survivability mode up to 100 hunt groups can be configured with a maximum of 32 users each, the weighted call routing pattern is not supported, and the supported hunt group patterns are sequential, parallel, peer and longest-idle. Source: [Site survivability for Webex Calling](https://help.webex.com/en-us/article/d68vi1/Site-Survivability-for-Webex-Calling), Limitations and restrictions Hunt Groups and Hunt Group Call Routing; Table 1 Hunt Group row. Checked 2026-09-16.
[^19]: The hunt group article's bulk procedure names a call pickup group, and its field table describes removing a single agent where its own step section describes agents (field report). Source: [Manage hunt groups in Control Hub](https://help.webex.com/en-us/article/o6rfjeb/Manage-hunt-groups-in-Control-Hub), Manage hunt groups in Control Hub, comma-separated file procedure and field table. Checked 2026-09-05.
[^20]: A shared voicemail box is created as a voicemail group in Control Hub and can receive messages for more than one person. Source: [Manage a shared voicemail and inbound fax box for Webex Calling](https://help.webex.com/en-us/article/mcjd4u/Manage-a-Shared-Voicemail-and-Inbound-Fax-Box-for-Webex-Calling), Manage a shared voicemail and inbound fax box. Checked 2026-09-05.