Introducing Help Center: Write Your Docs Once, Publish Them Anywhere
Most teams end up with their docs in one place and their product in another — a separate knowledge-base tool, a different login, a different design system, a link customers have to leave your app to click. The self-service support widget already let customers read a short Markdown note before reaching for a recording or a message. Help Center takes that further: a full, categorized, searchable-by-browsing article library, written right in your dashboard and published directly into your product.
No separate docs platform to license, theme, or keep in sync. One place to write, two ways to show it.
Two Ways to Publish the Same Content
Every article you publish is available through both of these at once — pick one, or use both for different parts of your product:
- Widget — a popup any button or link can open, the same trigger pattern as the support widget. Good for a persistent "Help" trigger in a nav bar or corner of your app.
- Embedded page — an iframe that renders the whole center inline, full height.
Good for a dedicated
/helpor/docsroute on your own site, no popup involved.
Neither one requires a rebuild when you edit an article. Publish a change in the dashboard and it's live in both places immediately.
A Two-Pane View by Default
Open the widget and it doesn't just show a flat list. By default it renders as a two-pane layout — a persistent, categorized article list on the left, the open article on the right — so customers can browse without losing their place. Prefer a smaller footprint? One click collapses it to a compact popup that swaps between the list and the article, the same way it always has.
Write Once, in Markdown
Articles are written in Markdown directly in your dashboard — headings, code blocks, links, images, all of it. Group them into categories so customers browse rather than search a flat list, and keep drafts unpublished until they're ready. A workspace can preview exactly what the live widget will render before anything goes out, using the same rendering the widget itself uses.
Match Your Brand
The widget ships with sensible defaults, but it doesn't have to look bolted on. Override colors and fonts with custom CSS scoped to the widget, so it reads as part of your product instead of a third-party overlay.
Add It in One Line
For the widget, drop one script tag on your site and mark any element as a trigger:
<script src="https://cdn.clairvio.dev/sdk/clairvio-help-widget.min.js"
data-workspace="cvio_your_sdk_key" async></script>
<!-- Add this attribute to any button or link: -->
<button data-clairvio-help>Help</button>For the embedded page, it's a single iframe:
<iframe
src="https://app.clairvio.dev/embed/help-center/cvio_your_sdk_key"
style="width:100%;height:600px;border:0;"
title="Help Center"
></iframe>Grab your workspace key from the dashboard and you're live — no build step, no dependency to install.
See It Live
We built our own Help Center on Help Center. The Help Center page on this site is a real, working install — the same widget your customers would get, showing our own published articles, with both embed methods on the page so you can compare them side by side before you decide which one fits your product.
When to Reach for Help Center
Clairvio's support tools cover three moments. Magic links are reactive — an agent pulls a specific customer into a session once a conversation is already underway. The support widget is for the instant something goes wrong — a customer clicks Help because they're stuck right now. Help Center is for everything before either of those: the setup steps, the "how do I" questions, the answers that stop a ticket from being opened in the first place. Run all three together and the widget's own help-docs path can point straight at the same articles.
Write it once. Let your customers find it wherever they run into a question.