1. Purpose
To standardize the configuration, management, and optimization of the Help Center and AI-powered Auto Assist. This SOP ensures a seamless self-service experience for customers while empowering agents through structured knowledge and automated guidance.
2. Help Center Hierarchy & Content Management
To maintain a searchable and intuitive knowledge base, all content must follow the established organizational structure.
2.1 Structural Hierarchy
Categories: The top-level containers. At least one category is required for the Help Center to function.
Note: If only one category exists, it remains hidden to end users to simplify the UI.
Sections: Nested within categories to group related articles.
Articles: Individual content pieces (tech notes, FAQs).
2.2 Permissions & Ownership
Article Ownership: Default ownership is assigned to the author but should be reassigned to the relevant Subject Matter Expert (SME) for long-term accountability.
Visibility Settings: * Agents/Admins Only: For internal processes and sensitive documentation.
All Users: For public-facing self-service.
Publishing Rights: Restrict "Publish" permissions to designated Leads/Admins to ensure quality control before content goes live.
3. Interface Customization & Brand Alignment
The Help Center should be visually consistent with the company brand to build user trust.
Theme Selection: Select themes from the Marketplace. Utilize free themes for iterative testing before investing in paid versions.
Visual Assets: Customize icons, brand colors, and header links to improve navigation clarity.
Activation Control: The Help Center visibility can be toggled "On" or "Off." Use the Deactivate setting during maintenance or phased rollouts to hide the portal from end users without affecting agent backend access.
4. AI-Powered Auto Assist Procedures
Procedures are the "instruction manuals" that allow AI to suggest the correct actions to agents.
4.1 Writing Procedures
Format: Use concise, step-by-step instructions.
Perspective: Write from the agent's point of view (e.g., "Check the user's subscription status" rather than "The system checks the status").
Naming: Use clear, descriptive titles so the AI can accurately match the procedure to the customer's query.
Integration: Include specific actions such as Tagging, Macros, and Field Changes within the procedure steps.
4.2 Testing & Quality Assurance
Before a full rollout, all Auto Assist procedures must be validated:
Controlled Group: Limit Auto Assist interaction to a specific test group of agents.
Test Environment: Create test tickets using email addresses not associated with agent profiles (AI ignores agent-to-agent comments).
Refinement: Iterate the procedure steps until the AI consistently offers the desired suggestions.
5. Agent Workflow Integration
Enhance efficiency by reducing context switching between the agent dashboard and the Help Center.
Agent Submissions: Enable the setting "Agents can submit/comment via Help Center."
Benefits: This allows agents to manage requests and view the knowledge base in a single interface, streamlining the support flow for multi-brand environments.
6. End-User Experience & Transparency
A transparent Help Center reduces ticket volume by discouraging duplicate submissions.
Request Tracking: Ensure users can see real-time statuses (Open, Waiting for Reply, Solved).
Profile Management: Allow users to track their followed articles and request history.
Deflection Strategy: Organize categories logically to encourage "Self-Service First" behavior, reducing the need for manual ticket creation.