TG Customer Service System 3-Day Trial Conversion Funnel: A Complete Guide from First Conversation to Plan Upgrade

Choosing a suitable TG customer service system based solely on feature lists is far from enough. To truly determine if it fits your business, you need to test it in real scenarios: from the moment a user sends a message, to agent replies, team collaboration, automated outreach, and compliance monitoring.

TG-Staff offers a 3-day free trial, enough for your team to conduct a complete “customer service system selection stress test.” This article uses TG-Staff as an example to walk you through the entire process from registration and setup, agent collaboration, automation configuration, to plan upgrade. Follow this guide, and after 3 days, you’ll be able to make a clear decision.

Why Do You Need a Trial Period to Validate a TG Customer Service System?

Many teams rely solely on website screenshots and feature comparison tables during selection, only to find issues like “inflexible routing rules,” “cumbersome agent collaboration,” or “lack of content moderation” after going live. The core value of TG customer service system trial is to help you answer three questions in real business flows:

1. Are features sufficient? Can agents efficiently handle conversations? Do routing rules cover your scenarios?
2. Is the team adaptable? Does multi-user operation lag? Are session transfers and internal collaboration smooth?
3. Is scaling easy? Does upgrading from Standard to Professional require reconfiguring the project?

Three days may be short, but following the plan below will cover key milestones from setup to decision-making.

Day 1: Build from Scratch and Send the First Conversation

Goal: Register TG-Staff, connect the first Telegram Bot, complete basic configuration, and have an agent reply to a user’s first message via the web interface.

Connect the Bot and Configure Basic Info

1. Register and log in to the console: Visit app.tg-staff.com, register via email or Telegram account, and automatically enter the 3-day free trial.
2. Connect the Bot: On the “Projects” page in the console, click “Add Bot” and enter your Telegram Bot Token (obtained from @BotFather). TG-Staff will automatically read the Bot’s existing settings.
3. Edit Bot profile: On the “Bot Profile” page, directly modify the avatar, name, and description without switching to BotFather. This is practical for branding.

Create the First Customer Service Agent and Initiate a Conversation

1. Add an agent: On the “Agent Management” page, click “Add Agent” and enter the agent’s Telegram username or email. The system will send an invitation link.
2. Agent logs into the web portal: The invited agent logs into app.tg-staff.com via the link to access the dedicated workspace.
3. Simulate a user sending a message: Use another Telegram account to send any content to your Bot (e.g., “Hello, I’d like to inquire about product pricing”).
4. Agent replies: On the “Conversation List” in the web portal, the agent will see the new conversation. Click on it, enter a reply, and send it. The first two-way chat is complete.

Day 2 · Hands-On with Agent Collaboration & Chat Routing

Objective: Test multi-agent chat handling, chat transfer, routing rules, and routing link attribution.

Multi-Agent Collaboration: Chat Transfer & Private Notes

1. Create a second agent: Repeat the agent creation steps from Day 1, ensuring both agents have permission to handle the project.
2. Simulate chat transfer: Agent A clicks “Transfer” in the chat window, selects Agent B, and confirms. Agent B will receive a transfer notification, and the chat history is fully preserved.
3. Try private notes (Pro trial): Open the notes feature in the chat window, enter an internal remark (e.g., “This user is VIP, quote needs manager approval”). Notes are visible only to agents, not to the user.

Configure Chat Routing Rules & Routing Links

1. Set up routing rules: In “Project Settings → Chat Routing”, select “Online Priority” mode. When multiple agents are online, new chats are assigned to online agents first; when all are offline, it falls back to round-robin. If you want specific agents to handle certain chats, set the project’s customer service scope to “Designated Agents” and check the corresponding agents.
2. Create a routing link: In the “Routing Links” module, create a new link, e.g., https://app.tg-staff.com/abc123. This short link points to your Bot; when clicked, it automatically redirects to Telegram and opens a chat with the Bot.
3. Simulate ad attribution: Open the routing link in a browser, appending ?source=facebook_ad&campaign=product_launch at the end. Then view the chat details; you will see the captured IP, browser UA, and URL parameters source and campaign in the “Source Info” section. This provides direct data for ad attribution.

Day 3 · Automation & Compliance Feature Validation

Objective: Test visual command flows, bulk messaging, and Pro-exclusive content moderation (including wallet address monitoring).

Build a Bot Auto-Reply Flow with Zero Code

