Crafting SaaS Help Center Category Names That Describe Jobs, Not Topics
A help centre is often treated like a filing cabinet: every article is assigned to a broad subject such as billing, settings or integrations. Visitors can see the label, but they still have to work out where their immediate problem belongs. That small decision creates hesitation, repeated searches and avoidable support tickets.
Strong category names describe the job a customer is trying to complete. Instead of “Account,” a category might say “Update your account details”; instead of “Technical,” it might say “Fix sign-in and connection issues.” The distinction turns navigation into guidance. It mirrors the language people use when they ask for help rather than the internal structure of the product or support team.
The work is therefore both a language exercise and an information architecture exercise. The best labels are specific enough to set expectations, broad enough to contain useful articles, and consistent enough to make every touchpoint feel familiar. They help Australian SaaS teams meet customers wherever they work, whether they are in Sydney at lunchtime or troubleshooting at home in Perth after dinner.
Category labels should guide, not classify
Topic labels describe what a collection contains. Job-led labels describe what a customer can accomplish there. “Product features” and “How-to guides” organise content from the publisher’s point of view; “Set up your workspace” and “Get reports to the right people” organise it from the customer’s point of view.
That customer-centred framing is especially valuable in self-service. Someone scanning the help centre is often already blocked: a payment failed, an invitation was not received, or a sync has stopped. A clear action gives them a likely route forward before they abandon the task or open a contact form.
Category names also establish a compact vocabulary for search, onboarding emails and chat replies. When the same phrasing appears throughout the product and support experience, customers do not need to translate internal terms into customer language at every step. They spend less mental energy deciding where to click, which reduces cognitive load and makes the knowledge base easier to maintain.
Find the jobs inside your support tickets
Start with evidence, not a blank page. Export a sample of tickets from the last quarter and highlight the customer’s intended outcome in their own words. Common requests tend to emerge quickly: restore access, correct an invoice, connect a tool, change permissions, export data or understand what a setting does.
Grouping those requests by outcome reveals duplicate labels and missing paths. If “billing” contains invoices, refunds, plan changes and tax documents, ask whether visitors need one general category or several clearer choices. The goal is not to add levels for their own sake; it is to remove the moment when a customer cannot identify the right destination.
For a wider product-design perspective, Rainy Lemon product thinking can prompt a useful review of your own structure. Apply that lens to the help centre by placing a recognisable customer goal beside each category and checking whether the label predicts the articles inside it.
Build a hierarchy around customer tasks
A practical architecture often has three layers: a broad purpose, a specific task and a focused answer. At the top, keep destination categories such as “Get started,” “Manage your service” and “Get help.” Below them, use task categories such as “Invite your team,” “Connect an integration” and “Fix a failed sync.” Individual articles then answer one precise question.
This creates a useful test. A customer should be able to scan the second level and say, “That’s my task,” without opening an article. If the label only makes sense after reading its contents, it is probably describing a topic too closely or trying to cover too many jobs.
Be careful with categories that combine a task and a feature name, such as “Configure reports in Dashboard 2.” They age quickly when the product changes. Prefer durable language: “Build and share reports.” The customer’s job remains recognisable even if the interface, plan or underlying technology moves.
Write labels that sound like help
Use an action verb plus the object the customer recognises. “Manage team access,” “Connect your accounting tool” and “Export customer data” are immediately understandable. Add a qualifier only when it resolves genuine ambiguity, such as “Fix a failed sync.” Keep names at similar levels of specificity, avoid internal acronyms and resist the urge to explain the category inside the label itself.
Consistency matters as much as clarity. Choose one core vocabulary and use it across categories, article titles, search synonyms and support macros. If the product calls a workspace a “workspace,” do not alternate between “organisation,” “company” and “team” across the help centre. For Australian audiences, use Australian English such as “help centre,” “organisation” and “authorise” where applicable, unless those terms conflict with the interface shown in screenshots.
Search behaviour can reveal where labels miss. A customer typing “reset password” may need a category called “Recover access,” while a visitor searching “change plan” expects “Manage your plan and billing.” Support aliases and search-console data can connect different expressions to the same job without forcing unnatural labels onto the navigation.
Test names with real customer language
Test categories with the people who use them, not only with colleagues who know the product. Give participants a short set of realistic goals, such as adding a colleague to a workspace or finding last month’s invoice, and ask them to choose the category they expect to open. Their hesitation shows where a name is ambiguous.
Also test the route from category to resolution. A precise label can attract the wrong article if the first result answers a neighbouring task. Review the category introduction, the first two recommended articles and the next step offered at the bottom of each page. A coherent path should repeat the customer’s goal while narrowing towards a successful action.
Consistency extends beyond the help centre. A customer who reads a cancellation policy before deciding to leave should not meet a different tone in support. The thinking behind SaaS churn prevention messaging applies here: honest, clear guidance at difficult moments protects trust, while confusing terminology makes the experience feel obstructive.
Make the taxonomy work for Australian customers
Local details belong in the examples and articles a category contains. Australian SaaS businesses may need to explain AUD invoices, GST treatment, business email deliverability and privacy controls. A label such as “Manage invoices and GST” is more useful than “Billing” when both concepts are part of the job, but a broader “Manage plans and invoices” may be better if the help centre serves several markets.
Time zones and service coverage add another layer. Support teams commonly work Australian Eastern Standard Time or Australian Eastern Daylight Time, while customers in Brisbane, Perth and beyond may contact outside those hours. Clear categories such as “Set up automatic replies” or “Schedule reports for your team” let self-service carry work forward when live assistance is unavailable.
Compliance language should be plain and specific. If the product handles personal information, explain how Australian Privacy Principles and the Privacy Act 1988 affect relevant settings in language customers can act on. “Control your personal data” is a strong task category; “Privacy compliance” is not. Localisation also means checking date formats, public-holiday references and the Australian spelling used across the customer journey.
Roll out the change without creating a second maze
Migration is a content project, not a simple find-and-replace exercise. Inventory every category, map old topics to new job-led groups, redirect valuable URLs and update links from the website, app, onboarding emails and sales material. Preserve familiar article titles when they already work, but revise introductions and search terms so each page aligns with the new category.
Track a small set of useful measures: category clicks, successful searches, article engagement, support-ticket deflection, contact volume after a failed search and the number of articles assigned to the wrong category. Segment results by device, customer segment and lifecycle stage where volume allows. The aim is not merely fewer clicks; it is more completed tasks and less effort.
Review the taxonomy on a schedule and after significant product releases. Retire redundant categories, split groups that have become overloaded and add synonyms where customers use a phrase the interface does not. A help centre should evolve with the jobs customers are trying to finish, while keeping its vocabulary stable enough that returning users can navigate with confidence.
If your current categories name subjects rather than outcomes, map your most common support requests to customer jobs. Select the categories receiving the most traffic, write a task-led name for each and test the new path with real customer goals before changing every article.
SaaS Minds, led by Victoria Rudi, can embed messaging expertise with your team or take on a defined category-naming project. Bring your category list, support tickets and search terms to a focused workshop and leave with clear names, a practical content map and a rollout plan your Australian team can use.