Complete guide for migrating from Echo TG to TG-Staff: Bot migration, agent configuration and speech library import checklist

If you are using Echo TG to manage Telegram customer service, you may have felt some limitations: single function, lack of internal control, insufficient multi-language support, or difficulty in improving team collaboration efficiency. Migrating to TG-Staff is an option worth considering. This article provides a complete migration guide from Echo TG to TG-Staff, covering Bot connection, agent permission configuration, word library import and diversion rule settings, to help you make a smooth transition, and attaches an executable checklist.

Why migrate from Echo TG to TG-Staff?

Echo TG is a lightweight tool suitable for simple message forwarding. But when your team needs more professional customer service operations capabilities, its shortcomings will gradually become apparent. TG-Staff is specially designed for Telegram Bot customer service and operation scenarios, and can solve many practical pain points of Echo TG users.

Common pain points of Echo TG users

• Single function: Echo TG mainly implements message echoing and lacks functions such as session management and agent collaboration. It is easy to get confused when multiple customer service staff work at the same time.
• No internal control mechanism: It is impossible to monitor the content sent by agents, and there are compliance risks when payment addresses and sensitive information are involved.
• Weak multi-language support: Cross-border teams need automatic translation capabilities, which Echo TG basically does not provide.
• Limited offloading capability: Sessions cannot be allocated to different agents according to rules, and orders are easily missed during peak consultation times.
• Lack of statistics: Unable to track key indicators such as user sources, session volume, and agent efficiency.

What problems can TG-Staff solve?

• Real-time two-way chat: Web agents have real-time conversations with Telegram users, supporting conversation tops, tags, and user portraits, making customer service work more orderly.
• Session diversion and diversion link: Supports two rules: “rotation distribution” or “online priority”, and cooperates with diversion link (magic link) to realize advertising traffic attribution, a complete link from social media to Bot to manual agent.
• Content Risk Control (Professional Edition): Automatically detect risk words before agents send messages, support configuration of wallet addresses, sensitive words, etc., and pop up a window to confirm or block sending after triggering, suitable for scenarios such as Web3 and exchanges.
• Automatic translation: The standard version includes AI translation, and the professional version additionally supports Google professional translation and DeepL professional translation. There is no need to switch tools for cross-border customer service.
• Multi-project management: Supports multiple Bot projects according to packages and unified console management.

Preparing for migration: What information do you need to collect?

Spending 30 minutes organizing your existing resources before migrating will prevent critical data from being missed in the process. It is recommended to check the following list one by one.

Export Bot Token and project information

• Bot Token: Log in to BotFather, find the Bot that needs to be migrated, and copy its Token. Note: Token is the control key of Bot and must not be disclosed.
• Bot information: Record the current avatar, name and description of the Bot. The TG-Staff console supports direct editing without jumping to BotFather.
• Project configuration screenshot: If there are any diversion rules, welcome messages, and menu settings in Echo TG, it is recommended to take a screenshot and save it.

Organize agent account and permission list

• Agent List: List all agent accounts (user names or emails) that need to be migrated, and their scope of responsibilities in Echo TG (such as only handling pre-sales, only handling after-sales).
• Permission allocation: TG-Staff supports project-level permission configuration, and you can set different operation scopes according to agent roles. It is recommended to mark in advance which items each agent needs to access.

Talk library and common reply backup

• Word Library File: Export common replies, FAQs, and template messages in Echo TG to text or CSV files. TG-Staff provides a visual command flow editor so you can recreate these contents with zero code.
• Multi-language version: If the script has multiple language versions, organize them together. TG-Staff’s automatic translation function can assist in multi-language responses, but it is still recommended to prepare the preset vocabulary in advance.

Step one: Create a project in TG-Staff and connect to Bot

1. Visit TG-Staff Console and register an account (free trial for 3 days, no credit card required).
2. After logging in, click “Project Management” → “New Project” in the left navigation.
3. Enter the project name (it is recommended to be consistent with the purpose of the Bot, such as “Pre-sales Customer Service”), and then paste the Bot Token obtained from BotFather.
4. Click “Save” and the system will automatically verify the validity of the Token. After the verification is passed, the Bot is successfully connected.
5. Return to the project list and check whether the Bot status is “Connected”. You can send a test message to the Bot to confirm that the message can flow to the TG-Staff console normally.

Step 2: Configure agent accounts and permissions

Agents in Echo TG may share a Bot account, but TG-Staff provides independent agent accounts. Each agent logs in to the web portal to receive users without interfering with each other.

Create agent account and password

1. Click “Agent Management” → “New Agent” in the console.
2. Enter the agent’s name and email (as the login account), and set the initial password. It is recommended to use the company email to facilitate subsequent management.
3. The agent login address is the same as the administrator: https://app.tg-staff.com/，使用邮箱和密码登录后，会自动显示被分配的项目。

Assign project permissions and customer service scope

1. On the agent editing page, check the items that the agent needs to access. You can set the scope of “all customer service” or “specified customer service”.
2. If you need to restrict agents to handle specific sessions, you can configure the customer service scope in the project settings. For example, a pre-sales agent only handles users from a certain diversion link.
3. It is recommended to create 1–2 test agents first, verify that the permission settings are correct, and then create the remaining agents in batches.

