Modern web coverage
The widget and support workflow are designed to fit more than a marketing homepage. Embed ZChat into customer portals, account areas, product dashboards, and web applications where customers need in-context help from a support team that still wants full deployment control.
Add chat to pricing pages, contact flows, and conversion paths where visitors need fast answers.
Support signed-in users directly inside account and subscription experiences without sending them elsewhere. Pass the name and email your portal already knows and the pre-chat form opens pre-filled, so customers never retype details you are showing them.
Provide contextual assistance inside application workflows where people actually get stuck.
Use widget layouts that sit comfortably inside modern page structures, from straightforward site layouts to more interactive web experiences.
Keep the support experience readable and useful on responsive pages, mobile screens, and richer application interfaces.
A chat widget written for a marketing homepage tends to fall apart inside an application - it collides with your CSS, asks a signed-in customer who they are, and routes every conversation to the same queue. These are the details that decide whether support inside a product feels native or bolted on.
Pass the name and email your portal already has and the pre-chat form opens pre-filled, so a logged-in customer is not asked to retype what is on the screen next to them. The visitor can still edit anything before starting.
This is convenience, not authentication - the values come from the browser and the server treats them as untrusted input.
Shadow DOM isolation means your stylesheet cannot leak into the widget and the widget cannot leak into your layout, which is the usual failure mode for chat inside a dense application UI.
The embed carries a department, so a billing area and a technical dashboard route to different queues with no server-side work. Custom pre-chat fields collect the context an agent needs before the first reply.
Use the plain script tag, or call ZChat.init() programmatically when a single-page application needs to control when the widget appears. Any page can also opt out of visitor monitoring entirely.
Yes, and you can hand it the identity the page already has. Pass the visitor's name and email in the embed and the pre-chat form opens pre-filled, so a signed-in customer is not asked to retype details you are already showing them. Treat it as convenience, not authentication: the values arrive from the browser and the server treats them as untrusted.
No. It renders inside a Shadow DOM, which isolates styles in both directions. Your CSS cannot leak in and break the chat window, and the widget cannot leak out and disturb an application layout.
Yes. The embed carries a department, so a billing screen and a technical dashboard can route to different queues without any server-side work on your side.
Yes. Custom pre-chat fields let you ask for an order number, account ID, severity or anything else, and the answers are stored with the conversation and shown to the agent. The server validates every submission against your own field definition.
Yes. The widget is responsive, follows the visitor's dark-mode preference, and can be initialised programmatically with ZChat.init() rather than a plain script tag when a framework needs to control when it loads.
ZChat gives you the installable server, web dashboard, website widget, and desktop agent tools in one self-hosted product you buy once and keep. Run it on infrastructure you trust and connect AI only if and how you want it.
Deployment
Install on Windows or Linux, behind IIS or Nginx, in a VM, or in Docker if that fits your stack.
Commercial model
One-time purchase, perpetual license, and no monthly per-agent bill attached to growth.
AI Flexibility
Use Ollama locally or connect OpenAI and Anthropic with your own provider accounts.