Weeks 2–4 · Warming up accounts
After 5 days you have mastered the system. In this stage the system runs itself; your job is to watch the right things at the right time — and leave alone what is working. Results do not arrive in 5 days; they arrive here, after 2–4 weeks.
The question for this stage: Are my accounts “alive”, and what do I need to do each day?
Ten minutes every morning. The rest is patience.
10 minutes each morning → Read the signs → Do the week’s job → Don’t sabotage yourself → Message support at the right time
Every morning — 10 minutes
Section titled “Every morning — 10 minutes”Same order, every day. Tick each item.
- Open Control Center — are all 20 phones online? For any that are off: re-plug power, wait 2 minutes, Scan again (see Day 1).
- Open Schedules — did last night’s scenarios run to completion? Any schedule showing an error or stopping halfway (see Day 3)?
- Skim each phone — is any phone logged out, asking for verification, or showing an unusual warning?
- Write one line in your log — date · phones online · accounts with odd signs · what you did. One line, but every single day.
- Anything odd → check the Signs table below. Not sure? Message support with the template and add “week … of warm-up”.
Signs an account is alive or in trouble
Section titled “Signs an account is alive or in trouble”| Alive — leave it alone | Watch out — act now |
|---|---|
| Stays logged in day after day | Logged out unexpectedly although nobody touched it |
| Scenarios run to completion every night | Scenarios stop halfway two nights in a row |
| No verification prompts | Repeated verification prompts within a few days |
| Engagement and views grow slowly but steadily | Numbers completely flat after 2 weeks, or a sharp drop |
| One proxy per phone, no duplicates | Several accounts in trouble at the same time |
What to do each week
Section titled “What to do each week”| Week | What you do | Done when |
|---|---|---|
| Week 1 (right after Day 5) | Run only the 5 trial accounts. Observe, log, add nothing, change nothing. | 5 accounts through 7 days without incident |
| Week 2 | 5 are stable → buy the rest and scale to 20 phones, one proxy per phone. Repeat Day 2 for each new phone. | 20 phones online, scenarios run to completion |
| Week 3 | Keep the configuration unchanged. If you have not picked a platform and niche yet, do it on Day 4–5. | Numbers start to move steadily |
| Week 4 | Review the log: which accounts are solid, which are weak. Decide what to keep, replace, or expand. | You can read your own log and know the next step |
Don’t do these
Section titled “Don’t do these”- Keep changing settings while numbers are flat — accounts need stability; change daily and you cannot tell what caused what.
- Share proxies to save money — the fastest way to lose a whole batch of accounts.
- Tap around manually on a phone that is running a scenario — mixed human/machine behaviour gets flagged.
- Scale to 20 immediately when the 5 trial accounts have not passed 7 days.
- Install apps from links in the old manual — use only the official APK folder from Day 2.
When to message support
Section titled “When to message support”Message right away — do not “wait a few more days” — in any of these situations:
- Two or more accounts in trouble on the same day
- Scenarios stopped two nights in a row although you checked the schedules
- A phone stays offline after re-plugging power and scanning
- Repeated verification prompts with no clear cause
Use the ready-made template and add one line:
- Warm-up stage: week ... · trouble started on ... (from the log)Done when
Section titled “Done when”Three common mistakes
Section titled “Three common mistakes”| ✕ | Mistake | Consequence |
|---|---|---|
| 1 | Tweaking scenarios every day out of impatience | Unstable accounts, and no way to tell which change caused the problem |
| 2 | Scaling to 20 after the 5 trial accounts were calm for only 2 days | Not enough data — risk of losing the whole batch on days 3–7 |
| 3 | Keeping no log | Cannot answer support’s “since when?”, so the wrong thing gets fixed |