Questions before you get started.

Create named, colored lists such as Clients, Follow up, or Family. Assign a conversation to more than one list through Chat details or the right-click menu, see colored label badges in the inbox, and filter by list, color, or No label. You can rename, recolor, or delete lists; deleting a list never deletes contacts or messages.

No. Lists are saved locally in TGBotSender. A list definition can be used across accounts on this device, but each account’s conversation membership is separate. Lists are not Telegram folders and are not included in Contact Sync or Team Chats list export/import. Your app’s database backup includes them.

You can connect multiple Telegram user accounts that you own or are authorized to use. Sign-in uses Telegram’s supported phone, code, two-step password, email, registration, or QR states. Telegram API credentials are provided by the account owner.

Mark private-chat contacts as team members to keep their conversations in a separate Team Chats view. The same person can appear separately under multiple Telegram accounts, with the sending account clearly identified. Team contacts are hidden by default in All Accounts and Account Chats; enable Show team chats to reveal them. This is local organization, not a shared assignment or permissions system.

Yes. Use Export team list in Team Chats to save a JSON file, sign in to the same Telegram accounts on the other device, then use Import team list and review the account matches before confirming. Import adds membership without removing existing members and reports skipped or failed contacts. The file contains Telegram identities and display names, not login credentials, internal notes, drafts, or message history. Later membership changes are not synchronized automatically.

Operational data is stored locally in a bundled SQLite database on your computer. Sensitive Telegram, bot, and AI credentials are kept in the operating-system credential vault rather than plain SQLite or browser storage.

Only if you want AI features. TGBotSender supports user-configured providers such as OpenAI, Gemini, Anthropic, and OpenRouter. API usage and charges are between you and that provider.

The default architecture does not route Telegram conversations, AI prompts, AI outputs, or provider API keys through an Odeysoft AI or messaging server. Licensing and update checks use the TGBotSender service.

No. It is a desktop workspace that can connect Telegram user accounts and separately manage Telegram bots created through Telegram’s official bot workflow.

No. Bot long polling, local schedules, AI auto reply, and rule-based automation require the computer to be on, connected to the internet, and TGBotSender to be running.

Describe the bot workflow you need and the builder prepares a reviewable blueprint using only supported TGBotSender commands, rules, buttons, callback actions, and flows. Generated behavior remains disabled until you review and apply it; the builder does not execute arbitrary code.

Yes. Choose visible members from a source group or select All Contacts for the connected account, choose a supported target group on that same account, and run the required eligibility preflight. Telegram permissions, privacy settings, Premium requirements, and rate limits determine each result.

Yes. Campaign schedules run locally. If the app was not running at the scheduled time, the missed-schedule recovery setting determines what happens when TGBotSender next opens.

Campaign workers use configured delays and respect Telegram FLOOD_WAIT responses. Telegram rules and account restrictions always apply, and no software can guarantee that an account will not be limited.

Yes. Message and media templates support standard variables and campaign/contact variables. Saved audiences can be created from contacts, tags, countries, usernames, phone data, consent rules, and manual contact selection.

You can prepare formatted text, photos, videos, audio, voice notes, documents, media albums, polls, quizzes, contact cards, and locations. Available options change with the selected sender and Telegram context. Supported bot messages can also attach inline keyboards or reply keyboards built visually without Bot API JSON.

Choose Reply keyboard in the bot keyboard builder, add and reorder rows and keys, then configure resize, one-time, persistent, selective, and input-placeholder behavior. Tapping a key sends its label as a user message, so commands and auto-reply rules can respond to it. You can also send a Remove keyboard action.

Save a hosted Mini App URL, assign a connected bot, and choose its launch-button label locally. Configure launch button shows the current and replacement menus for your confirmation before changing the bot’s default private-chat menu. Check Telegram button reads its current setting; Restore Commands brings back the commands menu. Saving, editing, reassigning, or deleting a local record does not change Telegram. BotFather still manages the profile’s Main Mini App and short name, and existing per-chat menu overrides are left unchanged.

