Get Started

Quickstart

Get DuggAI live in a few minutes — on Discord, your site widget, or both.

Running support in Discord? Start there

This page walks the website-widget install. If Discord is your main support channel — like most teams we work with — follow Discord installinstead. It's the same agent, knowledge base, and review queue; you can add the widget later.

What you'll have at the end

A chat bubble in the bottom right of your site.
An AI agent trained on your docs that auto-resolves common questions.
A dashboard where every conversation lands for triage.

Steps

Create your account
Sign up at /support/signup. The post-signup onboarding tour walks you through everything below end-to-end and provisions your project automatically.
Get your widget key
Open Dashboard → Integrations and click Generate API key. You get back a value like duggsupp_pk_a1b2c3…. This is your public widget key — it goes in your install snippet and is safe to commit. For production user verification you'll also use your org's signing secret (kept server-side); see Identifying users.
Drop the snippet
The minimum viable install is one script tag. Paste your real key in for data-key:
html
```
<script
  src="https://duggai.com/embed.js"
  data-key="duggsupp_pk_XXXXXXXXXXXX"
  defer
></script>
```
For Next.js / React / Vue / Svelte, see framework snippets. For an AI editor to wire it for you, see install via Cursor / Windsurf.
Train it on your docs
From the dashboard, paste your docs URL. The crawler ingests pages and indexes them for retrieval. Most docs sites finish in a few minutes. See Knowledge sources.
Send the first test message
Open your site, click the bubble, ask "How do I install your SDK?" — the bot should answer using your docs and cite the page it pulled from.

Where keys live in your app

Most teams put the public key in an env var so it's easy to rotate per environment:

bash

# .env / Vercel / Netlify / Railway env
NEXT_PUBLIC_DUGGAI_KEY=duggsupp_pk_XXXXXXXXXXXX
DUGGAI_SIGNING_SECRET=XXXXXXXXXXXX   # server-only, used by signed identify

Then reference process.env.NEXT_PUBLIC_DUGGAI_KEY in your snippet.

Add Discord too

The widget and Discord run on one agent, one knowledge base, and one review queue — add Discord whenever you're ready and the agent covers both channels. See Discord install.

What's next

Read Stack-aware agent — what makes the agent better than a generic RAG bot.
Read How the agent decides — the four actions (reply, ask, escalate, spawn_cursor) and the reasoning behind each.
Read Resolutions & escalations — what lands in your review queue and what auto-resolves.
Skim customization to match the bubble to your brand.