Glossary of Knowledge Base Article Types
Knowledge Base Article — A self-contained piece of documentation designed to answer a specific question, explain a process, or solve a recurring problem. In the context of a Telegram CRM for support teams, knowledge base articles serve as the primary reference for agents handling tickets in topic groups. They are typically stored in a centralized repository and can be linked directly to response templates or suggested automatically based on the content of a conversation thread.
Standard Operating Procedure (SOP) Article — A step-by-step guide that describes how to perform a routine task, such as resetting a password or processing a refund. These articles are essential for maintaining consistency in agent assignment and ensuring that every ticket follows the same workflow. An SOP article often includes a checklist, screenshots, and a clear definition of when escalation is required under the organization’s escalation policy.
Troubleshooting Guide — An article that helps agents diagnose and resolve common technical issues. It typically presents a symptom, a list of possible causes, and a sequence of fixes to try. In a Telegram CRM environment, troubleshooting guides are frequently paired with canned responses to speed up first response time. They are most effective when organized by product or error code.
FAQ (Frequently Asked Questions) Article — A collection of common questions and their concise answers. Unlike a troubleshooting guide, an FAQ article is not structured as a linear diagnostic path. Instead, it groups related queries under thematic headings. FAQ articles are often surfaced by a bot intake form when a customer types a keyword in the support chat, reducing the need for manual agent intervention.
Policy or Compliance Article — A reference document that outlines the rules, regulations, or internal policies that govern how a support team operates. Examples include data privacy guidelines, refund policies, and SLA definitions. These articles are critical for queue management because they inform agents how to prioritize tickets and when to escalate based on service level agreement commitments.
Process Flow Article — A visual or textual representation of a multi-step workflow, such as the journey of a ticket from creation to resolution. It often includes decision points, triggers for webhook integration events, and handoffs between teams. Process flow articles help agents understand their role in the larger support ecosystem and reduce confusion during agent assignment.
Onboarding Article — A specialized article designed to help new agents learn the support platform, including how to use the Telegram CRM, navigate topic groups, and apply response templates. Onboarding articles often include a checklist of tasks to complete before handling live tickets, such as configuring their profile or reviewing the escalation policy.
Product Update or Release Note — An article that communicates changes to a product or service, such as new features, bug fixes, or deprecations. Support teams rely on these articles to update their knowledge base integration and ensure that canned responses reflect the current state of the product. Release notes are typically time-sensitive and should be archived after a set period.
Case Study or Success Story — A narrative article that describes how a specific customer or scenario was handled successfully. For example, a case study might detail how a team used template automation to reduce first response time by a measurable margin. These articles are useful for training and for demonstrating the value of the support system to stakeholders.
Glossary Article — The type you are reading now. It defines key terms and concepts used across the knowledge base. A glossary article helps agents build a shared vocabulary and reduces confusion when they encounter unfamiliar terms like “webhook integration” or “ticket status” in other articles.
Comparison or Decision Matrix Article — An article that helps agents choose between two or more options, such as which response template to use for a particular issue or when to escalate versus resolve a ticket. It often includes a table that lists criteria and recommended actions, making it a practical tool for queue management.
Training Module Article — A longer-form article that combines multiple concepts into a learning unit. For instance, a training module might cover the entire lifecycle of a ticket, from the bot intake form submission to resolution and feedback collection. These articles are often used in conjunction with quizzes or practical exercises.
Reference Sheet — A compact, data-dense article that provides quick access to frequently needed information, such as a list of support hours, escalation contacts, or common error codes. Reference sheets are designed for speed and are often pinned in a Telegram topic group for easy access during high-volume periods.
Escalation Path Article — A focused document that details the specific steps an agent must take when a ticket cannot be resolved at the first level. It defines triggers, such as exceeding the first response time or encountering a security issue, and specifies which team or individual to notify. Escalation path articles are a critical component of any escalation policy.
Script or Talk Track Article — A word-for-word script that agents can use when handling sensitive or high-stakes interactions, such as billing disputes or account closures. These articles ensure that messaging remains consistent and compliant with company policy. They are often stored as response templates within the Telegram CRM.
Post-Resolution Follow-Up Article — Guidance on what to do after a ticket is closed, such as sending a satisfaction survey, updating the knowledge base if the solution was new, or logging a bug. These articles help teams continuously improve their resolution time and knowledge base integration.
Integration Setup Article — A technical guide for configuring connections between the Telegram CRM and other tools, such as a help desk platform, a CRM system, or a webhook integration service. These articles are typically written for administrators and include API endpoints, authentication steps, and testing instructions.
Performance Benchmark Article — An article that defines and explains key metrics used to measure support quality, such as first response time, resolution time, and ticket volume. It helps agents understand how their performance is evaluated and how it relates to the broader service level agreement.
Customer Communication Template — A pre-written message that agents can adapt for common scenarios, such as acknowledging a ticket, requesting additional information, or confirming a resolution. These templates are stored as canned responses in the Telegram CRM and are a cornerstone of efficient agent assignment.
Feedback Collection Article — Instructions on how to gather and process feedback from customers after a ticket is resolved. This might include guidelines for sending surveys, analyzing responses, and feeding insights back into the knowledge base to improve future articles.
Security and Privacy Article — A document that outlines best practices for handling sensitive customer data within the support system. It covers topics like data retention, access controls, and how to report a breach. These articles are essential for compliance with regulations and for maintaining customer trust.
What to Check When Using Knowledge Base Articles
- Verify that the article is the most current version by checking its last updated date or version number.
- Confirm that the article aligns with your organization’s current escalation policy and service level agreement.
- Ensure that any response templates linked from the article are still active and correctly configured in the Telegram CRM.
- Test any webhook integration or bot intake form references to ensure they still function as described.
- Review the article for consistency with other related articles in the knowledge base, especially those covering overlapping topics.
Reader Comments (0)