Conversation records
Transcripts matter for quality assurance, compliance, escalations, and institutional memory. ZChat stores session history where you host it, making it easier to review what happened without sending customer conversations to an outside chat vendor.
Find conversations by date, team member, customer details, or other session context when you need answers quickly.
Review real chat exchanges to improve response quality, handoff timing, and operator consistency.
When transcripts live in your environment, retention and governance decisions stay aligned with your own policies.
Scan historical conversations, find the record you need, and jump directly into detailed transcript review.
Keep timestamps, participant context, and message detail together so follow-up support is faster and more accurate.
A transcript is only worth keeping if you can find it again and act on it. ZChat stores the full record in your own database and gives your team the tools to work with it.
Filter sessions by agent, department, customer, email, tags or date range, then open any one for the full message-by-message record with timestamps in your local time.
Private internal notes attach to a session for your team only. Tags can be applied individually or to many sessions at once, so a batch of related conversations can be labelled after an incident.
Transcripts can be emailed to the visitor automatically when the conversation ends, so both sides keep the same record without an agent copying and pasting.
Awkward conversations sometimes need a follow-up. A visitor's IP can be blocked directly from the transcript view, and blocks support CIDR ranges and automatic expiry.
Transcripts live in your own SQL Server database and stay there until you remove them. Retention is your decision, not a plan limit - nothing is aged out by a vendor.
Yes. Sessions can be filtered by agent, department, customer name, email address, tags and date range, and each one opens to the full message-by-message transcript.
Yes. Each session has an internal notes field that is private to your team and never shown to the visitor - the right place for context like 'account flagged for billing review'.
Yes, and it can be automatic. When enabled, the conversation is emailed to the visitor after it ends so both sides keep a copy.
Yes. Sessions and missed chats export as CSV with proper escaping, and because the data is in your own database you can query it directly for anything a CSV will not cover. Privacy tooling covers per-visitor export and erasure requests.
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.