Everything you need to get from a fresh download to a running campaign. The same guidance lives inside the software, under Help — every screen explains itself there.
Three steps, about two minutes.
Get a licence code. Message @TelegraOneBot with /lisans and choose the free demo. You type your name and press Share Phone; the number is verified by Telegram itself, which is what keeps the demo to one per person. Your code arrives immediately.
Download and run. TelegraOne.zip extracts to a single .exe. There is no setup wizard. Windows may warn about an unknown publisher because the file is unsigned — choose More info → Run anyway.
Enter the code. On first launch you enter your licence code and contact details. The licence binds to this computer, and the ready-made API pool downloads on its own.
Three ways in, depending on what you already have.
Sessions → Bulk Import. Point it at your tdata folders or Telethon
.session files. Each one is verified by connecting to Telegram. Accounts
that fail are not deleted — they are kept apart as "dead" so your records stay honest.
If a folder contains twoFA.txt, the password is verified and stored
encrypted.
Sessions → Open New Session. Sign in with a phone number the usual way: code, then 2FA if the account has it. Pick a proxy before you start and the session is opened through it, so the account keeps the same exit point from its first minute.
Market → Buy Number and Create Account. A step-by-step window: provider and key, country and price, account setup, cost confirmation, live progress. The provider account and its balance are yours — TelegraOne only asks for a number on your behalf, and payment happens on the provider's own site.
Two things every account needs. Both are handled for you.
TelegraOne ships with a ready-made API pool. The app downloads it at startup and hands it out on a least-loaded basis, so no single credential carries the whole load. If you prefer your own, add it under API Settings → Add API List; the "Source" column tells yours apart from the shared ones.
Proxy Settings → Find Proxies pulls candidates from public lists and tests each one by connecting to Telegram — only proven proxies enter the pool. Service the Pool then does the upkeep: test everything, deactivate the dead, top the capacity back up. More on the proxy pool →
Free proxies are shared and short-lived, and whoever runs one can see that a connection exists and where it goes — though Telegram traffic is encrypted, so message content cannot be read. For accounts that matter, use a dedicated proxy and keep the free pool for trials and warm-up.
You define the work; the software manages speed and limits.
Collect contacts. Jobs → Contact Collection Plan. Pick a source group or channel and the rules: filter out bots, deleted accounts, people with no photo or no username. To reach people who are genuinely active, use the activity window (last hour, 6 hours, 24 hours, week, month) or "only those who posted" — the latter scans the group history instead of the member list and is the strongest signal of a live account.
Build the job.
Jobs → Message Campaign or Create Invite Plan. Write the message, choose the
target list, and set the counts: total, the limit per session and the delay between
actions. Use {hello|hi} for alternatives and {ad}
{soyad} for contact details — sending everyone the identical text gets
accounts restricted quickly.
Turn write actions on. Nothing that writes to Telegram runs until Allow write actions is enabled in Settings. This is deliberate: it makes the first write a decision you take, not an accident.
Watch it run. Live Job Monitor shows running jobs with live counters. Everything the software does lands in Records, timestamped, with a status filter and export.
Carrying group A's messages into group B, live.
Choose source (A) and target (B), then decide how the message should look in B: with the source hidden, so it reads as B's own post, or carrying a "forwarded" label. The account you use must be able to see A and to post in B. Several A → B rules can run at the same time.
Mirroring runs for as long as the application is open. If the target is in slow mode the rule waits rather than forcing messages through. For work that must continue with your computer off, mark the job to run on the server — that needs a paid licence.
The part that decides whether any of the rest was worth doing.
Account Tools → Warm-up. A new account only reads for the first days, then the accounts chat among themselves at natural intervals. An account still in the programme is kept out of campaigns automatically.
Every account gets an explainable risk score, and a high-risk account is pulled out of the engines. It looks like losing an account for a while; it prevents losing several.
FLOOD_WAIT, SLOWMODE and PEER_FLOOD responses are read properly and the account rests exactly as long as it must. Shortening delays to speed a campaign up almost always costs more time than it saves.
Accounts are spread across the least loaded proxy for a reason: many accounts behind one exit point read as a single operation. Leave the distribution alone unless you have a reason not to.
The sidebar shows your licence state and remaining days. In the bot, /durum lists your licence and any add-on quotas with their end dates.
In the bot: /fiyat for current packages, /satinal to pick one. A payment link arrives in the chat, and the moment the payment is approved your licence or quota is defined automatically.
Add a quota pack instead of changing plan: more sessions, more daily actions or more mirroring rules. Each pack runs for 30 days from the day you buy it, independently of when your licence ends.
A term package is added to your current end date, so you never lose the days you have left by renewing before they run out.
Check its proxy before you blame the account. A proxy that died quietly makes every job fail and looks exactly like an account problem. Service the Pool settles the question in one press.
Enter it in full without spaces. A code already used on another computer is refused; write to the bot to move the device.
Almost always the write-actions switch in Settings. The invite, message, reaction, join/leave and profile engines all wait on it.
Write to @TelegraOneBot — it reaches us directly. The announcement group carries release news and known issues.
A longer guide, with a screen-by-screen walkthrough and the full release history, is available in Turkish at telegraone.com/yardim. The same content is built into the software under Help, and follows the language you choose there.