Anti-Ban Protection

TeleSender's comprehensive anti-ban system protects your Telegram accounts through intelligent rate limiting, human behavior simulation, and adaptive responses to Telegram's feedback signals.

Overview

Account safety is TeleSender's top priority. Our multi-layered protection system helps you automate effectively while minimizing the risk of restrictions or bans.

Protection Layers

┌─────────────────────────────────────────────────┐
│                 TeleSender Anti-Ban             │
├─────────────────────────────────────────────────┤
│  Layer 1: Rate Limiting                         │
│  ├── Operation delays                           │
│  ├── Batch processing                           │
│  └── Daily/hourly limits                        │
├─────────────────────────────────────────────────┤
│  Layer 2: Human Behavior Simulation             │
│  ├── Random delays                              │
│  ├── Typing pauses                              │
│  └── Activity patterns                          │
├─────────────────────────────────────────────────┤
│  Layer 3: Adaptive Response                     │
│  ├── Error-based delay increases               │
│  ├── FloodWait handling                         │
│  └── Session warming                            │
├─────────────────────────────────────────────────┤
│  Layer 4: Operational Limits                    │
│  ├── Max operations/hour                        │
│  ├── Max operations/day                         │
│  └── Consecutive error thresholds               │
└─────────────────────────────────────────────────┘

Safety Profiles

TeleSender offers five pre-configured profiles:

Ultra Safe (Maximum Protection)

Best for: Valuable accounts, new accounts, after restrictions

{
  profile: "ULTRA_SAFE",
  delays: {
    scrape: 3000,      // 3 seconds
    send: 90000,       // 90 seconds (1.5 minutes)
    invite: 180000,    // 180 seconds (3 minutes)
  },
  sessionWarming: {
    initialMultiplier: 3,    // Start 3x slower
    rampUpSteps: 20,         // Gradual speed increase
  },
  batching: {
    batchDelay: 600000,      // 10 minutes between batches
  },
  cooldown: {
    afterOperations: 20,
    duration: 900000,        // 15 minutes
  },
  limits: {
    maxPerHour: 30,
    maxPerDay: 200,
  },
  randomization: {
    variance: 0.5,           // ±50% delay variance
    distribution: "gaussian",
  }
}

Safe (Balanced Protection)

Best for: Regular daily use, established accounts

{
  profile: "SAFE",
  delays: {
    scrape: 2000,      // 2 seconds
    send: 45000,       // 45 seconds
    invite: 90000,     // 90 seconds
  },
  sessionWarming: {
    initialMultiplier: 2,
    rampUpSteps: 15,
  },
  batching: {
    batchDelay: 300000,      // 5 minutes
  },
  cooldown: {
    afterOperations: 50,
    duration: 300000,        // 5 minutes
  },
  limits: {
    maxPerHour: 60,
    maxPerDay: 500,
  },
  randomization: {
    variance: 0.4,
    distribution: "gaussian",
  }
}

Moderate (Balanced Speed/Safety)

Best for: Experienced users, aged accounts

{
  profile: "MODERATE",
  delays: {
    scrape: 1000,      // 1 second
    send: 30000,       // 30 seconds
    invite: 60000,     // 60 seconds
  },
  limits: {
    maxPerHour: 100,
    maxPerDay: 1000,
  },
  randomization: {
    variance: 0.3,
  }
}

Fast (Speed Priority)

Best for: Testing, low-value accounts only

High Risk

Fast profile significantly increases ban risk. Use only for testing or on accounts you can afford to lose.

{
  profile: "FAST",
  delays: {
    scrape: 500,       // 0.5 seconds
    send: 15000,       // 15 seconds
    invite: 30000,     // 30 seconds
  },
  limits: {
    maxPerHour: 200,
    maxPerDay: 2000,
  }
}

Custom (User-Defined)

Create your own profile with full control over all settings.

Profile Comparison

Feature	Ultra Safe	Safe	Moderate	Fast
Send Delay	90s	45s	30s	15s
Invite Delay	180s	90s	60s	30s
Scrape Delay	3s	2s	1s	0.5s
Max/Hour	30	60	100	200
Max/Day	200	500	1,000	2,000
Ban Risk	Very Low	Low	Medium	High
Best For	New accounts	Regular use	Experienced	Testing

Configuration Guide

Accessing Anti-Ban Settings

1. Open TeleSender Options page
2. Navigate to Anti-Ban tab
3. Select or customize your profile

Basic Settings

Delay Configuration

Set operation-specific delays:

Setting	Description	Range
Scrape Delay	Between member fetches	500-5000ms
Send Delay	Between messages	5-300 seconds
Invite Delay	Between invitations	30-300 seconds

Delay Randomization

Add unpredictability to operations:

{
  randomization: {
    enabled: true,
    variance: 0.4,           // ±40% of base delay
    distribution: "gaussian", // Bell curve distribution
  }
}

Example: Base delay 45s with 40% variance = 27s to 63s actual delays

Advanced Settings

Session Warming

Gradually increase speed for new sessions:

{
  sessionWarming: {
    enabled: true,
    initialMultiplier: 2,    // Start at 2x normal delay
    rampUpSteps: 15,         // Take 15 operations to reach normal
    rampUpFactor: 0.9,       // Reduce delay by 10% each step
  }
}

How it works:

Operation #	Delay Multiplier	Actual Delay (base 45s)
1	2.0x	90s
5	1.6x	72s
10	1.3x	58s
15+	1.0x	45s

Batching

Group operations with breaks between batches:

{
  batching: {
    enabled: true,
    batchSize: 20,           // Operations per batch
    batchDelay: 300000,      // 5 minutes between batches
    delayVariance: 0.3,      // ±30% variance
  }
}

Cooldown Periods

Force breaks after sustained activity:

