Telegram promotion software for agencies: several clients in one panel

An agency runs many projects at once: every client has its own accounts, proxies, topic and schedule. In TeleTraff projects are split into pools, tasks go on a schedule, and you pay for threads per module, not per client.

  • A pool per client
  • Pay for threads, not clients
  • Tasks run with the browser closed
Account pools in TeleTraff: each project with its own accounts, proxies and ready and problem counters

In short

A Telegram promotion agency needs a way to keep client projects apart without paying for each client separately. In TeleTraff each client gets a pool with its own accounts and proxies, client tasks run on a schedule in Automation, and the plan counts threads in each module. The modules are the same for every client: neurocommenting, mailing, inviter, neurochat, parsers and the rest.

TeleTraff editorial teamUpdated: Checked in the panel

Clients never mix

Each pool has its own accounts and its own proxies. One proxy cannot sit in two pools, and in the account picker a click on a pool selects its free accounts.

Threads, not seats

The plan counts how many accounts work in a module at once. A fifth client costs nothing while you have threads to spare.

It runs without you

Schedules in Automation start tasks on the server. You can close the browser; the run history is kept.

What an agency needs for Telegram promotion

An agency runs projects from different niches at once: crypto, betting, info products, services. Each needs its own accounts, its own proxies and its own schedule. If everything sits in one heap, one day client A's account ends up in client B's task.

So an agency needs three things from the panel: keep projects apart, run work on a schedule and show the client what was done. The modules are the same for everyone; they are listed on the panel features page.

How to organise agency work in TeleTraff

  1. 01

    Create a pool per client

    Name the pool after the client and the topic, for example «Client A · crypto». The pool shows how many accounts there are in total, ready, working, warming up and in trouble. Details in the account pools guide.

  2. 02

    Bind proxies to the pool

    The pool menu has Assign proxy: the selected proxies are handed out to the pool's accounts in turn. One proxy cannot be in two pools at once.

  3. 03

    Tag accounts and give them a role

    Tags help you search and filter. The role says what the account is reserved for: a module offers only accounts with its role, and Reserve is never taken anywhere.

  4. 04

    Run modules per client

    In the account picker, open the Pools tab and choose the client's pool: its free accounts get selected. Take the client's placements from the open base or collect them with a parser.

  5. 05

    Put tasks on a schedule

    In Automation each schedule has its own steps and its own launch order. Upcoming runs are shown on the right.

  6. 06

    Put together the client's result

    What a run did is shown in the module itself, and the run log downloads with the Download log button. The overall picture is on the Runs tab in statistics.

Which panel features matter to an agency

Agency taskWhere in the panelHow it helps
Keep clients apartAccount poolsOwn accounts and proxies per client, ready and problem counters
Never mix up accountsTags and account roleA module offers only accounts with its role and leaves Reserve alone
Keep proxies in orderProxy centerChecks through Telegram, Quarantine, the pool or No pool for each proxy
Top up accountsMarketplaceBuy accounts and proxies inside the panel, import straight with a proxy
Run on a scheduleAutomationA schedule built from steps, a time zone, Run history
ReportModules, statisticsRun results, Download log, the Runs and Traffic tabs

Example: three pools in one panel

The pool names here are examples; you set your own.

A betting client

The «Betting · Brazil» pool: its own accounts and proxies for the right geo. Neurocommenting writes under posts in sports channels, and once a week the schedule runs mailing to a collected list.

A crypto client

The «Crypto · chat» pool: accounts talk in chats through neurochat, and the inviter brings people from a list into the client's chat. The proxies are its own and never overlap with betting.

Reserve

No module takes accounts with the Reserve role. When a client loses an account, the replacement comes from here and moves into that client's pool.

What pools and automation look like

Account pools: counters of ready and problem accounts, pools per niche with Accounts and Proxies buttons.
Account pools: counters of ready and problem accounts, pools per niche with Accounts and Proxies buttons. Demo data.
Proxy center: tiles for working, slow and dead proxies, the Assign proxies button and a table with protocol and country.
Proxy center: tiles for working, slow and dead proxies, the Assign proxies button and a table with protocol and country. Demo data.
Several accounts selected, with the bulk action bar at the bottom.
Several accounts selected, with the bulk action bar at the bottom. Demo data.
Automation: warm-up and mailing to a base in one schedule, with When and Upcoming runs on the right.
Automation: warm-up and mailing to a base in one schedule, with When and Upcoming runs on the right. Demo data.

How threads add up when there are many clients

A thread is one account busy with a task in a module right now. Threads are counted in each module separately and are shared by every client in the panel.

Example: three clients, each running neurocommenting on 15 accounts at once. That takes 45 threads in neurocommenting, which fits Pro with its 50 threads. Mailing for the same clients is counted separately and never touches the neurocommenting threads.

For 30 days: Starter with 10 threads costs $24, Pro with 50 threads $59, Ultimate with 100 threads $117. A paid plan does not limit how many accounts sit in the panel. Details on the pricing page.

What an agency should keep in mind

  • There are no separate client cabinets or staff seats in the panel: there is one workspace and one login to it.
  • A pool does not bind a run to itself: the module gets the list of accounts chosen at launch. New accounts in the pool do not join a task already running.
  • The panel does not build a ready client report. The result comes from run results, the run log and the account CSV export.
  • The Traffic tab in statistics counts people only through a connected funnel.

Terms on this page

Questions and answers

Can I run several clients in one panel?

Yes. Create a pool per client; each pool has its own accounts and proxies. In the account picker, a click on a pool selects its free accounts.

Do I pay for each client?

No. The plan counts threads, that is, accounts busy in a module at the same time. A paid plan does not limit how many clients and accounts sit in the panel.

Can I give access to staff or a client?

There are no separate staff seats or client cabinets: there is one workspace and one login to it. If you need a different setup, write to support.

How do I keep different clients' accounts apart?

Keep them in separate pools and give them a role. A module offers only accounts with its role, and no module takes accounts with the Reserve role.

Do tasks run with the browser closed?

Yes. The server runs the tasks. A schedule in Automation starts them by itself, and the outcome of every run is in Run history.

How do I show a client the result?

Every module has run results, and the run log downloads as a file. With a funnel connected, the Traffic tab in statistics shows how many people came.

Open base sections

Ready lists of channels and chats by topic: how many a section holds, how active they are and the top 20 by subscribers.

All base sections

Read next

More in this section

Other sections

Try the panel on a client project

3 days, no card: every module, 3 threads in each, up to 10 accounts. The clock starts with the first account you add.

Try it free