BuildBetter Docs

Write Help Docs from Customer Questions

You're answering the same questions over and over. "How do I export data?" "Where's the setting for X?" "Why isn't Y working?" Every answer is buried in a support ticket, never to be found again.

This guide shows you how to turn your most common customer questions into help documentation that deflects future tickets.

The Documentation Problem

Your reality:

The insight: Your support tickets already contain the perfect help articles. You just need to extract them.

What You'll Achieve

With BuildBetter:

Info: Time investment: 2-3 hours to create your first 5 help articles. Impact: Each article prevents 5-20 tickets/month.

Prerequisites

Success: BuildBetter account

Success: Support ticket history or call recordings with customer questions

Success: Place to publish docs (help center, Notion, Confluence, etc.)


Step 1: Find Your Most Asked Questions

[screenshot: Signals filtered for questions]

1. Import Support Data

If you haven't already:

2. Filter for Questions

  1. Go to Signals
  2. Filter by Type: Question
  3. Sort by frequency or count

[screenshot: Questions sorted by how many times asked]

You'll see:

3. Ask Chat for Top Questions

Query: "What are the top 10 most frequently asked customer questions? Group similar questions together."

[screenshot: Chat showing top questions with counts]

Example output:

Top 10 Customer Questions (Last 6 Months):

1. Export Functionality (67 tickets)
   - "How do I export to Excel?"
   - "Can I export to CSV?"
   - "Where is the export button?"

2. Account Settings (52 tickets)
   - "How do I change my email?"
   - "Can I update my password?"
   - "Where are account settings?"

3. API Access (41 tickets)
   - "Where is my API key?"
   - "How do I generate an API token?"
   - "API documentation link?"

[... continues]

Step 2: Extract Your Best Answers

[screenshot: Support ticket with good answer highlighted as signal]

1. Find Successful Resolutions

For each common question:

  1. Click on the question signal
  2. View all instances across tickets
  3. Look for answers that:
    • Resolved the issue quickly
    • Customer said "thank you" or "that worked"
    • Are clear and complete

[screenshot: Ticket thread showing question and successful answer]

2. Generate Article Draft

Query Chat: "Create a help article for [question topic]. Include: the question, step-by-step answer, screenshots needed, and common variations of this question."

[screenshot: Chat generating help article]

Example output:

Help Article: How to Export Your Data

Common Questions (67 tickets):
- "How do I export to Excel?"
- "Can I export to CSV?"
- "Where is the export button?"

Answer:

You can export your data in multiple formats:

Step 1: Navigate to Reports
- Click "Reports" in the left sidebar
- [Screenshot needed: Reports page]

Step 2: Select Export Format
- Click the "Export" button (top right)
- Choose format: CSV, Excel, or PDF
- [Screenshot needed: Export dropdown]

Step 3: Customize Export (Optional)
- Select date range
- Choose columns to include
- Click "Download"

Troubleshooting:
- Export button grayed out? You need View permissions
- Export taking long? Files over 10,000 rows take 2-5 mins
- Missing data? Check your date range filter

Related Articles:
- How to schedule automatic exports
- Export file size limits

3. Add Visual References

For each "screenshot needed":


Step 3: Prioritize Your Documentation

[screenshot: Documentation priority matrix]

1. Create Priority List

Query: "For each common question, tell me: ticket volume, deflection potential (% of tickets we could prevent), and effort to document (low/medium/high)."

Example output:

Documentation Priority Matrix:

🔴 HIGH PRIORITY (Do First)
1. Export Functionality
   - Volume: 67 tickets/6mo (11/month)
   - Deflection: 70% (8 tickets/month prevented)
   - Effort: Low (clear answer exists)
   - ROI: 4 hours/month saved

2. Account Settings
   - Volume: 52 tickets/6mo (9/month)
   - Deflection: 80% (7 tickets/month prevented)
   - Effort: Low
   - ROI: 3.5 hours/month saved

🟡 MEDIUM PRIORITY
3. API Access
   - Volume: 41 tickets/6mo (7/month)
   - Deflection: 60% (4 tickets/month)
   - Effort: Medium (needs dev input)
   - ROI: 2 hours/month saved

2. Start with Quick Wins

Focus on:

These give you biggest impact fastest.


Step 4: Publish & Measure

[screenshot: Help center with new articles published]

1. Publish to Help Center

  1. Copy article content to your help center
  2. Add screenshots
  3. Tag with keywords for search
  4. Link from related articles

2. Add In-App Links

Even better: Link to docs from your app

3. Track Impact

After 30 days:

Query: "Are we getting fewer tickets about export functionality since we published the help article?"

[screenshot: Ticket trend showing decline after doc published]

Measure:


Real Example: Taylor's Documentation Win

Background: Taylor is solo support at 40-person startup. 300 tickets/month. No help docs.

Week 1: Import 6 months of tickets to BuildBetter

Analysis:

Week 2: Created 3 help articles

Week 3: Added 2 more articles

Results after 60 days:

Most impactful: "Add team members" article

Taylor's quote: "I was writing the same answers over and over. BuildBetter showed me which questions to document first. 5 articles eliminated 70% of my repetitive tickets."


Best Practices

Success: Start with top 5: Don't try to document everything. Focus on highest volume questions.

Success: Use actual customer language: Title articles how customers ask, not how you'd describe it.

Success: Include variations: "How do I...?" + "Can I...?" + "Where is...?" all in same article for SEO

Success: Add screenshots: Visual guides work 3x better than text-only

Success: Link from app: Contextual help beats searchable help docs

Success: Update regularly: When you fix a bug or change UI, update docs immediately


Common Questions

What if customers still ask even with docs available?

Common reasons:

Track which articles have low deflection and improve them.

Should I document edge cases or just common scenarios?

Start with common (80% of tickets).

Add edge cases later if:

Don't document every possible scenario upfront.

How do I keep docs up to date?

When product changes:

  1. Update docs BEFORE releasing feature
  2. Review related support tickets after release
  3. Update docs based on new questions

Quarterly: Review top articles for accuracy

What if answer requires engineering fix, not docs?

Flag it for product/engineering:

BuildBetter helps you identify which is which. Product issues = engineering. Confusion = docs.


Next Steps


Stop answering the same questions. Write it once, help hundreds.

Info: Every repeated support question is an opportunity to create a help article. Document your top 10 questions and watch ticket volume drop 20-30%.

Note: Based on analysis of 300+ support teams. Average deflection rate per well-written help article: 60-80% for that specific question type.