How to Implement a 24/7 Duty Schedule with a Telegram Bot: A Complete Guide to Bot Fallback + Human Escalation Configuration

Customer messages never sleep. At 3 AM, while your team is resting, a query like “How do I place an order?” might slip away. For teams relying on Telegram Bot for customer service or operations, a 24/7 Telegram Bot duty schedule is not just a nice-to-have—it’s a must. This article breaks down a practical configuration plan: the bot fallback mechanism automatically handles off-peak visitors, and human escalation rules seamlessly take over when agents come online. No extra development needed—everything is done in the TG-Staff console.

---

Why Do You Need a 24/7 Duty Schedule? The Synergy of Bot Fallback and Human Escalation

Overseas users span multiple time zones, especially for cross-border teams. Without a duty schedule, your bot either stays silent when unattended (losing customers) or keeps repeating “Please wait” (poor experience). The core value of a 24/7 duty schedule lies in using automation to fill human gaps and smart escalation to ensure complex issues are not missed.

• Bot Fallback: When all agents are offline, the bot automatically replies with preset messages (e.g., menus, FAQs, collecting user info), so customers are not left waiting.
• Human Escalation: When agents are online or a user explicitly requests human help, the conversation is automatically transferred from the bot to a live agent, ensuring a seamless handover.

The logic is simple: the bot handles 80% of standard questions, while humans tackle 20% of complex scenarios. Configuring the duty schedule means defining this “switch moment.”

Bot Fallback: Automatic Reception When Unattended

The core mechanism of bot fallback is “default replies.” In TG-Staff, you can set up visual command flows or simple auto-reply rules to define how the bot responds when no human agents are online.

Typical fallback scenarios:

• Nighttime or holidays: Automatically reply with a menu to guide users to self-service.
• During peak hours with queues: Send a queue prompt, encouraging users to leave a message or schedule a callback.
• First contact with new users: Automatically send a welcome message to collect contact info or needs.

Key: Fallback messages must include an escalation prompt. For example: “Type ‘agent’ to transfer to a human,” or provide a menu button “Contact a human agent.” Otherwise, users might get stuck in the bot loop.

Human Escalation: When to Switch from Bot to Live Agent

There are typically three triggers for human escalation:

1. User Initiated: The user types keywords like “agent” or “customer service,” and the bot recognizes and initiates a transfer.
2. Bot Unable to Answer: Set up an “unmatched” branch in the fallback flow to automatically escalate unrecognized questions.
3. Routing Rules Auto-Trigger: For example, in “online-first” mode, when an agent is online, new conversations go directly to a human.

Combining the duty schedule with routing rules enables “dynamic switching”: agents online → human first; agents offline → bot fallback. No manual intervention needed.

---

Preparation: Ensure Your Bot Is Connected to TG-Staff and Basic Features Are Enabled

Before configuration, confirm the following prerequisites:

• Register a TG-Staff account and log in to the App Console.
• Bind your Telegram Bot in the console (get the token from BotFather).
• Complete basic settings: bot name, avatar, description (can be edited directly in the console, no need to go to BotFather).
• Add at least one agent account (for testing human escalation).

If not done yet, please refer to the official documentation for initialization. The free trial lasts 3 days, enough to complete all configuration tests.

---

Step 1: Configure Bot Fallback Messages—Let the Bot Auto-Reply When Unattended

In the “Command Flows” or “Auto Reply” module of the TG-Staff console, create fallback messages.

1. Enter the Visual Flow Editor: Select your bot project, click “Command Flows” → “New Flow.”
2. Drag a Start Node: Set the trigger condition to “New User Message” or “When No Agent Online.”
3. Add Reply Content: Write the fallback message in the node. It is recommended to include:
   • A greeting (e.g., “Hello! I am XX Assistant. Customer service is currently offline.”)
   • Self-service options (e.g., “1. View FAQs” “2. Submit an order request”)
   • An escalation prompt (e.g., “Reply ‘agent’ to transfer to customer service”)
4. Save and Enable: Ensure the flow status is “Enabled” and set it as the “Fallback Flow.”

Fallback Message Template Example:

你好，欢迎来到 XX 商城 🛒

当前客服休息中，但你可以：
1️⃣ 回复“帮助”查看常见问题
2️⃣ 回复“订单”查询物流
3️⃣ 回复“人工”留下联系方式，我们会在上班后第一时间联系你

也可以直接描述你的问题，我会尽量帮你解答。

---

Step 2: Set Up Duty Schedules and Human Escalation Rules—Achieve 7×24 Seamless Handover

This is the most critical step. The duty schedule defines “who is online at what time,” and the routing rules define “how conversations are assigned.”

Configure Duty Schedules: Specify Agent Online Hours and Coverage

TG-Staff agents’ status is automatically detected based on web login (online/offline). The duty schedule is not for “scheduled login” but defines expected coverage hours, working with routing rules to enable automatic switching.

1. Enter Project Settings: Select your Bot project and click “Agent Management.”
2. Add Agents: Assign accounts to each agent and set permissions (e.g., “reception only” or “view user profiles”).
3. Configure Online Hours: In agent details, set expected online hours (e.g., Mon-Fri 9:00-18:00). The system does not force agents to log in during these hours, but routing rules use this configuration for priority decisions.

Actual Operation Logic: Actual online/offline status is determined by web login status. The duty schedule mainly serves as a team scheduling reference and, in the “online-first” routing rule, as a fallback to Bot when all agents are offline.

Set Up Human Escalation Rules: Trigger Conditions for Bot-to-Agent Handover

