How to Build a Technical Support Knowledge Base for LED Therapy B2B Customers
Our technical support team was answering the same 10 questions every day. “How do I pair the Bluetooth?” “The device won’t turn on, what do I do?” “What’s the warranty?” Each support ticket cost us $8-12 in labor. We built a knowledge base (KB) with 50 articles covering the most common questions. Support tickets dropped 40%. The KB cost $2,000 to create (writer + platform) and saved $15,000/year in support costs.
A knowledge base is not just a FAQ. It’s a structured library of answers that customers can search before contacting support. Here’s how to build one that actually reduces support tickets.
The Knowledge Base Structure
A good KB is organized by user journey, not by internal departments.
| Category | Articles | Example Topics |
| Getting Started | 5-10 articles | Unboxing, first use, pairing Bluetooth, charging |
| Product Usage | 10-15 articles | Treatment modes, recommended duration, positioning |
| Troubleshooting | 15-20 articles | Device won’t turn on, won’t charge, lights not working, app issues |
| Specifications | 5-10 articles | Wavelength, irradiance, battery life, dimensions |
| Warranty & Returns | 5-10 articles | Warranty terms, how to return, RMA process |
| Safety & Care | 5-10 articles | Cleaning, storage, contraindications, eye protection |
The troubleshooting category is the most important. This is where customers go when they have a problem. If the KB answers their question, they don’t open a support ticket. Each troubleshooting article should follow a clear structure: Symptom → Cause → Solution.
The Article Structure
Every KB article should follow a consistent structure.
| Section | Content | Example |
| Title | Clear, searchable (include keywords) | “Device won’t turn on: Troubleshooting steps” |
| Symptom | What the customer experiences | “You press the power button, but the device doesn’t turn on. No lights appear.” |
| Possible causes | List 3-5 potential causes | 1. Battery not charged, 2. Battery not connected, 3. Button failure, 4. Controller failure |
| Solution steps | Numbered steps to resolve | “Step 1: Charge the device for 2 hours…” |
| When to contact support | Clear criteria for escalating | “If none of the above steps work, contact support with the following info…” |
| Related articles | Links to related topics | “Related: How to charge your device”, “Warranty information” |
The “when to contact support” is essential. You don’t want customers to contact support for issues they can solve themselves. But you also don’t want them to struggle when the issue is a real defect. Define clear escalation criteria.
The Article Writing Guidelines
Write for the customer, not for engineers.
| Guideline | Good Example | Bad Example |
| Use simple language | “The device needs to be charged for 2 hours before first use” | “The Li-ion battery requires a minimum of 2 hours of charging prior to initial operation” |
| Be specific | “Press and hold the power button for 3 seconds” | “Press the power button for a few seconds” |
| Include photos/diagrams | Photo of button with arrow pointing to it | Just text description |
| Anticipate follow-up questions | “If the light still doesn’t turn on, check that the cable is fully inserted” | Just “Check the cable” |
| Use numbered steps | 1, 2, 3, 4 | Paragraphs of text |
The photos/diagrams are essential. A photo of the device with arrows pointing to the button, the charging port, etc., is worth 1,000 words. Most customers scan the KB article, they don’t read every word. Visuals help them find the answer quickly.
The Knowledge Base Platform
Choose a platform that’s searchable and accessible.
| Platform | Pros | Cons | Cost |
| Zendesk Help Center | Integrated with Zendesk support tickets, searchable | Requires Zendesk subscription | $50-100/month (Zendesk) |
| Intercom Articles | Integrated with Intercom chat | Requires Intercom subscription | $50-150/month |
| Notion (public pages) | Flexible, easy to update | Not purpose-built for KB, weaker search | Free-$10/month |
| WordPress (KB plugin) | Customizable, you own the data | Requires setup, maintenance | Free-$50/month (hosting) |
| GitBook | Designed for documentation, searchable | More technical feel | $0-50/month |
The Zendesk/Intercom integration is the most valuable. When a customer opens a support ticket, the agent can see which KB articles they’ve viewed. This tells the agent what the customer has already tried. And the agent can suggest relevant KB articles in the ticket response.
The search function is the #1 feature. Customers don’t browse the KB by category. They search. “Device won’t turn on.” Make sure the search is fast and accurate. Most platforms have decent search.
What We’ve Learned
1. The KB reduced support tickets by 40%. Before KB: 150 tickets/month. After KB: 90 tickets/month. The 60 tickets/month reduction at $10/ticket = $600/month = $7,200/year saved. The $2,000 KB creation cost paid for itself in 3 months.
2. The troubleshooting category is the most-viewed. 60% of KB traffic goes to troubleshooting articles. Focus your writing effort there. The “Getting Started” category gets 20%, and the rest gets 20%.
3. The #1 article is “Device won’t turn on.” It accounts for 25% of troubleshooting views. The article walks through: 1) Is it charged? 2) Is the battery connected? 3) Is the button working? 4) Contact support. This one article prevented 300+ support tickets in the first year.
4. The KB must be updated when the product changes. We launched a new version of the mask with a different button layout. We forgot to update the KB. Customers were confused (“The article shows a different button”). Update the KB whenever the product changes. Assign someone to own this.
5. The KB reduces support ticket resolution time by 30%. Even when customers do contact support, they’ve often already tried the troubleshooting steps. The agent doesn’t have to walk them through “Is it charged?” etc. The ticket resolution is faster and the customer is happier.
Building a technical support knowledge base for LED therapy B2B customers requires organizing by user journey (Getting Started, Usage, Troubleshooting, Specs, Warranty, Safety), writing structured articles (title, symptom, causes, steps, escalation, related articles), using simple language and visuals, choosing a platform with good search and integration (Zendesk/Intercom recommended), and updating the KB when the product changes. The 40% reduction in support tickets we achieved with a KB saved $7,200/year for a $2,000 creation cost. The KB is not a nice-to-have — it’s a support cost reduction tool. Start with the top 10 most-asked questions, write articles for them, and expand from there. Your support team (and customers) will thank you.