TG Bot 7-Day Launch Checklist: Complete Inspection Items from Bot Creation to Agent Routing and Quality Assurance

Operating a Telegram Bot customer service system, the biggest fear is not the lack of tools, but discovering after launch that “agents are not assigned permissions,” “routing rules are not set,” or “agents accidentally sent out payment addresses.” Instead of fixing problems after they occur, it’s better to go through the checklist step by step within 7 days. This article uses TG-Staff as the core tool and provides an executable tg bot launch checklist, covering all stages from Bot creation to QA launch.

---

Day 1: Bot Basic Setup and Project Creation

The starting point of any customer service system is the Bot itself. On the first day, complete Bot creation, project binding, and basic information editing to ensure all subsequent functions have a foundation.

Create a Bot via BotFather and Obtain Token

1. Search and open @BotFather in Telegram.
2. Send the /newbot command, and follow the prompts to set the Bot name and username (username must end with bot).
3. BotFather will return a Token in a format like 123456:ABC-DEF1234ghIkl-zyx57W2v1u123ew11. Copy and save the Token; it will be needed later for project binding.

Create a Project in TG-Staff Console and Bind Bot Token

1. Visit the TG-Staff Console and register an account (free trial for 3 days).
2. Click “Create Project,” enter a project name (e.g., “Overseas Customer Service” or “Web3 Support”).
3. In the project settings, find the “Bot Token” field and paste the Token obtained from BotFather.
4. After saving, the system will automatically verify the Token’s validity. Once successful, your Bot is officially connected to TG-Staff.

Edit Bot Profile and Chat Background (Standard/Pro Differences)

TG-Staff allows you to edit Bot profile directly in the console without going to BotFather:

• Avatar: Upload a 512×512 pixel PNG/JPG image.
• Name: Bot display name (supports Emoji).
• Description: The introductory text users see when first opening the Bot.

For chat background, the Standard and Pro versions differ as follows:

Feature	Standard	Pro
Chat background type	Solid color background (selectable color)	Telegram native theme background (light/dark)
Customization level	Basic color selection	Follows TG system theme, more immersive

If you are a brand team or pursue visual consistency, it is recommended to use the Pro version’s TG theme background.

---

Day 2: Agent Accounts and Team Permission Configuration

A Bot project may have multiple agents handling chats simultaneously. Day 2 focuses on: creating agent accounts, assigning permissions, and ensuring the team works in an orderly manner.

Create Agent Accounts and Invite Team Members

1. In the console left menu, go to “Agent Management.”
2. Click “Add Agent,” enter the agent’s email or Telegram username.
3. The system will send an invitation link (via email) or Bot message (via Telegram) to the agent. Clicking the link, the agent logs in with their own account to join the project.
4. According to the plan quota (Standard: 3/5 agents, Pro: 20 agents), allocate account numbers reasonably.

Configure Project Permissions and Operation Scope

Each agent account can independently configure permissions:

• Project Scope: Which Bot projects the agent can access (suitable for teams managing multiple Bots).
• Operation Permissions: Whether the agent is allowed to create or modify automation flows, send bulk messages, view user profiles, etc.

It is recommended to initially grant all agents “customer service reception” permissions, and later open advanced features as needed. This prevents new agents from accidentally modifying flow configurations.

---

Day 3: Chat Routing Rules and Diversion Links

After a user sends a message from the Bot, how is it assigned to the appropriate agent? Day 3 configures routing rules and creates diversion links for ad attribution.

Set Routing Rules: Round Robin vs. Online First

In Project Settings → “Chat Routing,” you can choose two assignment modes:

• Round Robin (default): The system polls all authorized agents in order, assigning new chats sequentially. Suitable for scenarios with a stable number of agents and balanced workload.
• Online First: Prioritize assigning to agents currently in “Online” status. If all agents are offline, fall back to round robin. Suitable for teams with irregular agent schedules.

Recommendation: If team agents are often online simultaneously, use “Online First” to reduce user wait time. If the number of agents is small and working hours are fixed, “Round Robin” is fairer.

Create and Use Diversion Links for Traffic Attribution

