TG-Staff Command Flow Template Library: Four Replicable Structures for Welcome, After-Sales, Booking, and Transfer to Human Agent

When your Telegram Bot handles hundreds of consultations daily, and each reply involves repeatedly writing menus, manually routing users, and organizing user information, a reusable command flow template library can significantly reduce this repetitive work. TG-Staff’s visual command flow editor is designed for this—it enables non-technical teams to quickly build standardized bot interactions through drag-and-drop nodes, and templates can be copied across projects, achieving “design once, reuse multiple times.”

Why Do Telegram Bots Need “Command Flow Templates”?

Many teams encounter these pain points when operating Telegram Bots:

• Repeatedly writing menus: Every new bot project requires redesigning welcome messages, main menus, and branching logic, which is time-consuming and prone to omissions.
• Chaotic flows: Multi-step interactions (like booking or after-sales) lack a unified structure, causing users to drop off midway, and agents can’t understand the context when taking over.
• Difficult to reuse: Experience gained from one bot cannot be quickly replicated to another account or project, forcing the team to start from scratch.

The value of a template library lies in providing proven standardized structures that you can directly apply and tweak as needed, rather than starting from a blank canvas every time. TG-Staff’s template library is designed based on real customer service scenarios, covering the full chain from new user onboarding to after-sales tickets.

Quick Start with TG-Staff Visual Command Flow Editor

TG-Staff’s editor features a drag-and-drop interface with no coding required. Its core logic is: nodes + connections = interaction paths. Each node represents a bot message or action, and connections define the direction when a user clicks a button.

From Scratch to First Command: Three Steps to Get Started

1. Add a flow: In the TG-Staff console’s “Command Flow” module, click “Create Flow” and enter a name (e.g., “Welcome Menu”).
2. Drag nodes: Drag a “Message Node” from the left node panel onto the canvas, double-click to edit the text content.
3. Configure responses: Add buttons within the message node (e.g., “View Products”, “Contact Support”), then drag a new node and connect the button to the target node to complete the navigation logic.

The whole process is similar to building a flowchart, and you can complete a simple template in 15 minutes.

Node Types and Connection Logic

TG-Staff offers four common node types:

Node Type	Purpose	Typical Scenario
Message Node	Send text, images, or buttons	Welcome messages, menus, confirmation messages
Condition Node	Branch based on user input or tags	Determine if user selects “After-Sales” or “Booking”
Jump Node	Switch to another flow or external link	Jump from welcome menu to after-sales flow
Transfer to Human Node	Trigger session routing rules	After user clicks “Transfer to Human”, automatically assign to agent

Connection rules between nodes: Each button can only connect to one line, but a node can have multiple exits (e.g., the “Main Menu” node has three buttons, each connecting to “Product Introduction”, “FAQ”, and “Contact Support” nodes).

Four Replicable Command Flow Template Structures (Core Section)

The following four templates cover the most common Telegram Bot customer service scenarios. You can directly reference the node layout and response content to quickly build in TG-Staff’s editor.

Template 1: Welcome and Menu Navigation

Applicable Scenarios: Onboarding new users when they first open the bot, or standard replies after users send /start.

Node Layout:

• Start: User inputs /start or enters the bot for the first time.
• Message Node 1: Send welcome message + main menu buttons (Product Introduction / FAQ / Contact Support).
• Branches: Each button jumps to the corresponding node:
  • “Product Introduction” → Send a brief product list, ending with a “Back to Main Menu” button.
  • “FAQ” → Send an FAQ list; after the user selects a question number, the bot automatically replies with the answer.
  • “Contact Support” → Trigger the transfer to human node (see Template 4).

Best Practice: Keep the welcome message under 150 characters, and limit buttons to no more than 4 to avoid user fatigue. Always include a “Back to Main Menu” button at the end to prevent users from getting lost.

Template 2: After-Sales and Ticket Submission

Applicable Scenarios: Users encounter issues and need to submit a ticket (e.g., e-commerce refunds, SaaS technical faults).

Node Layout:

• Start: User clicks the “After-Sales” button.
• Message Node 1: Send problem category selection buttons (Order Issue / Technical Issue / Other).
• Condition Node: Based on user selection, jump to the corresponding description input node.
• Message Node 2: Prompt user to “Please briefly describe your issue; we will handle it as soon as possible.”
• Message Node 3: After user input, automatically reply with “We have received your feedback. Your ticket number is #{random code}. An agent will contact you within 30 minutes.”
• Transfer to Human Node: Simultaneously trigger a transfer request, sending ticket information to the agent.

Best Practice: After the user inputs the description, it’s recommended that the bot send a confirmation message containing the ticket number and estimated response time to reduce user anxiety. Ticket data is automatically recorded in the user profile, so agents can view the history when taking over.

Template 3: Booking and Schedule Confirmation

Applicable Scenarios: Consultation services, course registration, meeting booking, etc., where users need to select a time.

Node Layout:

