30 minutes to switch from Echo TG to TG-Staff: complete checklist (Bot unchanged)

If you are using Echo TG to handle Telegram customer service, but as your team expands, you find that the single-agent, no-diversion, and no-user-profile experience can no longer keep up with the pace of business—then it’s time to consider a more professional alternative. Switching from Echo TG to TG-Staff, the whole process only takes 30 minutes, and your Telegram Bot itself will not undergo any changes, and the user will be completely unaware.

This article provides a straightforward migration checklist that covers every step from preparation to final verification to help you complete the switch with zero disruption.

Why choose to switch from Echo TG to TG-Staff?

Echo TG is suitable for individuals or very small teams to get started quickly, but its limitations are exposed when your customer service team requires multi-person collaboration, multi-channel traffic drainage, or compliance and internal control. Here are the core differences between the two:

Comparative Dimensions	Echo TG	TG-Staff
Number of seats	Usually single seat	Standard version starts from 3 seats, Professional version has up to 20 seats
Session offloading	None	Alternate allocation/online priority two modes
Diversion link	None	Official short link, supports IP capture and advertising attribution
Automatic translation	None	The standard version includes AI translation, and the professional version supports DeepL, etc.
Content risk control	None	The professional version includes risk word monitoring and supports wallet address interception
Visual process editing	None	Drag-and-drop command process editor
User portraits and statistics	None	Professional version provides portraits and statistics
Multi-project management	Not supported	Support multiple Bot projects by package

Core Value of Migration: Your Bot username and Token remain completely unchanged, users continue to communicate through the original Bot, and the migration process is transparent to users. You only need to complete the configuration in the TG-Staff console, and your team will have access to multi-agent collaboration, automated offloading, and operational tools.

Preparation before migration (5 minutes)

Before starting any operation, complete the following 3 preparations. Although this step only takes 5 minutes, it can avoid 90% of subsequent pitfalls.

Get and save your Bot Token

Bot Token is the core asset of migration. Open Telegram, enter BotFather, enter /mybots, select your Bot, and click API Token to obtain the full Token.

• Copy the Token and temporarily save it in a safe location (such as a password manager or a local text file).
• If the Token has been leaked before, it is recommended to regenerate it after the migration is completed.

Back up Echo TG existing settings

Although Echo TG’s historical sessions cannot be directly imported into TG-Staff, you need to back up the following content in order to recreate it in TG-Staff:

• Auto-reply rules: Take screenshots or record all keyword replies, commands and trigger conditions configured in Echo TG.
• Commonly used command list: Reply content of commands such as /start, /help, etc.
• User Grouping or Label: If there is a custom grouping, record the grouping logic.

This information will be used in the third step of the reconstruction process.

Confirm that the TG-Staff package matches the team’s needs

TG-Staff offers a free trial (3 days), Standard and Professional versions. Choose based on your team size:

• Standard Edition (approximately $8.99/month): Suitable for a team of 1-3 agents, including core functions such as offloading links, conversation offloading, automatic translation (AI version), and group messaging.
• Professional Edition (approximately $16.99/month): Suitable for a team of 3-20 agents, additionally provides advanced features such as content risk control, unlimited translation, user portraits, TG theme backgrounds, etc.

**If you need to monitor the payment address sent by the agent (such as TRC20/ERC20 wallet address), or need user profile analysis, it is recommended to choose the professional version directly. ** For package details and annual payment discounts, please see the official website package page.

Step 1: Add your Bot project in TG-Staff (5 minutes)

Now the official migration begins.

1. Visit TG-Staff Console and register an account (new users automatically get a 3-day free trial).
2. After logging in, click on the left menu “Project” → “Create Project”.
3. Enter the project name (such as “Official Customer Service”), and then paste the Token you copied from BotFather in the Bot Token field.
4. Click Save. The system will automatically verify the validity of the Token and display the connection status as “Connected”.
5. Test whether the Bot responds normally: send any message to your Bot, and the TG-Staff console should display the conversation in real time.

Note: At this point your Bot is still running in Echo TG, TG-Staff is just a backup connection. User messages will be received by both Echo TG and TG-Staff, but TG-Staff will become the only processor only after you actively deactivate Echo TG’s webhook. We’ll do this in step four.

Step 2: Configure basic customer service process (10 minutes)

This step equips your team with immediate hosting capabilities. The core is to set session diversion rules, create agent accounts, and configure welcome messages.

Set session diversion rules (rotating distribution vs online priority)

In the TG-Staff console, enter “Project Settings” → “Session Offloading” and select the offloading mode:

