Contextual documentation

Help where users get stuck

Publish guides once and they appear in the same in-app widget you already embedded — no extra code changes — so users get answers without leaving your product.

4 min read

Same widget, no new install

Contextual documentation surfaces in the widget you already embedded for feedback and roadmap. There is no second script, no extra launcher, and no code change when you add guides. Write once in your Votiq knowledge base and publish to the portal and the in-app panel together.

Portal and in-app, one knowledge base

The same articles appear on your public portal and inside the product. Prospects and sales get shareable links; customers mid-task get help without opening a new tab. Keep one source of truth so the website and the app never disagree.

Deflect tickets before they start

When someone opens the panel to ask for help or leave feedback, answers sit beside the request form. That deflects repeat how-to questions before they become tickets, and leaves cleaner feedback when someone still needs a human.

Measure it simply: fewer repeat questions in the shared inbox, more self-serve completions, and docs that stay in sync with your changelog when you ship.

How it works

1. Write guides in your Votiq knowledge base.

2. Publish to the portal and the existing in-app widget.

3. Users get answers without leaving your product.

Start with a few cornerstone articles (getting started, submit feedback, read the roadmap), then expand whenever the same question shows up twice.

Ready to set up

Create a workspace and embed the widget.

Most teams go live in under an hour — then publish help articles next to feedback, roadmap, and changelog.