Diversion links (also called magic links) are a feature of TG-Staff Standard and above plans. They are short links (e.g., https://app.tg-staff.com/{code}). When a user clicks:

1. They are automatically redirected to your Telegram Bot.
2. During the redirect, the visitor’s IP address, browser information, and URL parameters are captured.

Use Cases:

• Place diversion links in Google Ads, Facebook ads to track user volume from each channel.
• Place diversion links on your website landing pages to distinguish organic traffic from paid traffic.
• Use diversion links in social media bios (e.g., Twitter, Instagram) to count referral effects from each platform.

How to create: In the console “Diversion Links” page, click “Create Link,” enter a name and the associated project. After generation, copy the short link.

---

Day 4: Visual Command Flow Building

When users enter the Bot, they see welcome messages and menus. Day 4 uses TG-Staff’s drag-and-drop flow editor to build user interaction paths with zero code.

1. In the console, go to the “Command Flow” module.
2. Drag a “Welcome Message” node from the left to the canvas, enter welcome text (can include Markdown formatting and buttons).
3. Add a “Menu” node, set button text and corresponding jump logic (e.g., “Contact Customer Service,” “View FAQ,” “Subscribe to Notifications”).
4. Connect the “Contact Customer Service” button to a “Transfer to Human” node, ensuring users automatically enter the agent chat queue after clicking.

---

Day 5: Bulk Messaging and Automatic Translation Configuration

Day five focuses on operational efficiency: reaching users in bulk and configuring automatic translation to reduce manual repetitive work.

Configure Automatic Translation

In Project Settings → “Automatic Translation,” select a translation engine:

• AI Translation (included in the Standard plan): Based on large language models, suitable for general scenarios.
• Google Professional Translation / DeepL Professional Translation (Professional plan): Higher translation quality, suitable for business or technical documents.
• Daily translation quotas vary by plan (see the official pricing page); the Professional plan offers unlimited translation.

Note: Does automatic translation translate messages sent by agents for display to users, or translate user messages for display to agents? TG-Staff supports bidirectional configuration; it is recommended to clearly check the directions “Agent → User” and “User → Agent” in settings.

Create a Bulk Broadcast Task

1. Go to the “Bulk Broadcast” module.
2. Select user segmentation criteria (e.g., “Active in the last 30 days,” “Never replied,” “Entered via split link A”).
3. Edit the broadcast content (text, images, buttons are all supported).
4. Set the sending time (send immediately or schedule).
5. After submitting the task, the system will automatically send based on the segment and track delivery rate and click-through rate.

---

Day 6: Content Moderation and Wallet Address Monitoring (Professional Plan)

For Web3, exchange, and NFT projects, agents mistakenly sending payment addresses is a major compliance risk. Day six covers configuring content moderation rules for Professional plan users.

Create Risk Phrases

1. Go to “Content Moderation” → “Risk Phrases.”
2. Click “Create Phrase,” enter a name (e.g., “Wallet Address”).
3. Add keywords: you can enter a full address (e.g., TXYZ1234567890) or an address fragment (e.g., first 8 characters TXYZ1234).
4. Select “Trigger Action”: pop-up for double confirmation (agent can still send) or block sending (agent cannot send).

Monitor Wallet Addresses

Add the following types of address fragments in the risk phrases:

• TRC20 address: Starts with T, length 34 characters.
• ERC20 address: Starts with 0x, length 42 characters.
• BTC address: Starts with 1, 3, or bc1.

View Trigger Records

In “Content Moderation” → “Trigger Records”, you can view the details of each blocked message:

• Agent information (account name, ID)
• Session ID
• Trigger time
• Hit risk words

Supports log export for internal compliance checks or audits.

---

Day 7: Quality Testing and SEO Landing Page Launch

On the final day, full-chain testing + deploying the diversion link to real channels.

Full-Chain Quality Inspection Checklist: Every Step from User to Agent

Check the following items one by one:

Check Item	Expected Result	Status
User sends a message via Bot	Bot auto-replies with a welcome message	□
User clicks “Contact Customer Service”	Message enters the agent queue	□
Agent receives new session notification when online	New session card appears on the agent end	□
Agent replies to the message	User receives the reply normally	□
Multilingual messages display correctly after auto-translation is enabled	Translation is correct on both agent and user sides	□
Clicking the diversion link redirects to the Bot	Redirect path is correct, no errors	□
When content moderation rules are triggered, agents cannot send prohibited content	Popup or successful block	□
After a bulk broadcast task is executed, users receive the message	Delivery rate > 95%	□

Deploy the Diversion Link to Landing Pages and Ad Channels

• Official website landing page: Use the diversion link on “Contact Us” or “Download App” buttons.
• Google Ads / Facebook Ads: Fill in the diversion link in the ad’s final URL field.
• Social media bios: Replace the “Link” position on Twitter, Instagram, LinkedIn with the diversion link.
• Email marketing: Insert the diversion link in the email body and add UTM parameters (e.g., ?utm_source=newsletter).

After deployment, view click data for each link on the TG-Staff console’s “Diversion Links” page to compare the traffic-driving effects of different channels.

---

Frequently Asked Questions

Q: Can I test all features during the free trial? A: Yes, you get a 3-day free trial upon registration, allowing you to experience the core features of the Standard and Pro versions (such as agents, diversion, visual workflows, bulk broadcast, etc.). Some Pro-exclusive features (like content moderation, wallet address monitoring) are also available during the trial.

Q: Do I need to use the diversion link (magic link) with ads? A: No. The diversion link is essentially a short link that can be deployed on any channel: official website, social media bios, emails, offline QR codes, etc. It automatically captures visitor IP and browser information for attribution analysis.

Q: What address formats are supported for wallet address monitoring in content moderation? A: Supports common on-chain addresses such as TRC20, ERC20, and BTC. You can add full addresses or address fragments (e.g., first 8 characters) in the risk word group, and the system will match and block them before the agent sends a message.

Q: What are the main differences between the Standard and Pro versions? A: The Standard version (approx. 8.99/month) is suitable for small teams and includes diversion links, session routing, agents, and auto-translation (AI translation has a quota). The Pro version (approx.16.99/month) adds content moderation, wallet address monitoring, unlimited translation/broadcast, user profiles, and Telegram theme chat backgrounds. For a detailed comparison, see the official pricing page.

Q: If an agent accidentally sends prohibited content, can it be traced? A: Yes, the Pro version’s content moderation module provides complete trigger record audits, including agent information, session ID, trigger time, and hit risk words. Logs can be exported for internal compliance checks.

---

Next Steps

• 👉 Register for a TG-Staff free trial and complete your Bot customer service system launch in 7 days.
• 📖 Check the official documentation for more detailed configuration tutorials.
• 🤖 Contact the customer service Bot for inquiries about plans or features.