TG-Staff Seat Login Complete Guide: Independent Account Configuration and First Use Steps for Staff Portal

When your Telegram Bot customer service team expands from one person to multiple members, sharing a single Bot Token quickly exposes issues of security, audit, and efficiency. Who is replying to which user? Who sent a sensitive message? Are offline agents still receiving session assignments?

TG-Staff solves these pain points through independent Staff Seat accounts and the Staff Portal. This article will guide you step by step, from admin account creation to staff login, workspace configuration, and the first session handling process. Whether you are a team admin or a soon-to-be staff agent, you will find immediately actionable steps here.

Why Does TG-Staff Need Independent Staff Accounts?

Before diving into the steps, understanding the value of independent accounts will help you configure permissions better.

• Security Isolation: Each staff member logs into the web portal with their own email and password, without sharing Bot Tokens or Telegram account credentials. Even if a staff account is compromised, the admin can disable it individually without affecting other agents or the bot.
• Audit Traceability: All session records, message sends, session transfers, and content moderation triggers are tied to specific staff members. Admins can check “who said what and when” in the console, enabling quality monitoring and compliance audits.
• Fine-grained Permissions: Admins can control which projects each staff member can see sessions from, whether they have session transfer permissions, and whether they can use advanced features like auto-translation or bulk messaging. Different staff levels see different workspace scopes.
• Status Management: Staff can independently toggle online/offline status. The system only assigns new sessions to online agents based on routing rules, preventing offline agents from being disturbed unnecessarily.

Step 1: Admin Creates Agent Accounts and Assigns Project Permissions

After logging into the TG-Staff App Console, the admin first enters the Agent Management module. This is the first step in configuring team members.

Steps to Add an Agent

1. Click “Agent Management” in the left navigation bar of the console.
2. Click the “Add Agent” button in the upper right corner of the page.
3. In the pop-up form, fill in:
   • Email: The agent’s work email, used for login and password recovery.
   • Password: Set an initial password (at least 8 characters, containing letters and numbers).
   • Display Name: The name displayed in the workspace and chat history. It is recommended to use the real name or employee ID.
4. Click “Save”. The system will automatically generate an invitation link (which can also be sent via email). The agent uses this link along with the account and password to log in for the first time.

Key Points for Project Permission Configuration

After adding an agent, you need to assign the projects (i.e., Bots) they can operate on. In the “Agent Management” list, find the agent and click “Edit” to enter permission configuration.

• Project Customer Service Scope: Select “All Customer Service” to allow the agent to handle all conversations in the project; select “Designated Customer Service” to choose specific Bots from the project list. Typically, new agents are initially set to “Designated Customer Service” to limit their scope until they become familiar, then permissions can be expanded.
• Routing Rule Impact: The project-level conversation routing rules (Round Robin / Online Priority) affect how agents receive new conversations. If the project uses “Round Robin”, agents must remain online to receive conversations in order; if “Online Priority” is used, the system will prioritize pushing conversations to currently online agents.
• Feature Permissions: In the Pro version, the admin can control whether agents are allowed to use features such as conversation transfer, notes, bulk messaging, etc. It is recommended to assign permissions based on job responsibilities—regular agents only have access to reception and transfer permissions, while team leads or admins can enable more management features.

Step 2: Agent First Login to Agent Portal

After receiving the invitation link, the agent can proceed with their first login.

Login Interface and Common Issues

1. Access the browser at https://app.tg-staff.com/ (Chrome or latest Firefox recommended).
2. Enter the email and password assigned by the admin on the login page.
3. Click “Login” to enter the workspace.

Common Login Issues:

• Forgot Password: Click “Forgot Password” on the login page, enter your email, and the system will send a reset link. If not received, check spam or ask the admin to resend the invitation from the console.
• Account Disabled: If login shows account unavailable, contact the admin to check agent status. Admins can enable/disable any agent in the console.
• Browser Compatibility: Use the latest Chrome or Firefox. Safari and Edge work fine, but some older versions may not support advanced features like auto-translation.

Workspace Overview After Login

After first login, you’ll see a clean workspace interface with the following main areas:

• Left Chat List: Shows all assigned conversations (sorted by latest message). Unread conversations are highlighted.
• Top Status Bar: Displays online/offline toggle, agent name and avatar, and notification settings.
• Center Chat Area: Message stream of the selected conversation. Each message shows sender, time, and content. Telegram user messages show user avatar and nickname.
• Right User Info Panel: Shows the current user’s Telegram ID, username, tags, and profile info (Pro version). Agents can view user history here.
• Bottom Input Area: Type text, send images/files, use auto-translate button (Standard+). Pro agents can also see content moderation prompts (if risk word detection is enabled).

