ConnectWiz Live Chat
Free channel — every planYour website already has traffic. Give it a voice.
One script tag adds a chat bubble that answers in seconds — trained on your content, styled like your brand, engineered not to slow your site down, and carrying a whole storefront, help center, booking desk and phone line inside one panel. This page lists everything it actually does.
Embedding & engineering
A widget your developers won’t veto
Most chat widgets are a megabyte of someone else’s framework wrapped in !important. Ours is an isolated Web Component with staged loading — auditable, cacheable, and invisible to your page speed until it’s needed.
One script tag — or full control
Paste one async snippet before </body> and you’re live. Prefer control? Manual-init mode defers everything until your own code says go, with a clean destroy for single-page apps.
Style-proof isolation
A real Web Component with Shadow DOM: your site’s CSS can’t break the widget, and the widget can’t break your site. Zero style bleed, in either direction, by construction.
Two-stage lazy loading
A tiny loader arrives after your content, asynchronously; the full app downloads only when it’s needed. The realtime layer itself is lazy — and if realtime is ever unavailable, the widget degrades gracefully instead of dying.
Your brand, generated
Three brand colors expand into a complete theme automatically — plus header styles, brand imagery, chat backgrounds, built-in or custom launcher icons, and pixel-level position offsets for desktop and mobile separately.
52 languages from one snippet
Interface strings are delivered per visitor’s language — even your custom header and welcome text can carry per-language translations in the same embed. Your own wording overrides any built-in string.
RTL that actually flips
Arabic, Hebrew, Persian and Urdu render right-to-left properly — direction is set per visitor locale, not left as an exercise for your CSS.
AI & handover
An AI that cites its sources — and hands over like it means it
Trained on five source types
Free text, Q&A pairs, uploaded documents, single pages — or your whole site by crawl, robots.txt respected. Wiz answers from what you actually publish, not from vibes.
Answers with citations
Optionally, every bot reply shows which of your sources it drew on — titles only, right under the bubble. Visitors see the answer is grounded; you see what your knowledge base is earning.
Handover, visibly staged
Three modes — a "talk to an agent" button, AI that escalates itself when confidence drops, or off. The visitor sees each stage: requested, connecting, agent joined. No black-hole handoffs.
A queue that tells the truth
When humans are busy, visitors see their position and an estimated wait, live — and get a "you’re up" banner with a sound when their turn arrives. Waiting is bearable when it’s honest.
Departments & agents, three ways
Route by the visitor’s own pick, by an AI classifier, or not at all — and optionally let returning customers resume with the agent who already knows them.
Bot replies, auto-translated
Wiz can answer in the conversation’s language regardless of what your knowledge base was written in — the visitor’s language is detected and the reply arrives in it.
Proactive & automations
The widget that reacts to what the visitor is doing
A pricing-page visitor at 80% scroll is not the same as a blog skimmer. The widget watches page, dwell time, scroll depth and more — and responds differently to each.
Proactive welcome, politely
A one-time greeting per browser — on page load with a delay you choose, or when the chat opens — optionally opening the panel and playing a sound, and gated to office hours so nobody is greeted into silence.
Teaser cards
A launcher-side popup with avatar, title and message — shown once, hideable on mobile, perfect for "new: annual plans" without a modal in anyone’s face.
20 condition types
URL, referrer, time on page, scroll position, returning visitor, country, city, language, logged-in state — even custom JavaScript variables from your own site. Compose them into rules that fire for exactly the right person.
Actions incl. live re-theming
Rules can send an in-chat message, show a popup, suggest help articles — or re-skin the running widget: campaign colors on the campaign page, a different header for enterprise visitors. Few widgets anywhere do this.
Forms where they belong
A configurable pre-chat form captures identity before the first message when you want it; an offline follow-up form collects contact details when you’re away — both land structured, not as chat soup.
Flows run in the widget
Your automation flows — buttons, cards, structured steps — run inside the chat panel with server-validated choices, and can greet visitors the moment the window opens.
Visitor intelligence
Anonymous today, a customer tomorrow — with the history intact
Visitors before they speak
Returning browsers are recognized without creating fake contacts; every visit logs its landing page, referrer and language — an analytics view your support tool actually owns.
Retroactive stitching
The moment a visitor writes or identifies, every prior anonymous visit binds to their contact — the "who was on the pricing page three times last week" question gets a name, honestly and after the fact.
First-visit ping, no spam
Agents who opt in get a live "new visitor online" notification with the landing page — fired only on a first-ever visit, never on every return, because notification fatigue kills the feature.
Visit history on the contact card
Session counts, first and last seen, recent pages and visits — aggregated across every browser stitched to that person, right where the agent is already looking.
The live page, live
Rules and agents can know the page the visitor is on right now — reported continuously, evaluated server-side, so "I see you’re on the checkout page" is knowledge, not creepiness theater.
Deletion done right
Delete a contact and their identity is unlinked while anonymous analytics survive — privacy compliance doesn’t have to torch your traffic history.
In-chat apps
One panel. A help center, a ticket desk, a booking page, a shop — and a phone.
Each mini-app appears only when you actually have qualifying content behind it — a shop with no priced products stays invisible, honestly.
Help center in the panel
Visitors browse and search your articles without leaving the page — and automations can suggest the right article for the page they’re on.
Tickets, in chat or standalone
Customers open and track support tickets inside the widget — or through a hosted ticket portal you can drop into any page as an iframe, running on the same session.
Self-service booking
Visitors book appointments against your real availability — the same resource-aware engine your team and your AI use, so a double-booking is structurally impossible.
A shop in the chat
Visitors browse your catalog, place orders and read back their own — with prices always snapshotted server-side from the catalog, never trusted from the browser.
Voice calls from the page
An in-widget WebRTC call button rings your team’s call center — off by default on purpose, because a phone nobody answers is worse than no phone.
Bridge to messaging apps
A "continue on WhatsApp / Telegram / …" strip hands the conversation to the channels people keep in their pocket — reachable even during the privacy gate, if you choose.
Accounts & SSO
From anonymous chat to full customer accounts — your call
Real end-user accounts
Register, log in, see past conversations, edit a profile — the widget can be a full customer portal, or stay a nameless chat bubble. Every piece is a switch.
Verified identity, gently
Email or phone as identity — required, optional or off — with one-time codes for verification and magic-link sign-in that’s consumed and stripped from the URL.
SSO from your own site
Your site (or our WordPress plugin) passes a signed token and logged-in customers are recognized without re-registering — with a lock-in-proof rule: "members only" mode can’t activate unless SSO is actually configured.
CAPTCHA when you want it
Registration can sit behind Cloudflare Turnstile — opt-in, with your own key — so bots stay out without making humans solve puzzles to say hello.
Notifications that reach them
Reply sounds with adjustable volume, in-tab browser notifications — and full offline web push through your own push app on your own domain, because that’s how web push actually works.
Conversations, managed
Visitors can close finished conversations and start new ones — or you cap it to one continuous thread per customer and the picker disappears entirely.
Privacy & abuse
Consent-first by architecture — and hardened for the open web
The widget runs on your customers' sites, in public, unauthenticated. That’s exactly why this layer got the most engineering.
Nothing stored before yes
The visitor identity token is minted in memory and written to the browser only after the consent question resolves. A visitor who never answers leaves no trace — most widgets write a tracking cookie on first paint.
Respects your consent platform
Already running OneTrust, Cookiebot, Didomi or TrustArc? The widget reads the visitor’s decision from your CMP: a "no" there stops us; an unanswered banner falls through to our own gate — the two are never confused.
Consent with evidence
Every consent is recorded server-side with the exact text shown, its version hash, language, time and context — and withdrawal is offered inside the widget, not hidden in an email footer.
Hardened rendering
Bot messages are sanitized against a strict allowlist — no images, no styles, no inline handlers — and every link opens in a new tab with the full security attributes. Chat content can’t script your site.
Visitors never see staff internals
Visitor and staff realtime channels are physically separate: agent identities, AI internals and assignment data never travel on the visitor’s connection. Not filtered out — never sent.
Layered abuse controls
Per-visitor, per-session and per-workspace rate limits, an IP and network ban list, message size caps, and tighter upload limits for the public surface than for staff — spam is an engineering problem here, not a support ticket.
Free channel
What it costs: nothing, on every plan
Included everywhere
- Free on every plan — including the Free plan, alongside Telegram
- Conversations count toward your plan’s normal allowance; AI answers draw on your AI credits
- The in-chat apps (help center, tickets, booking, shop, voice) follow their own features' plan availability
Why it’s the free one
Live chat is the highest-intent channel you’ll ever run — these people are already on your site, reading your pricing. Giving it away is not generosity; it’s the honest recognition that answered traffic is where every other channel’s value starts.
Give the traffic you paid for someone to talk to.
One script tag today; answered visitors tonight. Free on every plan.