Webex Calling hunt groups
Verified 2026-09-15 · 17 claims · sources tier 2 · 2 disputed
Also known as Longest Idle, Simultaneous, hunt group.
A Webex Calling hunt group distributes calls across members using 1 of 5 routing policies 9. Member limits vary by the chosen policy, ranging from 50 to 1000 members 10.
Routing policies and member caps
A hunt group distributes calls using circular, top down, longest idle, weighted, or simultaneous policies 9. The member limit depends directly on the selected policy 10:
| Routing policy | Member cap |
|---|---|
| Circular | 1000 10 |
| Top down | 1000 10 |
| Longest idle | 1000 10 |
| Weighted | 100 10 |
| Simultaneous | 50 10 |
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 11.
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 14. Sources disagree about whether turning off advance after a number of rings stops calls advancing or only suppresses a notification 6.
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 15.
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 7.
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 13. 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 12. Webex Contact Center is not mentioned in either hunt group article, where the phrase occurs 0 times 8.
See also
See also The Webex Calling feature access codes. See also Webex Calling call park. See also Webex Contact Center system limits reference.
Applicability
Across the claims in this article, the evidence covers Cisco Webex Calling, verified as of 2026-09-05. The deployment model is not covered by any claim in this article.
What remains uncertain
Sources disagree about whether turning off advance after a number of rings stops calls advancing or only suppresses a notification 6. Neither hunt group article states what a hunt group leaves in a call detail record or a report 12. Which other Control Hub feature articles carry the 1000 against 10000 contradiction is not covered by any claim in this article. The default values of the hunt group ring timers are not covered by any claim in this article.
See also
Related to
- Webex Calling call park — Where a call park recall escalates to
- Webex Contact Center system limits reference — Member caps that depend on the routing policy
Referenced by
- A documentation template and the defects it carriesstub — A second article carrying it with identical numbers
- A documentation template and the defects it carries — A second article carrying it with identical numbers
- The Webex Calling feature access codes — Supplies the codes the hunt group article names without numbers
- Webex Calling Call Queue as a product — Two features documented as siblings with no stated difference
- Webex Calling auto attendants — Promised as a destination in prose and not selectable
- Webex Calling voicemail — Where an unanswered hunt group call ends up
- What the Webex Calling detailed call history records — The recall destination the records name
Claims
| # | Claim | Status | Confidence | Verified |
|---|---|---|---|---|
| 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. Manage auto attendants · Manage auto attendants, opening prose against the menu action list, counted against the rendered article | fact | 0.90 | 2026-09-05 |
| 2 | A recall type field names a hunt group as the fallback recall destination. Reports for Your Cloud Collaboration Portfolio · Cloud collaboration reports, recall type field | fact | 0.90 | 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. Configure Call Queue · Configure Call Queue, announcements | fact | 0.90 | 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. Configure Call Queue · Configure Call Queue and Manage hunt groups in Control Hub, counted against the rendered article | fact | 0.90 | 2026-09-05 |
| 5 | The reference names hunt groups and supervisors as row subjects, and never mentions Webex Contact Center or a queue. Feature access codes for Webex Calling · Feature access codes for Webex Calling, whole table, counted against the rendered article | fact | 0.90 | 2026-09-05 |
| 6 | 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. Manage hunt groups in Control Hub · Manage hunt groups in Control Hub, comma-separated file field table against Edit hunt group call routing options | disputed | 0.60 | 2026-09-05 |
| 7 | 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. Manage hunt groups in Control Hub · Manage hunt groups in Control Hub, Known limitations against Bulk edit hunt groups | disputed | 0.60 | 2026-09-05 |
| 8 | Neither hunt group article mentions Webex Contact Center; the phrase occurs 0 times in both. Manage hunt groups in Control Hub · Both hunt group articles, counted against the rendered article | fact | 0.90 | 2026-09-05 |
| 9 | A hunt group distributes by one of 5 policies: circular, top down, longest idle, weighted or simultaneous. Manage hunt groups in Control Hub · Manage hunt groups in Control Hub, call routing policies | fact | 0.90 | 2026-09-05 |
| 10 | The member limit depends on the policy: 1000 for circular, top down and longest idle, 100 for weighted and 50 for simultaneous. Manage hunt groups in Control Hub · Manage hunt groups in Control Hub, call routing policies | fact | 0.90 | 2026-09-05 |
| 11 | Every documented hunt group outcome advances, forwards, diverts, or applies busy treatment or voicemail, and no path is described as dropping the call. Manage hunt groups in Control Hub · Manage hunt groups in Control Hub, routing and unreachable settings | inference | 0.60 | 2026-09-05 |
| 12 | 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. Manage hunt groups in Control Hub · Both hunt group articles, counted against the rendered article | fact | 0.90 | 2026-09-05 |
| 13 | 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. Work with hunt group calls on 9800/8875 · Work with hunt group calls on 9800 and 8875, whole article | field-pattern | 0.90 | 2026-09-05 |
| 14 | 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. Manage hunt groups in Control Hub · Manage hunt groups in Control Hub, call routing options | fact | 0.90 | 2026-09-05 |
| 15 | 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. Manage hunt groups in Control Hub · Manage hunt groups in Control Hub, temporary calling line identity | fact | 0.90 | 2026-09-05 |
| 16 | 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. Manage hunt groups in Control Hub · Manage hunt groups in Control Hub, comma-separated file procedure and field table | field-pattern | 0.90 | 2026-09-05 |
| 17 | A shared voicemail box is created as a voicemail group in Control Hub and can receive messages for more than one person. Manage a shared voicemail and inbound fax box for Webex Calling · Manage a shared voicemail and inbound fax box | fact | 0.90 | 2026-09-05 |
Sources
Configure Call Queue
Feature access codes for Webex Calling
Manage a shared voicemail and inbound fax box for Webex Calling
Manage auto attendants
Manage hunt groups in Control Hub
Reports for Your Cloud Collaboration Portfolio
Work with hunt group calls on 9800/8875
Cite this page
APA
WarmTransfer. (2026, September 15). Webex Calling hunt groups. WarmTransfer. https://warmtransfer.net/knowledge/webex-calling-hunt-groups
BibTeX
@misc{warmtransfer-webex-calling-hunt-groups,
title = {Webex Calling hunt groups},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/webex-calling-hunt-groups},
note = {Verified 2026-09-15}
}