Skip to content
Chatbotscape
Editorial flat-vector illustration for How to Set Live Chat Concurrency Limits
Published 9 min read

How to Set Live Chat Concurrency Limits

Quick answer: Start from what your agents already do, not from a number someone else published. Measure how many chats each agent really handles at once and how long each chat stays open. Set a starting limit per channel or team, close to that real level, configure it in your help desk, and decide what counts towards it and what visitors see when everyone is full. Then change it by one for two weeks and compare handle time, first response time, satisfaction and chats per agent-hour. Keep the setting that gives customers faster answers, not just the one that gives agents more chats.

Step 1: Measure the concurrency and handle time you have now

Export two to four recent weeks of chats with the agent, the time the chat was assigned and the time it was closed. From that, work out two numbers per agent and per team:

  • Average concurrency. Add up the minutes chats were assigned to the agent and divide by the minutes the agent was available for chat. An agent available for 16 hours over two days who handled 1,632 chat-minutes has an average concurrency of 1,632 ÷ 960 = 1.7.
  • Minutes per chat at each level. Group chats by how many others the agent had open at the time, and compare how long they stayed open. This is your average handle time split by load.

If your help desk only reports the configured limit, not the real average, this export is the only way to see the gap. Call Centre Helper's staffing advice rests on the same gap: it uses a factor of 1.7 for agents allowed two chats and 2.5 for three, because agents are not always at their maximum.

Step 2: Pick a starting limit by type of chat

There is no standard number. HubSpot's default limit is 3 and Call Centre Helper mentions 3 or 4 as an example, but none of the sources we read recommends a figure for every team. Choose a starting point from the work:

Type of chatWhat pulls the limit downWhat lets it go up
Short questions (order status, opening hours)Customers who reply instantly and expect the sameCanned responses and a bot that collects details first
Account or billing problemsChecking several systems per replyGood internal search and agent assist
Technical troubleshootingLong back-and-forth, screenshots, testingCustomers who go quiet while they try a fix
Sales and pre-purchaseA lost reply can mean a lost saleSimple, repeatable questions
Asynchronous messaging (WhatsApp, Messenger, in-app)Bursts when many customers reply at onceCustomers who answer hours later

A practical rule: start at your current peak concurrency for that team, rounded down, not above it. New agents usually start one lower than experienced ones.

Step 3: Configure the limit in your help desk

Each tool names and places the setting differently. As documented on 17 November 2026:

ToolWhereScope and range
ZendeskAdmin Center > Objects and rules > Omnichannel routing > Capacity rulesOne rule per agent; a default rule covers new agents. Messaging capacity up to 20, applied to messaging and live chat separately
IntercomWorkload management settings (balanced assignment)Workspace default, per-teammate override, and optional per-inbox limits checked on top. Expert plan
HubSpotSettings > Account Defaults > User Defaults > Enable capacity limitAccount-wide; default 3, up to 99. Service Hub Enterprise; Super Admin needed
LiveChatTeam > select agent > Change chat limitPer agent; repeat for each agent

Intercom's documentation gives a useful example of combined limits: a teammate with a total limit of 10 and a limit of 3 on one inbox receives at most 3 conversations from that inbox and up to 7 from others. That lets you keep a demanding queue at a lower load without lowering the agent's whole limit. In Zendesk, an agent can belong to only one capacity rule, so make one rule per group of agents rather than per channel mix. Inbox and assignment features differ by tool: see our Intercom review and Tidio review, and Zendesk and LiveChat.

Step 4: Decide what counts towards the limit

The same limit behaves differently depending on what is counted:

  • Quiet conversations. In Zendesk, inactive messaging conversations count only if an admin turns on "Count inactive conversations towards an agent's capacity", which is off by default. If customers on messaging reply hours later, leaving them out lets agents keep taking new chats.
  • Other channels. Intercom counts open conversations across the whole workspace, including channels without their own limit, such as WhatsApp and SMS. Zendesk counts email, messaging and calls under separate limits.
  • Manual assignment. Zendesk and Intercom both note that assigning by hand, or pulling a conversation, can push an agent past the limit. Tell managers when overriding is acceptable, or the limit stops meaning anything.
  • Tickets. Intercom counts tickets only if they are included in workload management.

