Kamflo Logo

Kamflo

← Back to Blog
Help CenterSelf-ServiceProduct Guide

What Is a Help Center? How to Publish One — and Why Every Business Needs It

A help center lets your customers find answers without waiting for a support agent. Here's everything you need to know — what it is, what to put in it, how to publish one with Kamflo, and how to measure whether it's actually working.

August 28, 2025·12 min read·By Kamflo Team

70%

Customers prefer self-service over calling or emailing support

67%

Businesses report reduced support tickets after adding a help center

24/7

Help centers work around the clock — your agents don't have to

What is a help center?

A help center — also called a knowledge base, self-service portal, or support documentation site — is a publicly accessible collection of articles, guides, FAQs, and tutorials that customers can use to find answers to their questions on their own, without contacting your support team.

Think of it as a library for your product. Instead of a customer emailing you to ask "How do I reset my password?" and waiting 45 minutes for a reply, they search your help center, find the answer in 30 seconds, and get on with their day. No ticket created. No agent involved. No waiting.

The best help centers are organized around the questions your customers actually ask — not the questions you think they ask. They're written in plain language, easy to search, and kept up to date as your product evolves.

📚

A help center is not the same as a FAQ page. A FAQ page is a single page with a handful of questions. A help center is a full, organized, searchable knowledge base with multiple categories, dozens or hundreds of articles, and a structure that scales with your product.

Why every business needs one

There are three distinct groups who benefit from a help center — and the benefits are different for each.

Your customers benefit from instant answers

Customers who can find answers themselves report higher satisfaction scores than customers who had to contact support — even when the support experience was good. The reason is simple: speed and autonomy. Nobody enjoys waiting for someone to tell them something they could have looked up themselves. A well-built help center respects your customers' time.

Your support team benefits from reduced volume

Every question your help center answers is a ticket your team didn't have to handle. Businesses that launch a well-organized help center typically see a 30–60% reduction in inbound support volume within the first three months. That's the same three months where your team's capacity either stays flat or gets reallocated to higher-value conversations — complex issues, escalations, VIP customers.

Your business benefits from SEO and trust

Help center articles rank in search engines. When someone types "how to connect WhatsApp to my customer support tool" into Google, your help center article — if written and structured well — can appear in the results. That's free organic traffic from people who are actively looking for what you offer. It also communicates credibility: a comprehensive help center signals that you're a serious, established product worth trusting.

💡

The ROI of a help center is straightforward: if your average support ticket costs $8–15 to resolve (accounting for agent time, infrastructure, and overhead), and your help center deflects 500 tickets per month, that's $4,000–$7,500 in savings every month. From a page that required maybe 20 hours to build.

What to include in your help center

The content of your help center should be driven by what your customers actually ask. The simplest way to figure this out is to look at your support inbox. What are the top 20 questions you've answered in the last month? Those become your first 20 articles.

Getting Started section

Every help center should have a clear "Getting Started" category. This is where you put the content that new customers need most — how to set up their account, how to complete their first meaningful action, and what to do if something isn't working from the beginning. Getting started content has the highest traffic and the highest impact on early retention.

FAQs — the most read articles

Frequently asked questions are the backbone of any help center. These are the short, direct answers to the most common customer questions. Good FAQs are concise — a paragraph or two, not an essay. They answer exactly one question, clearly, and link to longer articles if someone needs more depth.

How-to guides and step-by-step tutorials

How-to guides walk customers through doing something specific. "How to connect WhatsApp Business to your support channel." "How to train your AI bot on a custom knowledge base." "How to invite a team member." These are process articles — they have a beginning, a middle, and an end. The best ones include numbered steps, screenshots or diagrams where helpful, and a clear statement of what the customer should have achieved by the end.

Troubleshooting guides

Troubleshooting guides address things that go wrong. "Why am I not receiving messages from WhatsApp?" "Why is my chat widget not appearing?" "My bot isn't answering questions correctly — what do I do?" These articles are especially valuable because they deflect the most frustrated contacts — customers who are blocked and might otherwise escalate.

Billing and account management

Billing questions are among the most common support tickets for any SaaS product. How to upgrade, downgrade, cancel, get a refund, download an invoice, change payment methods. These are high-stakes topics for customers and should be handled clearly and honestly in your help center, not hidden or made deliberately hard to find.

A starting structure for any SaaS help center

🚀 Getting Started

Account setup, first channel, basic navigation

💬 Live Chat & Inbox

Connection requests, conversation management, agent workflows

🤖 AI Bots

Creating a bot, training on a knowledge base, bot testing

🔌 Integrations

WhatsApp, Instagram, Slack, Telegram, email setup

🎫 Ticketing

Creating tickets, priorities, escalation, resolution

💳 Account & Billing

Plan changes, invoices, payment methods, cancellation

🛠️ Troubleshooting

Common errors, integration issues, bot problems

How to publish a help center with Kamflo

Publishing a help center in Kamflo is built directly into the channel workflow. Each channel can have its own help center — which means if you manage support for multiple clients or products, each one gets its own branded, independent help center.

Step 1: Open the Help Center integration

Navigate to your channel in Kamflo and click the Integrations button on the channel card. In the integrations panel, find "Help Center" and click Set Up. This opens the Help Center setup wizard.

Step 2: Brand your help center

In the first step of the setup wizard, you configure everything visual: your help center's name, the welcome tagline customers see on the homepage, your logo, your favicon (the small icon in the browser tab), your primary brand color, and your footer text. This step alone is what makes your help center feel like a native part of your product rather than a generic third-party tool.

Step 3: Set your domain

