docs
/
Walkthroughs

Turn on live chat on your website

Create a chat configuration, embed it, make an agent available and verify a visitor-to-agent conversation.

STEP 1Configure widget
STEP 2Embed and staff
STEP 3Test both sides

Your finish line: a visitor on the site sends a message, an available agent receives and answers it, and the conversation survives a refresh.

- src: /images/visual-lessons/audit-chat-designer.png
  caption: Live demo screen: Chat Designer, Save and Embed Code. The displayed conversation is a designer preview, not a verified visitor-to-agent exchange.

1. Prepare the site and agent

Use a preview/test site and a second browser session for a fictional visitor. Sign in as the staff member who will answer. Confirm both sessions target the same organization; an embedded widget and an agent in different organizations cannot form a useful test.

2. Configure the widget

Open the chat designer from the available chat/CRM tools. The registered Studio route is /app/chat-designer. Select or create the chat configuration, review its greeting, appearance and behavior, and Save it. Record its configuration/Chat ID. Do not confuse chat mode, which supports live conversation, with qa mode.

3. Get the embed code

Open Embed Code. Select App Credential starts on the site's own chat app and lists apps as name (App ID); the generated HTML/React code carries the organization, the configuration (configId) and that App ID (appId), with Copy Code. The code holds no secret: the widget signs in by the website it is on.

Under the picker, a box lists the websites the app signs in on. Add every website the code goes on (type it, then Add; a full URL is cut down to its host). On a website that isn't listed, the visitor sees "Live chat isn't set up for this website yet. Please contact us another way." For the site itself, Site Config › Chat shows the same box with Add this site, and Set up chat adds the site's addresses for you. Never substitute an administrative account token for the app's App ID.

4. Add it to the website

Add the generated markup/scripts to the site’s supported custom-code or page integration surface. For a custom HTML site, the reference shows a stylesheet, container, initialization callback and loader script. Keep the IDs from your actual configuration; do not copy sample IDs as real values.

Load the rendered page and verify the widget appears. If it does not, inspect loading errors, the organization/configuration IDs and the actual public page—not only the editor canvas.

5. Make an agent available

Open the live chat desk or header Chat control. Set the agent’s presence/availability to accept work. Being signed in does not by itself prove the agent is available. Keep the staff session open while testing the visitor flow.

6. Test both sides

  1. In the separate visitor session, open the widget and complete its displayed visitor entry if requested.
  2. Send a test message. Check the waiting queue or active conversation on the agent side.
  3. Accept the conversation and reply. Verify the visitor receives it.
  4. Refresh and check the history. If you test handoff, verify the second agent actually receives the conversation.
  5. Repeat with the agent unavailable so you understand the configured queue/fallback experience.
Why a visible chat bubble is not enough

The bubble proves only that a UI loaded. A complete test covers visitor identity, the correct chat configuration, agent availability, message delivery and persisted conversation history.

Common problems

SymptomInspect
No widgetLoader/stylesheet request, organization and configuration IDs, rendered page markup
"Live chat isn't set up for this website yet"The website isn't on the app's websites (Chat Designer › Embed Code, or App Credentials › Allowed domains); the browser console names the reason
Visitor waits foreverAgent availability, queue and the selected organization
Wrong greeting or stylingWhich configuration the embed actually loads
Staff does not receive a messageLive connection errors and the actual queue/desk
Works on desktop but not mobileMobile connection, app availability and the signed-in account

Evidence: documentation and designer implementation reviewed; a new visitor-to-agent delivery test is still required. Embed reference · Agent desk · Mobile inbox and calls.