Detailed Explanation of Session Dispatch Rules in TG Customer Service System: Online First, Round-Robin Distribution, and Customer Service Scope Configuration

When your Telegram Bot starts handling dozens or even hundreds of user inquiries daily, a critical question arises: Who will reply to which message? Without a reasonable session dispatch mechanism, when multiple agents are online simultaneously, issues may occur such as multiple messages being grabbed by the same agent, some messages left unanswered, or agents passing the buck. This is exactly what session dispatch rules in the TG customer service system aim to solve.

This article will delve into the two core dispatch rules—Round-Robin Distribution and Online First—based on the actual configuration of TG-Staff, and explain how to finely control session flow by configuring the customer service scope. Whether you are a startup 3-person customer service team or a mid-sized operations team with 20+ agents, understanding these rules will help you significantly improve response efficiency.

What is Session Dispatch in TG Customer Service System? Why Is It Crucial?

Session Dispatch refers to the mechanism where, in a multi-agent environment, when a new Telegram user sends a message to the Bot, the system automatically assigns the session to a specific agent according to preset rules.

Without dispatch rules, the following problems arise:

• Message conflicts: Multiple agents reply to the same message simultaneously, leading to duplicate responses
• Missed messages: All agents assume someone else will handle it, resulting in no response
• Uneven workload: Some agents are overwhelmed while others are idle
• Response delays: User waiting time is uncontrollable, affecting conversion rates

A good TG customer service session dispatch solution should achieve:

• Automatic assignment: No manual intervention for new sessions
• Fairness: Balanced workload among agents
• Status awareness: Consider agents’ online/offline status
• Configurability: Adapt to different team work patterns

TG-Staff provides two dispatch rules and two customer service scope settings to meet various scenarios from fixed shifts to flexible scheduling.

Two Core Dispatch Rules: Round-Robin vs Online First

In the TG-Staff console, navigate to Project Settings → Session Dispatch, you can choose one of the two rules. These rules have different design goals and distinct applicable scenarios.

Round-Robin Distribution: Fair Assignment in Order, Suitable for Agents with Fixed Online Hours

How It Works

Round-robin is the default rule in TG-Staff. When a new session arrives, the system assigns sessions sequentially to the next authorized agent based on the agent list order. It’s like a queue system—the first session goes to Agent A, the second to Agent B, the third to Agent C, and the fourth back to Agent A.

Key Behaviors

• The system skips agents who are currently offline or busy and continues polling the next agent
• If all agents are offline, the message is assigned to the first agent in the list (as a fallback)
• The assignment order cycles through the agent list, ensuring no agent is perpetually under- or over-loaded

Applicable Scenarios

• Agents have fixed schedules with predictable online hours
• The team wants roughly equal workload among agents
• No need for dynamic adjustments based on real-time online status

Advantages: Fair, predictable, requires high attendance discipline
Disadvantages: If an agent temporarily goes offline without logging out, they may still be assigned sessions, causing user wait times

Online First: Dynamic Assignment, Prioritizing Active Agents

How It Works

Online First rules detect agents’ login status in real-time. When a new session arrives, the system prioritizes agents who are currently online and idle. If multiple agents are online, the session is assigned sequentially among online agents.

Key Behaviors

• The system refreshes agents’ online status every few seconds
• If all online agents are busy, the new session enters a queue and waits for an agent to become free
• When all agents are offline, the system automatically falls back to round-robin logic, assigning the message to an authorized agent (regardless of online status). This means even if agents are offline, the message is still delivered to an agent’s pending list, visible when they next log in

Applicable Scenarios

• Agents have irregular online hours, with some only online for a few hours
• The team is distributed across time zones, requiring maximum coverage
• Peak hours demand quick responses without waiting for offline agents

Advantages: Fast response, high resource utilization, suitable for flexible scheduling
Disadvantages: Online agents may bear more workload than offline ones, potentially reducing long-term fairness

Comparison of the Two Rules

Feature	Round-Robin	Online First
Basis for assignment	Agent list order	Real-time online status
Load balancing	Strictly fair	Dynamically favors online agents
Offline fallback	Assigns in order	Falls back to round-robin
Suitable team	Fixed shifts, stable attendance	Flexible scheduling, cross-timezone
Response speed	Medium	Fast

How to Configure Customer Service Scope: All Agents vs Specified Agents

In addition to dispatch rules, you can also limit which agents can participate in handling sessions for a project. TG-Staff provides two customer service scope settings:

• All Agents: All agent members under the project can receive and reply to sessions of that project
• Specified Agents: Only manually selected agent members can handle sessions for that project

Configuration Steps

1. Go to TG-Staff Console → Project Settings → Session Dispatch
2. In the “Customer Service Scope” dropdown, select “Specified Agents”
3. Check the agents you want to assign (provided these agents have been added as project members)
4. Save the configuration

Why Do You Need to Assign Customer Service Agents?

• Business Isolation: Suppose you run both an e-commerce bot and a community bot. The e-commerce team’s agents don’t need to see community conversations. By specifying the agent scope, you can completely isolate customer service teams across different business lines.
• Permission Hierarchy: Senior agents can handle all projects, while interns are only responsible for specific ones.
• Reduce Distractions: Agents only see conversations they are responsible for, avoiding information overload.

Session Routing + Diversion Link: A Complete Chain from Ad Traffic to Agent Handling

The value of session routing rules goes beyond internal management. When combined with TG-Staff’s Diversion Link, you can build a complete user conversion chain:

