Articles on: Troubleshooting

How does the Crisp chatbox handle high website traffic

Understand how the Crisp chatbox behaves on high-traffic websites and what changes when traffic reaches safety thresholds.


The Crisp chatbox is designed to scale on busy websites. At high volume, Crisp can adjust some real-time behaviors to protect performance while keeping visitor messaging available.


In this article:



How high-traffic mode works


On regular traffic, the Crisp chatbox opens a WebSocket connection for visitors so your team can see live visitors, start real-time conversations, and use features such as MagicBrowse.


On very busy websites, opening a real-time connection for every visitor can be expensive and less useful. Crisp can therefore reduce some real-time behavior while keeping the chatbox available for messaging.


High-traffic mode is rare. Most Crisp workspaces never reach it, and temporary traffic spikes only trigger it while the spike continues.


What visitors experience


Visitors still see the chatbox. If they click it, they may briefly see a loading state while the WebSocket connection is established. Once connected, the chatbox behaves normally for that visitor.


What operators experience


Some live visitor visibility can be less immediate. Operator online status in the chatbox may refresh less frequently, but core messaging remains available.


In high-traffic mode, operator online status can take longer to update. Other chatbox features such as $crisp JavaScript SDK calls and triggers are designed to continue working unless safety mode is reached.



High-traffic thresholds


High-traffic thresholds are counted over short rolling periods. Reaching a threshold does not remove the chatbox from your website; it only changes how Crisp optimizes real-time connections.


High-traffic thresholds:

  • Essentials and Plus paid plans → 1,000 chatbox displays per 5 minutes
  • Essentials and Plus trial plans → 250 chatbox displays per 5 minutes
  • Mini plan → 250 chatbox displays per 5 minutes
  • Free plan → 50 chatbox displays per 5 minutes


A visitor who loads the chatbox and keeps using a single-page app without reloading can still count as an active chatbox display while they remain active.


Reaching a high-traffic threshold does not disable the chatbox. Visitors can still open it and message your team.



Very high-traffic safety mode


If a website receives an unusually large number of visitors, Crisp can switch to safety mode to protect the platform and your website experience.


In safety mode, visitors do not open a WebSocket connection unless they click the chatbox to start a chat or already have an ongoing or past chat session. This means you may not see all real-time visitors browsing the website, but messaging still works.


Safety mode thresholds:

  • Essentials and Plus plans → 2,000 chatbox displays per 5 minutes
  • Mini plan → 500 chatbox displays per 5 minutes
  • Free plan → 100 chatbox displays per 5 minutes


Triggers and other automated messaging features can be temporarily disabled while safety mode is active, because those features depend on live connection and storage activity.


High-traffic safety mode alert


To check whether safety mode is active, open Crisp and go to the Visitors section. Crisp shows an alert when this mode is enabled.



What to do if you reach these limits


In most cases, you do not need to do anything. The system adapts automatically, and the limits are temporary. Once traffic drops below the threshold, normal real-time behavior resumes.


For planned high-traffic events:

  • Use automation carefully → avoid aggressive trigger campaigns during major traffic spikes
  • Prepare your team → expect visitor lists and online states to be less immediate
  • Monitor conversations → messaging remains the priority, so focus on active chats
  • Contact support for unusual cases → share traffic expectations if you anticipate exceptional sustained volume


Updated on: 03/05/2026

Was this article helpful?

Share your feedback

Cancel

Thank you!