Nuto Chatbot Demo

Test with different tenants and URLs • Style Dashboard

Configuration

Live chat robustness test

Live agent mode

Drops, mutes and inspects the widget's WebSocket to verify auto-reconnect, heartbeat and restore. Load the widget and open the chat window first (send one message so there is history). In live-agent mode, start a live chat first; the outage scenario then expects a human agent to write during the outage.

socket: none yet

sockets created: 0

last ping: —

last pong: —

Integration Code

Basic integration (defaults to production):

<script
  src="/widget/nuto-chatbot.min.js"
  data-auto-init="true"
  data-tenant-id="YOUR_TENANT_ID"
  data-environment="prod">
</script>

For test environment:

<script
  src="/widget/nuto-chatbot.min.js"
  data-auto-init="true"
  data-tenant-id="YOUR_TENANT_ID"
  data-environment="test">
</script>

Note: The data-environment attribute determines which API endpoint to use. Options: prod (default), test, or development

GTM Script (Advanced)

For Google Tag Manager with SPA navigation support:

Environment:

(https://chatbot-ui-env-test-truste.vercel.app/widget/nuto-chatbot.min.js)

<script>
  if (!window.NutoChatbot || !window.NutoChatbot.isInitialized()) {
    var s = document.createElement('script');
    s.src = "https://chatbot-ui-env-test-truste.vercel.app/widget/nuto-chatbot.min.js";
    s.setAttribute('data-auto-init', 'true');
    s.setAttribute('data-tenant-id', 'YOUR_TENANT_ID');
    s.setAttribute('data-environment', 'test');
    document.head.appendChild(s);
  }
</script>

Tip: The environment toggle above changes the data-environment attribute value in the GTM script.

[DEV LOG]

0 entries

--- No entries yet ---

Send a message to capture metadata