Write down the rule you choose so reports are read the same way each week.

Step 5: Plan what happens when everyone is full

When every agent is at the limit, new chats wait. Decide what visitors see:

  • LiveChat puts visitors in a queue and can show their position and estimated wait in the widget message.
  • HubSpot leaves new chats unassigned and lets each chat channel show a wait message, hide the launcher, or change nothing at maximum capacity.
  • Intercom holds conversations in the team inbox until a teammate has room.

A bot is useful here: it can answer the simple questions while visitors wait, or take details so the agent starts faster after the human handoff. The chatbot handoff design guide covers what to collect. Watch the chat queue and your abandonment rate as you change the limit; a lower limit with a long queue may serve customers worse than a slightly higher one.

Step 6: Test one change and keep the better setting

Change the limit by one for one team, keep everything else the same, and run it for two weeks. Compare before and after:

MeasureWhy it matters
Chats per agent-hourThe capacity you gained
Minutes per chatHow much each chat stretched
First response time and gaps between repliesWhat customers feel
CSATWhether customers noticed slower replies
Share of chats within your SLAWhether the promise still holds

Then put the new average concurrency, not the limit, into your staffing forecast. Call Centre Helper notes that handle time rises with concurrency, so a higher limit gives less extra capacity than it appears to.

Check the arithmetic

An invented example, not a measurement. A support team's average concurrency is 1.7 at a limit of 2, with chats open for 12 minutes. It tries a limit of 3 for two weeks: average concurrency rises to 2.4, but chats now stay open 16 minutes.

SettingCalculationChats per agent-hour
Limit 21.7 × 60 ÷ 128.5
Limit 32.4 × 60 ÷ 169.0, about 6% more
Limit 3 with a bot collecting details first2.2 × 60 ÷ 1310.2, about 20% more than limit 2

At limit 3 alone, each customer's chat takes a third longer for about 6 percent more capacity, which may not be worth it if satisfaction drops. In the third row, the team keeps limit 3 but adds a bot that collects the order number and issue before handoff; minutes per chat fall to 13 and the gain grows. The numbers are made up to show the method; your own two-week test is the only reliable answer.

Common mistakes

  • Copying a published number instead of measuring your own concurrency and handle time.
  • Using the limit in staffing maths when agents actually average fewer chats.
  • One limit for every kind of chat, so complex queues are overloaded and simple ones under-used.
  • Ignoring what counts, such as quiet messaging threads or other channels filling the limit.
  • Judging only by chats per hour, without checking reply gaps and satisfaction.

FAQ

How many chats should a live chat agent handle at once? As many as they can while keeping replies within your target and satisfaction steady. Measure it: HubSpot's default is 3 and Call Centre Helper mentions 3 or 4 as an example, but neither is a standard.

How do I set the chat limit in Zendesk, Intercom, HubSpot or LiveChat? Zendesk uses capacity rules under omnichannel routing; Intercom uses assignment limits under balanced assignment; HubSpot uses the chat capacity limit in user defaults; LiveChat sets a chat limit per agent in the Team section. See the table in step 3.

Does a higher concurrency limit lower customer satisfaction? It can, because customers wait longer between replies. Test a change for two weeks and compare CSAT and reply gaps, not just chats per hour.

Should messaging have a different limit from live chat? Often, yes. Customers on WhatsApp or in-app messaging may reply hours later, so counting quiet threads can block new chats. Zendesk leaves inactive messaging conversations out by default.

What happens to new chats when every agent is at the limit? They wait in a queue or the team inbox, or stay unassigned, depending on the tool. Decide what visitors see and let a bot answer simple questions in the meantime.

Should new agents have the same limit? Usually not. Start new agents one lower and raise it as their handle time settles.

Sources