Troubleshooting Agent Not Receiving Tickets

When a support agent stops receiving tickets in a Telegram CRM environment, the immediate reaction is often to assume a platform-wide failure. In practice, the root cause is almost always a configuration mismatch, a permission boundary, or a routing rule that has been silently updated. This guide walks through the most common failure modes, the diagnostic steps to isolate them, and the point at which escalation to a system administrator becomes necessary.

Symptom: Agent Shows as Online but Receives No New Tickets

The most frequently reported pattern involves an agent who appears active in the system—their status indicator shows green, they can view existing conversation threads, and they can send messages in reply to ongoing cases—yet no new tickets appear in their queue. New incoming requests from customers are visible to other team members or remain unassigned in the general support queue.

Begin by checking the agent’s assignment scope within the Telegram CRM. Most platforms allow administrators to restrict an agent’s visibility to specific topic groups, customer segments, or ticket categories. If the agent’s scope was recently narrowed—perhaps during a team reorganization or a cleanup of obsolete routing rules—they may no longer match the criteria for new incoming tickets. Navigate to the agent’s profile or role settings and verify that the assigned queues, topic groups, and customer filters include the channels from which tickets originate.

A related but less obvious cause is the agent’s capacity limit. Many Telegram CRM systems enforce a maximum number of active tickets per agent to prevent overload. If the agent is already handling their full allotment of open cases, the system will not assign additional tickets, even if the agent appears online. Review the agent’s current ticket count against their configured capacity. If they are at or near the limit, the solution is either to resolve or reassign existing tickets to free up capacity, or to adjust the maximum capacity setting for that agent.

Symptom: Tickets Are Created but Never Reach Any Agent

When no agent receives a new ticket, the problem typically lies in the routing logic or the integration between the customer-facing Telegram bot and the CRM. Start by examining the bot intake form configuration. If the bot is set to collect initial information from the customer and then create a ticket, ensure that the webhook integration between the bot and the CRM is functioning. A failed webhook call will result in the customer’s message being acknowledged by the bot but never converted into a ticket within the CRM.

Check the webhook logs in both the Telegram bot dashboard and the CRM’s integration settings. Look for HTTP status codes other than 200 or 204, or for timeout errors. If the webhook is failing intermittently, the CRM may not receive the ticket data at all. Re-establishing the webhook connection—often by re-entering the callback URL or regenerating the API token—resolves this issue in the majority of cases.

If the webhook is healthy but tickets still do not appear, inspect the routing rules. A common misconfiguration is a rule that routes tickets to a specific agent or group that no longer exists, or a rule that applies a condition that no incoming ticket can satisfy. For example, a rule that routes tickets tagged with “premium” only to agents who have a “premium_qualified” label will fail to assign any ticket if no agent currently holds that label. Review the active routing rules and verify that the conditions and target agents are still valid.

Symptom: Tickets Appear in the Queue but Are Not Assigned

In some setups, tickets are visible in a shared queue but are not automatically assigned to any specific agent. This is often by design—many teams use a manual assignment model where agents claim tickets from a pool. However, if the expectation is automatic assignment and it is not happening, the culprit is usually the agent assignment strategy.

Check the assignment method configured for the queue. Common strategies include round-robin, least-busy, and skill-based routing. If the strategy is set to “manual” or “unassigned,” the system will not push tickets to any agent. If the strategy is automated, verify that the agent meets the criteria for that strategy. For example, in a least-busy agent routing strategy, the system will only assign a ticket to an agent who has the lowest current workload and who is marked as available. If all agents are at capacity, the ticket will remain unassigned.

Another subtle issue is the agent’s availability status within the CRM. Even if the agent’s Telegram status shows online, the CRM may have a separate availability toggle. If the agent’s CRM status is set to “away,” “break,” or “offline,” the system will skip them during assignment. Instruct agents to verify their CRM status directly, not just their Telegram presence.

When the Problem Requires a Specialist

The diagnostic steps above cover the vast majority of cases where an agent is not receiving tickets. However, there are situations where the issue cannot be resolved through agent-level or team-lead-level configuration. Escalate to a system administrator or the CRM vendor’s support team when:

• The webhook integration shows no errors, but tickets are not being created from bot intake forms. This may indicate a deeper issue with the Telegram Bot API or the CRM’s event processing pipeline.
• Routing rules appear correct and agents are available, but tickets remain unassigned across the entire team. This suggests a systemic failure in the queue management or assignment engine.
• Changes to agent permissions or routing rules do not take effect, even after clearing caches or waiting for propagation. Some platforms have a delay or require a manual refresh of the routing configuration.
• The issue is isolated to a single agent, but their profile, capacity, and scope are identical to those of agents who are receiving tickets. In rare cases, this points to a data corruption issue in the agent’s user record.

Before escalating, document the exact steps you have taken: the configuration checks performed, the logs reviewed, and the timestamps of the failure. This information will significantly speed up diagnosis by the support team.

Preventive Measures and Ongoing Checks

To minimize the recurrence of this issue, incorporate the following checks into your regular team workflow. After any change to agent roles, routing rules, or bot integrations, run a test ticket through the system and confirm that it reaches the intended agent. Maintain a log of routing rule changes and the date they were applied, so you can correlate configuration updates with ticket assignment anomalies. Finally, review the escalation policy for your team to ensure that agents know the correct path for reporting assignment failures without waiting for a customer to complain first.

For a more structured approach to setting up and verifying your team’s routing logic, see our guide on checklist-for-setting-up-escalation-paths. If you are considering switching to an automated assignment model, the least-busy-agent-routing-strategy article explains the trade-offs and configuration steps. And for a broader view of how agent routing fits into your overall team management, the agent-routing-team-management hub provides a comprehensive framework.