In the “Routing Rules” module, select the “Online First” mode. This is the best option for dynamic switching:

• Agent Online: New conversations are automatically assigned to online agents (via round-robin or idle status).
• All Agents Offline: Conversations automatically fall back to the Bot fallback flow.

Steps:

1. Enter Routing Rules: Project Settings → Routing Rules.
2. Select Mode: Choose “Online First” (default mode is “Round Robin”).
3. Specify Agent Scope: Select “All Agents” or “Specific Agents” (e.g., only allow certain agents to handle human escalations).
4. Save and Activate.

Optional: Combine with Routing Links (Magic Links). If you drive traffic via ads or social media, use TG-Staff’s official domain short links (e.g., https://app.tg-staff.com/{code}). Visitors click to auto-navigate to the Bot while capturing source info. Combined with routing rules, this enables a complete flow: “ad traffic → Bot auto-reply → online agent handover.” Available in Standard plan and above.

---

Step 3: Test and Optimize—Verify Fallback and Escalation Work as Expected

After configuration, end-to-end testing is mandatory.

1. Simulate Offline Scenario:

   • Log out all agents (close Web console pages).
   • Send a message to the Bot from another Telegram account.
   • Expected Result: Bot auto-replies with fallback message, which should include an escalation prompt.

2. Simulate Online Scenario:

   • Log in an agent account (keep Web console open).
   • Send a message to the Bot again from another Telegram account.
   • Expected Result: Conversation automatically assigned to that agent; agent interface shows a new conversation prompt.

3. Test Escalation Trigger:

   • In the offline scenario, the user types “human” (or your set trigger word).
   • Expected Result: Bot replies “Transferring to customer service, please wait” while the system records the request. When an agent comes online, the conversation automatically transfers.

4. Common Troubleshooting:

Issue	Possible Cause	Solution
Fallback message not showing	Fallback flow not enabled or not active	Check flow status, ensure “Enable” and set as fallback flow
Human escalation fails	Escalation trigger word not configured or routing rule error	Confirm trigger word has transfer rule created in command flow
Conversation not auto-assigned	Routing rule not set to “Online First”	Check routing rule mode, ensure it is “Online First”

---

Advanced Tips: Combining Routing Links with User Profiles to Boost 7×24 Reception Efficiency

After basic setup, you can improve efficiency with the following features:

• Routing Links (Magic Links): Generate unique short links for different channels (e.g., ads, social media, email) to track conversion performance from each source. When users enter the bot via a link, the system automatically captures IP, browser info, and URL parameters for subsequent attribution analysis. Available in Standard plan and above.
• User Profiles (Pro): Record user history, orders, tags, etc. Combined with routing rules, you can prioritize high-value customers for human handoff. For example, set a condition: if a user’s historical order amount > $100, automatically tag them as VIP and assign them to an available agent first.
• Content Moderation (Pro): In human escalation scenarios, detect risk words (e.g., wallet addresses, sensitive terms) before an agent sends a message. If triggered, show a pop-up for double confirmation or block the message. Ideal for Web3, exchanges, and teams requiring compliance and internal controls.

---

Configuration Checklist

• Register TG-Staff and bind the Bot
• Create a Bot fallback message (with escalation prompt, e.g., “Type ‘agent’ to transfer”)
• Add agent accounts and assign permissions
• Set agent online hours (shift schedule)
• Configure routing rules (select “Online First” mode)
• Test offline scenario: Bot fallback responds correctly
• Test online scenario: Chat automatically transfers to a human agent
• Optional: Enable routing links to track ad sources
• Optional: Upgrade to Pro to enable user profiles and content moderation

---

Frequently Asked Questions

Q: Can the Bot fallback message include multiple options? How to set it up?

A: Yes. In TG-Staff’s visual command flow, use the drag-and-drop editor to build multi-step interactions, such as adding buttons for “FAQ” and “Contact Support”. Users can click to trigger corresponding replies or escalation requests. No coding required, all done via drag-and-drop.

Q: If some agents are online, how to ensure high-priority customers are transferred to a human agent first?

A: Through the “Online First” mode in routing rules, the system automatically assigns new chats to online agents. Combined with user profiles (Pro version), you can set conditions (e.g., historical order amount > $100) for priority transfer, which requires custom routing logic. It is recommended to configure VIP tag rules in the Pro version.

Q: After setting the shift schedule, do agents need to manually log in/out?

A: No. TG-Staff automatically detects agent status (online/offline) based on Web login. The shift schedule only defines the expected coverage period; actual transfer depends on the agent’s real-time status and routing rules. Agents only need to keep the Web console open to automatically receive chats.

Q: Can I test all features during the free trial?

A: The free trial includes Standard features (e.g., routing links, chat routing, auto-translation), but Pro features (e.g., content moderation, user profiles) require an upgrade. It is recommended to focus on testing the fallback and escalation workflows during the trial to ensure they meet your needs before upgrading.

Q: Does the Bot fallback message support multiple languages?

A: Yes. TG-Staff provides auto-translation (Standard version includes AI translation). You can configure multi-language versions in the fallback message, or use translation to convert user input and agent replies in real time. For multilingual teams, it is recommended to use mainstream languages (e.g., Chinese and English) in the fallback message along with translation.

---

Next Steps

• Register for a 3-day free trial of TG-Staff: app.tg-staff.com
• Read the documentation for detailed configuration: docs.tg-staff.com
• Contact the support Bot for help: @tgstaff_robot

Configure the tg bot 7x24 shift schedule to enable Bot fallback and human escalation to work together, so your team never misses a customer message.