No. The manager is local, but the Mini App itself must already be hosted at a public HTTPS URL. You remain responsible for the website, any backend, and secure handling of Telegram user data. Use a connected Telegram bot, not an ordinary user-account sender; Telegram Business is not required for this bot menu setup. The configured menu remains on Telegram when TGBotSender closes, while local bot reply workers still need the app running.

Request one-time payments for digital goods and services from an existing private-chat subscriber of your connected bot. Configure terms and support first, review the customer and price, then send the request. The customer accepts your terms before receiving the invoice. This release supports whole prices of 1–10,000 Stars per invoice, not cash prices, physical-goods orders, recurring subscriptions, or public multi-buyer checkout links. Stars Payments is for your bot’s customers; the website checkout for buying TGBotSender remains separate.

No separate hosted payment server or Telegram Business account is required for this local bot workflow. Keep your computer awake, online, TGBotSender running, and the bot enabled during checkout. Telegram requires a checkout response within 10 seconds, so payments can fail when the app is closed, the computer sleeps, or connectivity is unavailable. Do not use another polling app or webhook for the same bot.

No. Wait for a Telegram-confirmed payment, deliver the item through your normal process, then use Mark delivered to record fulfillment. It does not send a file or grant access. You can review and issue full refunds in Stars to the original payer, check the bot balance, and reconcile Telegram transaction history. Earned-reward withdrawals remain with the bot owner’s official Telegram/Fragment workflow and any external cash-out service; TGBotSender does not collect wallet keys or make bank payouts.

TGBotSender is packaged as a Windows .exe installer and a macOS .dmg. The Windows installer includes the required WebView runtime installer mode, so customers do not need development tools.

One license activates one computer at a time unless an offer says otherwise. You can self-deactivate a device before moving the license.

Yes. Enter your name and a @gmail.com address on the trial page, verify the email code, then submit your request. Each email can request a trial for this product once. Eligible first-time requests receive a trial key on the page and by email; additional requests from an IP that has already received a trial require admin approval.

Use the User Guide for setup and feature instructions, or contact support through the Contact page. The app Settings page also includes support, guide, and feedback links.

No. Monthly, Yearly, and Lifetime include the same features. Only the license duration differs. One license activates one computer at a time unless the checkout offer explicitly states otherwise.

A local-first Windows and macOS desktop workspace for Telegram accounts, contacts, groups, chats, campaigns, templates, automation, AI assistance, Telegram bots, and reports.

No. The packaged desktop installer includes the application components customers need. Development tools such as Node.js, Rust, pnpm, and SQLite are not customer prerequisites.

No. Campaign schedules, bots, rule auto replies, and AI auto reply run locally and require the computer, TGBotSender, internet access, and the relevant account connection.

Telegram API hashes, bot tokens, and AI keys use Windows Credential Manager or macOS Keychain. They are not stored as plain text in SQLite or browser storage.

Yes. Each Telegram user account has an isolated session, and each bot connection is managed independently.

The provider manager supports OpenAI, Google Gemini, Anthropic Claude, and OpenRouter, with an architecture that can add providers later. Users supply and pay for their own provider account.

Yes, when a compatible app is installed and detected. Open Settings → Integration, enable the app pair, and choose Manual or Live Contact Sync. This local desktop-to-desktop feature is separate from Telegram contact synchronization.

Yes. Import individual Markdown files or a folder with a top-level agent.md, plus supported knowledge documents. Relevant text may be sent to your configured AI provider, and the agent can propose a relevant managed file for sending. Use approval mode while testing.

One license activates one computer at a time unless the checkout offer explicitly states otherwise. Deactivate the old computer before moving the key.

Search this User Guide, use Settings → Help, or visit the website Contact page. Never send credentials or login codes to support.