# Telegram account pools and pool load _Creators · 6 min read · Updated 2026-11-08 · https://lanachat.ai/guides/account-pools/_ A Telegram account pool is the set of a creator's accounts that share the same market and the same traffic source; a tracking link pointed at the pool spreads its new fans over the accounts that are ready, so that no account is flooded. LanaChat weighs each account by its load against a cap of 2,000 messages per hour, and a returning fan always lands on the same account. For the idea behind pools, read [what is a pool](https://lanachat.ai/blog/what-is-a-pool.html). ## How is a pool formed? - **Same creator, same market, same traffic source**, in your workspace only. Set the market and the traffic source when you edit the account in [Telegram Accounts](https://lanachat.ai/guides/telegram-accounts/) (**Edit**, **Details**). - An account missing its market or its traffic source is in no pool and serves alone. ## Send a tracking link to a pool 1. Open **Tracking links** and create or edit a link (see [Tracking links](https://lanachat.ai/guides/tracking-links/)). 2. In **Telegram destination**, choose **Telegram pool** instead of one account. The field reads *Automatic split · ready accounts: N of M*. 3. Save. Each new fan then goes to a ready account of the pool of the account the link points at. ## Which accounts get new fans? Only ready accounts. LanaChat skips an account that cannot answer: - checked at each click: removed, switched off, disconnected, AI off, Telegram reply rights missing; - checked every few minutes: no licence, creator switched off, no published AI Brain, empty agency balance. ## How is the traffic split? - LanaChat weighs each ready account by its load, measured against a cap of 2,000 messages per hour per account. - From 70 % of that cap, its weight is cut to about a third; from 80 %, it gets no new fan while another account of the pool has room. - When every account of the pool is at 80 % or more, that limit moves up to 95 %, and back to 80 % as soon as one account is under 70 %. - If every account is past its limit, new fans are spread over all of them rather than refused. - **Returning fans**: a fan who clicks the link again lands on the same account. A technical cookie on the tracking domain remembers which one (90 days, never sent to anyone else); without it, a fingerprint of the connection does the same job. ## Hold traffic on one account In **Pool load**, **Hold traffic** on an account row stops new fans for that account. Fans already sent to it keep landing there for 24 hours at most, then go to the other accounts. **Release hold** puts it back in the split. ## What if no account is ready? A click is never lost. A returning fan goes back to the same account; otherwise the fan goes to the last account this link served while it was ready, otherwise to the account the link points at. Your agency is alerted: a notification in the Console, the `pool.no_ready_account` webhook and an email to your team. > Tip: When you are alerted, open **Pool load**: the pool lists why no account is ready (for example **AI off** or **Licence required**). Fix that reason, or add a ready account with the same creator, market and traffic source. ## Read the Pool load tab Each pool (a creator, a market and a traffic source) with the figures that drive the split of pool links. - **Each pool**: its status (**OK**, **Reduced**, **Stopped**, **Held**, **Not ready**…) and its load projected to the end of the hour against its capacity. Per account: the messages sent this hour and the projected load against the cap of 2,000 per hour. Amber from 70 % (reduced share), red from 80 % (no new fan; 95 % when every account of the pool is at 80 % or more). - **Load history**: one line per account over **24h** or **7 days**, with the ceiling as a dashed red line. Filter by traffic or market and hover a point to read each account's load. - **One card per creator**: each pool with the load of each account. **Pages serving a single account** lists the tracking pages that point at an account in no pool. ## FAQ ### Does a pool mix the accounts of two creators? No. A pool only holds the accounts of one creator with the same market and the same traffic source, in your workspace. ### Does a fan who comes back switch to another account? No. A returning fan lands on the same account, remembered for 90 days by a technical cookie on the tracking domain, or by a fingerprint of the connection. ### Is a click lost when every account is full or off? No. When every account is past its limit, new fans are spread over all of them; when none is ready, the fan still reaches Telegram and your agency is alerted. ### Does a new account join the split straight away? Only once it is ready: connected, with a licence, its AI switched on and the creator's AI Brain published. A new account is born with its AI off, so it gets no pool traffic until you switch it on. More on the [Telegram accounts feature page](https://lanachat.ai/features/telegram-accounts/). ## Related - [Telegram Accounts: accounts, pool load and stories](https://lanachat.ai/guides/telegram-accounts/) - [Tracking: links, domains and analytics](https://lanachat.ai/guides/tracking-links/) - [Telegram limits, bans and how LanaChat stays inside them](https://lanachat.ai/guides/telegram-limits-and-account-safety/) - [Track a new ad campaign from click to sale](https://lanachat.ai/guides/track-a-new-ad-campaign/)