Webex Contact Center system limits reference
Verified 2026-09-05 · 61 claims · sources tier 2 · 1 disputed
Also known as Active limits, Maximum limits.
Webex Contact Center defines configuration boundaries across tenants, routing constructs, media storage, and flow activities 319. Cisco defines active limits as operable limits for optimal performance and maximum limits as thresholds for maximum capacity, while recommending that administrators stay within maximum limit values 3.
Tenant and user configuration limits
A Webex Contact Center tenant is limited to 20000 active users, of which up to 3000 can be supervisors 44. Webex Contact Center supports unlimited concurrent agents at the organization level, meaning the 20000 user figure restricts configured user records rather than simultaneous agent sessions 14. Tenants are capped at 300 active sites 38 and 1500 active user profiles 43. An individual user profile's access rights can encompass at most 20 sites, 100 teams, 50 entry points, and 250 queues 43. The maximum auto-wrap-up timeout configurable in a desktop profile is 600000 milliseconds 17.
For entry points and dialing, a tenant supports up to 6000 active entry points and 1000 active outdial entry points 19. Tenants permit 15000 dialed numbers overall and up to 500 dialed numbers per entry point 18. Routing strategy configuration is limited to 200 global routing strategy entries and 500 global entry points referenced by routing strategies, with at most 20 routing strategies allowed per entry point 30. In addition, a tenant is capped at 5000 active global variables 21.
Cisco states that 17 named entities have a maximum limit on character counts for their Name field, but the documentation lists those entities without publishing any character count 26.
Routing, queues, and team limits
Webex Contact Center organizes queueing and distribution across agent-based, capacity-based, and skill-based models 421128.
| Entity or parameter | Active limit | Scope or rule |
|---|---|---|
| Agent-based teams | 3000 | Tenant maximum; holds at most 100 users 42 |
| Capacity-based teams | 100 total | At most 50 active, up to 100 inactive 11 |
| Capacity-based team concurrent calls | 5000 | 100 per team across 50 teams for an organization 10 |
| Inbound contact service queues | 11000 | Tenant maximum 16 |
| Outbound contact service queues | 5000 | Tenant maximum 16 |
| Team-based queues | 10500 | Tenant maximum 28 |
| Skill-based queues | 500 | Tenant maximum 28 |
| Active skills | 1000 | Value capped at 200, length at 50, enum list at 200, enum length at 50 40 |
| Skill profiles | 9000 | Holds at most 50 skills per profile 39 |
| Queue skill requirements | 50 | Maximum skill requirements per queue 2823 |
| Contact skill requirements | 10 | Maximum skill requirements for an individual contact 2223 |
For team routing, active limits specify 50 agents for a team and 10000 concurrent agents for a team 7. Call distribution groups allow up to 50 teams per call distribution group, 20 call distribution groups in a queue, and 250 teams in a queue across all call distribution groups 13. Under the call distribution group section, which governs the team-assignment queue model rather than skill-based queue assignment, the routing and queueing active limits specify a maximum of 500 agents for a queue 45. The table derives this 500 agents cap by multiplying maximum agents in a team by maximum teams for a call distribution group by maximum call distribution groups in the queue, though calculating the table's stated values of 50, 50, and 20 produces 50000 rather than 500 6. While captioned "Active and maximum configuration limits" and introduced with a reference to a "Maximum Limits" column, the routing and queueing table contains only "Configurations" and "Active Limits" columns, omitting maximum limits for its rows 41.
Contact service queue service level thresholds cap at 86400 seconds for telephony and chat, 604800 seconds for digital, and 1209600 seconds for email 34. Maximum time in queue caps at 86400 seconds for telephony and chats, 604800 seconds for digital, and 1209600 seconds for email 24. In the active configuration limits table, maximum time in a voice queue is listed as 1 day 25.
For outbound dialing, an organization is limited to 100 preview and progressive outbound campaigns, with at most 500 agents in a campaign 27.
Connectors, media, monitoring, and filters
There is no cap on the total number of connectors an organization can configure, but individual connector types enforce specific limits: 1 Webex Experience Management, 10 custom connectors, 5 Salesforce, 10 Google CCAI, 5 Webex Contact Center, 5 Bring Your Own Virtual Agent, and 10 Microsoft Dynamics 365 15. A tenant can also configure up to 100 Contact Center AI (CCAI) configuration entries 12.
Audio file storage allows up to 17250 audio files per tenant, with each file capped at 5242880 bytes and combined total storage capped at 2097152000 bytes 8.
Call recording allows up to 20 schedules per queue, while call monitoring allows up to 2000 schedules per tenant 29. Both recording and monitoring schedules can be scoped by up to 20 sites, 100 teams, or 500 agents, and monitoring schedules can additionally include up to 250 queues 29. A tenant is limited to 2000 concurrent call monitoring sessions, of which up to 1000 can be concurrent supervisor sessions 9.
Filter limits apply uniformly wherever an entity appears as a filter dimension: 250 for queues, 20 for sites, 100 for teams, 500 for agents, 50 for wrap-up codes, and 50 for tags in recording management 20.
Flow Designer self-loop limits
Cisco states that Flow Designer self-loop limits exist as a safeguard against logical errors caused by unintended loops so that such errors do not fail silently 32. Self-loop limits restrict the number of times an individual activity may loop back to itself within 1 interaction 3135:
- 0: Disconnect Contact 31
- 3: Upload Audio 33
- 10: Callback, Blind Transfer, Recording Control, Record, Call Progress Analysis, FeedbackV2, Schedule Callback 31
- 20: Start Media Stream 33
- 50: Virtual Agent, Virtual Agent V2 31
- 75: Bridged Transfer 31
- 100: Queue Contact, Queue to Agent, Set Caller ID, Collect Digits, Menu, Set Contact Priority 31
- 750: Escalate Call Distribution Group 31
- 1500: Advanced Queue Information 31
The limit of 100 for Set Contact Priority restricts loop iterations for that activity rather than establishing a priority value range 35.
WarmTransfer's reading of the sources is that the System Limits article publishes none of the Flow Designer custom-function limits held elsewhere in the corpus, omitting figures for functions per organization, memory per function, lines of code, or execution time 36. WarmTransfer's reading of the sources is that the documentation also omits limits for queue ranking, contact priority range, entry point and queue transitions per contact, agents per skill profile, proficiency skill range, and per-agent channel concurrency 37.
See also
- Webex Contact Center Flow Designer architecture
- Webex Contact Center queues teams and routing strategies
- Webex Contact Center preview and progressive outbound campaigns
- Author-written functions in Flow Designer
Applicability
Across the claims in this article, the evidence covers Cisco Webex Contact Center across cloud deployments, verified as of 2026-09-04.
What remains uncertain
Whether recording storage duration or volume is capped anywhere is not covered by any claim in this article. Whether the 500 agents per queue figure and the 1000 agent-assignment queue cap describe the same entity is not covered by any claim in this article. Whether any of these limits vary by licence tier, region, or support request is not covered by any claim in this article. Whether dialing modes other than preview and progressive share the outbound campaign limits is not covered by any claim in this article. Where Cisco intends the custom function limits to be published is not covered by any claim in this article. The maximum limits column the routing table's caption and introduction refer to is omitted from the published table 41. Why the agents-per-queue row's stated formula does not equal its stated result is not covered by any claim in this article. Whether Cisco announces changes to these limits anywhere a monitor could watch is not covered by any claim in this article. The character limits for the 17 entity Name fields are not published in the source documentation 26.
See also
Constrained by
- Webex Contact Center Flow Designer architecture — Republishes the self-loop table and omits the custom function limits
- Webex Contact Center business hours overrides and holiday listsstub — Caps business hours overrides and holiday lists at 5000 each
- Webex Contact Center preview and progressive outbound campaigns — The only campaign figures the corpus holds
- Webex Contact Center queues teams and routing strategies — Publishes the call distribution group caps the routing article omits
Referenced by
- Webex Contact Center bulk operations imports and export jobsstub — Bulk imports are the way an organisation approaches these caps
- Webex AI Agent Studio scripted and autonomous agents — Its own limits live in the AI Agent Studio guide rather than the System Limits article
- Webex Contact Center Flow Designer architecture — The Flow Designer guide names that article as canonical for numeric limits
- Author-written functions in Flow Designer — The published function limits are resource limits
- The interactions surface and scheduled call monitoring — Schedule maxima of 250 queues 100 teams 500 agents and 2000 schedules
- Webex Calling hunt groups — Member caps that depend on the routing policy
- What a Webex webhook guarantees — Query window rate limits and page bounds
Claims
| # | Claim | Status | Confidence | Verified |
|---|---|---|---|---|
| 1 | No source read in this tranche publishes a maximum agent count, entry point count or queue count for cloud Webex Contact Center in a migration context; the only concurrent agent ceiling found belongs to Webex Contact Center Enterprise. Contact Center: Transitioning from Cisco Unified Contact Center Enterprise to Webex Contact Center Deployment Guide · whole-guide scan of the March 2026 transition guide for scale figures | inference | 0.60 | 2026-09-05 |
| 2 | Webex Contact Center bulk operations limit any import file to 5,000 rows and larger datasets must be split across multiple files. Migrate Cisco Unified Contact Center Express to Webex Contact Center · Run the discovery tool for migration, step 6 | fact | 0.90 | 2026-09-05 |
| 3 | Cisco defines active limits as the operable limits for configurations to work optimally and maximum limits as the threshold limits for configurations to work at maximum capacity, and recommends staying within the maximum limit values. System limits in Webex Contact Center · paragraph immediately preceding Table 3 | fact | 0.90 | 2026-09-04 |
| 4 | The routing and queueing active limits give a maximum of 500 agents for a queue. System limits in Webex Contact Center · Table 3, Active and maximum configuration limits, maximum number of agents for a queue row | fact | 0.90 | 2026-09-04 |
| 5 | The 500-agents-per-queue limit is listed in the table's call distribution group section, which governs the team-assignment queue model, not skill-based queue assignment. System limits in Webex Contact Center · Table 3, Active and maximum configuration limits, maximum number of agents for a queue row | fact | 0.90 | 2026-09-04 |
| 6 | The routing and queueing table gives a maximum of 500 agents for a queue and defines it in the row label as maximum agents in a team multiplied by maximum teams for a call distribution group multiplied by maximum call distribution groups in the queue; using the same table's own values of 50, 50 and 20 that product is 50000, not 500. System limits in Webex Contact Center · Table 3, maximum number of agents for a queue row | fact | 0.90 | 2026-09-04 |
| 7 | The routing and queueing active limits give a maximum of 50 agents for a team and 10000 concurrent agents for a team. System limits in Webex Contact Center · Table 3, Active and maximum configuration limits, agents for a team rows | fact | 0.90 | 2026-09-04 |
| 8 | A tenant is limited to 17250 audio files, each up to 5242880 bytes, with a combined total size cap of 2097152000 bytes. System limits in Webex Contact Center · Table 1, Maximum allowed limit for tenants, Audio file rows | fact | 0.90 | 2026-09-04 |
| 9 | A tenant is limited to 2000 concurrent call monitoring sessions, of which up to 1000 can be concurrent supervisor sessions. System limits in Webex Contact Center · Table 1, Maximum allowed limit for tenants, Call monitoring rows; Table 3 concurrent calls for call monitoring row | fact | 0.90 | 2026-09-04 |
| 10 | The routing and queueing active limits give a maximum of 100 per capacity-based team, 50 capacity-based teams for an organisation, and 5000 concurrent calls for capacity-based teams, which the table derives as the product of the first 2 figures. System limits in Webex Contact Center · Table 3, Active and maximum configuration limits, capacity-based team rows | fact | 0.90 | 2026-09-04 |
| 11 | A tenant is limited to 100 capacity-based teams in total, of which at most 50 can be active and up to 100 can be inactive. System limits in Webex Contact Center · Table 1, Maximum allowed limit for tenants, Teams capacity based rows | fact | 0.60 | 2026-09-04 |
| 12 | A tenant is limited to 100 Contact Center AI configuration entries. System limits in Webex Contact Center · Table 1, Maximum allowed limit for tenants, CCAI Config row | fact | 0.90 | 2026-09-04 |
| 13 | The routing and queueing active limits give a maximum of 50 teams per call distribution group, 20 call distribution groups in a queue, and 250 teams in a queue across all call distribution groups. System limits in Webex Contact Center · Table 3, Active and maximum configuration limits, call distribution group rows | fact | 0.90 | 2026-09-04 |
| 14 | A footnote on the users row states that Webex Contact Center supports unlimited concurrent agents at the organisation level, so the 20000 figure caps configured user records rather than simultaneous agent sessions. System limits in Webex Contact Center · Table 1, Maximum allowed limit for tenants, Users row footnote | fact | 0.90 | 2026-09-04 |
| 15 | There is no maximum on the total number of connectors an organisation can configure, but each connector type has its own maximum: 1 Webex Experience Management connector, 10 custom connectors, 5 Salesforce, 10 Google CCAI, 5 Webex Contact Center, 5 Bring Your Own Virtual Agent and 10 Microsoft Dynamics 365. System limits in Webex Contact Center · Table 1, Maximum allowed limit for tenants, Number of Connectors row | fact | 0.90 | 2026-09-04 |
| 16 | A tenant is limited to 11000 inbound contact service queues and 5000 outbound contact service queues. System limits in Webex Contact Center · Table 1, Maximum allowed limit for tenants, Contact service queue rows | fact | 0.90 | 2026-09-04 |
| 17 | The maximum auto-wrap-up timeout configurable in a desktop profile is 600000 milliseconds. System limits in Webex Contact Center · Table 1, Maximum allowed limit for tenants, Desktop profiles maximum auto-wrapup timeout row | fact | 0.90 | 2026-09-04 |
| 18 | A tenant is limited to 15000 dialed numbers overall and 500 dialed numbers per entry point. System limits in Webex Contact Center · Table 1, Maximum allowed limit for tenants, Dialed numbers rows | fact | 0.90 | 2026-09-04 |
| 19 | A Webex Contact Center tenant is limited to 6000 active entry points and 1000 active outdial entry points. System limits in Webex Contact Center · Table 1, Maximum allowed limit for tenants, Entry points and Outdial entry points rows | fact | 0.90 | 2026-09-04 |
| 20 | The filter limits table publishes the same ceilings wherever an entity type appears as a filter dimension: 250 for queues, 20 for sites, 100 for teams and 500 for agents, with 50 for wrap-up codes and 50 for tags in recording management. System limits in Webex Contact Center · Table 2, Maximum System Limits for Filters | fact | 0.90 | 2026-09-04 |
| 21 | A tenant is limited to 5000 active global variables. System limits in Webex Contact Center · Table 1, Maximum allowed limit for tenants, Global variables row | fact | 0.90 | 2026-09-04 |
| 22 | The routing and queueing active limits give a maximum of 10 skill requirements for a contact. System limits in Webex Contact Center · Table 3, Active and maximum configuration limits, maximum skill requirements for a contact row | fact | 0.90 | 2026-09-04 |
| 23 | Webex Contact Center's system limits separately cap a queue at a maximum of 50 skill requirements, a different quantity from the 10 skill requirements permitted per contact. System limits in Webex Contact Center · Table 3, Active and maximum configuration limits, maximum skill requirements for a contact row | fact | 0.90 | 2026-09-04 |
| 24 | Maximum time in queue caps at 86400 seconds for telephony and chats, 604800 seconds for digital and 1209600 seconds for email. System limits in Webex Contact Center · Table 1, Maximum allowed limit for tenants, Contact service queue maximum time in queue rows | fact | 0.90 | 2026-09-04 |
| 25 | The routing and queueing active limits give a maximum time in a voice queue of 1 day. System limits in Webex Contact Center · Table 3, Active and maximum configuration limits, maximum time in a queue voice row | fact | 0.90 | 2026-09-04 |
| 26 | The article states that 17 named entities have a maximum limit on the number of characters usable in their Name field and then lists those entities without publishing any character count, so the limit it announces is not stated anywhere in the article. System limits in Webex Contact Center · unnamed table following Table 2 | fact | 0.90 | 2026-09-04 |
| 27 | The routing and queueing active limits give a maximum of 100 preview and progressive outbound campaigns for an organisation and 500 agents in a campaign. System limits in Webex Contact Center · Table 3, Active and maximum configuration limits, outbound campaign rows | fact | 0.90 | 2026-09-04 |
| 28 | A tenant can have up to 500 queues using the skill-based routing type and up to 10500 queues using the team-based routing type, and a queue's skill requirements are capped at 50. System limits in Webex Contact Center · Table 1, Maximum allowed limit for tenants, Queues rows | fact | 0.90 | 2026-09-04 |
| 29 | A tenant is limited to 20 call recording schedules per queue and 2000 call monitoring schedules, and both recording and monitoring schedules can be scoped by at most 20 sites, 100 teams or 500 agents, with monitoring schedules additionally scoped by up to 250 queues. System limits in Webex Contact Center · Table 1, Maximum allowed limit for tenants, Call recording schedule and Call monitoring Schedule rows | fact | 0.90 | 2026-09-04 |
| 30 | A tenant is limited to 200 global routing strategy entries and 500 global entry points referenced by routing strategies, with at most 20 routing strategies per entry point. System limits in Webex Contact Center · Table 1, Maximum allowed limit for tenants, Routing Strategy rows | fact | 0.90 | 2026-09-04 |
| 31 | The System Limits article publishes the same Flow Designer self-loop limits as the Flow Designer article: 0 for Disconnect Contact, 10 for Callback, Blind Transfer, Recording Control, Record, Call Progress Analysis, FeedbackV2 and Schedule Callback, 50 for Virtual Agent and Virtual Agent V2, 75 for Bridged Transfer, 100 for Queue Contact, Queue to Agent, Set Caller ID, Collect Digits, Menu and Set Contact Priority, 750 for Escalate Call Distribution Group and 1,500 for Advanced Queue Information. System limits in Webex Contact Center · Flow Designer self-loop limits table | fact | 0.90 | 2026-09-04 |
| 32 | Cisco states that the self-loop limits exist as a safeguard against logical errors caused by unintended loops, so that such errors do not fail silently. System limits in Webex Contact Center · paragraph introducing the self-loop limits table | fact | 0.90 | 2026-09-04 |
| 33 | The System Limits article's self-loop table adds 2 activities the Flow Designer article did not supply to the corpus: Upload Audio with a self-loop limit of 3 and Start Media Stream with a self-loop limit of 20. System limits in Webex Contact Center · Flow Designer self-loop limits table, Upload Audio and Start Media Stream rows | fact | 0.90 | 2026-09-04 |
| 34 | Contact service queue service level thresholds cap at 86400 seconds for telephony and chat, 604800 seconds for digital and 1209600 seconds for email. System limits in Webex Contact Center · Table 1, Maximum allowed limit for tenants, Contact service queue service level threshold rows | fact | 0.90 | 2026-09-04 |
| 35 | The Set Contact Priority row in the self-loop table gives a limit of 100, which is a cap on how many times that activity may loop back to itself within 1 interaction, not a priority value range. System limits in Webex Contact Center · Flow Designer self-loop limits table, Set Contact Priority row | fact | 0.90 | 2026-09-04 |
| 36 | The System Limits article publishes none of the Flow Designer custom-function limits the corpus holds: it contains no figure for functions per organisation, memory per function, lines of code or execution time, and does not use the words function, memory or execution in that sense anywhere. System limits in Webex Contact Center · whole document, absence confirmed by search | inference | 0.60 | 2026-09-04 |
| 37 | The System Limits article publishes nothing about queue ranking, contact priority range, entry point and queue transitions per contact, agents per skill profile, proficiency skill range or per-agent channel concurrency, all of which the corpus holds from the routing and Flow Designer articles. System limits in Webex Contact Center · whole document, absence confirmed by search | inference | 0.60 | 2026-09-04 |
| 38 | A tenant is limited to 300 active sites. System limits in Webex Contact Center · Table 1, Maximum allowed limit for tenants, Sites row | fact | 0.90 | 2026-09-04 |
| 39 | A tenant is limited to 9000 skill profiles, and a skill profile can hold at most 50 skills. System limits in Webex Contact Center · Table 1, Maximum allowed limit for tenants, Skill profiles rows; Table 3 maximum skills for a skill profile row | fact | 0.90 | 2026-09-04 |
| 40 | A tenant is limited to 1000 active skills, with a skill's text value capped at 200, its text length at 50, its enum value list at 200 entries and its enum length at 50. System limits in Webex Contact Center · Table 1, Maximum allowed limit for tenants, Skills rows | fact | 0.60 | 2026-09-04 |
| 41 | The routing and queueing table is captioned Active and maximum configuration limits and its introduction directs the reader to a Maximum Limits column, but the rendered table has only 2 column headings, Configurations and Active Limits, so no maximum limit is published for any row in it. System limits in Webex Contact Center · Table 3 caption and table header | fact | 0.90 | 2026-09-04 |
| 42 | A tenant is limited to 3000 agent-based teams, and an agent-based team can hold at most 100 users. System limits in Webex Contact Center · Table 1, Maximum allowed limit for tenants, Teams rows | fact | 0.90 | 2026-09-04 |
| 43 | A tenant is limited to 1500 active user profiles, and a user profile's access rights are capped at 20 sites, 100 teams, 50 entry points and 250 queues. System limits in Webex Contact Center · Table 1, Maximum allowed limit for tenants, User profiles rows | fact | 0.90 | 2026-09-04 |
| 44 | A tenant is limited to 20000 active users, of which up to 3000 can be supervisors. System limits in Webex Contact Center · Table 1, Maximum allowed limit for tenants, Users rows | fact | 0.90 | 2026-09-04 |
| 45 | Neither the Microsoft Dynamics 365 nor the Microsoft Teams article publishes a maximum number of connectors of its type. Configure Microsoft Dynamics 365 connector for Webex Contact Center · Both articles, read in full | fact | 0.90 | 2026-09-05 |
| 46 | Two of the connector articles publish a per-type maximum: 10 custom connectors and 5 Salesforce connectors, with 1 Webex Experience Management connector. Configure custom connector for Webex Contact Center · Per-type articles, stated maxima | fact | 0.90 | 2026-09-05 |
| 47 | The call queue publishes a default alongside the bound for several settings, among them a 30 second comfort message bypass, 3 call-back retries 5 minutes apart, a 60 second bounce time and a 30 second alert on hold. Configure Call Queue · Configure Call Queue, timer settings | fact | 0.90 | 2026-09-05 |
| 48 | Other call queue settings publish a bound and no default, among them the number of calls in queue, an overflow wait of up to 7200 seconds, a bounced call ring count of up to 20, 100 supervisors and 100 dialled numbers. Configure Call Queue · Configure Call Queue, queue and overflow settings | fact | 0.90 | 2026-09-05 |
| 49 | Functions carry 6 published limits: 200 functions per organisation, 128 MB of memory per function, 5000 lines of code, 5 seconds of execution, 10 input variables and 1 JSON output variable. Build and manage flows with Flow Designer · Create and manage functions, Important considerations and FAQs | fact | 0.90 | 2026-09-05 |
| 50 | The self-loop limit tables in the Flow Designer article and the system limits article agree on every value across all 21 activities. System limits in Webex Contact Center · Self-loop limits for Flow Designer activities table, compared cell by cell against the Flow Designer copy | fact | 0.90 | 2026-09-05 |
| 51 | The reconciliation and records interfaces cap a query window at 12 hours, rate-limit a partner to one initial request a minute per token scope with up to 10 further paginated requests, and cap a records page between 500 and 5000 with a default of 5000. Detailed call records webhook for Webex Calling in Partner Hub · Detailed call records webhook, Partner API endpoints and API Parameters | fact | 0.90 | 2026-09-05 |
| 52 | 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 |
| 53 | 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 |
| 54 | A configuration reading tool covers entry points, business hours, dial plans, dial numbers, skill profiles, auxiliary codes, teams, users, agent profiles, outdial identifiers and contact service queues, supports list and get operations, and is marked read-only. Contact Center MCP Server · Tools table, administrative configuration row | fact | 0.90 | 2026-09-05 |
| 55 | The call park group import file is capped at 1000 rows in two places and a bulk creation step describes a maximum of more than 10000 rows for each file. Manage call park in Control Hub · Manage call park in Control Hub, Bulk manage call park groups and Bulk add call park groups step 4 | disputed | 0.60 | 2026-09-05 |
| 56 | A location may hold up to 100 call park extensions, and a bulk upload may add up to 1000 extensions at a time. Manage call park in Control Hub · Manage call park in Control Hub, Add call park extensions and Add multiple call park extensions step 4 | fact | 0.90 | 2026-09-05 |
| 57 | The maximum number of agents assignable to an agent-based queue is 1000. Supervise and manage Contact Center queues · Supervise and manage Contact Center queues, Assign agents to queue | fact | 0.90 | 2026-09-05 |
| 58 | Routing allows a contact 25 entry point and queue transitions and 20 successful routing attempts, and queue ranking may be set on at most 50 queues. Understand Routing and Queueing in Webex Contact Center · Contact Routing and Queue Ranking | fact | 0.90 | 2026-09-05 |
| 59 | A monitoring schedule names at least 1 queue up to 250, at least 1 team up to 100, and either all agents or up to 500 chosen by hand, spans at most 6 months, and a tenant may hold 2000 schedules. Schedule call monitoring · Schedule call monitoring, limits | fact | 0.90 | 2026-09-05 |
| 60 | The stock reports carry a 13-month reporting window, default caps of 100000 grid rows and 10000 chart rows, a 30000-record cap on the survey response report, and a time picker at 15-minute granularity. Cisco Webex Contact Center Analyzer User Guide · Stock reports chapter, limits | fact | 0.90 | 2026-09-05 |
| 61 | The user voicemail article publishes 5 settings with a bound and no default: message deletion after 1 to 180 days, a passcode change window of 1 to 7 days, passcode expiry of 15 to 180 days, a passcode history of 10 to 24 and a passcode length of 6 to 30. Configure and manage voicemail settings for a Webex Calling user · Configure and manage voicemail settings, passcode and storage settings | fact | 0.90 | 2026-09-05 |
Sources
Build and manage flows with Flow Designer
Cisco Webex Contact Center Analyzer User Guide
Configure and manage voicemail settings for a Webex Calling user
Configure Call Queue
Configure custom connector for Webex Contact Center
Configure Microsoft Dynamics 365 connector for Webex Contact Center
Contact Center MCP Server
Contact Center: Transitioning from Cisco Unified Contact Center Enterprise to Webex Contact Center Deployment Guide
Detailed call records webhook for Webex Calling in Partner Hub
Manage call park in Control Hub
Manage hunt groups in Control Hub
Migrate Cisco Unified Contact Center Express to Webex Contact Center
Schedule call monitoring
Supervise and manage Contact Center queues
System limits in Webex Contact Center
Understand Routing and Queueing in Webex Contact Center
Cite this page
APA
WarmTransfer. (2026, September 5). Webex Contact Center system limits reference. WarmTransfer. https://warmtransfer.net/knowledge/webex-cc-system-limits
BibTeX
@misc{warmtransfer-webex-cc-system-limits,
title = {Webex Contact Center system limits reference},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/webex-cc-system-limits},
note = {Verified 2026-09-05}
}