System limits in Webex Contact Center

Publisher

Cisco Systems, Inc. (Webex Help Center)

URL

https://help.webex.com/en-us/article/n7s6ed7/System-limits-in-Webex-Contact-Center

Published

2026-08-18

Updated

unknown

Accessed

2026-09-05

HTTP status

200

License

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

Source notes citing this source

• Webex Contact Center caps the queue service level threshold at 86400 seconds for telephony and chat, 604800 for digital and 1209600 for email. in context
• Webex Contact Center limits an individual audio file to 5,242,880 bytes and total audio storage to 2,097,152,000 bytes. in context
• Webex Contact Center documents an active global variable limit of 5000 per tenant. in context
• Webex Contact Center enforces per-activity self-loop limits in flows as a safeguard against unintended loops, with documented values including 100 for Menu, 100 for Collect Digits, 10 for Blind Transfer and 50 for Virtual Agent. in context
• Webex Contact Center allows 3000 address books, 6000 entries per address book and 100000 address book entries in total. in context
• Webex Contact Center allows 400 Outdial ANI lists, 200 entries per list and 2000 Outdial ANI entries in total. in context
• Webex Contact Center allows 9000 skill profiles per tenant and 50 skills per skill profile. in context
• Webex Contact Center allows 1000 active skills per tenant. in context
• Webex Contact Center allows 20000 active users, 300 active sites and 3000 agent-based teams per tenant. in context
• The Webex Contact Center system limits page states no limit specific to bulk operations, so the per-job row, file size and concurrency caps are documented only in the Bulk Operations pages. inferred in context
• A tenant can have at most 5000 Business Hours entities. in context
• One holiday list can hold at most 150 holidays. in context
• A tenant can have at most 5000 holiday lists. in context
• One Overrides entity can hold at most 100 override entries. in context
• A tenant can have at most 5000 Overrides entities. in context
• The system limits table gives a maximum of 50 for the Working hours attribute of a Business Hours entity. in context
• The 50 Working hours limit most likely caps the number of shifts in one business-hours entity, because the admin UI models working hours as a list of shifts. inferred in context
• The current Webex Contact Center system limits article states unlimited concurrent agents at the organisation level and does not distinguish limits by media platform. in context
• Webex Contact Center multi-tenant attachment size caps appear to be governed by Webex Engage tenant settings rather than a published platform limit, because the System limits article lists audio file limits but no digital attachment limits. inferred in context
• The Webex Contact Center system limits page (updated 18 August 2026) appears to list no Functions-specific limits such as execution timeout, memory or code size. Its only flow-related limits seen are the self-loop limits for Flow Designer activities. inferred in context
• System-enforced self-loop limits apply to Flow Designer activities, for example Queue Contact 100, Blind Transfer 10 and Virtual Agent V2 50. in context
• The limits are 6,000 active entry points and 1,000 outdial entry points. in context
• The limits are 2,000 concurrent call monitoring sessions, 1,000 concurrent supervisor sessions and 3,000 supervisors. in context
• The queue limits are 500 for the skill-based routing type and 10,500 for the team-based routing type. in context
• A queue can have at most 20 call recording schedules. in context
• Flow Designer enforces self-loop limits per activity: 100 for Queue Contact, 1,500 for Advanced Queue Information and 750 for Escalate Call Distribution Group. in context
• The limits are 300 active sites, 3,000 agent-based teams, 50 active capacity-based teams and 50 teams per user. in context
• The limits are 1,000 active skills, 9,000 skill profiles and at most 50 skills in one skill profile. in context
• The system limit is 20,000 active users per Webex Contact Center organization. in context
• Apart from the self-loop limits, the WxCC system-limits article (updated 2026-08-18) lists no callback-specific limit, such as pending callbacks per queue. inferred in context
• The Flow Designer self-loop limit for the Schedule Callback activity is 10. in context
• The Flow Designer self-loop limit for the Callback activity is 10. in context
• The system maximum for Maximum time in queue on telephony queues is 86400 seconds (one day). in context
• The Callback activity has a Flow Designer self-loop limit of 10. in context
• Webex Contact Center allows up to 200 active desktop layouts. in context
• Webex Contact Center limits chat maximum time in queue and chat service level threshold to 86400 seconds (24 hours). in context
• Webex Contact Center limits the Digital media type's maximum time in queue and service level threshold to 604800 seconds (7 days). in context
• Webex Contact Center limits email maximum time in queue and email service level threshold to 1209600 seconds (14 days). in context
• The Webex Contact Center system limits page, as read on 2026-10-02, publishes no per-queue limit on queued chat or email tasks and no per-agent digital task maximum beyond multimedia profile settings. inferred in context
• A contact can carry at most 10 skill requirements, and a queue can hold at most 20 Call Distribution Groups and 250 teams across all its Call Distribution Groups. in context
• Advanced Queue Information has the highest documented self-loop limit, 1500; Escalate Call Distribution Group has 750. in context
• The self-loop limit for the Disconnect Contact activity is 0. in context
• The self-loop limit is 100 for Menu, CollectDigit, Set Caller ID and Set Contact Priority; 50 for Virtual Agent and Virtual Agent V2; 20 for Start Media Stream; and 3 for Upload Audio. in context
• Webex Contact Center enforces a self-loop limit of 100 on the Queue Contact activity and 100 on Queue To Agent. in context
• The self-loop limit is 10 for Callback, Blind Transfer, Schedule Callback, Record, Recording Control, Call Progress Analysis and FeedbackV2, and 75 for Bridged Transfer. in context
• The Webex Contact Center system limits table sets a maximum of 6000 active entry points per tenant. in context
• The Webex Contact Center system limits table allows at most 500 dialed numbers per entry point and 15000 dialed number to entry point mappings per tenant. in context
• The Webex Contact Center system limits article as fetched gives no calls-per-second or per-entry-point concurrent call capacity figure. inferred in context
• The system limits page lists a maximum of 10 dial plans per desktop profile. in context
• The system limits page lists a maximum of 400 outdial ANI lists and 200 entries per outdial ANI list. in context
• The system limits page lists a maximum of 1,000 active outdial entry points. in context
• Webex Contact Center allows a maximum of 5000 active global variables per tenant. in context
• Webex Contact Center allows a maximum of 200 active desktop layouts. in context
• 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. in context
• The routing and queueing active limits give a maximum of 500 agents for a queue. in context
• 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. in context
• 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. in context
• The routing and queueing active limits give a maximum of 50 agents for a team and 10000 concurrent agents for a team. in context
• A tenant is limited to 17250 audio files, each up to 5242880 bytes, with a combined total size cap of 2097152000 bytes. in context
• A tenant is limited to 2000 concurrent call monitoring sessions, of which up to 1000 can be concurrent supervisor sessions. in context
• 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. in context
• 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. in context
• A tenant is limited to 100 Contact Center AI configuration entries. in context
• 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. in context
• 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. in context
• 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. in context
• A tenant is limited to 11000 inbound contact service queues and 5000 outbound contact service queues. in context
• The maximum auto-wrap-up timeout configurable in a desktop profile is 600000 milliseconds. in context
• A tenant is limited to 15000 dialed numbers overall and 500 dialed numbers per entry point. in context
• A Webex Contact Center tenant is limited to 6000 active entry points and 1000 active outdial entry points. in context
• 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. in context
• A tenant is limited to 5000 active global variables. in context
• The routing and queueing active limits give a maximum of 10 skill requirements for a contact. in context
• 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. in context
• Maximum time in queue caps at 86400 seconds for telephony and chats, 604800 seconds for digital and 1209600 seconds for email. in context
• The routing and queueing active limits give a maximum time in a voice queue of 1 day. in context
• 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. in context
• 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. in context
• 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. in context
• 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. in context
• 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. in context
• 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. in context
• 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. in context
• 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. in context
• Contact service queue service level thresholds cap at 86400 seconds for telephony and chat, 604800 seconds for digital and 1209600 seconds for email. in context
• 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. in context
• 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. inferred in context
• 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. inferred in context
• A tenant is limited to 300 active sites. in context
• A tenant is limited to 9000 skill profiles, and a skill profile can hold at most 50 skills. in context
• 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. in context
• 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. in context
• A tenant is limited to 3000 agent-based teams, and an agent-based team can hold at most 100 users. in context
• 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. in context
• A tenant is limited to 20000 active users, of which up to 3000 can be supervisors. in context
• Webex Contact Center supports at most 2,000 concurrent call monitoring sessions. in context
• The call monitoring dashboard filters are limited to 250 queues, 100 teams and 500 agents. in context
• Call monitoring schedule filters also allow at most 20 sites. in context
• Webex Contact Center supports at most 1,000 concurrent supervisor sessions and 3,000 supervisor users. in context
• The published system limits list 6000 entries for an address book and 100000 total address book entries. in context
• The published system limits list 150 transfer targets and 10 dial plans for a desktop profile. in context
• The self-loop limit tables in the Flow Designer article and the system limits article agree on every value across all 21 activities. in context
• The system limits article contains no occurrence of the word function anywhere in its text, tables or headings, so it corroborates none of the published function limits. in context

Cite this source record

APA

WarmTransfer. (2026, August 18). System limits in Webex Contact Center. WarmTransfer. https://warmtransfer.net/knowledge/sources/cisco-help-n7s6ed7-wxcc-system-limits

BibTeX

@misc{warmtransfer-cisco-help-n7s6ed7-wxcc-system-limits,
  title  = {System limits in Webex Contact Center},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/sources/cisco-help-n7s6ed7-wxcc-system-limits},
  note   = {Cisco Systems, Inc. (Webex Help Center), accessed 2026-09-05}
}