### Explanation _No response_ ### Issue _No response_ ### Attestations - [ ] I have read and agree to the [Code of Conduct](https://docs.nhcarrigan.com/community/coc/) - [ ] I have read and agree to the [Community Guidelines](https://docs.nhcarrigan.com/community/guide/). - [ ] My contribution complies with the [Contributor Covenant](https://docs.nhcarrigan.com/dev/covenant/). ### Dependencies - [ ] I have pinned the dependencies to a specific patch version. ### Style - [ ] I have run the linter and resolved any errors. - [ ] My pull request uses an appropriate title, matching the conventional commit standards. - [ ] My scope of feat/fix/chore/etc. correctly matches the nature of changes in my pull request. ### Tests - [ ] My contribution adds new code, and I have added tests to cover it. - [ ] My contribution modifies existing code, and I have updated the tests to reflect these changes. - [ ] All new and existing tests pass locally with my changes. - [ ] Code coverage remains at or above the configured threshold. ### Documentation _No response_ ### Versioning _No response_ Reviewed-on: #21 Co-authored-by: Naomi Carrigan <commits@nhcarrigan.com> Co-committed-by: Naomi Carrigan <commits@nhcarrigan.com>
10 KiB
title
| title |
|---|
| Support Forum Moderation Training for Staff |
ESSENTIAL TRAINING FOR FORUM MODERATION TEAM
1. INTRODUCTION AND SCOPE
1.1. Purpose of This Training
This training document provides comprehensive guidance for Team members responsible for moderating our Support Forum at support.nhcarrigan.com. The Support Forum serves as our primary platform for structured support requests, bug reports, feature requests, and community feedback.
1.2. Forum Structure and Categories
Our Support Forum is organised into the following categories:
(a) Technical Support (ID: 5): Platform and product assistance;
(b) Bug Reports (ID: 6): Software issues and defect reporting;
(c) Feature Requests (ID: 7): Enhancement suggestions and new features;
(d) Community Feedback (ID: 8): General community input and suggestions;
(e) Policy Ideation (ID: 9): Policy suggestions and governance input;
(f) Accessibility Feedback (ID: 10): Accessibility barriers and improvements;
(g) Partnership Requests (ID: 11): Collaboration and partnership proposals;
(h) Legal Notices (ID: 12): Legal communications and formal notices;
(i) Billing Questions (ID: 13): Payment and subscription inquiries;
(j) Press Inquiries (ID: 14): Media and press communications;
(k) Marketing Proposals (ID: 15): Marketing collaborations and proposals.
1.3. Integration with Existing Policies
Forum moderation operates within our comprehensive policy framework:
(a) Content and Moderation Policy: Primary content standards and enforcement;
(b) Community Code of Conduct: Universal behavioural expectations;
(c) Community Support Policy: Guidelines for support interactions;
(d) Privacy Policy: Handling of sensitive information in forum posts;
(e) Accessibility Policy: Ensuring forum accessibility for all users.
2. FORUM-SPECIFIC MODERATION CONSIDERATIONS
2.1. Unique Characteristics of Forum Moderation
2.1.1. Asynchronous Communication
Key Differences from Real-Time Platforms:
- Extended response timeframes are acceptable and expected
- Conversations develop over days or weeks rather than minutes
- Users expect more thoughtful, detailed responses
- Documentation and searchability are primary concerns
2.1.2. Persistent Content
Long-Term Visibility:
- Forum posts remain searchable indefinitely
- Content serves as knowledge base for future users
- Higher standards for accuracy and completeness
- Regular review and updating of outdated information
2.1.3. Structured Support
Organised Communication:
- Clear categorisation enables efficient routing
- Topic-based organisation aids in knowledge management
- Threaded discussions maintain context
- Solution marking helps future users
2.2. Forum Moderation Best Practices
2.2.1. Thread Management
Effective Thread Moderation:
- Title Clarity: Ensure thread titles accurately describe the issue
- Categorisation: Move threads to appropriate categories when needed
- Duplicate Management: Merge duplicate threads while preserving context
- Solution Marking: Identify and mark solved threads
- Pinning: Pin important announcements or frequently referenced threads
2.2.2. Response Standards
Quality Expectations:
- Comprehensive initial responses that address all aspects
- Professional tone maintaining community warmth
- Clear action items or next steps
- Appropriate escalation when needed
- Follow-up on unresolved threads
3. CATEGORY-SPECIFIC GUIDELINES
3.1. Technical Support
Moderation Focus:
- Verify sufficient system information is provided
- Request clarification on reproduction steps
- Tag technical team members when appropriate
- Ensure privacy (no passwords, API keys, etc.)
- Mark solutions when issues are resolved
3.2. Bug Reports
Moderation Requirements:
- Confirm reports include reproduction steps
- Check for duplicate reports before allowing
- Apply appropriate priority labels
- Link to tracking systems when applicable
- Update thread status as bugs are addressed
3.3. Feature Requests
Management Approach:
- Encourage detailed use case descriptions
- Facilitate community discussion on proposals
- Consolidate similar requests
- Communicate feasibility assessments
- Update on implementation progress
3.4. Community Feedback
Engagement Standards:
- Acknowledge all feedback respectfully
- Encourage constructive criticism
- Synthesise feedback for leadership review
- Communicate how feedback influences decisions
- Create feedback summary reports
3.5. Policy Ideation
Special Considerations:
- Ensure proposals align with community values
- Facilitate inclusive discussion
- Document consensus and dissent
- Forward viable proposals to governance team
- Communicate policy development progress
3.6. Accessibility Feedback
Priority Handling:
- Treat accessibility issues with urgency
- Ensure reports include assistive technology details
- Coordinate with accessibility team
- Track resolution progress
- Verify fixes with reporting users
3.7. Partnership Requests
Professional Standards:
- Maintain confidentiality as requested
- Verify legitimacy of proposals
- Route to appropriate decision-makers
- Facilitate initial discussions
- Document partnership criteria clearly
3.8. Legal Notices
Critical Procedures:
- Immediate escalation to legal team
- Preserve all original content
- Document receipt timestamps
- Maintain strict confidentiality
- Follow legal response protocols
3.9. Billing Questions
Sensitive Information Handling:
- Never request payment details in public threads
- Offer private thread conversion for sensitive matters
- Verify account ownership before discussing specifics
- Coordinate with billing team for resolutions
- Document common issues for FAQ development
3.10. Press Inquiries
Media Relations:
- Verify journalist credentials when appropriate
- Coordinate with communications team
- Maintain professional brand representation
- Facilitate interview scheduling
- Track press engagement metrics
3.11. Marketing Proposals
Evaluation Criteria:
- Assess alignment with brand values
- Check for spam or low-quality proposals
- Facilitate community input when appropriate
- Route serious proposals to marketing team
- Maintain proposal tracking system
4. MODERATION TOOLS AND FEATURES
4.1. Forum-Specific Tools
4.1.1. Thread Management Tools
- Move Thread: Relocate to appropriate category
- Merge Threads: Combine duplicate discussions
- Split Thread: Separate off-topic discussions
- Pin/Unpin: Control thread visibility priority
- Lock Thread: Prevent further replies when needed
- Mark Solution: Identify resolved issues
4.1.2. User Management Tools
- Trust Levels: Understand user permission tiers
- User Notes: Document moderation history
- Warnings: Issue formal warnings when needed
- Suspensions: Temporary access restrictions
- Thread Permissions: Control individual thread access
4.2. Content Moderation Features
4.2.1. Automated Moderation
- Spam Filters: Automatic spam detection
- Trust Level Restrictions: New user limitations
- Flag Queue: Community-reported content review
- Word Filters: Prohibited content blocking
- Link Restrictions: External link moderation
4.2.2. Manual Moderation Actions
- Edit Posts: Correct or redact content
- Delete Posts: Remove policy violations
- Hide Posts: Temporary removal pending review
- Restore Posts: Reinstate incorrectly removed content
- Revision History: Track all content changes
5. COMMON SCENARIOS AND RESPONSES
5.1. Scenario: Duplicate Bug Report
Appropriate Response:
- Search for existing reports
- Link to original thread
- Merge valuable additional information
- Close duplicate with explanation
- Guide user to original discussion
5.2. Scenario: Vague Support Request
Effective Approach:
- Request specific information needed
- Provide template for details
- Offer examples of good reports
- Remain patient and helpful
- Follow up if no response
5.3. Scenario: Heated Feature Request Debate
De-escalation Strategy:
- Remind participants of community standards
- Refocus on constructive discussion
- Separate technical merit from personal attacks
- Issue warnings if necessary
- Lock thread if situation escalates
5.4. Scenario: Sensitive Information Posted
Immediate Actions:
- Edit post to remove sensitive data
- Private message user about removal
- Educate on security best practices
- Document incident for patterns
- Review similar posts for exposure
6. FORUM COMMUNITY BUILDING
6.1. Encouraging Participation
Engagement Strategies:
- Welcome new users warmly
- Recognise helpful community members
- Create regular discussion topics
- Showcase community solutions
- Celebrate milestones and achievements
6.2. Knowledge Base Development
Content Curation:
- Identify frequently asked questions
- Create comprehensive guides
- Maintain solution database
- Update outdated information
- Cross-reference related topics
7. METRICS AND REPORTING
7.1. Key Performance Indicators
Forum Health Metrics:
- Response time to new threads
- Resolution rate for support requests
- User satisfaction indicators
- Community engagement levels
- Moderator action frequency
7.2. Regular Reporting
Documentation Requirements:
- Weekly moderation summaries
- Category-specific activity reports
- Escalation tracking
- Community feedback synthesis
- Improvement recommendations
8. CONTINUOUS IMPROVEMENT
8.1. Feedback Integration
Process Improvement:
- Regular community surveys
- Moderator experience sharing
- Policy effectiveness review
- Tool and feature requests
- Best practice documentation
8.2. Professional Development
Ongoing Training:
- Forum software updates
- New moderation techniques
- Community management trends
- Accessibility improvements
- Cross-platform coordination
This Forum Moderation Training provides comprehensive guidance for moderating our Support Forum. For questions about forum moderation procedures or to report issues with the forum platform, please contact the Moderation Team Lead through the designated staff channels.