TG-Staff Onboarding Guide: 3-Day Trial Telegram Bot Customer Service Starter Checklist

Just registered for the TG-Staff trial and feel lost in the console? Don’t worry, the 3-day trial is enough to complete a full verification of the Telegram Bot customer service workflow. This article plans a Day1–Day3 TG-Staff onboarding task list, from connecting the Bot to agent reception, helping you make efficient use of 72 hours and quickly determine if this tool suits your team.

Why Does TG-Staff Onboarding Need a Day1–Day3 Rhythm?

The 3-day trial is a continuous 72-hour countdown. Without advance planning, you can easily waste precious time fumbling around. By following the rhythm of “Day1 Connect → Day2 Configure → Day3 Verify”, you can complete the following key actions before the trial ends:

Core Objectives of the Trial Period

• Day1: Connect your Telegram Bot to the TG-Staff platform and have at least one team member log into the agent portal.
• Day2: Configure conversation routing rules and basic automation flows (such as welcome messages), so the Bot can auto-reply before human intervention.
• Day3: Execute end-to-end testing to verify the complete chain from user sending a message → Bot auto-reply → agent manual handling, and experience features valuable to your business.

Avoid Common Onboarding Pitfalls

Many users skip basic configuration early in the trial and jump directly to advanced features (like internal control management or data statistics). But if you haven’t configured routing rules, agents may never receive conversations; if you haven’t created agent accounts, other team members can’t log in. It is recommended to follow the order in this article to ensure you can evaluate features based on real scenarios by the end of the trial.

Day 1 – Connect Telegram Bot and Create Staff Seats

The first day’s task is the most fundamental and crucial: connect TG-Staff with your Telegram Bot, and enable your team to start working via the Web console.

How to Obtain and Connect Your Bot Token

1. Open Telegram, search for @BotFather, and start a conversation.
2. Enter /newbot to create a new Bot, or /mybots to select an existing Bot.
3. Find the API Token field and click to copy (usually a string like 1234567890:ABCdefGHIjklMNOpqrsTUVwxyz).
4. Log in to the TG-Staff console (app.tg-staff.com), and find the Token input field under “Project Settings” or “Bot Management”.
5. Paste the Token and save; the system will automatically verify its validity.

After successful connection, you can edit the Bot’s avatar, name, and description directly in the console without needing to go back to BotFather—this is very convenient when you need to quickly adjust the Bot’s appearance.

Create Staff Seats and Assign Permissions

TG-Staff’s staff seats (Staff Seat) are independent Web portal accounts. The standard plan supports 3 staff seats, while the professional plan supports 5 or 20 (specific quotas are subject to the official plan page).

Steps:

1. In the left navigation of the console, find “Staff Management” or “Staff” entry.
2. Click “Add Staff”, enter the staff member’s name and email.
3. The system will send a login invitation to that email (including a temporary password or verification link).
4. After the first login, it is recommended that the staff member immediately change their password.
5. In “Project Permissions”, set the project scope that the staff member can access: you can specify all projects or limit to specific Bot projects.

Suggestion: Even if you are a solo user, create at least one staff seat for testing. If you want to test “conversation transfer” or “online-first routing” later, you can create a second staff seat on Day 2.

Day 2 – Configure Conversation Routing and Basic Automation

Day 2 is the key to making your Bot truly “smart”. You need to set up conversation routing rules to determine how user messages are assigned to staff, while also building a simple auto-reply flow so the Bot handles common questions before human intervention.

Choosing and Configuring Routing Rules

TG-Staff provides two routing modes, configurable under “Project Settings → Conversation Routing”:

Routing Mode	How It Works	Suitable Scenarios
Round Robin (default)	Sequentially polls authorized staff, each taking turns to receive new conversations	Teams with fixed schedules and stable staff numbers (e.g., daily shift customer service)
Online First	Prioritizes assigning to currently online staff; if all staff are offline, falls back to round robin	Teams with flexible response times and irregular staff online hours (e.g., distributed support teams)

How to Choose: If your team has a clear shift schedule (e.g., 3 people on morning shift, 2 on evening shift), “Round Robin” is fairer; if your team is distributed across time zones and wants messages handled immediately by whoever is online, “Online First” is more efficient.

Build a Welcome Message and Menu Without Code

TG-Staff’s “Visual Command Flow” editor uses drag-and-drop operations, so you don’t need to write a single line of code. Here is a simple beginner example:

1. In the console, find the “Flow Editor” or “Command Flow” entry.
2. Drag a “Start” node onto the canvas.
3. Connect a “Send Message” node, and enter a welcome message, for example: “Welcome to XX Official Customer Service! Please select the service you need: 1. Product Inquiry 2. Order Tracking 3. Human Agent”.
4. Add a “Wait for User Input” node, and set the branches corresponding to the user’s reply numbers.
5. Connect each branch to the corresponding reply content (e.g., selecting “1” sends a product introduction link, selecting “3” triggers a transfer to a human agent).

