Switch from Only TG to TG-Staff in one day: Complete implementation checklist and migration guide

If you are using Only TG to manage Telegram Bot customer service, but find that as your team expands, a single agent and lack of triage and attribution functions become bottlenecks, then migrating to TG-Staff may be your next natural choice. This article will provide an executable one-day migration checklist, covering Bot access, agent configuration, voice import and diversion rules, along with checklists and FAQs to help you make a smooth transition and avoid customer service interruptions.

Why migrate from Only TG to TG-Staff?

Only TG is an excellent Bot management tool, but it is mainly aimed at single-person operations or small communities. It has obvious shortcomings in multi-agent collaboration, session offloading, automated processes and content compliance. As a customer service and operation SaaS platform for Telegram Bot, TG-Staff provides the following core differences:

Comparative Dimensions	Only TG	TG-Staff
Number of seats	Usually single seat	3/5/20 Seat quota, independent account to log in to the Web portal
Session offloading	No built-in offloading	Rotating allocation / online priority, supports project-level configuration
Diversion link	None	Official short link captures IP, browser and URL parameters for ad attribution
Visual process	None	Drag-and-drop process editor, zero code to build Bot interaction
Content risk control	None	The professional version supports risk word detection and wallet address monitoring
Automatic translation	None	Standard version AI translation, professional version supports Google/DeepL
Multi-project management	Limited	Support multiple Bot projects by package

The core value of the migration is: Use a web console to uniformly manage all Bot customer service, automated processes and operational data, while at the same time achieving advertising traffic attribution through diversion links, and ensuring compliance and internal control through content risk control. Moreover, the entire migration process can be completed within one day, with almost no perception on the user side.

Preparation before migration (3 hours)

Spend 3 hours preparing the following to avoid unexpected interruptions during your migration.

Bot Token and permission confirmation

