HELP CENTER
Answers your customers can find without asking
Standalone portal
In-widget help
Article editor
Article feedback
How can we help?
Search articles
Getting started
Messenger setup
/help/getting-started/messenger/install
Install the messenger
Add one snippet, choose your tabs, and your help articles are searchable inside the same widget your customers already use.
Was this helpful?
Yes
No
THE PROBLEM
Support does not scale until customers can help themselves
The same question, every week
Your team retypes the same answer instead of solving the problems only they can solve.
Docs exist, nobody finds them
Content is scattered across a wiki, a PDF and someone’s Notion page, and search does not work.
Help lives somewhere else
Your customer is stuck inside your app, and your documentation is on a different domain in a different tab.
No signal on what is failing
You cannot tell which article is doing its job and which one is quietly sending people to your inbox.
Structured the way people search
Three levels, so an answer always arrives with its context.
Collections, categories, articles: group content so customers land somewhere that makes sense instead of on an orphan page.
Search across everything: every article, one keystroke away.
A real editor: write polished help content instead of fighting a text box.
Collection: Getting started
Category: Messenger
Article: Install the widget
Help, where your customer already is
The same knowledge base, two places, no duplicate content.
Inside the messenger: customers browse help without leaving your product or losing what they were doing.
As a standalone portal: a full public help center on your own domain, matching your brand colors automatically.
Never a dead end: the same widget has Messages, News and Roadmap when the article does not answer it.
Help
Messages
News
Roadmap
Search help without leaving chat
Built for search engines, not just search boxes
Every article lives at a readable, nested address that mirrors its place in your knowledge base.
Nested URLs make articles easier to share
The URL pattern is /help/collection/category/article, so links are self explanatory when a customer pastes one into Slack, and the structure is legible to search engines.
/help/billing/invoices/export-receipts
Find out what is not working
Readers mark an article as helpful or not, which gives you a clear signal on what is landing and what needs a rewrite. You stop guessing which docs to fix.
Article feedback
Helpful answers rise, weak articles get rewritten.
Self-serve is one stage of the loop
When the answer is not enough, the same customer-facing system carries the next step.
Start with one collection.
Write your first article today and it is live in your widget and your portal at the same time.