Anti-Ban Best Practices

TelePilot Pro includes advanced anti-ban technology, but following these practices maximizes account safety.

Golden Rules

  • Always warm up new accounts — 5-7 days minimum
  • Use multiple API keys — Group accounts by API key (5-10 per key)
  • Set realistic delays — 30-90 seconds between actions
  • Use spintax everywhere — Never send identical messages
  • Respect daily limits — 30-50 messages per account per day

    • Account Rotation Explained

    TelePilot Pro uses API-aware interleaved rotation:

    API Key 1: Account A → Account B → Account C
API Key 2: Account D → Account E → Account F
Alternating: A, D, B, E, C, F (interleaved across API keys)

    This prevents any single API key from appearing too active.

    What Triggers Bans

    | Action | Risk Level | Prevention |

    |---|---|---|

    | Same message to many users | 🔴 High | Use spintax |

    | Rapid-fire messages | 🔴 High | Add delays (30s+) |

    | Joining 50+ groups/day | 🟡 Medium | Limit to 20-30 |

    | Mass inviting | 🟡 Medium | Use account rotation |

    | New account + heavy use | 🔴 High | Warm up first |

    If You Get a FloodWait

    FloodWait means Telegram is rate-limiting you. TelePilot Pro handles this automatically:

  • Auto-pauses for the required duration
  • Rotates to other accounts while waiting
  • Resumes when the wait expires

    • If You Get a PeerFlood

    PeerFlood means your account is temporarily restricted:

  • Account is auto-skipped for 24 hours
  • Other accounts continue working
  • Account recovers automatically after cooldown
    • All Docs