Spaces:
Sleeping
Sleeping
Create content_gaps.md
Browse files- kb/content_gaps.md +51 -0
kb/content_gaps.md
ADDED
|
@@ -0,0 +1,51 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
# 📘 7. How to Identify Content Gaps Using Data
|
| 2 |
+
*Chat trends, search logs, case reasons, agent conversations*
|
| 3 |
+
|
| 4 |
+
|
| 5 |
+
Data reveals what users really need.
|
| 6 |
+
|
| 7 |
+
|
| 8 |
+
---
|
| 9 |
+
|
| 10 |
+
|
| 11 |
+
## 1. Use Search Logs
|
| 12 |
+
|
| 13 |
+
|
| 14 |
+
Identify:
|
| 15 |
+
- Zero-result searches
|
| 16 |
+
- High-search, low-click terms
|
| 17 |
+
- Searches that lead to cases
|
| 18 |
+
|
| 19 |
+
|
| 20 |
+
---
|
| 21 |
+
|
| 22 |
+
|
| 23 |
+
## 2. Analyze Support Channels
|
| 24 |
+
|
| 25 |
+
|
| 26 |
+
Look for:
|
| 27 |
+
- Repeated questions
|
| 28 |
+
- Confusing behaviors
|
| 29 |
+
- Missing information
|
| 30 |
+
|
| 31 |
+
|
| 32 |
+
---
|
| 33 |
+
|
| 34 |
+
|
| 35 |
+
## 3. Identify “Tribal Knowledge”
|
| 36 |
+
|
| 37 |
+
|
| 38 |
+
If agents rely on memory or Slack threads, content is missing.
|
| 39 |
+
|
| 40 |
+
|
| 41 |
+
---
|
| 42 |
+
|
| 43 |
+
|
| 44 |
+
## 4. Build a Content Gap Report
|
| 45 |
+
|
| 46 |
+
|
| 47 |
+
Include:
|
| 48 |
+
- Missing articles
|
| 49 |
+
- Outdated content
|
| 50 |
+
- Conflicting info
|
| 51 |
+
- Priority suggestions
|