• Rolling (default): New sessions poll all authorized agents in sequence. Suitable for teams with even message volume and similar agent capabilities. For example, with 3 agents, the first session is assigned to agent A, the second to agent B, the third to agent C, and the fourth to agent A again.
• Online Priority: Prioritize allocation to the current online agent, and fall back to turn-based allocation only when everyone is offline. It is suitable for scenarios that require quick response during peak hours, but please note that online agents may take on more sessions.

Recommendation: If your team has a small number of agents (3-5 people) and the schedule is fixed, just use “Rotate Assignment”; if the agents have many shifts or frequently switch online status, selecting “Online Priority” will be more flexible.

Invite team members and assign agent permissions

1. Enter “Agent Management” → “Create Agent”.
2. Enter the agent’s name and email address (for login).
3. Set project permissions: select “All Projects” or “Specified Projects” (if the team has multiple Bot projects).
4. Click Save. The system will generate a login link and send it to the agent.
5. The agent sets a password through this link and can log in to the [TG-Staff Console] (https://app.tg-staff.com/) to start receiving users.

Configure welcome message and automatic reply

In the “Command Flow” editor, drag the “Welcome” node to set the greeting message when the user enters the Bot for the first time. For example:

欢迎来到 [你的品牌]！请选择以下服务：
/help - 帮助中心
/order - 查询订单
/contact - 联系人工客服

If you need more complex multi-step interactions (such as collecting user emails, selecting issue categories, etc.), you can use the visual editor to add branch nodes without writing code.

Step 3: Migrate the old Bot’s automatic replies and commands (5 minutes)

Now migrate auto-reply rules and commands from Echo TG to TG-Staff.

Rebuild one by one in TG-Staff’s “Command Flow” editor based on the content you backed up before:

Functions in Echo TG	Corresponding operations in TG-Staff
Keyword automatic reply	Add “keyword trigger” node, set matching rules and reply content
/start Command	Create a “command” node, bind /start, and configure the welcome message
/help command	Create a “command” node, bind /help, and configure help text
Multi-step interaction	Use “branch” nodes to connect multiple steps in series to support conditional judgment
Scheduled/batch messages	Use the “bulk message” function to reach groups according to users (Professional version)

Migration Tips: If there are many rules in Echo TG, it is recommended to migrate the most commonly used 3-5 rules first, and then gradually add the remaining ones after it goes online.

Step 4: Verification and closing inspection (5 minutes)

This is the last step and the most critical step. After completing the following 5 checks, you can officially deactivate Echo TG.

Final Checklist

• Bot message response: Send a test message to the Bot to confirm that the TG-Staff console displays the session in real time and the Bot can reply correctly.
• Agent login and reception: The invited agent successfully logs in to the console, can see the test session, and can send reply messages.
• Session distribution is normal: Send multiple messages to confirm that the offloading rules take effect (alternative distribution or online priority distribution as expected).
• User message visibility: Send a message as an ordinary user and confirm that the message is fully displayed on the agent side (including pictures, files and other media).
• Translation/risk control function is normal: If you purchased the professional version, test whether automatic translation takes effect and whether content risk control blocks risky words as configured.

After confirmation, disable Webhook in Echo TG (usually turn off the “Enable Webhook” option in the Bot settings), and TG-Staff will automatically take over all message processing.

FAQ

**Q: Will users perceive changes when switching from Echo TG to TG-Staff? ** Answer: No. The Bot’s Token and username remain unchanged, users continue to communicate through the original Bot, and the migration process is completely transparent to users.

**Q: Can historical session data in Echo TG be migrated to TG-Staff? ** Answer: Currently, TG-Staff does not support direct import of historical session records of Echo TG, but new sessions will be recorded normally starting from the time the migration is completed. It is recommended to take screenshots and back up key session information before migration.

**Q: Will the Bot go offline during the migration process? ** Answer: No. You can complete the configuration in TG-Staff while Echo TG is running normally, and finally disable Echo TG’s Webhook. The Bot will remain online during the entire process.

**Q: Is the TG-Staff free trial period enough to complete the migration? ** Answer: Sign up to enjoy a 3-day free trial, which covers all functions of the standard version and is fully sufficient to complete migration testing and launch.

**Q: If you encounter problems after migration, is there technical support? ** Answer: You can get real-time help through the TG-Staff official customer service Bot (@tgstaff_robot), or you can check Document for detailed configuration guide.

Conclusion and next steps

Switching from Echo TG to TG-Staff is not a complicated surgery but an upgrade with clear steps. Within 30 minutes, your team can gain access to professional capabilities such as multi-agent collaboration, session offloading, and automatic translation, while your bots and users are not affected at all.

Take action now:

• → Register now TG-Staff Free Trial
• → Consult Migration Documentation for more detailed configuration guide
• → Contact @tgstaff_robot for 1v1 migration support

After 30 minutes, your Telegram customer service experience will be completely different.