1. Get the Bot Token bound in Only TG: Log in to BotFather (https://t.me/BotFather），输入 /mybots, select your Bot, click “API Token” to view and record the Token. If the Token has been leaked or is uncertain, please click “Revoke current token” in BotFather to generate a new Token.
2. Confirm Bot Privacy Mode: Check the Bot’s “Privacy Mode” setting in BotFather. If the bot needs to read all messages in the group, make sure the privacy mode is Disabled.
3. Check group permissions: If the Bot is added to the group, confirm that it has the necessary permissions to send messages, read messages, etc.

Team agent and permission planning

The TG-Staff package supports 3/5/20 seat quotas (see the official website package page for details). Complete the following planning in advance:

• List all agents who need to access: including customer service, operations, and managers.
• Assign Project Permissions: Each project can be configured as “All Customer Service” or “Specified Customer Service”. For example, pre-sales projects are only assigned to pre-sales agents, and after-sales projects are only assigned to after-sales agents.
• Determine the agent login method: TG-Staff uses email + password to log in, and prepare the agent email list in advance.

Back up existing data in Only TG

Although TG-Staff does not currently support one-click import, it is recommended to organize the following content:

• Common Reply Techniques: Copy the commonly used quick reply text in Only TG into the document.
• User label or group information: If there are user groups (such as VIP, new users) in Only TG, record the group name and conditions, and then manually label them through user portraits in TG-Staff.
• Automation Rules: Record the trigger conditions and response logic in Only TG, and then reconstruct them in the TG-Staff visualization process.

Connect Bot to TG-Staff console (2 hours)

After completing the preparation work, start the official migration.

1. Register and log in to TG-Staff: Visit https://app.tg-staff.com/，使用邮箱注册，自动进入 for a 3-day free trial.
2. Create Project: Click “Create Project” on the console, enter the project name (such as “Pre-sales Customer Service”), and select a package (you can experience the standard version functions during the trial period).
3. Input Bot Token: Paste the Token obtained from BotFather in the project settings and click “Connect”. The system will automatically verify the validity of the Token and establish a Webhook connection.
4. Edit Bot Information: Modify the Bot avatar, name and description directly in the TG-Staff console without jumping to BotFather. It is recommended to maintain a consistent brand image with Only TG to avoid user confusion.
5. Configure basic project settings: including time zone, language, default reply message, etc.

After the connection is successful, the Bot will automatically start receiving user messages. It is recommended not to close Only TG first, and then deactivate it after verification.

Configure agents and customer service workbench (2 hours)

The core advantage of TG-Staff is multi-agent collaboration. Here are the configuration steps:

Create agent account

1. Click “Add Agent” in “Agent Management” of the console.
2. Enter the agent’s email and password (or select “Send Invitation Email” to let the agent set it up by themselves).
3. Assign project permissions: Select which projects the agent can receive (all or specified).

Reception of multiple seats at the same time

• Enable “Multiple Customer Service Sessions”: Turn it on in project settings to allow agents to handle multiple user sessions at the same time.
• Configure session transfer: Agents can click “Transfer” on the session details page and select the target agent. Transfer records are retained in the session log.
• The professional version supports “Private Notes”: Agents can add notes that are only visible to themselves in the session, which is suitable for recording user needs or internal notes.

Automatic translation and user portrait

• Automatic Translation: Turn on the translation function in the project settings. The standard version includes AI translation (with daily quota), and the professional version additionally supports Google professional translation and DeepL professional translation. Agents can click the translation icon next to the message input box to translate sent or received messages with one click.
• User Portraits (Professional version): Click on the user’s avatar to view historical conversations, tags and statistical information. Tags (such as “high intent” and “VIP”) can be added manually and used later to group users.

Migration techniques and automated processes (3 hours)

Migrate the speaking skills and automation logic in Only TG to the visual command process of TG-Staff.

Import common reply phrases

• Method 1: Paste the organized text directly into the node content in the “Command Process”.
• Method 2: Use TG-Staff’s “Common Replies” function (if available) to add text templates directly.

Build a visual command process

1. Enter the “Command Flow” editor and drag the “Welcome” node to the canvas.
2. Set the welcome content (text, picture or button), then drag the “Menu” node to configure multi-step options (such as “1. Product consultation”, “2. Technical support”, “3. Manual customer service”).
3. Add a corresponding reply for each option, or add a “Transfer to Human” node at the end to transfer the conversation to the agent.
4. Save and publish the process.

Configure batch messaging

• Create a new task in the “Group Send” module and select the target user group (such as “All users with uncompleted orders”).
• Edit message content (supports text, pictures, buttons), set sending time, and execute after confirmation.
• Note: The batch sending function is unlimited in the professional version. The standard version may have daily quotas. For details, see the official website package page.

Configure offloading links and session offloading (1 hour)

This is one of the core value-added functions of TG-Staff compared to Only TG, and is especially suitable for advertising traffic and multi-channel attribution.

Create a diversion link

1. Click “Generate Link” in the “Diversion Link” of the console.
2. Select the associated project, and the system will generate a short link (such as https://app.tg-staff.com/{code}).
3. Use the link for advertising (Google Ads, Facebook, Twitter) or social media profiles.
4. After the user clicks on the link, it will first jump to the TG-Staff official domain name, capture the visitor IP, browser User-Agent and URL parameters (such as utm_source, utm_campaign), and then automatically jump to your Bot to start a conversation.

Configure session diversion rules

• Allocation in turns (default): Poll authorized agents in order, suitable for teams with a balanced number of agents.
• Online Priority: Prioritize allocation to currently online agents. If all agents are offline, fallback to rotational allocation.
• Project Customer Service Scope: Can be set to “All Customer Service” or “Specified Customer Service”. For example, only let agents from the pre-sales team handle the project.

Complete traffic diversion link: Advertisement → Diversion link → Bot automatic reply → Manual agent to undertake. Users are unaware, but you can track the conversion effect of each channel.

Migration checklist and go-live verification (1 hour)

Before the official full switch, please verify the following list item by item:

• Bot connection is normal: Send a message to the Bot to confirm that the TG-Staff console can receive and display the session.
• Agent Login and Permissions: Each agent logs in to the web portal via email and checks whether authorized project sessions can be viewed.
• Speech and process test: Simulate the user to go through the welcome → menu → switch to manual → agent reply, and confirm that there are no breaks.
• Diversion link test: Open the diversion link with a browser, confirm that it jumps to the Bot, and view the captured IP and parameters on the console.
• Translation Test: Send non-default language messages to confirm that automatic translation is normal (if there is a quota).
• Content Risk Control Test (Professional Edition): Configure a test risk word, let the agent send a message containing the word, and confirm that the secondary confirmation or blocking takes effect.
• Session transfer test: Agent A transfers the session to agent B, confirming that agent B can take over and see the history.

It is recommended to first conduct a grayscale test on a small range of users (such as 10–20 people) for 30 minutes. After confirming that it is correct, unbind the Bot in Only TG (or disable Only TG directly) and switch to TG-Staff in full.

FAQ

**Q: Can Only TG’s Bot Token be used directly in TG-Staff? **

Answer: Yes, as long as the Bot has not been deleted or reset in BotFather, it can be accessed in TG-Staff using the same Token. It is recommended to confirm that the Token is valid in BotFather before migration and check whether it has been bound to other platforms (such as Only TG) to avoid conflicts. TG-Staff will take over the messages via Webhook, Only TG will no longer receive new messages.

**Q: Will user sessions be interrupted during the migration process? **

Answer: No. The Bot itself does not interrupt operations, and users can still send messages normally. When migrating, TG-Staff takes over message reception and agents only need to log in to the web console to continue responding. The user side is completely unaware. Historical messages (if any) need to be exported in Only TG. TG-Staff cannot automatically synchronize old conversations.

**Q: Can the words in Only TG be imported into TG-Staff in batches? **

Answer: TG-Staff does not currently support one-click import. It is recommended to manually organize the text. Common replies can be pasted into the visual command process; batch mass sending content can be created directly in the mass sending module. If you have a lot of conversational skills, you can contact the customer service Bot (@tgstaff_robot) to inquire about whether there are import tools or customized solutions.

**Q: What attribution parameters does TG-Staff’s diversion links support? **

Answer: Diversion links can capture visitor IP, browser User-Agent and URL parameters (such as utm_source, utm_campaign, utm_medium, etc.). You can append any parameters after the ad link, and TG-Staff will record them in the user portrait to facilitate multi-channel attribution analysis. Standard and above plans are available.

**Q: If the team has multiple Bots, does TG-Staff support multi-project management? **

Answer: Supported. Depending on the package, multiple Bot projects can be managed. Each project independently configures agents, distribution and processes, which is suitable for teams operating multiple Bots (such as different product lines, different regions). Data is isolated between projects, and agents can assign permissions across projects.

Summary and next steps

Switching from Only TG to TG-Staff is not a big undertaking: it takes 3 hours to prepare, 5 hours to configure, and 1 hour to verify, all within a day. After migration, you will gain core capabilities such as multi-agent collaboration, diversion link attribution, visual automated processes, and content risk control, significantly improving customer service efficiency and operational transparency.

Next steps:

• Register for a free trial now: https://app.tg-staff.com/（3 days trial, no need to bind a card)
• View full documentation: https://docs.tg-staff.com/（涵盖所有功能的详细配置）
• Contact Customer Service Bot: https://t.me/tgstaff_robot（如遇问题，直接与技术支持对话）

If you are looking for a SaaS tool that can really improve the efficiency of Telegram Bot customer service, TG-Staff is worth a try. Migrating from Only TG can be completed in one day, without any user awareness, and team efficiency doubled.