TG-Staff 团队 avatar TG-Staff 团队

The complete guide to TGBot multi-agent offloading: online priority, round robin assignment, and supervisor intervention rules

tgbot Diversion customer service Telegram TG-Staff

#TGBot The complete guide to multi-agent offloading: online priority, polling allocation and supervisor intervention rules

As your Telegram Bot user base grows, relying on just one account to reply to messages will quickly encounter bottlenecks: message accumulation, response delays, and user churn. Multi-customer service offloading is the key to solving this problem - automatically assigning incoming conversations to multiple agents to ensure that each user can be taken over in time. This article takes TG-Staff as an example to explain in detail the two core rules of tgbot multi-customer service diversion (online priority and rotating allocation), the session transfer mechanism, the traffic attribution value of diversion links, and provides configuration steps and best practices.

Why does TGBot need multiple customer service branches?

When there is no diversion mechanism, the customer service process of a Telegram Bot usually looks like this:

  • All user messages flow into one account, and agents can only process them sequentially.
  • When encountering complex problems, the agent cannot transfer the problem and the user can only wait or repeat the description.
  • There is a backlog of messages during peak hours, and users are left without a reply.

Multi-customer service diversion solves three core pain points:

  1. Response speed: Multiple agents process in parallel, greatly reducing waiting time.
  2. Load Balancing: Prevent a certain agent from being overly busy and leaving other agents idle.
  3. Professional Undertaking: Complex problems can be transferred to more suitable agents to increase the resolution rate.

SaaS platforms such as TG-Staff have offloading logic built into the web console and can be configured without development. Standard edition and above packages support session offloading and multi-seat functions.

Detailed explanation of the two core distribution rules: online priority vs. rotational distribution

TG-Staff provides two diversion rules, and you can only choose one of them as a project-level strategy. Only by understanding their differences can you choose the solution that suits your team.

RulesPrinciplesApplicable scenariosAdvantagesDisadvantages
Online prioritySessions are assigned to currently online agents first; when all offline, they are assigned in turnThe customer service team is on duty in real time, and response speed is prioritizedUsers can almost always be taken over by online agentsFull-time agents may be busier, and part-time agents are idle
Allocation in turnsAll authorized agents are polled in order (regardless of online status)The number of agents is fixed and the workload needs to be balancedThe distribution is fair and no agents are idleOffline agents will be assigned, causing users to wait

Online priority: Maximize response speed

How it works: When a new session enters, the system will check all authorized agents under the project and filter out the currently online agents. If there is ≥1 online agent, they will be assigned to them in a round-robin manner; if all are offline, it will fall back to the round-robin allocation rule (all agents participate in polling).

FIT FOR TEAM:

  • The customer service team has clear duty hours, and agents can only pick up customers when they are on duty.
  • High requirements for response speed, and hope that user messages can go directly to online agents.

Note:

  • Agents need to keep the TG-Staff console or web page online, otherwise they will not be selected.
  • If the team agent is often offline, it is recommended to use “automatic reply” or Bot menu to handle basic questions to reduce the pressure of manual intervention.

Distribution in turns: fair load to avoid idle seats

How it works: The system maintains an agent polling list, and new sessions are assigned to the next agent in order, regardless of whether the agent is currently online. If the user fails to respond in time after being assigned, the session will continue to wait and will not be automatically transferred to another person (unless manually transferred).

FIT FOR TEAM:

  • The number of agents is fixed and all agents are online during a fixed period of time.
  • It is necessary to ensure that the workload of each agent is roughly the same to avoid anyone being idle.

Note:

  • Offline agents will be assigned sessions, but cannot respond in time, causing users to wait. It is recommended to use it with agent status reminder or scheduling system.
  • If team agents are located in different time zones, rotating assignments may cause some agents to be assigned during non-working hours.

How to configure TGBot multi-customer service distribution (step-by-step operation)

The following steps take the TG-Staff console as an example, and the logic on other platforms is similar.

Preparation before configuration

Make sure you have registered TG-Staff and completed Bot access. If you are not connected, please check the Quick Start Document first.

Step 1: Create or select a project

  • Log in to TG-Staff Console.
  • Click “Create Project” on the “Project” page, enter the project name and associate your Bot.
  • If you already have a project, go directly to the project settings.

Step 2: Add agents

  • In “Agent Management”, click “Add Agent”.
  • Enter the agent’s Telegram username or email (requires TG-Staff registration).
  • Set permissions for each agent: whether to allow session transfer, view all sessions, etc.
  • The standard version supports 3/5 seat quotas, and the professional version supports 20 seats. The details are subject to the package.

Step 3: Configure diversion rules

  • Enter the “Session Diversion” settings page.
  • Choose the splitting rule: Online Priority or Rotating Assignment. -Set the project customer service scope: You can select “All Customer Service” or “Specified Customer Service” (only specific agents can handle this project session).
  • Save settings.

Step 4: Test the diversion effect

  • Send a message to the Bot using another Telegram account.
  • Log in to the agent account and confirm that the session is assigned correctly.
  • Switch the agent online/offline status and observe whether the assignment rules take effect.

Conversation transfer and supervisor intervention: handling complex inquiries

