You have a high-traffic website and you're wondering if the Crisp chatbox can scale to your traffic? This article answers your questions!

The Crisp chatbox is designed to scale to high-traffic websites. Crisp runs on a distributed (ie. worldwide) network of servers that are able to handle regional traffic efficiently. We combine the power of Cloudflare (our CDN provider) with an efficient set of strategies to let us scale. This article describes the software strategies we implemented, that may slightly change how your Crisp chatbox behaves on an high-traffic website.

You can safely run Crisp on an high-volume / very-high-volume website, no matter which Crisp plan you are subscribed to. Subscribing to an Unlimited plan will however give you more realtime features at this scale.

Chatbox Modes

If you're running a high-volume website (ie. 20 page views per second at a sustained pace, ie this gives 1200 page views per minute), you may see the Crisp chatbox behavior change in a subtle way.

Here's why: the Crisp chatbox opens up a WebSocket connection for every visitor on your website, and each page view of each visitor. This is used to let you see the user live and open up a realtime conversation, or MagicBrowse the user. It is also used for the MagicMap feature.

However, on very large websites, those realtime features have less value: as you have so many visitors you'd prefer using automation: eg. Triggers rather than handling them by hand. Also, on our end, opening a WebSocket channel for every of your visitors becomes expensive at scale, thus the chatbox is designed to do it much less often. It still reports who's online, but the realtime features are a bit degraded.

Cases where the chatbox goes into "high-volume website" mode is very rare. If your website receives a lot of traffic at a sustained pace; or if you receive an unusual spike of traffic temporarily, you will experience such chatbox runtime mode. Most Crisp users will never experience this "high-volume" mode.

High-Volume Chatbox

If your Crisp chatbox goes in high-volume mode, your visitors will still see the chatbox as usual. However, the interface will not be immediately ready to chat for them if they click on the chatbox button. Your users will see a loading icon (it takes approximately 1 second to connect), which will be visible while the chatbox establishes a WebSocket connection to Crisp servers to begin chat.

Once then, the chatbox will behave as normal for this visitor, indefinitely (ie. as on low-volume or medium-volume websites). This means the chatbox for this very specific visitor will open up a WebSocket connection for each visit, so that you can still use all the real-time features of Crisp with people you chatted with.

The chatbox will be a bit longer to update the "online" status of your operators (it will be refreshed every 30 minutes, not instantly). All chatbox features will work as normal though (eg. $crisp JavaScript SDK, Triggers, etc.).

High-Volume Thresholds

Depending on your Crisp plan, the "high-volume website" thresholds (ie. quotas) are not the same.

All thresholds are accounted for per-minute, and cleared off every minute. If your website receives a sudden spike of traffic, it will thus be considered high-volume only for the time of the spike, and not for longer periods.

Thresholds

Reaching a threshold does not disable the Crisp chatbox from your website. Once the threshold is reached for the current minute, the Crisp chatbox will continue to behave as normal. See explanations above for what differs.

Unlimited Plan: 800 chatbox displays per minute
Unlimited Plan (Trial mode): 200 chatbox displays per minute
Pro Plan: 300 chatbox displays per minute
Basic Plan: 80 chatbox displays per minute
Was this article helpful?
Thank you!