What is in-app support?

What is in-app help?

In-app help is the self-serve layer of in-app support: a help launcher (usually a question-mark button) that opens a help panel inside the product. The panel searches the help center, shows suggested articles and often links to a video or a way to contact the team.

The advantage over a separate help center is that the user keeps their place. They don't lose the half-finished form in another tab, and the panel can suggest articles for the page they're on.

The limit is that articles are written once for everyone. They describe the general path, in the product's vocabulary, and the user still has to map it onto their own account and do every step.

How does in-app chat work?

In-app chat opens a conversation from inside the product, either with a support person or with an AI agent that answers first and passes to a person when it can't help.

Good in-app chat carries context the user would otherwise have to type: who they are, their plan, the page they're on, what they did just before they asked. A support person who can see that the user is an admin on the reports page, and that their last export failed, skips the first three questions.

Chat with a person suits problems that need judgment, like billing disputes or bugs. Chat with an AI agent suits the large volume of "how do I" and "where is" questions, at any hour.

What is in-app contextual help?

In-app contextual help is help attached to a specific part of the screen: a short explanation on a field, a link next to a setting, a tooltip on an icon, or a help panel that opens to the article for the current page.

It works because it answers before the user has to ask, at the point of confusion. Take a payroll product: a new admin reaches the tax settings screen, unsure which filing frequency applies. A line of contextual help under the field ("Your filing frequency is on the registration letter from your tax agency") does more than a full article three clicks away.

The tradeoff is upkeep. Every piece of contextual help is tied to a screen, so it has to change whenever the screen does.

When should in-app support do the task, not just explain it?

Most in-app support explains. That's right for questions about why something works the way it does. But a large share of what users ask is really a request: "how do I add a teammate to the Finance workspace?" means "add this person to the Finance workspace."

When support can only explain, the user reads the steps and then does them. When an agent can act, it confirms the details, does the step within that user's permissions and shows the result. The user gets the outcome without the detour through the instructions.

Foldspace puts both in one help panel: the Product Agent answers from the product's knowledge when the question is why, takes users to the right page when they need to look, and carries out the actions it has been built for, through the product's own APIs, when the question is really a request.