Skip to main content

SCA Customer Knowledge Base Publishing Guide

Purpose​

This comprehensive guide ensures flawless publication of content to the Symphony Core Customer Knowledge Base portal. Following these guidelines will prevent formatting issues, maintain brand consistency, and deliver maximum value to prospects and customers.

🚨 CRITICAL FORMATTING RULES​

Rule #1: NEVER Use HTML Code Blocks​

The knowledge base system renders HTML instead of displaying it as code. This causes major formatting problems.

❌ WRONG:

<!-- This will render as actual HTML -->
<div class="example">
  <p>Content</p>
</div>

✅ CORRECT: SCA's Automated Features:

  • Professional Headers: Automatically includes company logo and branding
  • Dynamic Content: Business information inserted automatically
  • Template Variables: Contact-specific details populated automatically

Rule #2: Describe Functionality Instead of Showing Code​

Focus on WHAT the system does and WHY it benefits the user, not HOW it's technically implemented.

❌ WRONG: "SCA uses this HTML structure..." ✅ CORRECT: "SCA automatically generates professional email headers with your company logo and branding"

Rule #3: White-Label Terminology​

Always use "SCA" (Symphony Core App) instead of "GHL" (GoHighLevel) throughout all content.

📝 CONTENT STRUCTURE FRAMEWORK​

Article Hierarchy​

Use this exact structure for maximum impact:

  1. Executive Summary (2-3 sentences)
  2. Understanding Options (3 approaches)
  3. Detailed Feature Comparison (tables with clear winners)
  4. Critical Risk Analysis (⚠️ section highlighting dangers of alternatives)
  5. SCA Advantage Explanation (detailed benefits)
  6. Advanced Features (unique SCA capabilities)
  7. Implementation Recommendations (by business size)
  8. Cost Comparison (quantified savings)
  9. Migration Strategy (step-by-step transition)
  10. Conclusion (clear positioning and call-to-action)

Section Formatting Standards​

Headers:

  • H1: Article title only
  • H2: Major sections with ##
  • H3: Subsections with ###
  • Use descriptive, benefit-focused headers

Emphasis:

  • Bold for feature names and key benefits
  • Italics for file references and screenshots
  • ✅ ❌ for clear advantage/disadvantage indicators

Lists:

  • Use bullet points for features and benefits
  • Use numbered lists for processes and steps
  • Keep list items concise but descriptive

🎯 COMPETITIVE POSITIONING STRATEGY​

The Three-Option Framework​

Always present THREE options to establish SCA as the premium choice:

  1. Traditional/Competitor Approach (Limitations highlighted)
  2. SCA Native Solution (Professional capabilities)
  3. SCA Advanced/Hybrid (Best-in-class performance)

Comparison Tables​

Use this exact format:

| Feature | Competitor | SCA Option A | SCA Option B |
|---------|------------|--------------|--------------|
| **Key Feature** | Limitation | SCA Advantage | SCA Advantage |
| **Risk Factor** | ❌ High Risk | ✅ Protected | ✅ Protected |

Winner Declaration: Always end comparison sections with "Winner: [SCA Solution] - [Brief compelling reason]"

⚠️ CRITICAL RISK POSITIONING​

The "Hidden Danger" Framework​

Every article MUST include a section highlighting critical risks of NOT using SCA:

Structure:

  1. The Hidden Danger of [Alternative Approach]
  2. What Happens When [Problem Occurs]?
  3. Real-World Scenario: The [Disaster Type]
  4. Business Cost of [Problem]
  5. Industry Statistics

Risk Escalation Pattern​

Show how problems compound:

  1. Initial problem occurs
  2. Problem affects other business areas
  3. Cascading failures impact operations
  4. Recovery becomes expensive/difficult
  5. Long-term damage to business

SCA Protection Contrast​

Always follow risk scenarios with SCA's protection:

  • How SCA isolates problems
  • Automatic response systems
  • Business continuity maintenance
  • Expert support availability

🖼️ IMAGE AND MEDIA GUIDELINES​

Image Upload Process​

📍 IMPORTANT: Always upload images to the SCA - Operations sub account media folder before referencing them in articles.

Steps:

  1. Navigate to SCA - Operations sub account
  2. Go to Media Storage (as shown in provided screenshot)
  3. Upload all article images to appropriate folders
  4. Use the generated URLs in your knowledge base articles

Screenshot Specifications​

Required Screenshots:

  1. Interface Comparisons - Side-by-side SCA vs competitor interfaces
  2. Configuration Screens - SCA setup processes
  3. Feature Demonstrations - SCA capabilities in action
  4. Analytics Dashboards - Performance comparisons
  5. Mobile Views - Responsive design examples

Naming Convention:

  • sca-[feature-name]-[description].png
  • Example: sca-email-builder-interface.png

Screenshot Requirements:

  • High resolution (minimum 1200px width)
  • Clean, professional interface (no test data)
  • Highlight key features with callouts if needed
  • Show SCA branding clearly

Screenshot Reference Format​

## Screenshot References for Documentation

Include these specific screenshots in your knowledge base:

1. **[Feature Name]**
   - *File: sca-[feature]-[description].png*
   - [Description of what screenshot demonstrates]

2. **[Comparison Name]**  
   - *File: sca-vs-[competitor]-[feature].png*
   - [Explanation of comparison being shown]

💰 PRICING AND VALUE POSITIONING​

Cost Comparison Framework​

Traditional/Competitor Costs:

  • Monthly base cost
  • Required additional tools
  • Setup/development time (hourly rate)
  • Ongoing maintenance effort

SCA Complete Solution:

  • All-inclusive monthly pricing
  • Optional premium features (with clear ROI)
  • Minimal setup time with support
  • Automated maintenance

