Operator handbook
Practical answers for people who run volume on TGRU - catalog, checkout, drip, crypto, tickets, and the reseller API.
Telegram services only: members and subscribers, views, reactions, story views, poll votes, comments, Premium, Stars, bot starts, referrals, and SEO-oriented lines. Every card shows rate, limits, and guarantee notes.
Match budget to retention. Aged/Premium lines cost more and hold better. Mixed is the everyday default. Cheap lines move fast but may thin out - price reflects that.
Yes, some. Non-drop products refill inside the window listed on the card. No window printed means no refill promise.
Only on products that say Lifetime Guarantee in the title or description. Everything else is bound to the printed refill policy.
Most delivery needs a public username or invite that our systems can reach. Private-only targets usually fail - check the service notes.
When a service name includes a country or language, that filter applies. Generic lines do not force a region.
Create an account → Add funds → open New order → pick a service → paste the public link → set quantity → confirm. Watch status under Orders.
Spreading delivery across timed runs so growth looks organic. Configure run size, number of runs, and minutes between them. Cancel anytime to reclaim unfired runs on balance.
No. Cancel if still pending, or request review cancel once in progress so refunds match remaining quantity.
One line per job: service_id | link | quantity on the Mass tab of New order.
On covered orders, use Refill from the order row inside the guarantee period. Only our delivered count is restored.
We delivered some but not all units. Undelivered cost returns to balance automatically.
Common causes: target went private, post deleted, username changed, or provider-side capacity. Ticket us with the order ID if the listed window has passed.
No - finish one, then start the next. Parallel jobs scramble refill baselines.
Add funds lists live methods. After network confirmation (crypto) or processor approval (cards where enabled), balance updates for immediate ordering.
Typically USDT on major networks, BTC, ETH, TON, and whatever else is enabled on the deposit screen that day.
Prefer TRC-20 for fees when available. Double-check network and send the exact invoice amount.
Balance is for panel spend. Refunds and partials also land on balance, not back to your exchange wallet.
Talk to support first. Unilateral disputes can lock the account under the terms.
Underpayments may sit until reconciled. Do not trim the transfer to cover gas - pay fees from spare funds.
Turn on 2FA in Account. Use a unique password. Never share OTP codes.
Sign-in → Forgot password → follow the email link. Only the registered address receives it.
TGRU staff will never ask for Telegram login codes, seed phrases, or card PINs. Public order links only.
One business or person per account unless wholesale terms say otherwise. Ban evasion via alts is prohibited.
Open a ticket with your email, last deposit hash if relevant, and recent order IDs for manual review.
API docs after login. Rotate if leaked - rotation invalidates the previous secret.
Yes, Perfectpanel-style actions: services, add, status, multi-status, refill, balance.
Stay polite. Burst scraping or shared keys risk revocation. Prefer multi-status and mass flows.
Yes - resell under your brand. You own support for your buyers and must pass through compliance with these terms.
Volume pricing is arranged per account when available; otherwise public rates apply.
From Tickets. Keep one thread per issue and include order IDs.
Staffed continuously. First reply is usually within a few hours. Do not open “speed” tickets in the first minutes of a normal start window.
Order ID, service name, target URL, screenshot of the live counter if drop is claimed, and UTC time of the issue.
On the Terms of service page - required reading before large deposits.
File a ticket anyway. Edge cases are normal; we would rather diagnose once than watch bad orders repeat.
No questions matched. Adjust the keyword or open a ticket.