• Start: User clicks the “Booking” button.
• Message Node 1: Send service list buttons (e.g., “Basic Consultation / Advanced Plan / Enterprise Customization”).
• Condition Node: Based on selection, jump to the corresponding time slot selection node.
• Message Node 2: Send date selection buttons (showing only the next 7 days to avoid long lists).
• Message Node 3: Send specific time slot buttons (e.g., “09:00-10:00 / 10:00-11:00”).
• Message Node 4: Prompt user to “Please enter your contact information (phone number or email).”
• Confirmation Node: Summarize information (service + date + time + contact info) and send confirmation buttons “Confirm Booking / Modify Info”.
• End: After user confirms, reply with “Booking successful! We will remind you 15 minutes before the scheduled time.”

Best Practice: Use “dynamic options” for date and time slot buttons (TG-Staff supports reading available times from external APIs) to prevent users from selecting fully booked slots. After successful booking, the bot can automatically send a calendar invitation link.

Template 4: Transfer to Human Agent and Session Routing

Applicable Scenarios: Users need human agent intervention, or the bot cannot answer automatically.

Node Layout:

• Start: User clicks the “Transfer to Human” button.
• Message Node 1: Send “We are transferring you to a human agent, please wait…” and display a queue prompt.
• Condition Node: Check if there are any online agents (determined by TG-Staff’s session routing rules).
• Branches:
  • Online agents available → Trigger the transfer to human node, automatically assigning an agent.
  • No online agents → Send “All agents are currently offline. We will record your issue and prioritize it when they come online.” Simultaneously save the user’s message to a pending queue.

Best Practice: Collect user issue tags (e.g., “Order Issue”, “Refund”) on the bot side before triggering routing. This way, when an agent takes over, the user profile already contains tag information, allowing them to directly address the issue without asking again.

How to link templates with “Session Routing”?

The “Transfer to Agent” node in command flows does not work independently; it needs to work with TG-Staff’s session routing rules to achieve seamless transition from bot conversations to human agents.

Configuration Steps:

1. In TG-Staff console, go to “Project Settings” and enable the “Session Routing” feature.
2. Choose routing mode: Round Robin (default, sequentially polls agents with permissions) or Online First (prioritizes online agents, falls back to round robin when all are offline).
3. In the command flow editor, drag the “Transfer to Agent” node; the system will automatically detect configured routing rules.
4. Optional: Set trigger conditions for the “Transfer to Agent” node (e.g., only within specific project support scope).

When a user clicks “Transfer to Agent”, TG-Staff automatically invokes the routing rule to assign the session to an online agent. The agent will see the user’s chat history (including tags and descriptions collected in the template) in the Web console, without switching tools.

From Templates to Operations: Batch Messaging and User Profiles in Sync

Command flow templates are not just static interaction structures; they can integrate with TG-Staff’s batch messaging and user profiling features to form an operational closed loop:

• User Segmentation: Through conditional nodes in templates, record user choices (e.g., “selected after-sales” or “appointment successful”), and these tags are automatically written into user profiles.
• Targeted Push: When batch messaging, filter audiences by user profile tags. For example, push “service expiry reminders” to users who “booked successfully”; send “solution updates” to users who “submitted after-sales tickets”.
• Template Iteration: Based on user behavior data after messaging (e.g., click-through rates, completion rates), adjust template node order or button copy to continuously optimize conversions.

For example, an e-commerce Bot can first collect user preferences via a “Welcome & Menu Navigation” template, then handle complaints with an “After-Sales & Ticket Submission” template, and finally use batch messaging to push new campaign entries to frequent questioners—all data managed within TG-Staff’s single platform.

Frequently Asked Questions

Q: Can TG-Staff command flow templates be copied to other projects?

A: Yes. In the TG-Staff console’s flow editor, you can export a created flow as JSON and import it into other projects under the same account, making it easy to reuse template structures across multiple Bots. If you are using multiple projects under the same plan, simply tweak button copy and node content after copying.

Q: Does the “Transfer to Agent” node in templates require additional configuration?

A: Yes. It is recommended to pre-configure session routing rules (e.g., “Online First”) in project settings to ensure transfer-to-agent requests are automatically assigned to online agents; if all agents are offline, you can set fallback replies or queue prompts. TG-Staff supports customizing offline reply text in the “Transfer to Agent” node.

Q: Can non-technical users independently build these four templates?

A: Yes. TG-Staff’s visual editor uses drag-and-drop, requiring no programming background; following the node structure provided in this article, you can configure a simple template within 15 minutes. For more complex logic (e.g., dynamic options or API calls), refer to the official documentation or contact customer support.

Q: Does the template support automatic multi-language translation?

A: Yes. Messages sent in command flows go through TG-Staff’s automatic translation engine (AI translation included in the Standard plan), and the Bot can automatically convert reply content based on the user’s language preference. You only need to write copy in one language (e.g., Chinese) in the template, and the system handles multi-language scenarios automatically.

Q: Can I use these templates during the free trial?

A: Yes. Registering for TG-Staff grants a 3-day free trial, during which you can fully experience the visual command flow editor and all template features; after the trial ends, upgrade to the Standard or Pro plan as needed to continue using them. It is recommended to build at least one complete flow based on this article’s templates during the trial period to test its integration with routing and user profiles.

---

If you want to get started quickly, you can directly visit the TG-Staff website to register for a free trial, or contact @tgstaff_robot for a one-on-one demo. For more in-depth technical details, refer to the Command Flow chapter in the TG-Staff documentation.