TG-Staff Session Routing Demo: Online-First vs Round-Robin Configuration Tutorial and Use Cases

When you run a Telegram Bot customer service team, one of the most headache-inducing issues is: Which agent should handle a user’s message? If distribution is uneven, some agents are swamped while others have nothing to do; if distribution is slow, users wait too long and churn. That’s the core problem TG-Staff Session Routing solves.

TG-Staff is a customer service and operations SaaS platform for Telegram Bots. Its session routing feature allows you to intelligently assign user requests to different agents. This article provides a step-by-step tutorial on configuring two routing modes—Online-First and Round-Robin—and helps you decide which mode suits your team through scenario comparisons.

What is TG-Staff Session Routing and Why Is It Crucial for Your Telegram Bot Customer Service?

Session Routing means: when a user sends a message via your Telegram Bot, the system automatically assigns that session to an agent (Staff) based on preset rules.

Without routing, common problems include:

• Missed tickets: All messages flood one agent who gets overwhelmed and misses messages.
• Slow responses: Users wait minutes or longer for a reply.
• Chaotic assignment: Multiple agents reply to the same user, causing conflicting information.

TG-Staff’s session routing uses two modes (Round-Robin and Online-First) to achieve automatic, fair, and efficient distribution. Combined with Diversion Links for ad attribution, it forms a complete loop from lead acquisition to customer service. For cross-border teams, Web3 projects, or any team relying on Telegram for customer service, this directly impacts user experience and conversion rates.

Two Core Routing Modes: Online-First vs Round-Robin

TG-Staff offers two routing rules with completely different logic, suited for different team structures and shift scenarios.

Round-Robin: Fair Rotation, Load Balancing

Round-Robin is TG-Staff’s default routing rule. The logic is simple: the system maintains a circular list of authorized agents and assigns new sessions sequentially.

• How it works: Suppose there are 3 agents (A, B, C). The first session goes to A, the second to B, the third to C, the fourth back to A, and so on.
• Pros: Each agent handles roughly the same number of sessions, achieving load balancing. Ideal for teams with stable agent numbers and equal workload distribution.
• Cons: It doesn’t check if an agent is online. If B is offline, sessions may still be assigned to B (they appear when B comes online), causing longer wait times for users.

Online-First: Faster Response, Prioritizes Online Agents

Online-First mode prioritizes agents’ real-time online status.

• How it works: When a new session arrives, the system scans all authorized agents, finds those currently online, and assigns the session to one of them (in order or randomly). If all agents are offline, the system automatically falls back to Round-Robin, assigning the session to the first agent in the list (visible when they come online).
• Pros: Ensures user messages are seen and handled promptly by online agents, leading to faster responses. Suitable for flexible shifts, part-time agents, or peak hours requiring quick responses.
• Cons: If most agents are online simultaneously, one online agent might receive multiple consecutive sessions (because offline agents are skipped), resulting in less balanced load than Round-Robin.

Case Demo: Configuring Session Routing Rules for Your TG Bot (Step-by-Step Tutorial)

The following steps use the TG-Staff console as an example. Assume you have already registered and linked your Telegram Bot.

Step 1: Log in to the Console and Enter Project Settings

1. Visit https://app.tg-staff.com/ and log in with your account.
2. In the left navigation bar or project list, select the Bot project you want to configure.
3. Click into the project’s “Customer Service Settings” or “Routing Rules” area. If you can’t find it, refer to the “Session Routing” section in the official documentation https://docs.tg-staff.com/.

Step 2: Configure Project Agent Scope

Before configuring routing rules, you need to determine which agents can participate in routing.

• On the customer service settings page, find the “Project Agent Scope” option.
• Select “All Agents”: All agents (including admins) in the project can receive routed sessions.
• Select “Specified Agents”: Check specific agents from the list; only selected agents can participate in routing.

Note: If an agent is not selected, even if online, they will not receive auto-routed sessions from this project. This is a prerequisite for routing to work.

Step 3: Select Routing Rule and Save

1. In the “Routing Rule” dropdown, you’ll see two options:
   • Round-Robin
   • Online-First
2. Choose the mode you need (e.g., “Online-First”).
3. Click “Save”. The rule takes effect immediately; no bot restart is needed.

