Activation as a surface your PM owns. Not an eng ticket.
Walkthroughs you can update in Knolbase Admin without filing a ticket. Funnel data with intent (you see what users were trying to do when they quit). Cohort experiments without a deploy.
Engineering tickets per flow update
To embed the widget
To ship a new walkthrough
Activation is your top metric. Most tools do not move it.
You see drop off. You do not see why.
The funnel tells you 38% drop between step 3 and step 4. It does not tell you what the user was trying to do on step 3, or what they typed in the support chat 2 minutes after they quit. So you guess.
Static help decays per release.
Help docs and recorded tutorials are stale the moment you ship a release. Your PM writes a Notion page nobody reads. Adoption does not move.
Engineering becomes the onboarding team.
Most onboarding tools require eng to update DOM selectors every time the UI changes. The PM owns the flow, eng files the tickets, the backlog grows.
Activation as a surface your team owns end to end.
You ship the product. Knolbase handles the activation surface.
When a user signs up, Knolbase walks them through what to do first based on what they said they wanted. Not a generic tour. The PM updates the prompts. Eng never sees a ticket.
Funnel data with intent.
Knolbase tells you what the user was trying to do when they quit, in their own words. The chatbot logs every question. The session intel sits next to the funnel chart, so your weekly review actually leads to a fix.
Cohort experiments without a deploy.
Define a cohort in Knolbase Admin. Ship a different flow to that cohort. Compare outcomes against control. No experimentation framework to build. No engineering time.
From signup through feature adoption.
Self serve activation
Adaptive activation walkthroughs for every PLG signup, with real Q&A on the screen they are stuck on.
Feature adoption
When you ship a feature, Knolbase surfaces it to the users who would use it, in the page where they would use it. Not in a launch email.
An AI agent inside your product
Ship the in product AI surface customers already expect. Knolbase is trained on your docs only, branded as yours, and you control what it can answer.
Integrations PMs care about
Auth, analytics, CRM, support stack. The data flows we need to do our job, not a sandbox.
Frequently asked questions
For the portal: nothing. For the in product widget: a script tag and the user variables you already pass to your analytics provider. That is the engineering surface.
Knolbase is the layer that turns your videos and docs into a personalized portal, an in product video surface, and a chatbot. Most teams keep their help center as the back of house source of truth and let Knolbase deliver the personalized front of house experience.
Yes. Define cohorts in Knolbase Admin, ship different flows to each, and compare outcomes. No deploys, no eng time, no feature flag system to integrate.
Knolbase surfaces walkthroughs based on signals you send it (route, user attributes, events), not your DOM selectors. A UI change does not break the widget, so your team does not file a ticket every release.
Tools and use cases for product teams.
See it on your funnel data.
30 minute call. We embed the widget on a screenshot of your product, walk through a real user question, and show you what the funnel intel looks like.