Advanced tip: Add a “Transfer to Human” node at the end of the flow to ensure that when users choose human service, the conversation correctly enters the agent queue. This way, the bot can automatically handle 80% of common questions before a human takes over, reducing agent workload.

Day 3 – Validate the Full Chain and Evaluate Key Features

Day 3 is the acceptance day. You need to perform end-to-end testing and try out features that bring business value, to provide a basis for deciding whether to renew.

End-to-End Testing: From User Message to Agent Reply

1. Simulate a user scenario: Use another Telegram account (or a friend’s phone) to send a message to your bot (e.g., “Hello, I’d like to inquire about products”).
2. Observe the auto-reply: The bot should first reply with the welcome message and menu you built on Day 2.
3. Select human service: Enter the corresponding number (e.g., “3”) in the menu to trigger the transfer to a human agent.
4. Log in to the agent portal: Open the “Conversations” page in the web console; you should see a new conversation assigned to an online agent.
5. Send an agent reply: Click on the conversation, enter a reply, and confirm that the message reaches the user in real time.

If all the above steps go smoothly, your core TG-Staff Onboarding chain is working.

Try Out Split Links and Auto-Translation

Split links (magic links): If your plan includes this feature (Standard or above), create a split link in the console. Share the link on social media or ad platforms, and simulate a user click. Then check the “Visitor Log” or “Attribution Analysis” page in the console to confirm whether URL parameters, IP, and browser information are captured. This is very valuable for ad traffic and channel effectiveness evaluation.

Auto-translation: In the agent conversation interface, find the translation toggle (usually a language icon). Once enabled, messages sent by the agent are automatically translated into the user’s language, and the user’s messages are translated into the agent’s language. You can find a test user who speaks a different language to verify the accuracy and real-time nature of the translation.

Day1–Day3 Checklist (Printable Version)

Day	Task	Status
Day1	Get Bot Token and connect to TG-Staff	□
	Create at least 1 agent account and log in to test	□
	Set agent project permission scope	□
Day2	Choose and configure session routing rules (Round Robin/Availability First)	□
	Set up an automated flow with welcome message + FAQ menu	□
	Create a second agent (optional, for testing collaboration)	□
Day3	End-to-end testing (User → Bot → Agent)	□
	Try routing links (if supported by your plan)	□
	Test auto-translation	□
	Evaluate core features and decide on renewal	□

After the Trial: How to Choose a Renewal Plan

After 3 days of trial, you should have a good feel for TG-Staff’s core capabilities. Here are some dimensions to consider when choosing a plan:

• Number of agents: If your team has only 1–2 people handling customer service, the Standard plan (3 agents) is sufficient; if your team has more than 3, or you need to assign dedicated agents to different projects, consider the Pro plan (5 or 20 agents).
• Translation needs: The Standard plan includes AI translation, suitable for everyday cross-language communication; the Pro plan additionally supports Google Professional Translation and DeepL Professional Translation, ideal for scenarios requiring high translation quality (e.g., formal business communication).
• Internal control: If you run a Web3, exchange, or NFT business and need to monitor agent messages for sensitive information (e.g., specific wallet addresses), the Pro plan’s content moderation feature is essential.
• Payment method: TG-Staff supports Stripe subscription (credit card) and USDT (TRC20) on-chain payment. If you prefer cryptocurrency, you can select USDT payment in “My Subscription”.

For plan prices and cycles, see the official plans page. Subscriptions are available in 30/90/180/360-day cycles, with annual payments usually offering additional discounts.

FAQ

Q: When does the 3-day trial start?

A: It starts the moment you successfully register and activate your account in the TG-Staff console (app.tg-staff.com), counting down 72 hours. We recommend preparing your Bot Token and agent emails before registering to avoid wasting trial time.

Q: Will my trial configurations be deleted after expiration?

A: After the trial expires, your project configurations (such as flows and routing rules) will be retained for a period (usually 7 days), but agents won’t be able to log in to serve users. Once you renew, all features will be immediately restored, and your configurations will not be lost.

Q: I’m the only operator. Do I need to create multiple agents?

A: We recommend creating at least 1 agent account for testing. If you’re working alone, one agent seat is enough. However, if you want to test “session transfer” or “availability first routing,” you can create a second test agent to simulate team collaboration.

Q: Can I use routing links (magic links) in the trial?

A: Routing links are a feature of the Standard plan and above. If your trial does not include this feature, focus on other core features (such as session routing and auto-translation) during Day3 testing. It’s not necessary to try every feature.

Q: If I don’t connect a Bot Token on Day1, will my trial time be wasted?

A: Yes. The trial period is a continuous 72 hours. We recommend following the Day1–Day3 rhythm in this article and preparing all materials (Bot Token, agent emails) before registering, ensuring you have clear tasks for each day.

---

Now start your TG-Staff Onboarding journey! Register for a trial now (app.tg-staff.com) and spend 3 days validating your Telegram Bot customer service workflow. If you encounter any issues, refer to the official documentation or contact the support bot @tgstaff_robot for help.