TG-Staff Visual Command Flow Example: A Complete Guide from Welcome Message to Human Handoff

When you use a Telegram Bot for customer service or community management, the most basic and headache-inducing issue is often: When a user sends a message, how should the Bot respond? If you rely entirely on manual replies, it’s inefficient and costly; if you code a Bot, it requires development resources and repeated debugging.

TG-Staff’s visual command flow editor is designed to solve this dilemma. It lets you build the complete interaction chain from “user’s first contact” to “human agent handoff” with zero-code drag-and-drop, like building blocks. This article will walk you through four typical nodes—Welcome, Menu, Appointment, and Human Handoff—step by step, demonstrating how to build a production-ready Bot command flow, helping you quickly master the core operations of the tgstaff command flow.

---

Why Visual Command Flow: The Complete Chain from Welcome to Human Handoff

A well-designed command flow helps your team achieve three things:

1. Automatic triage: Users don’t have to wait; the Bot handles common questions first (e.g., service introductions, pricing inquiries), reducing the burden on human agents.
2. Pre-collection of information: Using form nodes to collect user names, needs, and contact details so agents have full context when they take over.
3. Smooth human handoff: When a user needs human help, one click transfers them to a customer service session, with assignment rules (round-robin/online-first) executed automatically by the system.

TG-Staff’s visual editor encapsulates all this logic into node cards. You just drag, drop, connect, and fill in text to quickly build a Telegram Bot auto-reply system. Below, we’ll build from scratch using four typical scenarios.

---

Node 1: Building a Welcome Node—First Impression on User’s First Contact

When a user sends /start or any message to your Bot for the first time, the Welcome node is their first stop. A friendly welcome message reduces bounce rates and guides them into the subsequent flow.

Configuring Welcome Text and Variables

In the TG-Staff console’s “Command Flow” page, click “Add Node” → select “Welcome Node”. In the right editing panel, you can input the welcome text and insert dynamic placeholders to personalize the reply.

Example configuration:

你好 {username}！👋 欢迎来到 [你的品牌名] 的官方客服 Bot。

我是你的智能助手，可以帮你：
- 查看服务与报价
- 预约产品演示
- 联系真人客服

请选择下方菜单开始吧。

Where {username} is a pre-built variable in TG-Staff that automatically replaces with the user’s Telegram display name. You can also use variables like {first_name} and {user_id}; see the documentation for details.

Connecting the Welcome Node to a Menu Node

After editing the welcome message, find the “Next” connection point at the bottom of the node, drag a line to the “Menu Node” you’ll create. This way, after the user receives the welcome message, the Bot will automatically send menu options.

---

Node 2: Designing a Menu Node—User Self-Service Entry Point

The Menu node lets users quickly find information by clicking buttons, without typing complex text.

Adding Button Options and Jump Targets

Add a “Menu Node” in the editor, then click “Add Button”. Suppose your business scenario is B2B SaaS customer service; you can set up the following buttons:

Button Text	Jump Target Node	Description
📋 View Services	Text Reply Node (displays service list)	User self-service browsing
📅 Book Demo	Appointment Node	Jump to form collection
💬 Contact Support	Human Handoff Node	Direct transfer to live agent

Each button corresponds to a “Jump Target”. You need to create the corresponding nodes (e.g., Appointment Node, Human Handoff Node) in advance, then select them in the button configuration.

Configuring Menu Fallback and Timeout Handling

Users may send irrelevant messages or make no selection. In the Menu node’s “Advanced Settings”, you can configure:

• Default Reply: When the user inputs something not in the button options, the Bot replies “Please click the buttons below to select a service, or type ‘agent’ to contact support.”
• Timeout Prompt: Set a 60-second inactivity timeout, after which the Bot automatically sends “Are you still there? Reply anytime if you need help.”

This prevents user churn due to flow deadlock.

---

Node 3: Creating an Appointment Node—An Auto-Form to Collect User Information

The Appointment node is essentially a “form collector”, suitable for scenarios where you need users to fill in their name, phone, email, or notes.

Add a “Text Reply Node” (or “Form Node”, depending on the editor’s actual name) in the editor, then configure multiple input fields. For example:

1. Field 1: Name (required, text input)
2. Field 2: Contact Email (required, text input, with format validation hint)
3. Field 3: Requirement Description (optional, multi-line text)

Key configuration: In the node settings, check “Write submitted data to user profile” so agents can see all the user’s filled information in the sidebar when they take over. You can also configure “Notify agent after submission” to send an internal notification to the designated agent.

