Pacing is not stalling

Almost everyone new asks the same thing: can the interval be shorter. It can, the setting is right there. The question is what happens after it is.

Pacing comes down to three things: the random wait between contacts, the random wait between steps inside one sequence, and how many people each account will reach in this run. Push all three to the limit and you will get through more in a night. The cost is that the account becomes very easy to recognise, and once an account is gone, bringing a new one up takes far longer than the hours you saved.

A random range beats a fixed value, which is the part people skip over. One message exactly every fifteen seconds is a machine. Somewhere between fifteen and fifty is a person answering messages on and off. The client also adds randomised delays, simulated typing and scrolling, all of which apply with the task and need no configuration.

The per-account ceiling is the other half. It is not there to limit you; it is there so one account is not worked too hard in a single run. If you have several accounts, spreading the volume across them is steadier than making one carry the whole batch.

One more thing: the skip rules run before anything is sent, and anyone skipped does not count against the ceiling. A well-kept list therefore hands your quota back to the people who should actually receive the message.