A help center gives customers answers before they wait for a person. For a SaaS the software matters less than what you put in it and where it shows up. This post lists what to look for and what to write first.
What should help center software do?
- Show up inside your product, not only on a separate website. Most questions come while a person is using the app.
- Hold more than one kind of content. Short FAQs for quick answers, longer articles for how-tos, and guided tours for tasks that are easier to show.
- Sit next to chat. When the answer is not there, the person should be able to start a conversation from the same panel.
- Show only what exists. An empty tab is worse than no tab.
- Respect who the person is. Tours and answers should match the visitor.
How does a help center work in JustOneCX?
It lives in the chat widget. When a visitor first opens the panel, they see tabs: Chat, Help (FAQs), Articles and Learn (tours the visitor can start themselves). A tab only shows when it has something to read. If nothing besides Chat has content, the panel opens a conversation right away.
What should you write first?
Do not write a hundred articles. Start from real questions.
- Week 1: turn on chat and read every conversation.
- Week 2: tag the repeats. A question that comes up a third time is an FAQ.
- Week 3: publish five FAQs, in the customer's words, with a short answer each.
- Month 2: write articles for anything an FAQ cannot cover. Add screenshots.
- Then: for "click here, then here" answers, build a tour and offer it in the Learn tab.
How do you know it works?
Look at what still reaches chat. If many people ask how to do the same thing, the product may need to change, not the help text. Review it monthly.
Next steps
The chat and help center guide goes through the order step by step. The help center feature page lists what it includes.