Embeddable widgets
Drop your knowledge base
into the tools people already use.
Two widgets — one for your customers, one for your team — both embed with a single script tag. Search, chat, branded to match. Knowledge where users already are, not where they have to go.
Knowledge in the wrong place is invisible knowledge.
Your customer is on your homepage, two clicks away from a sale, and has a question about pricing. You want them to find the answer without leaving the page. Sending them to help.yourcompany.com risks losing them entirely.
Your contact centre agent is on a live call inside Salesforce or your custom desktop. They need a policy, fast. Tab-switching to a second app costs them three seconds and the customer's attention.
The fix isn't a better URL. It's bringing the knowledge base into the workspace.
Two widgets. One script tag each. Same knowledge base.
The external help widget drops onto any page of your customer-facing site. It surfaces public articles, runs the AI chatbot scoped to public content, and inherits your brand colours and logo. Customers search and chat without leaving the page they're on.
The internal widget embeds inside any tool that supports a script or iframe — CRM, agent desktop, custom internal portal. It surfaces whatever your team member has permission to see, including internal articles, and runs the internal chatbot. Agents stay where they're working.
Both widgets pick up your workspace branding and serve directly from your KB. A single script tag, loads asynchronously, never blocks page rendering.
Pick the right widget for the audience
External help widget
For your customers
Sits on any page of your customer-facing website. Customers click the launcher, search public articles, ask the AI chatbot, escalate when needed. Branded to match your site, no full-page redirect.
Scope: public articles only. Origin allowlisted server-side.
Internal widget
For your team
Embeds inside any CRM, agent desktop, or internal portal. Authenticated team members search whatever their role and team-scoped article access allow. Mid-call agents stop tab-switching, knowledge comes to them.
Scope: respects each user's role and team-scoped article access.
What's in the box
Single script tag install
Drop one line into your site or CRM page. Loads asynchronously, lazy-loads the full bundle, never blocks rendering.
Search and AI chat
Full-text search across articles, documents, and slides. Optional AI chatbot with the agentic loop. Same engine as the main app, scoped to the widget's audience.
Branded to match
Inherits your workspace branding automatically — colours, logo, and styling all match what's set in your KnowledgeScout admin. No CSS, no fiddling.
Configurable escalation
When chat or search can't find an answer, the escalation action is yours to set: a contact form (emailed to you) or a URL link to wherever your support flow lives. Users always have a clear next step.
Origin allowlisted
Per-tenant origin allowlist enforced server-side. If your script tag ends up on an unauthorised site, the widget returns 401 and refuses to load.
Permission-respecting
External widget shows public articles only, regardless of how it's prompted. Internal widget respects each user's role and team-scoped article access.
Performance-friendly
Bundle under 50 KB gzipped. Defer-loaded. Lazy-loaded full UI. Lighthouse scores stay clean.
Mobile-first
Responsive layout. Adapts cleanly to small screens, including iframe-embed contexts. The widget works as well on a phone as on a wide desktop.
Analytics
Searches, chat sessions, escalations all tracked separately for the widget. See what customers or agents are asking, what's escalating, what content's missing.
Who this is for
SaaS companies wanting fewer tickets
Drop the external help widget on your dashboard, marketing site, or in-app help section. Customers self-serve answers without leaving what they were doing. Tickets that reach your team are the genuinely hard ones.
Contact centre operations
Embed the internal widget inside Salesforce, HubSpot, Zendesk Agent Workspace, or your custom desktop. Agents stop tab-switching mid-call. The KB comes to them.
Customer success teams
In-app onboarding flows, public help portals, marketing site help launchers. The same widget on every surface, the same content underneath.
Operations teams running internal portals
If you've got a SharePoint home page, an intranet, or a custom internal portal, embed the widget so staff can search the company knowledge base without leaving it.
Why KnowledgeScout's widgets
One source of truth, three surfaces
Article you wrote, served through the main app, the help centre portal, the external widget, the internal widget, and to AI agents via MCP. One curation effort. Five places it shows up.
Both widgets included on Business and Enterprise
Not a separate add-on. Not a per-conversation surcharge. Not "contact sales for pricing." Both widgets are part of the plan.
Performance-conscious by default
Defer-loaded, lazy-rendered, small bundle. Won't tank your Lighthouse score or your customer's first contentful paint. The launcher is the only thing on the page until someone clicks it.
Origin-allowlisted, abuse-resistant
Per-tenant allowlist enforced server-side. Your widget only loads on domains you've authorised. Stolen script tags stop working at the config endpoint.
Common questions
How do I install a widget?
Drop a single script tag onto your page. The widget loads asynchronously, so it never blocks page rendering. The bundle is small (under 50 KB gzipped) and served from a CDN. You configure colours, position, and behaviour in your KnowledgeScout admin, no redeploys needed.
Can I embed a widget inside my CRM or agent desktop?
Yes — that's what the internal widget is for. It can sit inside any tool that supports an iframe or embed script, including most CRM and agent-desktop platforms (Salesforce, HubSpot, Zendesk Agent Workspace, custom internal portals). Agents search and chat without leaving their primary workspace.
What's the difference between the external and internal widgets?
The external help widget is for your customers: it sits on your public website, surfaces public articles only, and runs the customer-facing AI chatbot if enabled. The internal widget is for your team: it sits inside your CRM or internal tools, surfaces all content the agent has permission to see, and runs the internal AI chatbot. Same engine, different scope.
How does the widget handle branding?
The widget picks up your workspace branding automatically — colours, logo, and rounded-corner styling all match what you've set in your KnowledgeScout admin. No CSS, no designer needed.
Will the widget slow down my website?
No. The widget loads with the defer attribute and never blocks page rendering. It's lazy-loaded and only fetches its full bundle when the user opens it. The launcher button alone is a few KB. Page Lighthouse scores are unaffected.
Can the widget be abused on unauthorised sites?
No. The widget backend enforces an allowed-origins list per tenant. If someone copies your script tag onto another site, the widget will return a 401 from the config endpoint and refuse to load. Only domains you've authorised can run your widget.
Which plans include widgets?
Both the external help widget and the internal embeddable widget are on Business and Enterprise plans. Startup plans get the full knowledge base and AI chatbot through the main app, but not the embeddable widgets.
Knowledge where users already are.
Drop a script tag, inherit your branding, ship in minutes. Two widgets included on Business and Enterprise.