Why I Think Our Widget Is One of the Best in the Business (And Yes, I Know How That Sounds)

I know exactly how the title reads. A founder calling his own widget one of the best in the business is the kind of line that makes people close the tab. So let me earn it, or at least explain why I keep saying it out loud.

When most people hear the word widget, they picture a little chat bubble in the bottom corner of a website. You click it, a box pops up, you type a question, you get a paragraph back. Useful, sometimes. But it’s a Q&A box. That’s the whole thing.

That’s not what we built. And the difference is the reason I get a bit carried away talking about it.

A widget should be a full interface, not a suggestion box

The way I think about it, the widget is where the knowledge actually shows up. Not in the admin app your editors log into. Where the work happens. Inside a CRM while an agent is on a call. On an intranet page. On your customer-facing site. That’s the moment someone needs an answer, and that’s the moment most widgets let you down, because they hand back a flattened blob of text and nothing else.

So we made ours resurface the real thing, right there in the answer.

If the content that answers your question has a table in it, the widget brings the table back to you. Rows and columns, laid out, not mashed into a run-on sentence. If the answer lives in a step-by-step with a screenshot, the screenshot comes back with it. Diagrams, product photos, annotated images, they surface as images, in the widget, the same way they’d look if you opened the full article. Resurfacing the pictures in the content back to you is the part we shipped most recently and it’s quietly the one I’m proudest of. An answer that says “click the green button in the top right” is fine. An answer that shows you the green button in the top right is better, and most widgets simply can’t do it.

That sounds like a small thing. It isn’t. A huge amount of real knowledge is visual. Where a setting lives. What the right screen actually looks like. Which of two similar options you’re really on. Strip the tables and pictures out and you’ve lost half the answer.

It surfaces the interactive stuff too

Plenty of knowledge isn’t a paragraph at all. It’s a process you walk through, or a check that someone passed.

We have guided workflows, which are branching step-by-steps. The reader answers a question, the workflow shows them the next step based on that answer, and it keeps going until they’ve reached the end. Troubleshooting trees, onboarding checklists, “which of these applies to you” decisions. Those run inside the widget. The person clicks through them where they are, instead of being bounced out to a separate page and losing their place.

Quizzes work alongside them. If you need to confirm someone actually understood a policy, not just that they scrolled past it, you can put a quiz behind the content and the widget takes the reader straight to it. For anyone in a regulated industry, that combination, the content and the proof someone engaged with it, is the bit that usually gets a nod.

The workflow features around it

A few more things sit alongside the widget that most people don’t expect from something they think of as a chat bubble.

You can push notifications to people, so a widget isn’t only something they open when they’re stuck, it can also surface the thing you need them to see. Read acknowledgements let you track who’s confirmed they’ve read a critical update, which matters a lot more in some industries than others. And the widget deep-links into Knowledge Paths, our training journeys, so someone can go from “I have a quick question” to opening the full onboarding path on that topic in a single click.

On the security side, since people always ask: the internal widget is domain-locked, so it only runs on sites your admin has approved, and it’s email-gated, so a first-time user confirms their work email before they see anything. It uses a modern auth standard under the hood. I’ll spare you the acronym here, but if you’re the kind of buyer who asks that question, we have a good answer.

The honest bit

Two admissions, because a post like this needs them.

First, most teams won’t use every one of these features on day one, and that’s fine. You can run the widget as a plain search box and add nothing else. The depth is there when you grow into it, not a wall you have to climb before you get value. I’d rather build the full interface and let you switch parts off than ship the chat bubble and call it done.

Second, a widget is only ever as good as the content behind it. A beautiful interface over a stale, half-wrong knowledge base is just a faster way to get to the wrong answer. That’s why we didn’t build the widget as a standalone thing. It sits on top of the whole platform, the review dates, the version history, the flags and helpful-votes that tell your editors when something’s gone off. The widget delivers the knowledge. The platform keeps that knowledge worth delivering. Take one without the other and the whole point falls apart.

So, is it the best widget in the business? I can’t prove that, and I’d be suspicious of anyone who claimed they could. What I can tell you is that I’ve yet to see one that renders the real content, runs guided workflows in place, and connects back to a system that keeps it all current. Until I do, I’m going to keep saying it, and cringing slightly every time.

Have a look for yourself and tell me I’m wrong. I genuinely want to know.

The KnowledgeScout Team