A small SaaS team needs both live chat and a help center, but not on the same day. Chat tells you what people ask. The help center answers the questions that repeat. This guide gives the order I would use. I am building JustOneCX (disclosure), so the setup uses its chat widget and Help center. The advice works with any tool.
Why start with chat?
A help center only works if you already know the questions. Before you have users, you do not. Chat is how you find out. After 20 or 30 conversations you can see which three or four questions come up again and again. Those are your first FAQs. This is my opinion from how support usually works, not a measured result.
How does the chat widget work?
The SDK mounts a chat bubble in the bottom-right corner. You need no extra code.
- A visitor clicks the bubble. The SDK creates or resumes their open conversation.
- Messages arrive live over a WebSocket. If the socket does not connect within about three seconds, the widget polls every four seconds while the panel is open.
- Your team replies from the Inbox in the dashboard.
Outside business hours the visitor sees your offline message. It is shown only in the widget and is not saved as a conversation. Set business hours and the offline message before you turn chat on. An unattended bubble with no message is worse than no chat.
How do you make the replies faster?
- Use saved replies for questions you answer more than twice.
- Set routing rules so conversations reach the right person.
- Add a note, not a reply, for internal context.
- Look at what the person did in the product before they wrote. A conversation with the user's history takes less time to answer.
When do you add a help center?
When the same question shows up a third time. Then:
- Write the answer as an FAQ. Short, in the customer's words.
- Publish it. Only published FAQs show in the widget.
- If an answer needs more room or screenshots, write an article instead.
- If the answer is "click here, then here", build a tour and offer it in the Learn tab so people can start it themselves.
The Help center tabs only show when they have content: Help needs at least one published FAQ, Articles at least one published article, Learn at least one tour offered to the visitor. If no tab besides Chat has content, the panel opens a conversation right away.
A starting setup
- Day 1: chat on, business hours set, offline message written.
- Week 2: read every conversation. Tag the repeats.
- Week 3: publish five FAQs from the repeats.
- Month 2: write articles for anything an FAQ cannot cover.
- Then each month: look at what still reaches chat and decide: FAQ, article, tour or product fix.
The last one matters most. If many people ask how to do the same thing, the product might need to change, not the help text.
What next?
Read the guides for live chat and the Help center. If you want to see it first, you can book a demo.