Support AI Skill

Self Service Portal Optimization

Design, build, and continuously optimize a self-service portal that enables customers to find answers and resolve issues without contacting support. Use when building a help center, improving self-service deflection rates, optimizing knowledge base search, reducing ticket volume through self-help, or measuring self-service effectiveness. Triggers on phrases like "self-service portal", "help center design", "deflection strategy", "self-help portal", "self-service optimization", "help center metrics", "customer self-service", "portal UX", "deflection rate", "self-service analytics".

Self-Service Portal Design & Optimization

Build and continuously optimize a self-service portal that empowers customers to find answers independently — reducing ticket volume, improving response times, and lowering support costs.

Workflow

Audit current self-service channels (help center, FAQ, community, chatbot).
Analyze self-service usage data: search terms, article views, deflection rate.
Identify gaps: Topics with high search volume but low satisfaction.
Create/improve articles using customer language (from ticket analysis).
Optimize search: synonyms, suggestions, result ranking.
Implement portal UX best practices: clear navigation, fast search, mobile-friendly.
Add interactive elements: decision trees, diagnostic tools, video tutorials.
Measure deflection impact and iterate continuously.
Promote self-service at right moments in customer journey.

Portal Architecture

SELF-SERVICE PORTAL STRUCTURE
===============================

Core Components:
  1. SEARCH BAR (prominent, above the fold):
     → Natural language search (understands "how do I reset my password")
     → Auto-suggestions as user types (from popular searches + article titles)
     → Did-you-mean suggestions for typos
     → Search result categories: Articles, Videos, Community Posts, FAQs
     → Result ranking: Relevance + recency + popularity

  2. KNOWLEDGE BASE (organized by topic AND task):
     → Topic categories: Account, Billing, Features, Integrations, Troubleshooting
     → Task categories: Get Started, Configure, Use Daily, Troubleshoot, Manage
     → Each article: Clear title, step-by-step instructions, screenshots, video
     → Article metadata: Author, last reviewed date, applicable versions, tags

  3. COMMUNITY FORUM:
     → Customer-to-customer Q&A
     → Agent participation (marking answers, adding expertise)
     → Voting system (upvote helpful answers)
     → Topic categories mirror knowledge base structure

  4. DIAGNOSTIC TOOLS:
     → Interactive troubleshooting wizard (guided questions → solution)
     → System status checker (is your integration working?)
     → Configuration validator (is your setup correct?)
     → Self-fix tools (reset password, update billing, etc.)

  5. VIDEO LIBRARY:
     → Short tutorials (2–5 minutes each)
     → Organized by topic, featured on relevant articles
     → Transcripts for accessibility and searchability
     → Embedded YouTube or hosted on portal

PORTAL NAVIGATION MODEL:
  ════════════════════════════════════════════════════════════════════════
  Homepage Layout:
  ┌─────────────────────────────────────────────────────────────────┐
  │  [SEARCH BAR - "How can we help?"]                    [Sign In] │
  ├─────────────────────────────────────────────────────────────────┤
  │                                                                 │
  │  QUICK ACTIONS (top 5 most common tasks):                      │
  │  [Reset Password] [Update Billing] [Cancel Subscription]       │
  │  [API Docs] [System Status]                                   │
  │                                                                 │
  │  RECENTLY VIEWED (personalized if logged in):                   │
  │  • How to configure webhook integrations                       │
  │  • Export data to CSV                                          │
  │                                                                 │
  │  POPULAR ARTICLES (this week):                                  │
  │  • Setting up two-factor authentication (450 views)            │
  │  • Understanding billing cycles (380 views)                    │
  │  • Troubleshooting sync errors (320 views)                     │
  │                                                                 │
  │  CATEGORY CARDS (6 categories with icons):                     │
  │  [Getting Started] [Features] [Billing] [Integrations]         │
  │  [Troubleshooting] [API Docs]                                  │
  │                                                                 │
  │  COMMUNITY HIGHLIGHTS:                                          │
  │  • "How I automated my workflow" - 42 upvotes                 │
  │  • "Best practices for team onboarding" - 38 upvotes          │
  │                                                                 │
  │  SYSTEM STATUS: [All Systems Operational] ✓                    │
  │                                                                 │
  └─────────────────────────────────────────────────────────────────┘

Article Creation Best Practices

KNOWLEDGE BASE ARTICLE STANDARDS
==================================