Verification: Send a message to your Bot from another Telegram account. Check the session assignment records in the console’s “Sessions” list. If the agent is online, the session is assigned quickly; if offline, it follows the fallback rule.

How Diversion Links Work with Session Routing for Precise Attribution?

Diversion links (also called magic links) are a powerful feature of TG-Staff. They are essentially official domain short links (e.g., https://app.tg-staff.com/{code}). When a user clicks the link, TG-Staff will:

1. Capture the user’s IP address, browser information, and URL parameters (such as utm_source, utm_campaign).
2. Automatically redirect the user to your Telegram Bot (via Deep Link).
3. After the user enters the Bot, the Bot can send an automatic reply (welcome message, menu), and then seamlessly assign the user to a human agent based on session routing rules.

Typical scenario: You run ads on Google Ads, and the ad link points to a diversion link. When a user clicks, TG-Staff records attribution information like “from Google Ads Campaign A.” After the user enters the Bot, the system automatically assigns the user to the currently online agent based on the “online first” rule. The agent can see the user’s source channel in the user profile, enabling targeted service.

Diversion links and session routing are independently configured but work together. Diversion links handle traffic direction and attribution, while routing rules decide who takes over. Together, they form a complete conversion chain: Ad → Social Media → Bot → Human Agent.

Comparison of Applicable Scenarios: Which Routing Mode Should You Choose?

Dimension	Round Robin	Online First
Core Logic	Round-robin across all authorized agents	Prioritize currently online agents
Load Balancing	Excellent (even distribution)	Fair (online agents may handle more)
Response Speed	Moderate (may assign to offline agent)	Fast (only assigned among online agents)
Team Size Suitability	Small to medium (3-20 agents)	Medium to large (5-20+ agents)
Scheduling Needs	Fixed shifts, rotation	Flexible scheduling, part-time agents
Typical Scenario	Standard plan small team, each with fixed hours	Pro plan team with part-time online agents

When to Choose “Round Robin”: Stable Support Team, Shift-Based

Example: You are a Standard plan user (3 agent slots), team members work fixed hours daily, e.g., morning, afternoon, night shifts each with one agent. You want each agent to handle roughly the same number of sessions to avoid imbalance. Round robin is the best choice—it automatically rotates, ensuring fairness.

Note: If an agent goes offline temporarily, their sessions won’t automatically transfer to others. Ensure at least one agent is online during each shift in the schedule.

When to Choose “Online First”: Flexible Scheduling, Peak Hour Emergency

Example: You are a Pro plan user (20 agent slots), team members are in different time zones, some are part-time and only online at specific times. You want user messages to be immediately handled by an online agent, not assigned to someone who starts work in 3 hours. Online first is better—it prioritizes response speed over load balancing.

Note: If all agents are offline, the system falls back to round robin. Arrange at least 1-2 agents online during critical hours, or enable offline message notifications (e.g., push alerts via Telegram Bot).

Frequently Asked Questions

Q: Does the TG-Staff free trial support session routing?

A: Yes. During the 3-day free trial, you can experience all features of the Standard plan, including session routing. After the trial expires, you need to subscribe to the Standard or Professional plan to continue using it.

Q: If I configure “Online Priority” and all agents are offline, what happens to user requests?

A: The system will automatically fall back to “Round Robin” mode, assigning the request to the first agent in the authorized agent list, and it will be displayed once that agent comes online. It is recommended to keep at least one agent online or enable offline message notifications.

Q: Can I switch routing rules for the same Bot project at different times?

A: Currently, the TG-Staff console supports manual switching of routing rules at any time without redeploying the Bot. You can flexibly adjust according to your customer service shift schedule.

Q: Do routing rules affect the tracking of Diversion Links?

A: No, they do not. Diversion Links are responsible for capturing visitor information and ad attribution, while routing rules determine which agent handles the user after they enter the Bot. These are independently configured but work together. You can use Diversion Links for attribution and Online Priority rules to ensure quick responses.

---

Experience TG-Staff Session Routing Now

• Sign Up for Trial: Visit https://app.tg-staff.com/ to register and enjoy a 3-day free trial of Standard features, including session routing and diversion links.
• Read Documentation: Go to the TG-Staff official documentation https://docs.tg-staff.com/ for more configuration details and API instructions.
• Contact Support: If you encounter configuration issues, you can directly contact the official customer service Bot: @tgstaff_robot.