After completing the Appointment node, you can connect it to a “Success Notification Node” (e.g., “Thank you for booking, we will contact you soon”), and also add a button “For further communication, click to transfer to human” to ensure users can always get human assistance.

---

Node 4: Setting Up a Human Handoff Node—From Bot Auto-Reply to Agent Takeover

The Human Handoff node is the “exit” of the entire flow. When a user needs human service, it automatically creates a customer service session and assigns it to an agent.

Configuring Session Assignment Rules

After adding a “Human Handoff Node”, configure in the right panel:

• Project Agent Scope: Select “All Agents” or “Specific Agent Group”.
• Assignment Rules: Supports “Round-Robin” (assigns to authorized agents in order) or “Online-First” (preferentially assigns to currently online agents; if all are offline, falls back to round-robin).

It’s recommended to use “Online-First” during peak support hours to ensure users connect to a human as quickly as possible. If your team has a small number of agents (e.g., 3-5), “Round-Robin” is more fair.

Agent Experience After Human Handoff

When a user triggers the Human Handoff node, the agent will see a new session in the “Live Sessions” list of the TG-Staff Web console. Upon clicking into it, the session sidebar will automatically display the user’s previous interaction records in the Bot flow (which menu buttons they clicked, what form fields they filled), so the agent doesn’t need to ask again and can directly take over the conversation.

---

End-to-End Workflow & Publishing — From Editor to Bot Launch

After creating the four nodes, connect them in the following order:

欢迎节点 → 菜单节点 → (按钮分别跳转至) 预约节点 / 转人工节点 / 其他回复节点

Once connected, click the “Test Mode” button in the top right corner of the editor to simulate user interaction:

• Send /start → Should receive welcome message → Menu automatically pops up
• Click “Book a Demo” → Enter form → Fill in information → Receive confirmation
• Click “Contact Support” → New conversation created automatically → Agent sees the new conversation

After confirming, click “Save & Publish.” Once published, your Telegram Bot’s auto-replies will be instantly updated without needing to restart the bot or reconfigure the webhook. If you need to make changes later, simply adjust the node configuration in the editor and publish again to overwrite the old flow.

---

Advanced Tips: Combining Diversion Links with User Profiles to Optimize Flows

TG-Staff’s Diversion Links allow you to generate unique short links for different channels (e.g., Google Ads, Twitter posts, Telegram groups). When a user enters the bot via a diversion link, the system captures source channel, IP, browser info, etc., and writes them into the user profile.

In your command flow, you can use this profile data for conditional branching:

• If a user comes from “Ad_A,” the welcome message shows “Exclusive A Campaign Offer”
• If a user comes from “Community_B,” the menu prioritizes community-specific services

To do this, add a “Conditional Branch Node” between nodes, directing the flow based on user profile fields (e.g., source_channel). For detailed configuration, see the TG-Staff documentation.

---

FAQ

Q: How many node types does TG-Staff’s visual command flow support?
A: Currently, it supports welcome nodes, menu nodes, text reply nodes, human handoff nodes, conditional branch nodes, etc. For the exact list, refer to the editor’s actual node palette.

Q: Can I create multiple command flows for one bot?
A: Yes. TG-Staff supports multiple flows per project. You can design and switch between different scenarios (e.g., pre-sales inquiry, after-sales support).

Q: After publishing a flow, will the old replies in the bot be overwritten immediately?
A: Yes. After saving and publishing, the Telegram Bot’s auto-replies will instantly update to the new flow configuration without restarting the bot or resetting the webhook.

Q: In a human handoff node, how does the agent know which menu options the user previously selected?
A: TG-Staff syncs user interaction records (e.g., menu button clicks, form field entries) to the user profile in the session sidebar. The agent can view the context directly after taking over.

Q: Can I fully test the command flow during the free trial?
A: Yes. During the 3-day free trial, you have access to all standard features, including the visual command flow editor and human handoff nodes. We recommend completing flow setup and testing within the trial period.

---

Next Steps: Build Your First TG-Staff Command Flow

If you haven’t signed up for TG-Staff yet, get started now: visit https://app.tg-staff.com/ to register and get a free 3-day trial. Create a new project in the console, and follow the four-node example in this article to drag and drop your first bot command flow.

If you run into issues, check the official documentation or contact customer support bot @tgstaff_robot for real-time help. Once you’ve built your flow, feel free to screenshot and share it, or ask the support team for optimization tips.