Article Structure:
  → Title: Action-oriented, customer language ("How to export your data to CSV")
     NOT: "Data Export Functionality" (too vague, corporate language)
  → Summary: 2–3 sentences explaining what the article covers
  → Prerequisites: What the customer needs before starting
  → Step-by-step: Numbered instructions, one action per step
  → Screenshots: Annotated, current UI, relevant to step
  → Expected result: What customer should see after completing steps
  → Related articles: 2–3 linked articles for next steps
  → Still need help?: CTA to create ticket (pre-filled with article context)

Content Guidelines:
  → Tone: Conversational, helpful, customer-first
  → Length: 300–800 words (comprehensive but scannable)
  → Language: 8th grade reading level (accessible to all)
  → Avoid: Jargon, internal acronyms, assumed knowledge
  → Use: Bold for UI elements, code blocks for technical values
  → Update: Review quarterly; flag outdated articles

ARTICLE TYPES:
  ════════════════════════════════════════════════════════════════════════
  Type                  | When to Use               | Length     | Structure
  ════════════════════════════════════════════════════════════════════════
  How-to Guide          | Step-by-step task         | 500–800w   | Prerequisites → Steps → Result
  Troubleshooting       | Problem + solution        | 300–600w   | Symptoms → Cause → Fix
  FAQ                   | Common question           | 100–300w   | Question → Direct answer
  Overview              | Concept explanation       | 400–700w   | What → Why → How it works
  Release Notes         | New features              | 200–500w   | Feature → Benefit → How to use
  Video Tutorial        | Complex visual task       | 2–5 min    | Embedded video + transcript
  Decision Tree         | Multiple possible paths   | Interactive| If X, do Y → Else, do Z
  ════════════════════════════════════════════════════════════════════════

ARTICLE QUALITY CHECKLIST:
  → Is the title searchable (contains terms customers would type)?
  → Does the first paragraph answer the core question?
  → Are steps numbered and in logical order?
  → Is each step one action (not multiple combined)?
  → Are screenshots current and annotated?
  → Is there a clear expected result?
  → Are related articles linked?
  → Is there a "Still need help?" CTA?
  → Has article been tested with a real customer/new user?
  → Is the reading level accessible (below 10th grade)?

Search Optimization

SEARCH ENGINE OPTIMIZATION FOR PORTAL
=======================================

Search Quality Metrics:
  ════════════════════════════════════════════════════════════════════════
  Metric                            | Target
  ════════════════════════════════════════════════════════════════════════
  Search success rate               | > 75%
  Zero-result searches              | < 10%
  Click-through rate (search results)| > 60%
  Avg results per search            | 5–10 (not too few, not too many)
  First-result relevance            | > 70%
  Search-to-ticket conversion       | Track (lower = better search)
  ════════════════════════════════════════════════════════════════════════

Search Enhancement Strategies:
  1. SYNONYM MAPPING:
     → "login" = "sign in" = "access account" = "authentication"
     → "charge" = "billing" = "payment" = "invoice"
     → "sync issue" = "sync problem" = "data not updating" = "not syncing"
     → Map customer language to article language
     → Maintain synonym dictionary (review monthly)

  2. SEARCH SUGGESTIONS:
     → Top searched terms (update weekly)
     → Article titles as suggestions
     → "People also searched" (from search log analysis)
     → Seasonal suggestions (tax season → billing articles)

  3. RESULT RANKING:
     → Factors: Keyword match + recency + popularity + engagement
     → Boost: Articles with high CSAT/ratings
     → Bury: Outdated articles, low-engagement articles
     → A/B test ranking algorithms

  4. ZERO-RESULT HANDLING:
     → "No results found" → "We couldn't find articles for 'XYZ'"
     → Show: Similar articles (fuzzy match)
     → Show: "Most helpful articles" fallback
     → Show: "Ask the community" CTA
     → Log: Zero-result search term (review for content gap)

SEARCH TERM GAP ANALYSIS (Monthly):
  ════════════════════════════════════════════════════════════════════════
  Search Term            | Volume | Has Article | Action Needed
  ════════════════════════════════════════════════════════════════════════
  "how to cancel"        | 230    | Yes         | Boost ranking
  "two factor auth"      | 185    | Yes         | Add synonym
  "export my data"       | 145    | No          | CREATE ARTICLE
  "webhook not working"  | 120    | Partial     | Improve article
  "api rate limit"       | 98     | No          | CREATE ARTICLE
  "change email address" | 87     | Yes         | Add to quick actions
  "bulk update users"    | 76     | No          | CREATE ARTICLE
  ════════════════════════════════════════════════════════════════════════

Deflection Measurement

DEFLECTION ANALYSIS
====================

