Troubleshooting
Resources

Troubleshooting

Common problems and the fix in one place.

The widget doesn't appear

  1. Open the browser console — search for [DuggAI].
  2. Check Network — is duggai.com/embed.js returning 200, and does duggai-widget.js load when you open the bubble?
  3. Confirm your data-key is set and correct — without it the loader refuses to load and logs a warning.
  4. If the script loads but the bubble doesn't render, check that nothing on your page hides high-z-index fixed elements.

The bot replies in the wrong language

The agent auto-detects the user's language from their message and replies in kind. If it's guessing wrong on very short messages, the fix is usually a clearer first message — once there's enough text, detection settles.

The agent ignores my docs

  • Confirm the source is indexed: Knowledge → Sources shows last sync time.
  • If it's stuck on "crawling," check the docs site is publicly accessible. The crawler doesn't handle auth-walled docs by default.
  • If a specific page is missing, paste the URL into the per-source Recrawl field — forces a single-page recrawl.
  • If the agent still doesn't cite the source, open the conversation in History — each reply lists the sources it retrieved (with a match score). If your doc isn't there, retrieval failed (vocabulary mismatch is the usual culprit).

Discord bot is silent

  • Confirm the bot has permission to read messages in that channel.
  • Check the channel is in your watched-channels list in the dashboard's Discord settings (an empty list means it listens everywhere).
  • For threaded replies, check the bot has the "Create public threads" / "Manage threads" permission.

I've run out of credits on Free

Free includes a one-time 50-credit trial. When it's spent the bot stops auto-replying and new messages get a short "out of credit" notice instead of an AI answer. Upgrade to Starter (2,500 credits / month) or add top-up credits to keep the agent answering. See Pricing & credits.

Check the retrieved sources
For most "the bot is wrong" issues, the answer is in the conversation detail: each reply shows the sources the agent retrieved. If the right source isn't there, your knowledge base needs work; if it's there but the answer was still off, sharpen that source or add an operating-manual note. There's no confidence dial to tune — the agent decides per ticket.

Still stuck

Email support@duggai.com with the conversation ID and a screenshot. Same-business-day reply.