No matter how reasonable the diversion rules are, there will always be situations that agents cannot handle independently. At this time, session transfer and supervisor intervention mechanisms are needed.

Pay attention to permission configuration

The supervisor needs to grant “Transfer” and “View All Sessions” permissions in the project settings, otherwise he will not be able to intervene in other agents’ sessions.

Two scenarios for session transfer

Scenario 1: The agent cannot answer

  • When agents encounter inquiries beyond their own capabilities (such as technical issues, complaint escalation), they can transfer the conversation to more professional colleagues.
  • In the TG-Staff session interface, click the “Transfer” button and select the target agent or project.
  • After the transfer, the original agent loses the operation permission of the session (unless reassigned).

Scenario 2: The agent leaves work or changes shifts

  • If an agent is about to leave work, the currently unprocessed conversations can be transferred to a successor colleague.
  • It is recommended to add notes (Professional version function) to the conversation to explain the current processing progress and to-do items to reduce information gaps in handover.

How supervisors monitor and intervene

Supervisors (usually with “View All Sessions” permission) can via the TG-Staff console:

  • View allocation records: View the allocation history of each session in the “Session Log”, including allocation time, allocation rules, and current agents.
  • Monitor online agents: Check which agents are online and which are offline in real time, making it easy to manually adjust the traffic distribution strategy.
  • Manually take over session: If an agent does not respond for a long time, the supervisor can directly take over the session or reassign it to another agent.

Offload linking is a premium feature of TG-Staff, available for Standard and above plans. It is essentially a short link (such as https://app.tg-staff.com/{code}) that users click to automatically jump to your Telegram Bot and trigger the diversion process.

Complete link: Advertising/Social Media → Diversion link → Bot automatic reply → Manual agent to undertake

Core Value:

  • Attribution Tracking: The diversion link will automatically capture the visitor’s IP, browser information, and URL parameters (such as utm_source, utm_campaign), making it easier for you to analyze the traffic diversion effect of each channel.
  • Seamless connection: Users do not need to manually enter the Bot user name, one-click jump, reducing the bounce rate.
  • Cooperate with the diversion rules: After the user enters the Bot, he or she will automatically enter the diversion queue and be handled by an online agent or in turn.

Configuration method:

  1. Enter the “Diversion Link” page in the TG-Staff console.
  2. Click “Create Link” and set the target Bot and jump parameters.
  3. The system generates short links and places them on advertising platforms, social media or email marketing.

Best practices: Reduce session waiting and improve agent efficiency

  1. Adjust the offloading rules according to peak hours: If the team has full-time agents on duty during specific periods, it is recommended to use “online priority”; if the agents are evenly distributed and all online, consider “rotating allocation”. You can also manually switch rules at different times (TG-Staff supports modification at any time).

  2. Use automatic replies to handle basic questions: Before diversion, Bot should be configured with a welcome message, FAQ menu or command process (TG-Staff’s visual process editor can be implemented with zero code). Frequently asked questions are automatically answered by Bot, and human agents only handle complex requests, greatly reducing agent pressure.

  3. Set agent status reminder: It is recommended that agents stay online after logging in and complete the session transfer before going offline. The TG-Staff console will display the online status of the agent, and the supervisor can adjust the diversion strategy accordingly.

  4. Use user portraits to predict needs: The professional version provides the user portrait function. Agents can see the user’s historical conversations, tags and behavioral data before picking up customers, prepare response strategies in advance, and reduce repeated inquiries.

  5. Regularly check allocation records: Analyze agent response time and volume through session logs, discover bottlenecks or abnormal allocation (such as an agent being frequently assigned but responding slowly), and adjust rules or train agents in a timely manner.

FAQ

**Q: Can online priority and rotation allocation be used at the same time? ** Answer: They cannot be enabled at the same time. TG-Staff currently only supports selecting one of them as a project-level diversion rule. You can switch according to the team working mode.

**Q: When an agent is offline, will the session be assigned to him? ** Answer: In online priority mode, sessions will only be assigned to online agents; in rotational assignment mode, offline agents will also be assigned, but they will not be able to respond in time. It is recommended to enable online priority or only use turn-based allocation to ensure that the agent is online.

**Q: How to let the supervisor see the session records of all agents? ** Answer: In the project settings, add the supervisor account as an agent and enable the “View All Sessions” permission. Supervisors can monitor all sessions from the console.

**Q: Does the Diversion Link need to be configured separately? ** Answer: Yes. After creating a diversion link in the TG-Staff console, a short link will be automatically generated. Place it on an advertising or social media platform, and the user will jump to the Bot after clicking it. The system will capture the visitor information and enter the diversion process.

**Q: Can I experience the multi-customer service diversion function during the free trial period? ** Answer: Yes. Sign up to enjoy a 3-day free trial. The standard version and above packages support session offloading and multi-seat functions. The experience can be fully configured during the trial period.


If you are building or optimizing Telegram Bot’s customer service system, you might as well start with tgbot multi-customer service diversion. TG-Staff provides out-of-the-box online priority and rotation allocation rules, and with session transfer, diversion links and internal control management, it can cover most customer service scenarios from traffic drainage to after-sales.

👉 Sign up for TG-Staff free trial 📖 View full document 💬 If you have any questions, please contact customer service Bot: @tgstaff_robot