Included with everything
Profile Templates
What a template holds, what applying one actually does to an account, and the cooldowns that pace a rollout across a pool.
In this guide
01What this module is
The profile is what someone sees after clicking the name on a comment. An account with no picture, no bio and a default name reads as exactly what it is. A template is that profile built once and applied across a batch: name, surname, bio and avatar, stored as one reusable object.
It is included with any purchase, and it is the smallest of the modules — one page holding a grid of templates, plus the Apply template action over on the Accounts page. Everything expensive about it happens on the engine side, in the pacing.
A template applies identically to every account it touches. The same first name, the same surname, the same bio, the same picture. There is no per-account variation built into this — if you want a batch that does not look like one batch, that is several templates applied to several groups, not one template with randomness in it.
02Map of the page
Two places, not one. The templates themselves live on their own page; applying them happens where the accounts are.
- 01Templates page — toolbarA single New template button, top right.
- 02Templates page — gridOne card per template, three across on a wide screen. Clicking a card opens it for editing; each card also carries its own delete button. With no templates yet, an empty state stands in with the same create button.
- 03Create / Edit dialogTemplate name, Name, Surname, Description, Avatar. The same dialog for both, with the title and wording changing.
- 04Accounts page — Apply templateIn the bulk actions bar. Pick a template, apply it to the current selection, watch a progress step report per-account results.
03Building a template
IllustrationNot the live panel — nothing here is connected: no state, no saving, no requests. Click a control to read what it does.
Template nameCreate / Edit dialog
- What it does
- Names the template inside ATREOX. It is a label for you — never applied to any account.
- Required
- Yes. It is the only required field; the Save button stays disabled while it is empty.
NameCreate / Edit dialog
- What it does
- The Telegram first name written onto every account this template is applied to.
- Applied how
- Identically. Every account in the batch ends up with this exact first name.
- Also used by
- The {first_name} token in the Description below, which substitutes this value.
SurnameCreate / Edit dialog
- What it does
- The Telegram last name, applied identically to every account in the batch.
- Optional
- Yes — leave it blank and accounts get a first name only, which is ordinary on Telegram.
DescriptionCreate / Edit dialog
- What it does
- The account bio. This is the one field with room for a call to action, since it is what a reader sees after clicking through from a comment.
- The token
- {first_name} is replaced with the template’s own Name field. It does not vary per account — it is a convenience for writing the bio once, not a source of variation.
- Two limits
- The dialog counts twice: the raw text against 200 characters, and the text after substitution against 70. Both must pass or Save stays disabled.
- Why 70
- That is the length that actually reaches Telegram after the token is filled in. A long token and a short-looking template can still overflow it, which is why the second counter exists.
AvatarCreate / Edit dialog
- What it does
- One image, shared by every account the template is applied to.
- Formats
- PNG or JPEG.
- Size
- Up to 5 MB.
- Optional
- Yes. Leave it out and the template applies names and bio only, touching no picture.
- On edit
- Choosing a new file replaces the current avatar for the template; accounts pick it up the next time it is applied.
04Applying one to a batch
Applying happens on the Accounts page, not here. Select the accounts, press Apply template in the bulk actions bar, choose which template, and the rollout starts as a background task with a progress readout.
IllustrationNot the live panel — nothing here is connected: no state, no saving, no requests. Click a control to read what it does.
Apply templateAccounts page → bulk actions bar
- What it does
- Writes the template’s name, surname, bio and avatar onto every selected account, one at a time.
- Progress
- The dialog switches to a progress step with a per-account result. Closing it does not stop the run — a corner widget keeps the task and takes you back to it.
- No templates yet
- The picker is replaced by a note pointing at the Profile Templates page.
- What it does not touch
- Usernames. A template has no username field; that is a per-account edit on the Accounts page, and it has its own much slower cooldown.
Three things can make an individual account come back unchanged, and all three are reported per account rather than failing the batch:
| Reason | What it means | What to do |
|---|---|---|
| Resting | The account is inside the 72-hour lockout that Auto-Warmup applies on the Accounts page. Template application is blocked for the whole window, and the message says how many hours are left. | Wait it out, or apply to the rest of the batch and come back. |
| Rate limited | This account had a profile change less than an hour ago. The message says roughly how many minutes remain. | Retry after the hour. This is per account, not pool-wide. |
| Floodwait | Telegram asked the engine to slow down. Three of these in a row pauses the run for 30 minutes. | Nothing — it resumes on its own. |
Note the asymmetry in the resting rule: the 72-hour lockout blocks the bulk template path only. Editing one account's profile by hand on the Accounts page is deliberately still allowed during rest.
05How a rollout is paced
Nothing here is configurable — the pacing is fixed in the engine, and it is the reason a template applied across a hundred accounts is not a hundred simultaneous profile writes.
| Rule | Value | Scope |
|---|---|---|
| Profile change cooldown | One change per hour | Per account |
| Username change cooldown | One change per 48 hours | Per account |
| Gap between accounts in a rollout | 30 to 90 seconds, randomised | Per run |
| Floodwait tolerance | 3 in a row pauses the run for 30 minutes | Per run |
| Connections | One account connected at a time, then disconnected | Whole module |
The username cooldown is deliberately slower than the others. A username is the most visible and searchable thing on a profile, so it is worth changing far less often than a bio — and it is counted per account, so rolling a change across a pool scales with the pool rather than queueing behind one shared timer.
06First run
Create one template. Name it for the audience it is meant to read as, not for the batch it will go on — you will reuse it.
Fill in Name and, if you want one, Surname. Both go on every account identically.
Write the bio and watch the second counter, the interpolated one, not the first. That is the number Telegram sees.
Add an avatar if you have one. It is optional, and a template with no picture still applies names and bio.
Go to the Accounts page, select a batch that is past its 72-hour rest, and use Apply template.
If you are running more than one niche, build more than one template. One template across the whole pool gives every account the same face, which is fine for a small batch and obvious on a large one.
Templates are also used by Active Warmup. Its Gradual profile updates action re-applies an account’s assigned template on a schedule, through this same pipeline and these same cooldowns — which is why that action stays switched off until a template exists to apply.