The help center was always a stopgap

A help article can be accurate and still fail to answer a customer's question. "Why can't I export this report?" needs a different answer when the export control has moved, when the customer's role cannot use it, and when they are viewing a report that cannot be exported.

A help center gives you a place to explain the workflow. The customer still has to work out which explanation applies to their screen.

Why the knowledge base goes stale

An article records the workflow someone checked when they wrote it. If the navigation changes later, its instructions need an edit. An assistant using that article as its only source has the same outdated directions to work from.

Even a recent article has limits. A guide written for workspace owners may be correct for owners and unhelpful to a member who cannot see the same controls. Adding a permissions note improves the guide, but the customer still has to recognize that it describes their problem.

The freshness tax covers the work of keeping those instructions current. Helping someone use them also requires context about what they are trying to do and what is available to them.

What teams keep trying

Reviewing docs as part of a release is useful. So is checking important articles on a schedule. Clear ownership gives the support team someone to contact when a screenshot or instruction needs an update.

A well-maintained help center can explain a billing policy, define a term, or give someone the background to make a decision before they open the product.

For a task inside the product, though, asking the customer to find an article and translate it into actions adds work. If they have already followed the instructions and cannot find the button, sending the same article again does little to help. Support needs to establish what they can see and why their experience differs.

What we built instead

Frigade Assistant combines product knowledge with the screen the customer is using. It learns workflows by signing in and using the product, then uses that understanding to answer questions and guide people through tasks.

You can also connect documentation. A data-handling policy might explain where an exported report can be shared, something clicking through the reporting page would not tell the agent. Your team's guidance supplies that context.

Product access matters, too. Give the learning account access to the workflows you want it to understand. Where roles have different experiences, you can use separate agents and learning accounts for those experiences. A successful test with an owner's account is not sufficient evidence that the member experience works.

What changes when the product is the source of truth

The assistant has a way to learn navigation without waiting for someone to describe each click in an article. As the product changes, it can relearn the workflows. Your team still needs to maintain the connected policies and review how it answers.

The export question is a useful test. Ask it from the accounts your customers use. Does the answer lead to a control that account can access? If the task requires a different role, does it explain that requirement? When the answer is wrong, correct it and check again.

Keep the help center for explanations people need to read or refer back to. Evaluate the assistant on whether it helps them finish the task that brought them there. That gives your next content review a specific starting point: the questions customers still cannot resolve.

Can an in-product assistant replace a knowledge base?

An assistant can provide navigation and task guidance that would otherwise require an article. A knowledge base remains useful for policies, concepts, and information that is not visible in the interface. Frigade can use connected documentation alongside what it learns from the product.