AI Widget

Point it at your help docs, your website or your Notion, and the same chat widget you already embed starts answering visitors in your brand voice — pulling real answers from your knowledge, matching curated FAQs instantly, capturing leads, and handing off to a human the moment it's unsure.

What you get

• Trained on your content, not the internet — Answers come from your knowledge base — articles you write, pages we crawl from your site, or a synced Notion — retrieved and grounded so the bot never invents prices, policies or promises. If the docs don't cover it, it says so and fetches a human.
• Every lead, kept and routed — Anyone who gives the bot an email or phone number becomes a lead on that widget, with every answer they gave. One “Widget lead” automation turns it into a contact, notifies the team or starts a follow-up — and links the conversation to the record. Bot turns show right in the shared inbox, and handoff is a normal assignment.
• Deterministic-first, so it's cheap and reliable — Curated FAQs and conversation flows answer instantly and for free; only genuine open questions use the model and draw an AI credit. Out of credits? It falls back to FAQs and a human — the widget never breaks.
• You can see where every value came from — Each detail the bot captures records whether it matched a recognised format or was inferred by AI — which model, how confident — and which field it wrote to. Personal data is redacted in that log, with an optional retention window. Try the bot in the editor's live preview before it goes live — nothing is saved.
• Give it a goal, not just answers — Tell a bot what to find out — name, email, company, budget — and drag the list into the order it should ask. It asks one question at a time, appended to a real answer, at most twice each, and everything it learns lands in one lead per conversation.
• You decide who answers — Four modes: AI first then a human, AI only, humans only, or — the useful one — humans while your team is online and in hours, with the bot picking up after that. Whichever you choose, the bot stops the moment a teammate replies or takes the conversation, so it can never talk over a live agent.
• Several knowledge bases, granted per bot — Keep product docs, policies and reseller-only material in separate knowledge bases, then grant each bot the ones it may answer from — or leave it on everything. A support bot and a partner bot can run on the same site and give deliberately different answers. Visitors only ever see the articles you pick for a widget's Help tab.

Capabilities at a glance

• Retrieval-augmented answers over your knowledge base, brand-matched to your widget
• Curated FAQ matched before the model — instant, free answers
• Ingest your website (crawl) or sync a Notion database into the knowledge base
• Per-widget lead capture (email or phone makes a lead) with CSV export and a “Widget lead” automation trigger
• Confidence-based human handoff into the shared inbox
• ManyChat-style conversation flows: ask, branch, capture, route, hand off
• One website per knowledge base, rescanned in step — pages removed from your site leave the bot too
• Manage it all from the AI assistant and MCP: create articles, mine FAQs from past chats, generate flows
• Runs from the one Solstral tag you already install; internal Help tab reuses the same knowledge
• Answering modes: AI first / AI only / humans only / AI when the team is offline
• Goals on each bot: an ordered list of details, asked one at a time while it answers
• Progressive capture into ONE lead per conversation
• Qualification scoring + conditions with a real "unknown" outcome, written onto the record for flows to filter on
• Provenance on every AI-derived value (source, model, confidence) with PII redaction and retention
• Live preview in the widget editor that answers with the real bot — nothing saved
• Agenda runs are a report source — qualification rates by agenda, channel or period
• The lead form, the bot's goal and a volunteered email all fill the same lead — never two for one person
• Manage agendas from the AI assistant / MCP: create, dry-run, publish, assign
• Bot steps aside automatically when a teammate replies or takes the conversation; hand it back from the Inbox