Step 3: Import the vocabulary library and set common replies

TG-Staff provides two ways to manage speech: visual command process (suitable for welcome messages, menus, and multi-step interactions) and quick replies (suitable for agents to manually select common replies). You can choose the appropriate solution based on the speech structure in the original Echo TG.

• Migrate welcome message and menu: Enter the “Command Process” module in the console and use the drag-and-drop editor to rebuild the welcome message, keyword reply and multi-step process. No code is required, just drag and drop nodes such as “Send Message”, “Waiting for User Input” and “Conditional Branch”.
• Migrate FAQ and template replies: Add frequently used replies one by one in the “Quick Replies” module. Supports category management (such as pre-sales, after-sales, logistics), agents can directly click to send during the conversation.
• Use automatic translation: If you need to reply in multiple languages, TG-Staff’s automatic translation function can translate a message with one click when sending it. The Standard Edition has a daily translation quota, and the Professional Edition has a higher quota.

Step 4: Configure session diversion rules and diversion links

This is a critical step in restoring the offloading logic in Echo TG. TG-Staff provides two diversion rules and diversion link functions to ensure that user inquiries can be accurately assigned to agents.

Set project-level diversion rules

1. Enter project settings → “Session Offloading”.
2. Select the diversion rule:
   • Allocation in turns (default): Poll authorized agents in order, suitable for teams with a fixed number of agents.
   • Online Priority: Prioritize allocation to online agents, and fall back to alternate allocation when all are offline. Suitable for agent shifts or part-time scenarios.
3. Set the customer service scope: select “All Customer Service” or “Specified Customer Service”. If some agents only handle specific projects, select the latter and check the corresponding agents.

Generate diversion links and replace the original entrance

1. In the “Diversion Link” module, click “New Diversion Link”.
2. The system generates a TG-Staff official domain name short link (such as https://app.tg-staff.com/{code}).
3. Configure this link into your advertisements, social media, and official website entrances. After the user clicks, it will jump to the Bot and automatically capture IP, browser information and URL parameters for attribution tracking.
4. It is recommended to replace all the original Echo TG entrances with new diversion links to ensure that all users are diverted through TG-Staff.

Migration Checklist and Verification Steps

After completing the above steps, use the following checklist to verify each item to ensure that the system is running stably.

Verification items	Status (✓/✗)
Bot displays “Connected” in the TG-Staff console
At least one agent can log in to the web portal
Agents send messages and Telegram users can receive them
Telegram user replies, agents can see them in the console
The diversion link can jump to the Bot normally and start the session
Sessions are assigned to designated agents according to rules
The conversation library/quick reply content can be sent normally
The automatic translation function (if enabled) works normally
Content Risk Control (Professional Edition) detection rules take effect
All agents can log in and operate normally

If any verification item fails, first check whether the corresponding configuration is correct, or consult TG-Staff official documentation for detailed instructions.

FAQ

Q: Will the historical chat history in Echo TG be retained after migration?

Answer: No. TG-Staff and Echo TG are independent platforms, and historical chat records cannot be automatically migrated. If you need to preserve important conversations, it is recommended to export from Echo TG before migrating (e.g. screenshot or export to CSV). After migration, TG-Staff will record all new sessions from scratch.

Q: Does TG-Staff support multi-language customer service?

Answer: Supported. TG-Staff provides automatic translation function. The standard version includes AI translation, and the professional version additionally supports Google professional translation and DeepL professional translation. When an agent sends a message, he or she can translate the reply into the user’s language with one click. In addition, you can also preset multi-lingual responses in the vocabulary library and implement multi-lingual menus through visual command processes.

Q: Can I use Echo TG and TG-Staff at the same time during my move?

Answer: Yes, but please note: one Bot Token can only be bound to one platform. If you connect a Bot to TG-Staff, Echo TG will not be able to use the Bot at the same time. It is recommended to register for a free trial of TG-Staff first, use the new Bot or temporary Bot for verification during the testing phase, and then migrate the official Bot’s Token to it after confirmation. You can also test some functions in TG-Staff first and then switch to all functions.

Q: If there is a problem with the Bot during the migration process, how can I quickly roll back?

A: You can reset the Bot Token in BotFather at any time, and then rebind the new Token to Echo TG (if Echo TG supports manual token entry). However, please note that resetting the Token will cause the Bot connection in TG-Staff to become invalid. It is recommended to keep the configuration screenshot of Echo TG before migration and ensure that there is a backup token solution. The safest approach is to go through the migration process completely on a test Bot first, and then operate the official Bot.

Q: Can a full migration be completed during the free trial period?

Answer: Yes. TG-Staff provides a 3-day free trial, which is enough to complete Bot access, agent configuration, conversation library import and diversion rule settings. After the trial period expires, if you choose to renew, all configurations will be automatically retained. It is recommended to complete the core configuration and testing during the trial period. After confirming that the system is stable, you can then choose a suitable package (standard or professional version) to subscribe. For details, see [Official Package Page] (https://tg-staff.com/).

---

If you encounter any problems during the migration process, please contact TG-Staff Customer Service Bot for one-on-one migration guidance. You can also directly visit the TG-Staff Console to sign up for a free trial and start your migration journey.