In this guide
What you’ll finish with
A single working widget installation on the intended domain, checked on desktop and mobile.
Before you begin
- A configured and tested Website Chat agent.
- A live client plan.
- Permission to publish code on the client’s website.
Check the client before copying the install
In KugaClient workspace › Website Chat › Deploy
Open Deploy inside the correct client workspace and choose Widget. Confirm the business and intended domain before copying the generated installation. Each client’s code points to that client’s agent.
Review Agent Configuration and Website Chat’s Customise tab first. The installation should represent the name, opening message, placement and footer that the client has approved. The Support page option is separate and is currently marked as unavailable.
- The intended client is selected.
- The messenger has been tested with approved knowledge.
- The domain and live subscription are correct.
- Widget is the selected deployment option.
Add the generated widget code once
Copy the code supplied in Deploy rather than constructing your own client identifier or reusing another business’s embed. Add it through the client website’s supported custom-code mechanism. The exact setting belongs to the website platform, theme or CMS you are maintaining.
Check whether a previous widget installation already exists in a global template or tag manager. Two installations can produce duplicate launchers or competing behaviour. Keep a record of where you added the code.
- Find the website’s global custom-code or template area.
- Check for an existing Kuga installation.
- Add the supplied widget code once.
- Publish the website change and record the installation location.
Test the published page
In KugaClient workspace › Website Chat › Conversations
Open the public website in a fresh browser session. Start a conversation, ask a source-backed question and check the saved record in Conversations. This confirms that the public website is reaching the intended agent.
If the widget does not appear, inspect the published page rather than only the CMS editor. Check the published code, browser errors and any content security or consent settings used by that site. If you need support, provide the public URL and the specific installation location.
- The launcher appears once.
- The approved agent name and messages are displayed.
- The agent answers a known test question correctly.
- The saved conversation belongs to this client.
Check placement on a real phone
In KugaClient workspace › Deployments › Website Chat › Customise › Placement
Test a narrow mobile screen with the site’s menus, cookie controls and sticky buttons visible. Open the messenger, type a message with the keyboard active and close it again. The placement should leave the client’s important website actions accessible.
Adjust placement in Customise if the launcher competes with a booking button or other fixed element. Recheck the public website after saving.
- The launcher does not cover the site’s primary action.
- The open messenger and keyboard remain usable.
- The close control is visible and works.
- Long answers and booking links fit the message area.
Verify follow-up and optional attribution
In KugaClient workspace › Contact Requests
Run an enquiry that should create a Contact Request. Open the saved request and confirm the name, contact method and summary. Check the agreed notification destination as part of the same test.
Deploy also includes Capture UTM fields. It is off until enabled. If campaign attribution is part of the agreed service, enable it deliberately and test a public visit with campaign parameters. Confirm the captured context before relying on it in a report or webhook.