Deflection Rate Calculation:
  → True deflection: Customer searched/helped themselves AND would have
    contacted support WITHOUT self-service
  → Measured by:
     1. Post-article survey: "Were you able to resolve your issue?"
        Yes + "I was going to contact support" = Deflected
     2. Search → no ticket created (within 24 hours)
     3. Chatbot → article offered → customer accepts → no escalation
  → Typical deflection rate: 30–60% of total support demand

DEFLECTION METRICS:
  ════════════════════════════════════════════════════════════════════════
  Metric                            | Current   | Target
  ════════════════════════════════════════════════════════════════════════
  Self-service deflection rate       | 42%       | > 50%
  Articles read before ticket        | 1.2       | Track
  Search-to-ticket rate              | 28%       | < 25%
  Community post deflection          | 15%       | > 20%
  Chatbot deflection                 | 25%       | > 30%
  Total self-service sessions/month  | 12,000    | Growing
  Cost per self-service session      | $0.10     | < $0.15
  Cost per agent-assisted ticket     | $8.50     | Track
  ════════════════════════════════════════════════════════════════════════

DEFLECTION ROI:
  → Tickets deflected: 4,200/month (42% of 10,000 total demand)
  → Cost per deflected ticket: $0.10 (portal hosting, content creation)
  → Cost per agent ticket: $8.50
  → Savings per deflected ticket: $8.40
  → Monthly savings: 4,200 × $8.40 = $35,280
  → Annual savings: $423,360
  → Portal cost: $24,000/year (platform + content team)
  → Net savings: $399,360/year
  → ROI: 1,564%

SELF-SERVICE PROMOTION POINTS:
  → In-product: "Having trouble? Check our help center" (after error)
  → Email signatures: "Self-service portal: [link]"
  → Post-purchase: "Getting started guide: [link]"
  → Before chat: "Check these articles first?" (show top 3 relevant)
  → Onboarding flow: Embedded help center links at each step
  → Status page: Related help articles during outages

Integration Points

Help Desk (Zendesk Guide, Intercom Articles, Help Scout Docs): Knowledge base platform, article publishing, search
Analytics (Google Analytics, Mixpanel, Amplitude): Portal usage tracking, search analytics, funnel analysis
Search Engine (Elasticsearch, Algolia, Typesense): Full-text search, synonym management, result ranking
Community Platform (Discourse, Circle, Zendesk Sunshine): Customer forum, Q&A, voting
Chatbot (Intercom, Crisp, custom): Article suggestions, deflection, escalation
Video Platform (YouTube, Wistia, Vimeo): Video hosting, analytics, embedding
CMS (Contentful, WordPress, custom): Content management, workflow, versioning
CRM (Salesforce, HubSpot): Customer context for personalized portal experience

Edge Cases

Zero-result search frustration: Customer searches, finds nothing, gives up
Fallback: Always show "most helpful articles" even with zero results
CTA: "Can't find what you need? Ask the community" or "Contact support"
Log and review: Weekly review of zero-result search terms
Content gap alert: Notify content team when search term appears 10+ times with zero results
Fuzzy matching: Suggest similar terms automatically

Outdated articles causing harm: Customer follows old instructions, gets confused
Review cadence: Quarterly article review cycle
Stale content flag: "Last reviewed [date]" visible to customers
Customer feedback: "Was this article helpful? Yes/No" → flag consistently rated "No"
Version-specific: Tag articles by product version; show relevant versions
Breaking change protocol: Update all affected articles within 48 hours of release

Article exists but customer can't find it: Search not returning right result
Synonym update: Add customer language to synonym dictionary
Title optimization: Use customer language in article titles
Boosting: Manually boost important articles in search results
Category navigation: Ensure logical category structure
Breadcrumbs: Help customers understand where they are in hierarchy
Analytics: Track "searched but didn't click" patterns

Mobile portal experience: 40%+ of self-service traffic from mobile
Responsive design: Portal works perfectly on phones and tablets
Touch-friendly: Large tap targets, easy scrolling
Fast load: < 2 seconds on mobile (optimize images, minimize JS)
Mobile-specific: Simplified navigation, prominent search
Progressive Web App: Installable, works offline for cached articles

Multi-language support: Customers in different countries
Translation strategy: Professional translation (not just Google Translate)
Prioritization: Translate top 100 articles first (by search volume)
Native speakers: Use community members or native-speaking staff for review
URL structure: /en/help/article, /es/help/article, /fr/help/article
Auto-detect: Redirect to language based on browser/locale settings
Fallback: Show English if translation not available (with language switcher)

Disclaimer: All rights reserved by Circulos AI. These skills are specifically designed for Claude Code, Claude Cowork, Codex, and OpenClaw. When using or referencing any skill, please provide proper attribution to Circulos AI.