First confirm live chat is on for the site and the current domain is allowed. Install details are in Install & enable.
| What you see | Check first |
|---|---|
| No bubble | The switch was saved and the page reloaded. The script tag does not say data-chat="false". The current domain is on the allowed list. A narrow window or a phone browser may be hidden by Hide bubble on mobile. The network panel should show same-origin w-chat.js |
| The bubble works but the inbox never gets the message | When the quota is used up and overage billing is off, a new visitor only sees the message form. See Billing & quotas |
| No sound | The inbox sound toggle may be off. A muted tab, or a browser that has not been allowed to show notifications, leaves a badge and no sound. That prompt is a browser notification, not a separate push app to install |
| Translation does nothing | Free has no automatic translation. The switch is Two-way auto translation on Greeting & translation. If the platform has no AI, or translation does not finish within about 3 seconds, the original is sent and the inbox says it failed. See Two-way translation |
| It says disconnected | The visitor window and the inbox both reconnect on their own, waiting longer each time: up to about 15 seconds for the visitor window and about 10 for the inbox. Send again after it returns. The open conversation is still there |
| You are online but visitors see offline | Outside office hours the bubble uses the offline greeting even if an agent marked themselves online. Inside hours someone must be Online. Away and offline do not count. See Hours & offline |
| The agent side stays on connecting | Check whether the member is a Viewer. Viewers cannot use live chat. If a reload does not help, check whether the browser blocks the chat gateway |
A strict content security policy can block the script, the gateway connection, or the page inside the chat window. See CSP, blockers & networks.