Step 3: Configure Personal Preferences and Work Environment

Agents can customize the workspace appearance and features to improve efficiency.

• Chat Background: Standard users can choose solid colors; Pro users can switch to TG-themed backgrounds (light/dark), matching the Telegram client visual style for a seamless experience.
• Language Interface: The agent portal supports Chinese and English. Switching languages in personal settings does not affect chat content with Telegram users.
• Message Notifications: Set notification methods (browser popup or sound alert) in the top status bar. Enable notifications to avoid missing new conversations.
• Auto-Translation: Standard+ plans support auto-translation. Agents can enable “Translate on Send” or “Translate on Receive” in settings. Send translation automatically converts agent’s Chinese input to the user’s language; receive translation converts user’s foreign messages to the agent’s reading language.

Step 4: Start Serving—Conversation Routing and Real-Time Two-Way Chat in Action

After configuration, agents can start serving real users. Here’s a typical conversation flow:

1. Receive Routed Conversations: When a user enters via a routing link or Bot welcome message, the system assigns the conversation to an online agent based on routing rules (round-robin or first available). The agent’s chat list updates in real-time.
2. Click to Start Chat: Click a conversation entry to view user messages in the chat area. Agents can reply with text, images, or files. All messages sync in real-time—sent messages appear instantly to the user, and user replies refresh immediately in the workspace.
3. Use Auto-Translation: If the user speaks a foreign language, agents can click the translate button above the input area (or enable auto-translation) to translate replies before sending. Standard uses AI translation; Pro can choose Google or DeepL professional translation. Note daily translation quotas (see pricing page).
4. Handle Multiple Conversations: If multiple users are chatting, agents can switch between conversations in the left list. Each conversation maintains its own context without interference. Pro agents can also use “Private Notes” for internal notes (visible only to themselves) to track to-dos.
5. Conversation Transfer and Collaboration: If an issue cannot be resolved, agents can transfer the conversation to another agent or admin. Select the target agent and provide a reason (for audit). The receiving agent gets notified and continues the chat.

Security and Compliance After Agent Login (Pro Edition)

If your team has enabled content moderation (internal control management), agents will need to pay attention to system prompts when sending messages.

• Risk Word Detection: When an agent’s message contains project-configured risk words (such as specific wallet addresses or sensitive terms), the system will display a warning window. The agent must confirm twice before sending, or the message may be blocked entirely (depending on admin configuration).
• Audit Logs: All messages that trigger risk words are recorded in the console’s “Content Moderation Logs.” Admins can view the triggering agent, conversation, time, and specific risk words. Agents should note that all messages are subject to audit.
• Wallet Address Monitoring: For Web3, exchange, or NFT teams, admins may configure specific TRC20/ERC20/BTC addresses or address fragments as risk words. When agents send outbound messages, the system automatically scans for these addresses to prevent accidental or unauthorized sending of payment addresses.

Agents should proactively understand their project’s internal control rules to avoid account suspension or audit triggers due to violations.

Frequently Asked Questions

Q: Can an agent account be logged into multiple devices at the same time?
A: An agent account can only maintain an active session in one browser at a time. If you try to log in from another device, the previous session will be forcibly disconnected. It is recommended that agents use a fixed device or browser for work.

Q: What if an agent forgets their password?
A: On the agent login page, click “Forgot Password,” enter the email used during registration, and the system will send a password reset link. If you don’t receive the email, check your spam folder or contact the admin to resend the invitation from the console.

Q: How can agents switch between online and offline status?
A: There is an online/offline toggle switch at the top of the agent portal. When offline, the system will not assign new conversations, but agents can continue handling existing ones. It is recommended to switch to offline before taking a break to avoid conversation backlog.

Q: Can admins view agent chat history?
A: Yes. Admins can view all agents’ chat history, conversation transfer records, and content moderation trigger logs (Pro edition) in the console’s “Conversation History.” This supports quality monitoring and compliance audits.

Q: What languages does the agent portal support?
A: Currently, the TG-Staff agent portal supports Chinese and English. Agents can switch languages in their personal settings. This does not affect the language of chats with Telegram users (which is determined by the user’s end).

---

With the steps above, you have mastered the complete process for TG-Staff agent login and usage. From admin creation of independent accounts to agent first login and workspace setup, to actual reception and compliance operations—this system provides professional team management and collaboration capabilities for Telegram Bot customer support teams.

Recommended Next Steps:

• Sign up for TG-Staff Free Trial (3 days, no credit card required) to experience the agent portal and independent account management.
• First invite 1-2 agents to test the login process and familiarize yourself with permission configuration and routing rules, then onboard your team in batches.
• For issues, refer to the Official Documentation or contact the support Bot @tgstaff_robot.