schedule_send manygram
menu Menu
How it works Features Safety Tech stack FAQ settings Admin

manygram

Message customers in one Go.

Welcome to manygram — explore how bulk messaging in Telegram works safely and efficiently through account rotation, deduplication, and pacing control.

play_circle See the flow dashboard Open Admin
* Demo only. Not for commercial or spam usage. Respect platform Terms & local laws.

High-level flow

  1. database Import targets (recipients) → de-dupe by recent days.
  2. group Assign message groups with per-message gaps, hourly caps, & account pool.
  3. schedule Scheduler picks next eligible account & recipient respecting pacing rules.
  4. send Delivery via Telegram client; result stored with status & timestamps.
  5. insights Logs & insights visible in Django Admin (success, fails, retries).

How it works

table_view

Recipients & Groups

Upload/import recipients, organize into Message Groups with caps, gaps, & de-dupe rules.

manage_accounts

Accounts Pool

Rotate through active accounts; inactive accounts are blocked by validation.

pace

Pacing & Caps

Per-message gap (min/max), hourly caps, and daily de-dupe to avoid repeats.

rule

Privacy & Ownership

Querysets restricted by add_by (required) and owner (optional) fields.

monitoring

Logging

Message attempts/statistics captured in admin for audits & debugging.

tune

Configurable

Switch knobs per group without code changes; safe defaults baked in.

Key features

  • check_circle Account rotation & inactivity checks.
  • check_circle Per-group min/max message gap & hourly caps.
  • check_circle De-duplication within configurable days.
  • check_circle Admin validation: inactive accounts cannot be saved into groups.
  • check_circle Privacy filter: add_by required; owner optional.
  • check_circle Delivery logs with status & timestamps.
  • check_circle Background tasks handle delivery automatically.
  • check_circle Built-in scheduler automates daily campaigns and routine jobs.

Safety & Compliance (Demo)

This project is presented for portfolio demonstration only. Always follow Telegram’s Terms, local regulations, and obtain recipient consent. Pacing, caps, and dedupe help reduce risk; they do not guarantee compliance.

Try it yourself

login Open Admin

warning Use your own Telegram account at your own risk. This project does not guarantee ban-prevention. Follow Telegram Terms and local laws.

  1. account_circle 1) Add a Telegram Account

    Admin → Bulk Messaging (sidebar) → Accounts (top tabs) → “+ Add”. Save, then verify / sign-in (phone + code). Only active accounts can be used.

  2. person 2) Create a Profile (sender identity)

    Go to Profiles (top tabs) → “+ Add”. Set a name, pick the Account to send with.

  3. contacts 3) Import Recipients

    Open Recipients. Import/upload targets. The system de-dupes by the configured dedupe days.

  4. group 4) Create a Message Group

    Go to Message Groups. Set per-message gap (min/max), hourly cap, and dedupe days. Select Accounts (only active allowed) and attach Recipients.

  5. draw 5) Compose Message Content

    From a profile’s Detail → Contents tab, write your message or template. Keep it short, natural, and compliant.

  6. schedule 6) Run or Schedule

    Click Run Messaging to start now, or set a schedule. Background workers rotate accounts, honor gaps/caps, and log every attempt. Check Send Logs → Attempts for results.

shield Proxy & safety notes

  • Prefer static residential (or ISP) proxies tied to the account’s usual country.
  • Keep per-message gap realistic (e.g. 90–300 s) and hourly caps conservative.
  • Avoid sending the same content repeatedly; vary text, add delays, and respect opt-outs.
  • Warm up new accounts slowly; sudden bursts trigger risk signals.
  • Even with pacing + proxies, bans can still happen. This demo does not guarantee avoidance.
Admin views only show records you created or manage — keeping data private and relevant to you.

Tech stack

Backend

  • Django + DRF
  • Admin: Django-Unfold
  • Celery/Beat + Redis (optional)

Messaging

  • Telegram client integration
  • Account rotation & validation
  • Logging & retries

Ops

  • Sentry test route
  • Docker-ready
  • DRF for API Expose(coming soon)

FAQ

Is this a commercial product?

No. This is a portfolio demonstration to show the architecture, admin UX, and the background task scheduler that orchestrates pacing, retries, and delivery (e.g., Celery/Beat + Redis).

Can I try it?

Messaging is enabled here with safety limits (rate-limited, masked recipients). For full access, sign in.

Does it prevent bans?

No system can guarantee that. Pacing, caps, and dedupe help reduce risk; compliance remains your responsibility.