The ClientEngage Visitor Chat is a fully-featured real-time chat for your websites. A clear and simple web-based administration allows you to conveniently chat with your visitors. And best of all: Visitor Chat comes with a Windows-based client out-of-the-box. Without having to visit the Visitor Chat’s admin-interface you will be notified from your Windows tray and can start chatting straight away!
Whilst chatting, your visitors can navigate through your website and after every page-load, the chat will go back to it’s previous state: they won’t lose any messages.
Live Support Chat – System Requirements
In order to be able to use ClientEngage Visitor Chat, you must fulfil the following system requirements:
- Apache 2 HTTP Server
- Preferably with mod_rewrite enabled
- PHP with a version of greater than PHP 5.2.8
- MySQL with a version of greater than MySQL 5 (i.e. with InnoDB support)
- Preferably a subdomain/domain for use with ClientEngage Visitor Chat
- Safe mode: off
- Enough server-resources for the number of concurrent chatters you expect
- jQuery: if your site does not use jQuery, VisitorChat will automatically include it. If your site does use jQuery, it is important that you use a version greater than 1.9.1
- Finally, the PHP PDO extensions have to be installed
System requirements of the Windows-based client
- .NET4 Framework (will be installed if not already available)
- Windows XP (SP3), Windows Vista, Windows 7, Windows 8
How does the live support chat script “work”?
The chat employs AJAX technologies and regularly checks with the server for any new messages. When you are actively chatting, the interval is 2.5 seconds. However, once activity goes down, this interval slowly decreases to only every 10 seconds. If you are not signed-up in a chat, it will contact the sever only every 25 seconds to check if any administrators are online. So you see: VisitorChat automatically determines the right combination of user experience & server load.
A note on server performance
This chat system employs AJAX technologies and does not rely on WebSockets for its communication. This means that anyone can run Visitor Chat, as long as your server fulfils the requirements outlined below. However, this also means that this system is not intended for ultra-heavy-duty use: so don’t build the next Facebook and try to have 10m people use this at once. That being said, on average server-specifications, there is nothing stopping you from having several concurrent conversations.