Savings Calculation: Always include: "Annual Savings with SCA: $[X,XXX] compared to [alternative approach]"

ROI Justification Elements​

  • Time savings (hours × hourly rate)
  • Avoided risks (potential loss prevention)
  • Increased efficiency (productivity gains)
  • Professional capabilities (competitive advantage)

📊 BUSINESS SEGMENTATION STRATEGY​

Implementation Recommendations Structure​

Always provide three tiers:

Small Business (0-X customers/employees):

  • Recommended SCA solution
  • Why it fits this segment
  • Key benefits for size
  • Growth accommodation

Growing Business (X-XX range):

  • Recommended SCA solution
  • Advanced features needed
  • Scalability considerations
  • Professional requirements

Enterprise (XX+ range):

  • Premium SCA solution
  • Enterprise-specific benefits
  • Advanced integration needs
  • Dedicated support levels

🔄 MIGRATION AND IMPLEMENTATION GUIDANCE​

Migration Strategy Template​

Moving from [Current Solution] to SCA:

  1. [Preparation Step] - Data export and analysis
  2. [Configuration Step] - SCA system setup
  3. [Import Step] - Data migration process
  4. [Customization Step] - Feature configuration
  5. [Testing Step] - Validation and optimization
  6. [Launch Step] - Go-live process

Timeline: Always provide realistic timeframes Support: Mention available implementation assistance

✍️ WRITING STYLE GUIDELINES​

Tone and Voice​

  • Professional but accessible
  • Confident without being arrogant
  • Helpful and solution-focused
  • Urgent when discussing risks
  • Aspirational when describing benefits

Customer-Centric Language​

  • Focus on business outcomes, not features
  • Use "you" and "your business" frequently
  • Avoid technical jargon unless necessary
  • Emphasize competitive advantages
  • Include real-world scenarios

Power Words and Phrases​

For Benefits:

  • "Professional infrastructure designed for..."
  • "Automatic protection against..."
  • "Seamless integration with..."
  • "Enterprise-level capabilities..."
  • "Complete solution that..."

For Risks:

  • "Critical risk of..."
  • "Hidden danger of..."
  • "Catastrophic impact when..."
  • "Business-threatening consequences..."
  • "Devastating effects of..."

🔍 QUALITY ASSURANCE CHECKLIST​

Pre-Publication Review​

Content Requirements:

  • Uses SCA terminology (not GHL)
  • Includes executive summary
  • Has comparison tables with clear winners
  • Contains critical risk analysis section
  • Provides implementation recommendations
  • Includes cost comparison with savings
  • Offers migration strategy
  • Ends with compelling call-to-action

Formatting Check:

  • No HTML code blocks or technical implementation details
  • Proper header hierarchy (H2, H3 structure)
  • Consistent formatting throughout
  • Screenshots uploaded to SCA media storage
  • Image references properly formatted
  • Tables formatted correctly
  • Lists are properly structured

Competitive Positioning:

  • Three-option framework implemented
  • SCA positioned as premium solution
  • Competitor limitations clearly highlighted
  • Risk scenarios demonstrate urgency
  • Benefits quantified where possible

Business Value:

  • ROI clearly demonstrated
  • Business segment recommendations included
  • Real-world scenarios included
  • Industry statistics support arguments
  • Migration path clearly outlined

📋 COMMON MISTAKES TO AVOID​

Technical Mistakes​

❌ Including HTML/CSS code examples ❌ Using technical implementation details ❌ Showing backend configuration screenshots ❌ Referencing specific API endpoints or technical specs

Content Mistakes​

❌ Using GHL instead of SCA terminology ❌ Focusing on features instead of business benefits ❌ Not including risk analysis for alternatives ❌ Missing cost comparisons and ROI calculations ❌ Vague implementation recommendations

Formatting Mistakes​

❌ Inconsistent header structure ❌ Missing comparison table winners ❌ No screenshot references ❌ Poor list formatting ❌ Missing call-to-action

Positioning Mistakes​

❌ Not establishing SCA as premium solution ❌ Weak competitive differentiation ❌ Missing urgency in risk scenarios ❌ No business segmentation strategy ❌ Unclear migration path

🚀 PUBLICATION WORKFLOW​

Step-by-Step Process​

  1. Content Creation

    • Use the provided template structure
    • Research competitor limitations thoroughly
    • Identify specific SCA advantages
    • Develop compelling risk scenarios

  2. Screenshot Preparation

    • Take high-quality screenshots in SCA
    • Upload to SCA - Operations media storage
    • Note file names for article references
    • Ensure professional appearance

  3. Content Review

    • Complete quality assurance checklist
    • Verify all white-label terminology
    • Confirm competitive positioning strength
    • Validate business value propositions

  4. Publication

    • Copy content to knowledge base portal
    • Add screenshots using media storage URLs
    • Test formatting and links
    • Review final published appearance

  5. Post-Publication

    • Monitor for formatting issues
    • Track engagement and feedback
    • Update content based on user questions
    • Maintain accuracy with SCA updates

📞 SUPPORT AND RESOURCES​

When to Use This Guide​

  • Creating new knowledge base articles
  • Updating existing customer documentation
  • Developing competitive positioning content
  • Training team members on content creation

Additional Resources​

  • SCA feature documentation (for accuracy)
  • Competitor analysis reports (for positioning)
  • Customer feedback (for pain points)
  • Sales team insights (for objections)

Success Metrics​

  • Customer self-service resolution rates
  • Prospect engagement with articles
  • Sales team usage of content
  • Competitive win rates improvement

This guide ensures every knowledge base article delivers maximum value while maintaining professional standards and effective competitive positioning. Follow these guidelines for flawless content that drives business results.