telegram_channel_ops v1.0.0

name: "telegram_channel_ops" description: "Run a Telegram channel or group like an operation: broadcast cadence, content mix, growth, bots, moderation, and monetization. Triggers on requests to start, grow, audit, or monetize a Telegram channel or group; set up channel bots; plan posting schedules; or build Telegram-native revenue."

Telegram Channel Ops

Purpose

Turn a Telegram channel or group from a hobby feed into a durable media asset: predictable cadence, healthy metrics, working automation, clean moderation, and stacked revenue. Covers both halves of the job: channels (broadcast, unlimited subscribers, signed posts, view counters) and linked discussion groups (up to 200,000 members, granular admin roles).

Workflow

1. Intake. Get the channel's goal (audience growth, revenue, community, or launch vehicle), current size, niche, and whether a discussion group exists. A channel with no goal gets a goal before it gets a schedule.
2. Audit. Pull the last 30 days of post stats. Score against benchmarks in references/cadence-and-growth.md (reach rate, reaction rate, CTR, retention, churn). Name the single weakest metric; fix that first.
3. Cadence plan. Set a weekly posting rhythm from the templates in references/cadence-and-growth.md. Hold a 3:1 value-to-pitch ratio: three value posts for every promotional one. Pin a welcome/index post.
4. Automation. Pick bots from references/bots-and-automation.md. For bot-built broadcasts, validate the plan with bin/broadcast_planner.py so rate limits are respected by design, not discovered by 429s.
5. Moderation. Set group rules per references/moderation.md: pinned guidelines, slow mode, bot-assisted spam filtering, admin escalation ladder.
6. Monetization. Stack models from references/monetization.md in order of effort: Telegram Ads revenue share first, then sponsored posts, subscriptions/paywalls, affiliates, bots/Mini Apps.

Output Contract

Every engagement ends with one of:

• Channel plan: goal, weekly cadence grid, content-mix percentages, pinned-post draft, KPI targets for 30 days.
• Audit report: metric scores vs benchmarks, the weakest metric, three prioritized fixes with effort estimates.
• Broadcast plan: message list, recipient count, rate-limit-validated schedule (run through bin/broadcast_planner.py), 429 fallback behavior.
• Monetization stack: ordered revenue models with eligibility status (e.g. 1,000+ subscriber threshold for the Ads share) and claim steps.

Operating Rules

• Verify every platform fact against references/sources.md or a current primary source before acting on it. Rate limits, payout thresholds, and feature availability change; never quote them from memory.
• Never promise engagement or revenue numbers. Give ranges from the benchmarks doc and mark third-party CPM figures as estimates, not platform rates.
• Never recommend fake engagement (paid members, auto-view services). If a client is using them, flag the brand-safety risk plainly.
• Always disclose sponsorship: every sponsored post marked "Ad" or "Sponsored". Follow FTC endorsement guidelines and local rules.
• Bots that collect user data must disclose what they collect and why; comply with applicable data protection rules.
• Bot API rate limits are hard: 1 msg/sec per private chat, 20 msg/min per group, ~30 msg/sec bulk. Honor retry_after exactly. Never loop-send in a tight loop.
• Channels and groups have different jobs. A broadcast channel is not a community; a discussion group is not a billboard. Route the request to the right half of the workflow.