Choose between two options. The free option gives you a Kamflo subdomain in the format help.kamflo.com/your-workspace. Available on all plans. The Pro option lets you use your own custom domain — help.yourcompany.com — by adding a simple CNAME record to your DNS settings. This makes your help center completely brand-native.

Step 4: Organize your content

Define your article categories. You can choose from suggested categories (Getting Started, Account & Billing, Integrations, Troubleshooting, etc.) or add your own custom categories. Set your search bar placeholder text, decide whether to enable "Was this helpful?" article ratings, and whether to show a "Contact Support" button at the bottom of the help center for customers who still can't find what they need.

Step 5: Preview and publish

The preview step shows you exactly how your help center will look — with the correct colors, logo, and layout. A quick checklist confirms everything is in place before you go live. When you're ready, click Publish. Your help center is live immediately.

You can publish your help center before you've written a single article. Start with the structure — categories, domain, branding — and add articles in the weeks that follow. An empty but branded help center can go live the same day you sign up for Kamflo.

Step 6: Add articles from your Kamflo dashboard

After publishing, return to your channel and use the Help Center editor to write and publish articles. Each article belongs to a category, has a title, a rich text body, and optional metadata like read time and related articles. Articles can be saved as drafts before publishing, and published articles can be updated at any time without going through the setup wizard again.

Branding and customization

Your help center is a customer-facing product. It should look and feel like your brand — not like a generic third-party tool your customers have never seen before. Kamflo gives you full control over the elements that matter most for brand consistency.

Name & tagline

The H1 of your help center homepage. Should match your product's voice — professional, friendly, or technical, depending on your audience.

Logo

Appears in the header on every page of your help center. Use your horizontal wordmark or logo mark. PNG with transparent background works best.

Favicon

The small icon in the browser tab. When customers bookmark your help center, this is what they see. Use your logo mark — not the full wordmark.

Primary color

Used for buttons, links, hover states, and the category cards. Should match your product's main brand color for visual consistency.

Custom domain

The URL of your help center. help.yourcompany.com reads more professionally than a third-party subdomain and ranks better in search.

Footer text

Your copyright notice and any additional legal links you want at the bottom of every page.

How to write good help center articles

The technical setup is the easy part. The content is where most businesses struggle — not because they don't know their product, but because they write for people who already understand it. Your articles should be written for a customer who is confused, possibly frustrated, and looking for the fastest possible answer.

Start with the question, not the explanation

Most articles bury the answer. They spend three paragraphs explaining why the feature exists before they tell the customer what to do. Start with the answer. Then explain the context if needed. A customer searching "how do I reset my password" wants the reset steps in the first 50 words — not a paragraph about the importance of account security.

Use numbered steps for processes

Any article that involves a sequence of actions should use numbered steps. Not bullet points — numbered steps. Customers are following along while taking the action. They need to know where they are in the sequence. "Step 3 of 5" is immensely more useful than a bulleted list of things to do.

One article per topic

Resist the temptation to cover multiple questions in one article. "How to manage your account" covers too much. Break it down: "How to change your email address," "How to update your password," "How to change your plan." Specific articles rank better in search, are easier to link to, and are faster for customers to scan.

Keep the reading level accessible

Write at a reading level that a 12-year-old could follow. Not because your customers are children — but because customers reading support articles are under cognitive load. They're already confused about something. Simple, direct language reduces that load. Jargon increases it.

How to measure help center performance

Publishing a help center isn't the end of the work — it's the beginning. The articles that get the most views tell you what customers are struggling with most. The articles rated "not helpful" tell you where your documentation is failing. The search terms with no results tell you what articles you haven't written yet.

Metric

What it tells you

Target

Search deflection rate

% of users who search and find an article without contacting support

50%+

Article helpful rating

Whether your articles actually answer the customer's question

85%+

Top search terms

What customers are looking for — and whether you have it

Review weekly

Searches with no results

Topics you haven't documented yet

Publish ASAP

Contact rate after visit

How often customers still contact support after visiting the help center

Under 15%

Frequently asked questions

How long does it take to set up a help center in Kamflo?

The setup wizard takes 5–10 minutes. That includes branding, domain, and category configuration. You can publish immediately with zero articles and add content in the days and weeks that follow. Your first 10 articles can be written in a single focused afternoon.

Can I have a different help center for each channel?

Yes. Each channel in Kamflo can have its own independently branded help center. If you manage multiple client brands or product lines, each channel's help center is fully separate — different name, different logo, different domain, different articles.

Do help center articles rank in Google?

Yes, if your help center is on a custom domain and articles are well-structured with descriptive titles and clear content. Articles targeting specific question-based keywords (e.g. 'how to connect WhatsApp Business to customer support') can rank well, especially for long-tail search terms your competitors haven't covered.

Can customers submit a request directly from the help center?

Yes. Kamflo's help center can show a 'Contact Support' button that opens your live chat widget or submits a support ticket. You control whether this button appears, and it can be positioned at the bottom of articles or as a persistent floating button.

What happens to my help center if I downgrade my plan?

If you downgrade from a plan that includes a custom domain to one that doesn't, your help center remains live but reverts to the Kamflo subdomain. All articles and branding are preserved. You can re-add the custom domain at any time by upgrading.

Can I track which articles lead to support tickets?

Kamflo's analytics show article views, helpful ratings, search queries, and exit patterns. Articles with high 'not helpful' ratings that also correlate with high ticket volume are your priority for improvement.

Ready to publish your Help Center?

Set up a branded, searchable self-service portal for your customers in under 30 minutes — free to start.

Create your Help Center →