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

Claims citing this source

• 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. fact in context
• The routing and queueing active limits give a maximum of 500 agents for a queue. fact 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. fact 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. fact in context
• The routing and queueing active limits give a maximum of 50 agents for a team and 10000 concurrent agents for a team. fact in context
• A tenant is limited to 17250 audio files, each up to 5242880 bytes, with a combined total size cap of 2097152000 bytes. fact in context
• A tenant is limited to 2000 concurrent call monitoring sessions, of which up to 1000 can be concurrent supervisor sessions. fact 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. fact 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. fact in context
• A tenant is limited to 100 Contact Center AI configuration entries. fact 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. fact 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. fact 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. fact in context
• A tenant is limited to 11000 inbound contact service queues and 5000 outbound contact service queues. fact in context
• The maximum auto-wrap-up timeout configurable in a desktop profile is 600000 milliseconds. fact in context
• A tenant is limited to 15000 dialed numbers overall and 500 dialed numbers per entry point. fact in context
• A Webex Contact Center tenant is limited to 6000 active entry points and 1000 active outdial entry points. fact 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. fact in context
• A tenant is limited to 5000 active global variables. fact in context
• The routing and queueing active limits give a maximum of 10 skill requirements for a contact. fact 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. fact in context
• Maximum time in queue caps at 86400 seconds for telephony and chats, 604800 seconds for digital and 1209600 seconds for email. fact in context
• The routing and queueing active limits give a maximum time in a voice queue of 1 day. fact 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. fact 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. fact 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. fact 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. fact 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. fact 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. fact 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. fact 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. fact 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. fact 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. fact 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. inference 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. inference in context
• A tenant is limited to 300 active sites. fact in context
• A tenant is limited to 9000 skill profiles, and a skill profile can hold at most 50 skills. fact 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. fact 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. fact in context
• A tenant is limited to 3000 agent-based teams, and an agent-based team can hold at most 100 users. fact 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. fact in context
• A tenant is limited to 20000 active users, of which up to 3000 can be supervisors. fact 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. fact 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. fact 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}
}