Choose a module based on the task you want to complete. Each article covers entry points, steps, permissions, and common questions. New users should read the getting started guide first.
Module directory
| Module | Purpose | Where to find it |
|---|---|---|
| Accounts and workspaces | Sign-in, profiles, team invitations, roles, and switching workspaces | Personal account; Settings → Workspace and members |
| Telegram accounts | Connection, runtime status, member grants, and disconnection | Settings → Telegram accounts |
| Messages | Unified inbox, replies, media, search, group actions, and marking chats read in bulk | Messages |
| Message templates and storage | Quick replies, variables, attachments, and capacity | Settings → Message templates; Billing and storage |
| Auto-replies | Keywords, schedules, group mentions, and manual-takeover pauses | Settings → Auto-reply |
| Broadcasts | Recipient selection, preflight checks, test sends, schedules, and results | Broadcasts |
| Tickets | Issue tracking, assignees, comments, attachments, custom fields, and SLA | Tickets; conversation or message context menu |
| Workspace analytics | Current backlog, response efficiency, message volume, and account performance | Analytics |
| Data and privacy | Chat exclusions, restoration, visibility, and read-status effects | Settings → Data and privacy |
Understand permissions
An operation requires workspace membership, module permissions, Telegram account grants, and Telegram's own permissions at the same time. Seeing a ticket does not grant access to its linked chat. Permission to send manual messages does not imply Broadcast permission.
Owners and administrators generally inherit workspace account capabilities. Ordinary members need grants for specific accounts. Message actions remain subject to account connectivity, chat exclusions, and Telegram restrictions. Tickets also have their own granular permissions.
Current feature boundaries
| Feature | Current scope |
|---|---|
| Sensitive words | Listed in Settings but currently unavailable |
| Billing and storage | Storage quotas and file details are available; automatic billing and charging are not included |
| Manual reception | Independent acceptance, transfer, and cross-workspace reception lease plans are on hold. Auto-reply pauses and ticket assignments are not this feature |
| Broadcasts | Implemented, with acceptance checks outstanding for real sending, multiple processes, and failure cases. Validate the deployment before enabling |
| Tickets | Three implementation batches are complete. The target environment must run the relevant migrations; code delivery does not mean the site has been upgraded |
| Worker high availability | Independent multiple nodes are supported; automatic failover and rebalancing are not currently available |
Report an issue to your administrator
Provide the time and time zone, workspace, module, steps, exact page error, and any visible task or ticket identifier. For message issues, also include the actual Telegram account used, send status, and whether you checked the result in Telegram.
Do not paste passwords, sign-in codes, tokens, session files, or complete configuration files into a report. Mask unrelated customer information in screenshots and logs.
Back to documentation home