Ad/Social Media → Diversion Link → Bot Auto-Reply → Human Agent Handling

How Does the Diversion Link Capture Visitor Information?

The diversion link is an official short domain provided by TG-Staff, formatted like https://app.tg-staff.com/{code}. When a user clicks this link, the system captures the following information before redirecting to your Telegram bot:

• IP Address: Understand the user’s region
• Browser Information: Device type, operating system, browser version
• URL Parameters: You can append parameters like ?utm_source=facebook&utm_campaign=summer_sale to the ad link, and the system records the source channel for each visitor

This information is associated with the user’s session, allowing agents to see directly which channel and device the user came from, facilitating personalized communication and attribution analysis.

Combining Session Routing to Handle Consultation Peaks

Suppose you run a Facebook ad campaign, and a surge of users floods in with inquiries. Here’s what happens:

1. User clicks the diversion link → enters the Telegram bot
2. Bot auto-replies with a welcome message and collects basic information
3. After the user inputs a question, the session enters the TG-Staff queue
4. Online-first rule takes effect: The system automatically assigns the session to currently online agents, preventing overload on a single agent
5. If all agents are busy, new users receive a queue notification, reducing anxiety about waiting

This combination not only improves response efficiency but also leverages diversion link attribution data to evaluate conversion performance across different ad channels, optimizing your ad strategy.

Common Configuration Issues and Precautions for Session Routing

Here are some pitfalls that users often encounter during actual configuration. Knowing them in advance can save you trouble.

Issue 1: Routing rule changes not taking effect

Reason: Routing rules only affect new sessions initiated after the modification. Ongoing sessions will not be reassigned unless manually transferred by an agent.

Troubleshooting advice: After modifying the rules, send a new message to the Bot from a different Telegram account to see if it is assigned according to the new rules.

Issue 2: In online-first mode, all agents are offline—where do new messages go?

Explanation: The system falls back to round-robin logic and assigns messages to agents with permission (regardless of online status). This means messages will appear in the pending list of offline agents, who can see them when they next log in.

Recommendation: If you want users to get an immediate response, consider setting an automated reply in the Bot, such as “Customer service is currently offline. We will reply within 24 hours.” Also, enable the offline notification feature for agents.

Issue 3: After selecting “Specific agents” in the agent scope, the list is empty

Reason: You haven’t added the agents as project members first. You need to go to Project Settings → Member Management, add the agents, then return to the routing settings to select them.

Issue 4: Agent status not syncing (showing online but actually away)

Explanation: TG-Staff determines agent online status based on web login status. If an agent closes the browser without logging out, the system may still consider them online. It is recommended that agents actively log out when leaving, or set an automatic logout time.

TG-Staff Session Routing: Advantages over Other Telegram Customer Service Systems

Compared to Telegram’s native multi-admin feature or other third-party customer service tools, TG-Staff’s session routing offers the following differentiated advantages:

Feature	Telegram Native Multi-Admin	Ordinary Third-Party Tools	TG-Staff
Routing Rules	None, all admins see all messages	Usually only round-robin	Round-robin + Online-first two rules
Agent Scope	Cannot isolate by project	Partially supported	All agents / Specified agents flexible configuration
Offline Fallback	No special handling	Usually direct assignment	Online-first falls back to round-robin
Routing Links	Not supported	A few support	Built-in, supports URL parameter tracking
Auto Translation	Not supported	Partially supported	Standard edition includes AI translation, Pro supports DeepL/Google
Content Moderation	Not supported	A few support	Pro edition includes risk word detection + wallet address monitoring

If your team needs the combination of online-first + agent scope + routing links, TG-Staff is one of the few SaaS platforms in the Telegram ecosystem that can fully provide these features.

Frequently Asked Questions

Q: Will changing session routing rules affect ongoing sessions?

A: No. Routing rules only affect new sessions initiated after the change. Already assigned sessions will continue to be handled by the original agent, unless the agent manually transfers the session to another colleague.

Q: In online-first mode, where do new messages go when all agents are offline?

A: The system automatically falls back to round-robin logic, assigning new messages to agents with permission (regardless of online status). The message will appear in that agent’s pending list and can be seen when they next log in. It is recommended to enable agent offline notifications or set a waiting prompt in the bot’s auto-reply.

Q: Can I set different routing rules for different bot projects?

A: Yes. TG-Staff supports multi-project management. Each bot project can independently configure routing rules (round-robin/online-first) and agent scope (all agents/specified agents). This means you can set online-first for an e-commerce bot and round-robin for a community bot without interference.

Q: Do routing links support tracking conversion effects from different ad channels?

A: Yes. Routing links can capture URL parameters. You can append parameters like ?utm_source=facebook or ?utm_campaign=summer_sale to your ad links. The system records each visitor’s source channel, and agents can see this information in the user profile for subsequent attribution analysis.

Q: After specifying an agent scope, can agents not in the list still see sessions for that project?

A: No. Only agents added to the project’s agent scope have permission to view and reply to sessions under that project. This helps isolate customer service teams across different business lines, preventing data leaks or misoperations.

---

If you are looking for a Telegram customer service system that supports flexible routing rules, give TG-Staff a try. Sign up for a 3-day free trial, no credit card required, and experience core features like online-first, routing links, and auto translation.

• Try it free: https://app.tg-staff.com/
• Read docs: https://docs.tg-staff.com/
• Contact support: @tgstaff_robot