For customer support
A help centre your customers
will actually use.
Branded self-service. AI chatbot grounded in your public articles. Embeddable widget for any page on your site. Fewer tickets, faster answers, and customers who didn't have to wait for your team.
Most help centres are dumping grounds.
Articles written years ago, never reviewed. Search that returns ten results, none of them right. No clear taxonomy. Nothing on-brand. Customers click around for two minutes, give up, and raise a ticket your team has to answer manually.
Then you bolt a chatbot on top of the same mess. The bot quotes a 2022 article that contradicts the 2024 one, and now your customer is more confused than before.
A help centre that works deflects tickets. A help centre that doesn't, generates them.
Same content. Two audiences. One source of truth.
KnowledgeScout lets you write an article once and choose its audience: keep it internal for your team, or make it public so customers see it too. Each article has a visibility setting, so internal procedures stay internal and public guides reach the help centre automatically. No duplicate writing. No two-sided sync.
The customer help centre runs on your own custom domain (such as help.your-company.com), or on the default your-company.knowledgescout.io subdomain. Either way, full custom branding — your colours, your logo, your tone. Customers search, browse categories, or ask the AI chatbot, which answers from your public articles only and cites every source.
For customers who never leave your main site, drop the embeddable widget into any page. Same content, same AI, no full-page redirect. They get answers right where they are.
Three places your customers can self-serve
All powered by the same articles. All on-brand. All grounded in content your team has actually approved.
Branded help centre
Public help portal on your custom domain or your-company.knowledgescout.io. Custom branding. Categories, search, popular articles. SEO-friendly so your content actually gets found.
Help widget
Floating chat widget you embed on any page of your site. Search and AI chat without leaving the page. Inherits your colours. Loads async, never blocks page render. More on the AI chatbot →
AI bots via MCP
Plug Fin, Copilot Studio, Agentforce, or your own bot into a read-only MCP endpoint scoped to public content. The bot answers customers from your verified articles, with citations.
What it includes
Two designs + full branding
Pick from two design templates, then customise the hero image, brand colours, logo, and which articles or categories sit on the homepage. On-brand without writing a line of CSS.
Public/internal toggle per article
Each article has a visibility flag. Public articles surface in the help centre and through customer-facing AI. Internal stays internal.
Grounded AI chatbot
Customers ask in plain English, get answers cited from your public articles. Says "I don't know" when it doesn't, instead of inventing a policy.
Search analytics
See what your customers are searching, what's returning no results, and what topics generate the most chat. Your content roadmap, written by them.
SEO-friendly out of the box
Server-rendered HTML, sitemap, structured data. Your help articles get indexed and start ranking for the questions customers Google.
Article feedback
Customers vote thumbs-up/down on articles. Your team sees which content lands and which needs rewriting. The signal is direct.
Configurable escalation
When chat or search can't find an answer, the escalation action is yours to set per workspace. A contact form that emails you, or a URL link to whatever fits your support flow.
Built for teams that want fewer tickets
SaaS companies
Your customers should self-serve the routine stuff so your support team can focus on the genuinely hard problems. A real help centre, not a faux one.
Service businesses
If you answer the same five questions every week, those answers belong on a public help centre, not in your inbox. The widget on your homepage closes the loop.
Customer success teams trying to scale
When CS asks the same question 50 times a quarter, that's content. Turn the answer into an article once. Let search and the AI deliver it forever.
Anyone replacing Zendesk Guide or Intercom Articles
If you're paying for a help centre as part of a bigger ticketing suite and only using a fraction of it, KnowledgeScout is the focused tool that does this one job well.
Why KnowledgeScout for the help centre
One knowledge base, two audiences
Your team and your customers read from the same articles. Update once, both audiences see the change. No duplicate writing, no sync drift.
Grounded AI, not a hallucination engine
The chatbot only answers from your public articles. If the answer isn't there, it says so. No invented policies, no "confidently wrong" responses your team has to clean up.
Embeddable widget out of the box
No extra fees, no separate add-on. The customer-facing widget is included on Business and Enterprise. Drop it on any page, configure colours, ship.
Pricing without ticket-volume gotchas
Per-user pricing, no per-ticket or per-conversation surcharges. Scale your customer base without your help-centre bill scaling alongside it.
Common questions
Can the help centre be on my own domain?
Yes. Your help centre can run on a custom domain (such as help.your-company.com), or on the default your-company.knowledgescout.io subdomain — both with full custom branding (logo, colours, fonts to match yours). The embeddable widget can also sit on any page of your existing website, regardless of where the help centre itself lives.
How do I control what's public vs internal?
Every article has a visibility setting: internal or public. Internal articles stay within your team and never leave their view, regardless of who or what is asking. Public articles appear in your customer help centre and are visible to customer-facing AI bots through the read-only MCP endpoint, and they're still available to your team in-app, so you don't write the same thing twice.
Does the AI chatbot work for customers too?
Yes. The AI chatbot is available on the customer help centre, scoped to public articles only. It cites its sources, links back to the original article, and says so when it doesn't have an answer rather than making one up. You control whether it's switched on per workspace.
What happens when chat or search can't find an answer?
The escalation action is configurable per workspace. Two options: a built-in contact form that emails the question to you, or a URL link to wherever your support flow lives — live chat, help desk, community forum, anywhere. The same escalation runs whether AI is on or not, so customers always have a clear next step when the knowledge base doesn't have an answer.
How does the help widget embed work?
Drop a single script tag onto any page of your website. The widget loads asynchronously, so it doesn't block page rendering. Customers can search your help articles and chat with the AI without leaving the page they're on. The widget inherits your branding.
What about widget loading speed?
The widget loads with the defer attribute, so it never blocks page rendering. The bundle is small (under 50 KB gzipped) and served from a CDN. We allowlist your origin server-side to prevent the widget being abused on unauthorised sites.
Which plans include the customer help centre?
The branded help centre is on Business and Enterprise. So is the embeddable customer-facing help widget, and the internal embeddable widget (for embedding inside CRMs, internal portals). Startup plans get the in-app AI chatbot for your team only — no external customer-facing surfaces.
Stop generating tickets your help centre should be deflecting.
Branded portal, AI chatbot, embeddable widget. One source of truth, two audiences served.