- Where do I find my public key?
- Dashboard → your chatbot → Embed tab. The key starts with ac_ and is safe to expose in client-side HTML — it's scoped to a single chatbot and read-only.
- Can I run different chatbots on different pages?
- Yes — load each one with its own public key. Each chatbot has its own knowledge base, branding, and lead inbox. Studio plan lets you run 3, Agency lets you run 20.
- Will the widget slow down my site?
- No measurable impact. The script is loaded async (it doesn't block parsing or first paint), the widget only mounts when a user clicks it open, and the bundle is ~80 KB gzipped. We use Vercel's edge network for global delivery.
- Does it conflict with my site's CSS?
- Never. The widget renders inside a Shadow DOM — your CSS can't reach into it and ours can't leak out. Tested against Bootstrap, Tailwind, vanilla CSS, and a dozen WordPress themes.
- What if I have a Content Security Policy?
- Add chat.aetherisinnovations.com to script-src, api.chat.aetherisinnovations.com to connect-src, and (if your widget logo loads from Supabase) your Supabase project domain to img-src.
- How do I verify it's working?
- Open your site, look for the launcher in the bottom-right corner. Click it. If you see the welcome message you configured, you're live. If nothing appears, open DevTools → Network and confirm widget.js loaded with status 200.
- Can I hide the widget on specific pages?
- Yes — only include the script on pages you want it on. For most platforms that means scoping the snippet to specific page templates rather than the global footer.
- Do you have a native HubSpot / Salesforce / Pipedrive integration?
- Not yet — by design. Native integrations have a long maintenance tail (OAuth refresh, field-mapping UI, per-vendor API drift), so for v1 we built one outbound webhook that covers all of them via Zapier or Make. Once a paying customer asks for a specific native integration we'll prioritize that one. The webhook is already in production — see Lead routing above.
- Is the webhook signed? How do I verify it's really from Aetheris?
- Today: requests carry the User-Agent header `Aetheris-Webhook/1.0` and originate from our backend's outbound IP, but there's no HMAC signature yet. For now, treat the webhook URL itself as a secret — it's per-client and rotatable from Settings. HMAC signing with a per-client secret is on the near-term roadmap.
- What if my webhook is down when a lead comes in?
- We retry up to 3 times with exponential backoff (~0.5s, ~1s, ~2s) on any 5xx response or transport error. After that the lead is still safely persisted in the dashboard inbox and the notification email (if configured) — only the webhook delivery is dropped. CSV export gives you a permanent backfill path.