help-center-design
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseHelp Center Design
帮助中心设计
Design AI-first help centers, knowledge bases, FAQs, and learning materials.
This skill reflects the shift from static help portals to AI-powered, embedded, personalized self-service systems.
设计AI优先的帮助中心、知识库、FAQ以及学习资料。
该能力体现了从静态帮助门户向AI驱动、嵌入式、个性化自助服务系统的转变。
Workflow (Use As Default Order)
工作流程(默认执行顺序)
- Define scope and constraints
- Audience/personas, product area(s), product versioning, channels (web/in-app), compliance requirements, localization needs.
- Inventory current knowledge
- Top tickets, top searches, top articles, top escalation reasons, and known content owners.
- Build information architecture
- Category structure, tagging, navigation, URL strategy, and internal linking.
- Standardize content
- Article types, templates, AI-friendly writing rules, and visual standards.
- Instrument and measure
- KPIs, event tracking, dashboards, and search query logging.
- Add AI support safely
- Retrieval-first answers, citations, confidence thresholds, escalation rules, and transactional guardrails.
- Run knowledge operations
- Governance, freshness detection, release-driven updates, and continuous optimization.
Expected outputs (adapt to request):
- Help center taxonomy map + tag schema
- Top 20 article backlog (by impact) + templates
- Analytics spec (events + dashboard KPIs)
- AI support spec (RAG sources, escalation thresholds, safety rules)
- Operating cadence (owners + review schedule)
- 定义范围与约束条件
- 受众/用户画像、产品领域、产品版本、渠道(网页/应用内)、合规要求、本地化需求。
- 盘点现有知识内容
- 高频工单、热门搜索、高访问量文章、主要问题升级原因,以及已知的内容负责人。
- 构建信息架构
- 分类结构、标签体系、导航设计、URL策略和内部链接。
- 标准化内容
- 文章类型、模板、AI友好的写作规则和视觉标准。
- 部署监控与度量
- 关键绩效指标(KPI)、事件追踪、仪表盘和搜索查询日志。
- 安全集成AI支持
- 检索优先的回答机制、引用来源、置信度阈值、问题升级规则和交易安全防护。
- 运行知识运营
- 治理机制、内容新鲜度检测、版本驱动的更新和持续优化。
预期输出(可根据需求调整):
- 帮助中心分类体系图 + 标签架构
- 影响度Top20文章待办清单 + 模板
- 数据分析规范(事件 + 仪表盘KPI)
- AI支持规范(RAG数据源、升级阈值、安全规则)
- 运营节奏(负责人 + 审核时间表)
Quick Reference
快速参考
Content Type Decision Matrix
内容类型决策矩阵
| User Need | Content Type | Format | AI Role |
|---|---|---|---|
| "How do I..." | How-To | Step-by-step | Suggest next steps |
| "Why isn't..." | Troubleshooting | Problem -> Cause -> Fix | Diagnose & resolve |
| "What is..." | Conceptual | Explanation | Summarize context |
| "Quick answer" | FAQ | Q&A pairs | Instant response |
| "Full specs" | Reference | Tables, lists | Search & retrieve |
| "Learn feature" | Tutorial | Video + interactive | Personalized path |
| 用户需求 | 内容类型 | 格式 | AI角色 |
|---|---|---|---|
| "如何操作..." | 操作指南 | 分步说明 | 建议下一步操作 |
| "为什么无法..." | 故障排查 | 问题->原因->解决方案 | 诊断并解决问题 |
| "什么是..." | 概念解释 | 说明文档 | 总结上下文信息 |
| "快速解答" | FAQ | 问答对 | 即时响应 |
| "完整规格" | 参考文档 | 表格、列表 | 搜索与检索 |
| "学习功能" | 教程 | 视频+交互式内容 | 个性化学习路径 |
Platform Selection (Verify Pricing And Plan Limits)
平台选择(请核实定价与计划限制)
| Company Stage | Platform | Monthly Cost | Best For |
|---|---|---|---|
| Enterprise | Zendesk | $55+/agent | Complex workflows, compliance |
| Growth/SaaS | Intercom | $29/seat + $0.99/resolution | Conversational, PLG |
| SMB/Startup | Freshdesk | $29-69/agent | Budget-friendly, native AI |
| Developer-focused | GitBook/Notion | $0-20/user | Docs-as-code |
See references/platform-guides.md for setup/migration notes and data/sources.json for curated comparison sources.
| 企业阶段 | 平台 | 月均成本 | 适用场景 |
|---|---|---|---|
| 企业级 | Zendesk | $55+/agent | 复杂工作流、合规要求 |
| 成长期/SaaS | Intercom | $29/seat + $0.99/resolution | 对话式交互、PLG模式 |
| 中小企业/初创公司 | Freshdesk | $29-69/agent | 高性价比、原生AI功能 |
| 开发者导向 | GitBook/Notion | $0-20/user | 文档即代码模式 |
更多设置/迁移说明请查看references/platform-guides.md, curated对比数据源请查看data/sources.json。
2025-2026 Best Practices
2025-2026年最佳实践
Key Shifts
核心转变
| Aspect | Traditional (Pre-2024) | Modern (2025-2026) |
|---|---|---|
| Support model | Separate help portal | Embedded in-app help |
| AI role | Search assistant | Higher automation with safe escalation |
| Search | Keyword matching | Semantic + RAG |
| Content | Text-heavy articles | Visual-first (video, GIF, screenshots) |
| Personalization | Same for all users | By role, version, behavior |
| Maintenance | Manual curation | AI-driven freshness detection |
| Navigation | Category browsing | Conversational + contextual |
Avoid quoting hard statistics without verification; refresh trends and benchmarks via data/sources.json when needed.
| 维度 | 传统模式(2024年前) | 现代模式(2025-2026) |
|---|---|---|
| 支持模式 | 独立帮助门户 | 嵌入式应用内帮助 |
| AI角色 | 搜索助手 | 高自动化+安全升级机制 |
| 搜索方式 | 关键词匹配 | 语义搜索+RAG |
| 内容形式 | 纯文本为主的文章 | 视觉优先(视频、GIF、截图) |
| 个性化程度 | 所有用户统一内容 | 按角色、版本、行为个性化 |
| 维护方式 | 人工整理 | AI驱动的内容新鲜度检测 |
| 导航方式 | 分类浏览 | 对话式+上下文导航 |
引用硬统计数据前请先核实;如需更新趋势与基准数据,请查看data/sources.json。
AI-First Principles
AI优先原则
- Agentic Resolution — AI executes tasks (refunds, bookings, updates), not just answers
- Semantic Understanding — Intent-based search, not keyword matching
- Proactive Assistance — Surface help before users ask
- Content Freshness — Auto-detect stale content, suggest updates
- Multi-Source Synthesis — Pull from docs, tickets, Slack, release notes
- Memory-Rich AI — Retain context across sessions for personalized support
- 智能任务执行 — AI不仅回答问题,还能执行任务(退款、预订、更新)
- 语义理解 — 基于意图的搜索,而非关键词匹配
- 主动协助 — 在用户提问前主动提供帮助
- 内容新鲜度 — 自动检测过期内容,建议更新
- 多源合成 — 从文档、工单、Slack、版本说明中提取信息
- 记忆型AI — 跨会话保留上下文,提供个性化支持
Emerging Trends (2026)
2026年新兴趋势
| Trend | Description | Impact |
|---|---|---|
| Voice Search | Users speak instead of type to find information | Requires natural language KB content |
| Proactive AI | AI detects/resolves issues before users report | Reduces inbound support volume |
| Embedded Help | Help surfaces in-context, not separate portal | Higher engagement, lower friction |
| AI Operations Lead | New role supervising AI agent behavior | Shift from execution to oversight |
| Hallucination Mitigation | RAG grounding to reduce AI fabrication | Requires citation/source linking |
| 趋势 | 描述 | 影响 |
|---|---|---|
| 语音搜索 | 用户通过语音而非文字查找信息 | 需要自然语言风格的知识库内容 |
| 主动式AI | AI在用户报告前检测并解决问题 | 降低 inbound支持请求量 |
| 嵌入式帮助 | 帮助内容在上下文场景中展示,而非独立门户 | 更高参与度、更低使用门槛 |
| AI运营负责人 — 新增角色,负责监督AI Agent行为 | 从执行转向监管 | |
| 幻觉缓解 | 基于RAG的事实锚定,减少AI生成错误内容 | 需要引用来源链接 |
Help Center Architecture
帮助中心架构
Category Structure Rules
分类结构规则
HIERARCHY LIMITS
- Maximum depth: 2-3 levels
- Top-level categories: 5-9 (cognitive load principle)
- Articles per category: 10-20 (scannable)
- Avoid: Deep nesting, internal org structureHIERARCHY LIMITS
- Maximum depth: 2-3 levels
- Top-level categories: 5-9 (cognitive load principle)
- Articles per category: 10-20 (scannable)
- Avoid: Deep nesting, internal org structureRecommended Top-Level Categories
推荐顶级分类
STANDARD CATEGORIES (adapt to product)
1. Getting Started — First-run, setup, quick wins
2. [Core Feature 1] — Primary use case
3. [Core Feature 2] — Secondary use case
4. Account & Billing — Settings, payments, security
5. Integrations — Third-party connections
6. Troubleshooting — Common issues, error codes
7. API & Developers — Technical documentation
8. What's New — Changelog, releasesSTANDARD CATEGORIES (adapt to product)
1. Getting Started — First-run, setup, quick wins
2. [Core Feature 1] — Primary use case
3. [Core Feature 2] — Secondary use case
4. Account & Billing — Settings, payments, security
5. Integrations — Third-party connections
6. Troubleshooting — Common issues, error codes
7. API & Developers — Technical documentation
8. What's New — Changelog, releasesNavigation Patterns
导航模式
- Breadcrumbs — Always show location in hierarchy
- Related Articles — 3-5 contextually relevant links
- Next Steps — Guide to logical next action
- Search Prominence — Above fold, always visible
- Popular Articles — Surface high-traffic content
- 面包屑导航 — 始终显示当前在层级中的位置
- 相关文章 — 3-5个上下文相关的链接
- 下一步操作 — 引导至逻辑后续动作
- 搜索突出显示 — 页面顶部,始终可见
- 热门文章 — 展示高流量内容
Article Types (Keep The Set Small)
文章类型(保持精简)
- How-To: task completion, 3-10 steps
- Troubleshooting: symptoms -> causes -> solutions
- FAQ: fast answers with links to deeper docs
- Conceptual: explain terms and mental models
- Reference: precise specs (tables, limits, error codes)
Use the copy-paste templates in references/article-templates.md.
- 操作指南:任务完成,3-10个步骤
- 故障排查:症状->原因->解决方案
- FAQ:快速解答,附带深度文档链接
- 概念解释:解释术语与思维模型
- 参考文档:精确规格(表格、限制、错误代码)
可使用references/article-templates.md中的复制粘贴模板。
AI Integration Patterns
AI集成模式
Chatbot Architecture
聊天机器人架构
MODERN AI SUPPORT FLOW (2025)
User query
-> Intent detection (semantic understanding)
-> RAG retrieval (KB + tickets + docs)
-> Response and action (answer and/or execute task)
-> Escalation check (confidence below threshold?)
-> Human agent (if needed)MODERN AI SUPPORT FLOW (2025)
User query
-> Intent detection (semantic understanding)
-> RAG retrieval (KB + tickets + docs)
-> Response and action (answer and/or execute task)
-> Escalation check (confidence below threshold?)
-> Human agent (if needed)Agentic AI Capabilities (2025-2026)
智能AI能力(2025-2026)
| Capability | Example | Platform |
|---|---|---|
| Task execution | Process refund | Ada, Zendesk AI |
| Appointment booking | Schedule call | Chatbase, Calendly |
| Account updates | Change plan | Fin AI, custom |
| Ticket creation | Escalate to human | All platforms |
| Multi-system lookup | Check order + shipping | MCP integrations |
| 能力 | 示例 | 平台 |
|---|---|---|
| 任务执行 | 处理退款 | Ada, Zendesk AI |
| 预约预订 | 安排通话 | Chatbase, Calendly |
| 账户更新 | 更改套餐 | Fin AI, 自定义开发 |
| 工单创建 | 升级至人工客服 | 所有平台 |
| 多系统查询 | 检查订单+物流状态 | MCP集成 |
Content for AI Consumption
AI可消费的内容规范
markdown
AI-FRIENDLY WRITING RULES
DO:
- Clear headings with keywords
- Structured data (tables, lists)
- Explicit step numbering
- Error messages verbatim
- Unique article titles
DON'T:
- Ambiguous pronouns
- Implicit assumptions
- Marketing fluff in support content
- Duplicate content across articlesSee references/ai-integration.md for RAG setup, evaluation, and escalation patterns.
markdown
AI-FRIENDLY WRITING RULES
DO:
- Clear headings with keywords
- Structured data (tables, lists)
- Explicit step numbering
- Error messages verbatim
- Unique article titles
DON'T:
- Ambiguous pronouns
- Implicit assumptions
- Marketing fluff in support content
- Duplicate content across articles更多RAG设置、评估与升级模式请查看references/ai-integration.md。
Metrics & KPIs
指标与KPI
Core Metrics
核心指标
| Metric | Definition | Benchmark |
|---|---|---|
| Self-Service Rate | % issues resolved without agent | 60-80% |
| Deflection Rate | Tickets avoided via KB | 30-50% |
| Search Success | % searches -> helpful result | >70% |
| CSAT (KB) | Article helpfulness rating | >80% positive |
| Time to Resolution | Self-service completion time | <3 min |
| Zero-Result Rate | Searches with no results | <5% |
| 指标 | 定义 | 基准值 |
|---|---|---|
| 自助服务率 | 无需人工介入解决的问题占比 | 60-80% |
| 工单分流率 | 通过知识库避免的工单占比 | 30-50% |
| 搜索成功率 | 搜索后获得有用结果的占比 | >70% |
| 知识库CSAT评分 | 文章有用性评分 | >80%好评 |
| 解决时长 | 自助服务完成时间 | <3分钟 |
| 零结果搜索率 | 无结果的搜索占比 | <5% |
Content Health Metrics
内容健康度指标
FRESHNESS INDICATORS
- Last updated > 6 months -> Review required
- Last updated > 12 months -> Likely stale
- No views in 90 days -> Consider archive
- High bounce rate -> Content mismatch
QUALITY INDICATORS
- Thumbs down > 20% -> Rewrite needed
- Escalation after viewing -> Content gap
- Search -> immediate exit -> Title mismatchFRESHNESS INDICATORS
- Last updated > 6 months -> Review required
- Last updated > 12 months -> Likely stale
- No views in 90 days -> Consider archive
- High bounce rate -> Content mismatch
QUALITY INDICATORS
- Thumbs down > 20% -> Rewrite needed
- Escalation after viewing -> Content gap
- Search -> immediate exit -> Title mismatchROI Calculation
ROI计算
SELF-SERVICE ROI FORMULA
Monthly Savings = (Deflected Tickets x $13) - Platform Cost
Example:
- 1,000 deflected tickets/month
- $13 average agent cost
- $500 platform cost
- ROI = ($13,000 - $500) = $12,500/monthSee references/metrics-optimization.md for instrumentation, dashboards, and optimization playbooks.
SELF-SERVICE ROI FORMULA
Monthly Savings = (Deflected Tickets x $13) - Platform Cost
Example:
- 1,000 deflected tickets/month
- $13 average agent cost
- $500 platform cost
- ROI = ($13,000 - $500) = $12,500/month更多监控、仪表盘与优化方法请查看references/metrics-optimization.md。
Learning & Onboarding
学习与入门
In-App Help Patterns
应用内帮助模式
| Pattern | Use Case | Tools |
|---|---|---|
| Tooltips | Field-level guidance | Native, Appcues |
| Hotspots | Feature discovery | UserPilot, Pendo |
| Checklists | Onboarding progress | Whatfix, Chameleon |
| Tours | New feature intro | Intercom, Appcues |
| Contextual Help | Error recovery | Custom, Zendesk |
| 模式 | 适用场景 | 工具 |
|---|---|---|
| 提示框 | 字段级指导 | 原生工具, Appcues |
| 热点指引 | 功能发现 | UserPilot, Pendo |
| 任务清单 | 入门进度追踪 | Whatfix, Chameleon |
| 功能导览 | 新功能介绍 | Intercom, Appcues |
| 上下文帮助 | 错误恢复 | 自定义开发, Zendesk |
Tutorial Best Practices (2025)
教程最佳实践(2025)
VIDEO TUTORIALS
- Length: 2-4 minutes (40% higher completion)
- Format: Screen recording + voiceover
- Chapters: Clickable sections
- Captions: Always include (accessibility)
INTERACTIVE GUIDES
- Click-through walkthroughs
- Sandbox environments
- Progress saving
- Skip option for experienced usersSee references/learning-paths.md for onboarding sequence design, accessibility, and measurement.
VIDEO TUTORIALS
- Length: 2-4 minutes (40% higher completion)
- Format: Screen recording + voiceover
- Chapters: Clickable sections
- Captions: Always include (accessibility)
INTERACTIVE GUIDES
- Click-through walkthroughs
- Sandbox environments
- Progress saving
- Skip option for experienced users更多入门序列设计、无障碍与度量方法请查看references/learning-paths.md。
Knowledge Operations (2026)
知识运营(2026)
Operate the help center like a product:
- Assign owners per category and per top article; define review cadence and SLAs for updates.
- Use release notes, incident reports, and ticket trends as automatic triggers for content updates.
- Use freshness signals (search exits, escalation after article view, downvotes) to prioritize rewrites.
See references/knowledge-ops.md for governance, workflows, and checklists.
像运营产品一样运营帮助中心:
- 为每个分类和热门文章分配负责人,定义审核节奏与更新SLA。
- 将版本说明、事件报告和工单趋势作为内容更新的自动触发条件。
- 使用新鲜度信号(搜索退出、查看文章后升级、差评)优先安排重写任务。
更多治理、工作流与检查清单请查看references/knowledge-ops.md。
Implementation Checklist
实施检查清单
Phase 1: Foundation (Week 1-2)
阶段1:基础搭建(第1-2周)
REQUIRED:
- Choose platform (Zendesk/Intercom/Freshdesk)
- Define category structure (5-9 top-level)
- Create article templates for each type
- Set up analytics tracking
- Configure search settings
REQUIRED:
- Choose platform (Zendesk/Intercom/Freshdesk)
- Define category structure (5-9 top-level)
- Create article templates for each type
- Set up analytics tracking
- Configure search settings
Phase 2: Content (Week 3-4)
阶段2:内容建设(第3-4周)
REQUIRED:
- Audit existing documentation
- Migrate/rewrite top 20 articles
- Add visual content (screenshots, GIFs)
- Implement internal linking
- Set up redirects from old URLs
REQUIRED:
- Audit existing documentation
- Migrate/rewrite top 20 articles
- Add visual content (screenshots, GIFs)
- Implement internal linking
- Set up redirects from old URLs
Phase 3: AI Integration (Week 5-6)
阶段3:AI集成(第5-6周)
REQUIRED:
- Enable AI chatbot
- Configure RAG/semantic search
- Set escalation thresholds
- Test common queries
- Monitor resolution rates
REQUIRED:
- Enable AI chatbot
- Configure RAG/semantic search
- Set escalation thresholds
- Test common queries
- Monitor resolution rates
Phase 4: Optimization (Ongoing)
阶段4:持续优化(长期)
REQUIRED:
- Review zero-result searches weekly
- Update stale content monthly
- A/B test article titles
- Analyze escalation patterns
- Expand based on ticket trends
REQUIRED:
- Review zero-result searches weekly
- Update stale content monthly
- A/B test article titles
- Analyze escalation patterns
- Expand based on ticket trends
Resources
资源
| Resource | Content |
|---|---|
| article-templates.md | Complete templates for all 5 article types |
| taxonomy-patterns.md | Category structures, tagging, search optimization |
| ai-integration.md | RAG setup, chatbot config, platform integrations |
| platform-guides.md | Zendesk, Intercom, Freshdesk, GitBook setup |
| learning-paths.md | Onboarding sequences, tutorial design, courses |
| metrics-optimization.md | KPI tracking, analytics, A/B testing |
| knowledge-ops.md | Governance, workflows, and operating cadence |
| sources.json | Curated sources with |
| 资源 | 内容 |
|---|---|
| article-templates.md | 5种文章类型的完整模板 |
| taxonomy-patterns.md | 分类结构、标签体系、搜索优化 |
| ai-integration.md | RAG设置、聊天机器人配置、平台集成 |
| platform-guides.md | Zendesk, Intercom, Freshdesk, GitBook设置指南 |
| learning-paths.md | 入门序列设计、教程开发、课程建设 |
| metrics-optimization.md | KPI追踪、数据分析、A/B测试 |
| knowledge-ops.md | 治理机制、工作流、运营节奏 |
| sources.json | 带 |
Trend Awareness Protocol
趋势感知协议
REQUIRED: When users ask recommendation questions about help centers, knowledge bases, or support platforms, run a quick web search to confirm current trends before answering. Prefer sources flagged in data/sources.json, plus official docs for any platform you recommend.
add_as_web_search: trueREQUIRED: 当用户询问关于帮助中心、知识库或支持平台的推荐问题时,请先进行快速网络搜索以确认当前趋势,再给出回答。优先使用data/sources.json中标记为的数据源,以及你推荐的任何平台的官方文档。
add_as_web_search: trueTrigger Conditions
触发条件
- "What's the best help center platform?"
- "What should I use for [knowledge base/FAQ/support]?"
- "What's the latest in customer self-service?"
- "Current best practices for [AI support/chatbots]?"
- "Is [Zendesk/Intercom/Freshdesk] still relevant in 2026?"
- "[Zendesk] vs [Intercom] vs [other]?"
- "Best AI chatbot for customer support?"
- "What's the best help center platform?"
- "What should I use for [knowledge base/FAQ/support]?"
- "What's the latest in customer self-service?"
- "Current best practices for [AI support/chatbots]?"
- "Is [Zendesk/Intercom/Freshdesk] still relevant in 2026?"
- "[Zendesk] vs [Intercom] vs [other]?"
- "Best AI chatbot for customer support?"
Required Searches
必做搜索
- Search:
"help center best practices 2026" - Search:
"[specific platform] vs alternatives 2026" - Search:
"AI customer support trends January 2026" - Search:
"knowledge base platforms 2026"
- Search:
"help center best practices 2026" - Search:
"[specific platform] vs alternatives 2026" - Search:
"AI customer support trends January 2026" - Search:
"knowledge base platforms 2026"
What to Report
汇报内容
After searching, provide:
- Current landscape: What support platforms/tools are popular NOW
- Emerging trends: New AI capabilities, patterns, or platforms gaining traction
- Deprecated/declining: Approaches or tools losing relevance
- Recommendation: Based on fresh data, not just static knowledge
If web search is unavailable, state that constraint and proceed with best-effort static guidance.
搜索后,请提供:
- 当前格局: 目前流行的支持平台/工具
- 新兴趋势: 正在兴起的AI能力、模式或平台
- 已淘汰/衰退: 逐渐过时的方法或工具
- 推荐方案: 基于最新数据,而非静态知识
如果无法进行网络搜索,请说明该限制,然后基于现有静态知识提供最佳建议。
Example Topics (verify with fresh search)
示例主题(请通过新鲜搜索核实)
- Help center platforms (Zendesk, Intercom, Freshdesk)
- AI support agents (Fin AI, Ada, Forethought)
- Knowledge base tools (Document360, GitBook, Notion)
- In-app guidance (UserPilot, Pendo, Chameleon)
- Self-service AI capabilities and resolution rates
- Semantic search and RAG for support
- Help center platforms (Zendesk, Intercom, Freshdesk)
- AI support agents (Fin AI, Ada, Forethought)
- Knowledge base tools (Document360, GitBook, Notion)
- In-app guidance (UserPilot, Pendo, Chameleon)
- Self-service AI capabilities and resolution rates
- Semantic search and RAG for support