Glossary of Routing Priority Levels
Routing priority levels are numerical or categorical tags assigned to incoming support tickets within a Telegram CRM system. They determine the order in which tickets are surfaced to agents, the speed of first response, and the escalation path if resolution is delayed. These levels form the backbone of queue management in topic-based support groups.
Terms and Definitions
Priority Level
A priority level is a value, typically ranging from low to critical, that indicates the relative urgency and business impact of a ticket. It is assigned either automatically by a bot intake form based on keyword analysis or manually by an agent during triage.Low Priority
Low priority applies to non-urgent inquiries such as general product questions, feedback, or feature requests. These tickets are placed at the back of the work queue and may be answered during off-peak hours. First response time is typically longer, and no escalation policy is triggered automatically.Medium Priority
Medium priority covers standard support requests—account issues, billing questions, or guidance on product usage. These tickets receive a moderate first response time target and are handled by frontline agents. If unresolved within a defined window, they may be reclassified or escalated.High Priority
High priority is reserved for issues that disrupt normal operations but are not yet critical—such as payment failures, service degradation, or data access problems. These tickets bypass the regular queue and are assigned to senior agents. The escalation policy often triggers after a shorter interval.Critical Priority
Critical priority denotes system outages, security breaches, or compliance violations. Tickets at this level are flagged immediately, assigned to the most senior available agent, and may trigger a multi-channel alert via webhook integration. Resolution time is measured in minutes rather than hours.First Response Time (FRT)
FRT is the elapsed time between ticket creation and the first agent reply. Priority levels directly influence FRT targets: critical tickets may require a reply within minutes, while low-priority tickets might allow several hours. This metric is often tracked as part of a service level agreement.Resolution Time
Resolution time measures the total duration from ticket creation to closure. Higher-priority tickets are expected to have shorter resolution times. If a ticket exceeds its resolution time target, an escalation policy may automatically reassign it to a higher tier.Escalation Policy
An escalation policy defines the rules for reassigning a ticket to a more experienced agent or team when it remains unresolved past a threshold. Priority levels dictate the escalation criteria: critical tickets escalate after one missed SLA window, while medium tickets may escalate after two.Queue Management
Queue management refers to the system that organizes tickets based on priority, agent availability, and workload. In a Telegram topic group, tickets are represented as conversation threads. Agents can reorder their personal queue by filtering or sorting by priority level.Agent Assignment
Agent assignment is the process of matching a ticket to an agent. Routing rules consider priority level, agent skill set, and current workload. High-priority tickets are assigned to agents with fewer active tickets, ensuring faster attention.Ticket Status
Ticket status indicates the current stage of a ticket: open, in progress, waiting on customer, or resolved. Priority levels can influence which status transitions are allowed. For example, a critical ticket cannot be moved to "waiting on customer" without manager approval.Service Level Agreement (SLA)
An SLA is a contract between the support team and stakeholders that defines acceptable response and resolution times for each priority level. It is not a guaranteed metric but a target that the team strives to meet. SLAs are monitored via dashboards and reports.First Response SLA
First response SLA is the specific target for initial reply time per priority level. For example, critical tickets might have a 5-minute target, while low tickets have a 4-hour target. Breaching this SLA triggers notifications to team leads.Resolution SLA
Resolution SLA defines the maximum time allowed to close a ticket. This target varies by priority and complexity. If a ticket exceeds its resolution SLA, it may be automatically escalated or re-prioritized.Canned Response
A canned response is a pre-written reply used to answer common questions quickly. Priority levels influence which canned responses are suggested. For critical tickets, agents may be prompted to use a specific template that includes escalation contact information.Bot Intake Form
A bot intake form is a Telegram bot that collects initial information from a customer. Based on the answers, the bot assigns a preliminary priority level. This automation helps sort tickets before an agent reviews them.Webhook Integration
A webhook integration sends real-time notifications to external systems when a ticket changes priority or status. For example, a critical ticket can trigger a webhook to a incident management platform or a team chat channel.Knowledge Base Integration
Knowledge base integration links relevant articles to a ticket based on its priority and topic. Agents can quickly suggest solutions without leaving the Telegram interface. This is especially useful for medium and high priority tickets where speed matters.Escalation Routes
Escalation routes are predefined paths for moving a ticket to a higher tier. Each priority level has a default route. Critical tickets may escalate directly to a senior engineer, while low tickets might escalate to a team lead.Monitoring Agent Workload
Monitoring agent workload involves tracking the number of active tickets per agent and their priority distribution. If an agent has too many high-priority tickets, the system may pause new assignments to prevent burnout and missed SLAs.Re-prioritization
Re-prioritization is the act of changing a ticket's priority level after initial assignment. This can happen if new information emerges, the customer requests urgency, or the ticket remains unresolved. The system logs all priority changes for audit purposes.Priority Matrix
A priority matrix is a visual or logical grid that maps ticket urgency (time sensitivity) against impact (business consequence). It helps agents and managers decide the correct priority level during triage.Time to Acknowledge
Time to acknowledge is the period before an agent claims responsibility for a ticket. For high-priority tickets, this should be near zero. Acknowledgment can be automated via webhook integration or manual via agent action.Ticket Aging
Ticket aging tracks how long a ticket has been open at its current priority level. Aged high-priority tickets are flagged for review. The system may automatically escalate tickets that exceed aging thresholds.Priority Override
Priority override allows a manager or senior agent to manually change a ticket's priority level, bypassing the automatic rules. This is used in exceptional circumstances, such as a VIP customer or a widespread outage.What to Verify
When configuring routing priority levels in your Telegram CRM, ensure that:
- The automated priority assignment rules align with your team's capacity and business goals.
- SLA targets for each priority are realistic and agreed upon by all stakeholders.
- Escalation policies are documented and tested with dry runs.
- Agents understand the criteria for manual re-prioritization.
- Monitoring dashboards display real-time priority distribution and SLA adherence.
Reader Comments (0)