Get Started

Verify the bubble

A short checklist to confirm the widget is loading, identifying users, and reaching the agent.

1. The bubble appears

Reload your site. The DuggAI bubble should appear in the bottom-right corner. If it doesn't:

  • Open the browser console — look for [DuggAI] (or legacy [DuggSupport]) errors.
  • Check Network — the request to duggai.com/embed.js should be 200.
  • If the request 401s, your widget key is wrong or revoked. Regenerate it from the dashboard.

2. A test message reaches the agent

Click the bubble, type "hello", send. You should see:

  • A typing indicator within ~200ms.
  • A reply within ~5 seconds.
  • The conversation appearing in your dashboard inbox.

3. The agent uses your docs

Ask a question that's answered in your indexed docs. The reply should cite the doc page it pulled from. If it doesn't, your docs probably haven't finished indexing — check Knowledge sources for sync status.

4. User identity is reaching the dashboard

If you're calling identify(), you should see the user's email and ID on the conversation in the dashboard. To test:

js
window.DuggAI.identify({
  id: "test-user-123",
  email: "test@example.com",
  traits: { name: "Test User" },
});

Send a new message after calling identify. The conversation should be tagged with the test user in the dashboard.

5. Page context is captured

The widget auto-captures the current URL and page title. The agent uses this to give page-aware answers. You can see what was captured in the conversation detail view in the dashboard.

Common gotcha
If you have a strict CSP and the widget never loads, the issue is almost always connect-src blocking the WebSocket. See CSP notes in Manual install.

What to look at next