Install the Widget

Open Publish for the agent and copy the snippet shown there. It contains the correct host and publishable key for your deployment.

Standard embed


<script src="https://dukon2.vercel.app/widget.min.js" data-widget-key="YOUR_WIDGET_PUBLISHABLE_KEY" defer></script>

Replace the example key with the value shown on your Publish page. Add the snippet once to the shared layout used by every page that should show the launcher.

The standard mode renders the widget directly in the page and keeps the launcher fixed near the lower-right corner.

Isolated iframe mode


<script src="https://dukon2.vercel.app/widget.min.js" data-widget-key="YOUR_WIDGET_PUBLISHABLE_KEY" data-render-mode="iframe" defer></script>

Use iframe mode when the host site’s CSS or JavaScript interferes with the standard widget. The script creates the iframe and grants microphone permission for voice input.

Where to put the script

Either of these placements works:

inside <head>; or
just before the closing </body> tag.

Keep defer so the widget does not block the rest of the page. In a CMS or tag manager, choose a site-wide placement and make sure the tag is not injected twice.

Updates and caching

Keep the stable /widget.min.js URL from the Publish page. Engine 64 serves it with a short browser cache and updates the file when a new widget build is released, so you do not need to version the URL yourself. A returning visitor may keep the previous build briefly while the browser revalidates it.

Test the installation

After publishing your website:

Open the page in a private window and confirm that one launcher appears.
Send a question and confirm that a response streams back.
Submit the lead form if it is enabled, then check Contacts and Conversations.
Test on a phone-sized viewport and on every hostname you allowed.

For a custom client, inspect the chat response and retain X-Conversation-Id. The supplied widget handles this automatically.