This guide is for support agents, operators, and team leads using TgSpark for the first time. By the end, you should be able to enter the correct workspace, find a Telegram account you are allowed to use, and complete a message-handling task.
Understand the main objects
| Name | Meaning | Example |
|---|---|---|
| Member account | Your personal identity for signing in to TgSpark | An agent's sign-in email |
| Workspace | The scope of team collaboration and business data | A customer support team |
| Workspace role | Determines which team matters you can manage | Owner, administrator, member |
| Telegram account | The actual identity that sends and receives messages | The team's Telegram support account |
| Conversation | A private chat, group, or channel under a Telegram account | A support account's chat with a customer |
| Message template | Text and attachments inserted into manual replies | A welcome message or information pack |
| Ticket | A record for following an internal issue over time | Following up on a customer refund |
| Worker | The background process that connects to Telegram | Maintained by operations; ordinary members do not operate it |
Member accounts and Telegram accounts have separate sign-in flows. A member can join multiple workspaces but still needs access to specific Telegram accounts after joining. The same Telegram account can be linked to multiple workspaces; its actual messages and read status still belong to that one Telegram account.
Before you begin
Ask your team lead for:
- The site address and your member sign-in method. If joining a team, obtain your invitation link.
- The name of the workspace you should enter.
- The Telegram account you should use and whether you need View, Send, or Broadcast permission.
- A test chat you control for learning the workflow. Sending creates real Telegram messages.
If you are responsible for connecting a Telegram account, you also need access to its mobile Telegram app. Phone-number sign-in requires receiving a Telegram verification code, plus the corresponding password if two-step verification is enabled.
Step 1: Sign in to your member account
- Open the site provided by your team.
- Sign in using email and password or an email verification code, according to the available options.
- If registration is available, new users should verify their email, enter a display name, and set a password. Registration and new passwords require 12–128 characters.
- If you forgot your password, use the available recovery entry. If it is unavailable, contact your site administrator.
A missing registration entry usually reflects site configuration. Do not try the old HotGo administration demo accounts on the member site. Email verification codes and Telegram sign-in codes come from different services and belong on their respective pages.
Success looks like: the workspace selection page opens, or you return automatically to a workspace you still have permission to access.
Step 2: Create or join a workspace
For an existing team, open your invitation link, sign in to the invited account, verify the workspace and role, and accept. If the identity does not match, ask the inviter to check your email or user identifier.
To create your own team, enter a name and default time zone on the workspace selection page, then select Create and enter. The creator becomes the owner. The time zone affects scheduled-task displays, auto-reply schedules, and analytics dates, so use the team's actual time zone.
Once inside, use the workspace switcher in the sidebar to enter another workspace. Check the current workspace name after every switch.
Success looks like: you see the main Messages, Broadcasts, Tickets, Analytics, and Settings navigation. Individual action buttons still depend on permissions.
Step 3: Prepare a usable Telegram account
If the team has already connected accounts, open Messages and check whether they are visible. If View permission is missing, ask an administrator to grant it under Settings → Telegram accounts → Member grants.
If a new account is needed, a person with connection permission should:
- Open Settings → Telegram accounts and start the connection flow.
- Choose QR-code sign-in and confirm through Settings → Devices → Scan QR code in the mobile Telegram app, or choose phone-number sign-in.
- Enter the Telegram verification code and any required two-step verification password. Keep the connection dialog open during sign-in.
- Wait for a success confirmation, then check account runtime status.
- Grant ordinary members View, Send, Broadcast, or Manage grants permissions separately.
Success looks like: the account is connected and ready, and conversations appear in Messages. If connection succeeds but the account is not ready, ask an administrator to check the Worker. Repeated QR scans usually do not fix an offline node.
Step 4: Find a conversation and reply
- Open Messages. The default All accounts view can be narrowed to one account.
- Search by conversation name or ID. Check normal/archived views and type filters if needed.
- Open a test conversation you control. Verify the actual Telegram account in the chat header and sending area.
- Enter a short message and select Send, or press Ctrl / Command + Enter.
- Wait for confirmed success. If the result awaits confirmation, check the original task rather than repeatedly resending.
Success looks like: the system confirms a successful send and the test recipient receives the message. A queued status alone is not successful delivery.
Opening a conversation and viewing the latest messages in the foreground can mark it read. To view without changing read status, use Silent preview in the conversation context menu. Read status also affects other users of the same Telegram account.
Step 5: Learn the common modules
| Task | Entry point | Read more |
|---|---|---|
| Invite colleagues and adjust team permissions | Settings → Workspace and members | Accounts and workspaces |
| Connect a support account and grant member access | Settings → Telegram accounts | Telegram accounts |
| Reply, search, quote, and send attachments | Messages | Messages |
| Save a welcome message or insert information attachments | Settings → Message templates | Message templates and storage |
| Configure keyword and group-mention replies | Settings → Auto-reply | Auto-replies |
| Send notices to explicitly selected recipients | Broadcasts | Broadcasts |
| Follow a customer issue over time | Tickets or the conversation context menu | Tickets |
| Review pending replies, response efficiency, and trends | Analytics | Workspace analytics |
| Hide particular chats and restore your own exclusions | Settings → Data and privacy | Data and privacy |
Start and finish each workday
First check your workspace and Telegram account, then review connection status, conversations awaiting replies, and My unfinished tickets. Before leaving, handle failed or uncertain sends, save content you need to retain, and update ticket statuses.
Chat drafts and pending attachments are not permanent storage. Resolve unsent content before refreshing or closing the page. Update-protection prompts do not replace saving proactively.
First-time troubleshooting
| Problem | First action |
|---|---|
| No workspace is available after sign-in | Create one or ask the inviter to confirm membership |
| You can enter a workspace but cannot see accounts | Confirm the workspace, then ask an administrator to check View grants |
| You can read messages but cannot send | Check Send permission, runtime status, and chat exclusions |
| Accounts exist but conversations are missing | Clear filters, check archives and sync progress, then confirm the account is ready |
| A send remains pending confirmation | Check the original task and Telegram; do not simply resend |
| A feature is missing from the page | Check its documented availability, then ask an administrator to confirm deployment version and migrations |
See module help for more operations and troubleshooting.