{
  cooldown: {
    enabled: true,
    afterOperations: 50,     // Trigger after 50 operations
    duration: 300000,        // 5 minute break
  }
}

Operation Limits

Set hard caps on activity:

{
  limits: {
    maxPerHour: 60,
    maxPerDay: 500,
    strictEnforcement: true, // Hard stop at limit
  }
}

FloodWait Handling

When Telegram returns a FloodWait error, TeleSender:

1. Pauses all operations immediately
2. Waits for the required duration (plus buffer)
3. Logs the event for analysis
4. Adjusts future delays upward
5. Resumes automatically

{
  floodWait: {
    bufferMultiplier: 1.2,       // Add 20% to wait time
    backoffOnRepeat: true,       // Increase delays on repeated floods
    pauseCampaign: true,         // Pause entire campaign
    maxConsecutive: 3,           // Stop after 3 consecutive floods
  }
}

FloodWait Statistics

Track FloodWait events:

┌─────────────────────────────────────────┐
│ FloodWait Statistics                     │
├─────────────────────────────────────────┤
│ Total events: 5                          │
│ Last event: 2 hours ago                 │
│ Average wait: 127 seconds               │
│ Longest wait: 300 seconds               │
│ Current delay adjustment: +15%          │
└─────────────────────────────────────────┘

Human Behavior Simulation

Random Pauses

Simulate human typing and reading:

{
  humanBehavior: {
    enabled: true,
    randomPauses: {
      enabled: true,
      minDuration: 1000,       // 1 second
      maxDuration: 5000,       // 5 seconds
      frequency: 0.2,          // 20% chance per operation
    }
  }
}

Time Window Restrictions

Operate during realistic hours:

{
  timeWindows: {
    enabled: true,
    activeHours: {
      start: 8,                // 8 AM
      end: 22,                 // 10 PM
    },
    avoidPeakHours: true,      // Slower during 9-17
    weekendMode: true,         // Reduced activity on weekends
  }
}

Adaptive Rate Limiting

TeleSender's AdaptiveRateLimiter adjusts behavior based on results:

Success Response

When operations succeed:

• Gradually decrease delays (by successDecrease %)
• Continue normal operation
• Update success statistics

Error Response

When operations fail:

• Increase delays (by errorIncrease %)
• Check error type and severity
• Potentially pause operations

{
  adaptive: {
    enabled: true,
    errorIncrease: 0.5,        // +50% delay on error
    successDecrease: 0.05,     // -5% delay on success
    minDelay: 10000,           // Never go below 10s
    maxDelay: 300000,          // Cap at 5 minutes
  }
}

Monitoring and Statistics

Real-Time Dashboard

The Anti-Ban tab displays:

┌─────────────────────────────────────────┐
│ Anti-Ban Status: Active                  │
│ Profile: SAFE                           │
├─────────────────────────────────────────┤
│ Session Statistics                       │
│ ├── Total operations: 156               │
│ ├── Successful: 148                     │
│ ├── Failed: 8                           │
│ ├── FloodWaits: 2                       │
│ └── Current delay: 47.2s                │
├─────────────────────────────────────────┤
│ Limits Status                            │
│ ├── Hourly: 45/60 (75%)                 │
│ └── Daily: 156/500 (31%)                │
├─────────────────────────────────────────┤
│ Next cooldown in: 4 operations          │
└─────────────────────────────────────────┘

Statistics Tracking

{
  statistics: {
    totalOperations: 156,
    successfulOperations: 148,
    failedOperations: 8,
    floodWaitCount: 2,
    totalFloodWaitTime: 254,   // seconds
    operationsThisHour: 45,
    operationsToday: 156,
    consecutiveErrors: 0,
    currentDelay: 47200,       // ms
    sessionStart: 1704067200000,
  }
}

Best Practices

For New Accounts

1. Use Ultra Safe profile for first 2 weeks
2. Enable session warming
3. Keep daily operations under 50
4. Manually use the account regularly

For Established Accounts

1. Use Safe profile for regular operations
2. Monitor FloodWait frequency
3. Stay within daily limits
4. Take breaks between large campaigns

After Restrictions

If your account received warnings or temporary restrictions:

1. Stop all automation for 48-72 hours
2. Use account manually during this period
3. Switch to Ultra Safe profile when resuming
4. Reduce operation volume by 50%
5. Gradually return to normal over 1-2 weeks

Recovery Strategies

After FloodWait

1. Complete the mandatory wait
2. Add 20% buffer time
3. Resume with increased delays
4. Monitor for repeated floods

After Peer Flood

1. Stop ALL operations immediately
2. Do not use automation for 24-48 hours
3. Use account manually (light usage)
4. Return with Ultra Safe profile
5. Rebuild activity gradually

After Ban Warning

1. Stop automation completely
2. Review Telegram's message carefully
3. Wait minimum 1 week before resuming
4. Consider using different account for automation
5. Implement strictest possible settings

Custom Profile Builder

Create a custom profile:

1. Go to Anti-Ban → Custom Profile
2. Configure each setting individually
3. Save your profile
4. Test with small operations
5. Adjust based on results

Example Custom Profile

{
  name: "My Custom Profile",
  delays: {
    scrape: 2500,
    send: 60000,
    invite: 120000,
  },
  randomization: {
    variance: 0.35,
    distribution: "gaussian",
  },
  limits: {
    maxPerHour: 40,
    maxPerDay: 400,
  },
  adaptive: {
    enabled: true,
    errorIncrease: 0.3,
    successDecrease: 0.02,
  }
}

---

Quick Reference

Risk Level	Profile	Use Case
Minimal	Ultra Safe	Valuable accounts
Low	Safe	Daily operations
Medium	Moderate	Aged accounts
High	Fast	Testing only

---

Next: Learn about Campaign Builder →