1. Go to the “Command Flow” module and click “New Flow”.
2. Using the drag-and-drop editor, drag a “Welcome Message” node from the left component library and enter: “Hello! Welcome. Please select a service: 1. Product Inquiry 2. Technical Support 3. Human Agent”.
3. Drag a “Menu Selection” node and configure three buttons corresponding to the three options.
4. Set subsequent nodes for each option: e.g., when “Human Agent” is selected, trigger a “Transfer to Human” node that automatically assigns the user to an online agent.
5. Save and publish the flow. Send a message to the Bot on Telegram to test if the interaction works as expected.

Content Moderation & Wallet Address Monitoring (Pro Trial)

1. Configure risk phrases: In the “Content Moderation” module, create a new risk phrase, e.g., “Sensitive Payment Address”. In the keyword list, enter a real TRC20 address snippet (e.g., TXYZ123), and select the group as “Block”.
2. Associate with project: Associate this risk phrase with the current test project, and enable the “Pre-send Detection” toggle.
3. Agent triggers moderation: Have an agent reply in the Web portal with a message containing TXYZ123. The send button will be disabled, and a popup will warn: “Message contains risk words, please confirm before sending.”
4. View audit logs: In “Moderation Audit”, you can see the trigger record, including agent username, chat ID, trigger time, and risk word content. This is an important compliance control for Web3 and crypto teams.

Before Trial Ends · How to Decide on Upgrading?

Before the 3-day trial ends, evaluate based on your business needs:

Requirement Scenario	Recommended Plan	Reason
Basic customer service + multi-agent + chat routing	Standard	Covers core features, from $8.99/month
Need routing link for ad source attribution	Standard or above	Standard includes routing links
Extensive multilingual support + unlimited translation	Pro	Pro offers unlimited translation quota
Content moderation + wallet address monitoring	Pro	Pro-exclusive features
User profiles + deep data analytics	Pro	Standard does not include user profiles
Team larger than 20 agents	Pro	Pro supports up to 20 agents (Standard supports fewer)

If your team needs routing link attribution, multi-agent collaboration, and bulk messaging, Standard is sufficient. If you need content moderation, unlimited translation, and user profiles, we recommend Pro. Annual discounts are available on the pricing page.

Upgrade Operation: Stripe & USDT Payment Methods

1. In the console, click “My Subscription” to view your current plan and expiration date.
2. Click “Change Plan”, select Standard or Pro in the popup, and choose the subscription period (30/90/180/360 days).
3. Choose a payment method:
   • Stripe: Supports credit cards or PayPal; you will be redirected to Stripe Checkout to complete payment, and the plan takes effect immediately.
   • USDT (TRC20): The system generates a payment address and amount; after transferring via on-chain wallet, the plan status syncs automatically (usually within minutes).
4. After successful payment, return to the console to confirm the subscription status is updated. All configurations during the trial (Bots, flows, agents, chat records) are retained—no need to rebuild.

FAQ

Q: Can I test all paid features during the 3-day trial?

A: Yes. TG-Staff trial grants full access to Standard features, and Pro features (content moderation, unlimited translation, user profiles, etc.) are also available for testing. We recommend following the Day 1–3 plan to test each feature.

Q: Will data be lost after the trial ends?

A: No. After the trial expires, chat records, configured flows, user data, etc., remain in the project. Once you renew the subscription, you can continue using them without reconfiguration.

Q: How to choose between Standard and Pro?

A: The key differences are content moderation, translation quota, and user profiles. If your team is involved in Web3/crypto compliance monitoring or needs extensive multilingual support, choose Pro; if it’s basic customer service with routing, Standard is enough.

Q: What’s the difference between USDT and Stripe payment?

A: Stripe supports credit cards/PayPal and activates instantly; USDT (TRC20) is suitable for teams preferring on-chain payments, and the plan status syncs automatically after the transfer. Both can be selected in the console.

Q: Can I add multiple Bot projects during the trial?

A: Yes. The free trial allows adding Bot projects according to the plan’s quota; the maximum number of Bots differs between Standard and Pro, as shown in the console.

---

3 days may be short, but it’s enough to complete a full evaluation of a TG customer service system. From the first chat to plan upgrade, every step provides data to support your decision.

• Register for TG-Staff trial: https://app.tg-staff.com/
• Read full documentation: https://docs.tg-staff.com/
• Contact support Bot (@tgstaff_robot) for one-on-one assistance