ReelPilot

Automate every Reel comment flow, one Reel at a time.

ReelPilot is an enhancement to an existing Instagram automation Telegram bot that lets users create independent automation rules for individual Instagram Reels. It is designed for creators, marketers, and operators who need separate messages, replies, and follow-gated delivery per Reel without cross-triggering or shared configuration leakage.

Business Goals

  • Increase feature adoption among existing bot users by 25% within 90 days of release.
  • Improve paid conversion or upgrade intent from active users by 15% within 60 days by adding Reel-specific automations.
  • Reduce support tickets related to mixed-up comment triggers and shared delivery settings by 40% within 45 days.
  • Maintain at least 95% of existing bot users on the upgraded version without breaking legacy flows for 30 days after rollout.
  • Achieve a 60% weekly activation rate for users who visit the new Reel Automation Manager at least once.

User Goals

  • Let users create separate automation rules for each Reel in under 2 minutes.
  • Allow users to send different delivery messages, links, and replies for each Reel.
  • Prevent one Reel’s comments from triggering another Reel’s automation.
  • Show clear follow-gated delivery behavior with safe fallback when verification fails.
  • Provide visibility into delivery history, failures, and automation status per Reel.

Non-Goals

  • Rebuilding the Telegram bot from scratch.
  • Replacing the existing general comment reply or delivery systems.
  • Supporting Instagram account growth tactics, spam behavior, or policy evasion.
  • Guaranteeing delivery when Instagram API access, rate limits, or account restrictions block an action.

Creator Ops Nina, 31 - Nina manages multiple promotions from one Instagram account and needs separate comment automation for each Reel. She wants to avoid sending the wrong PDF or product link to the wrong audience.

Creator Ops Nina, 31

  • As a creator ops manager, I want each Reel to have its own reply and delivery setup, so that campaigns stay isolated.
  • As a creator ops manager, I want to see which comments were handled and which failed, so that I can troubleshoot quickly.
  • As a creator ops manager, I want follow-gated delivery to ask non-followers to follow and comment again, so that premium material is protected.

Agency Admin Leo, 38 - Leo oversees multiple clients and multiple Instagram accounts in one Telegram workspace. He needs safe controls, approval visibility, and account-level monitoring without mixing data across users.

Agency Admin Leo, 38

  • As an agency admin, I want to manage Reel automations per connected account, so that each client campaign is isolated.
  • As an agency admin, I want to pause a problematic Reel automation safely, so that I can stop bad sends immediately.
  • As an agency admin, I want usage and error statistics across users, so that I can monitor service health.

Solo Seller Maya, 27 - Maya sells digital products and uses Instagram Reels to drive leads into Telegram-delivered guides. She needs a simple setup flow that works without technical knowledge.

Solo Seller Maya, 27

  • As a solo seller, I want to pick a Reel and attach a message and link, so that I can launch quickly.
  • As a solo seller, I want default behavior to handle every eligible comment, so that I do not need complex keyword rules.
  • As a solo seller, I want to edit or disable an automation later, so that I can adjust campaigns without rebuilding them.

Reel Discovery and Selection · High priority

  • Users must be able to fetch Reels from connected Instagram accounts and choose a specific Reel to automate. The selection experience must show enough metadata to prevent mistakes.
  • Display Reel media ID, caption preview, thumbnail if available, and publication date for each fetched Reel.
  • Support pagination or refresh for accounts with many Reels, with a clear loading state and no duplicate entries.
  • Require the user to choose one connected Instagram account before browsing its Reels.
  • Store Reel identity using account ID plus media ID so automations remain scoped correctly.
  • Handle missing thumbnail or caption data gracefully without blocking creation.

Independent Reel Automation Setup · High priority

  • Each Reel must have a fully independent automation configuration that does not inherit or share settings from other Reels or from the global comment reply system.
  • Allow per-Reel delivery text, URL, media/material assignment, public reply template, follow requirement, non-follower instruction, and trigger mode.
  • Default trigger mode must be every eligible new comment, with optional keyword filtering.
  • Support multiple automations per account, with each automation tied to one Reel only.
  • Provide edit, pause, resume, disable, and delete actions for each automation.
  • Keep the existing general delivery and comment reply systems separate and unchanged.

Comment Processing and Duplicate Protection · High priority

  • The automation engine must process comments safely and idempotently, using strict status tracking and duplicate prevention to avoid double sends or cross-Reel leakage.
  • Track processing by account ID, Reel media ID, comment ID, commenter user ID, and automation ID.
  • Use explicit processing states such as pending, replied, delivered, blocked, failed, and retryable.
  • Never mark a comment as completed until all required operations for that workflow succeed or are safely terminal.
  • Prevent one comment from triggering multiple Reel automations unless the user explicitly created overlapping automations on purpose.
  • Add retry-safe handling for transient API errors and store the reason for failure or blocking.

Follow-Gated Delivery Workflow · High priority

  • Protected delivery flows must use strict follower verification and must never leak protected material if verification is unknown or fails.
  • Support a strict verification outcome model: FOLLOWING, NOT_FOLLOWING, UNKNOWN.
  • If follow requirement is off, send only that Reel’s assigned material after the public reply if configured.
  • If follow requirement is on, send protected material only after verified FOLLOWING status.
  • If verification is NOT_FOLLOWING, send the configured instruction telling the user to follow and comment again.
  • If verification is UNKNOWN or API error occurs, block protected delivery, log the failure, and schedule safe retry when appropriate.

Operations, Monitoring, and Recovery · Medium priority

  • The system must remain reliable after restarts and provide sufficient visibility into failures, throughput, and automation health.
  • Persist automation configuration and processing state in JSON-backed storage with atomic writes and synchronization.
  • Recover active automations and scheduled jobs after restart from persisted configuration instead of relying only on memory.
  • Track per-automation statistics such as comments seen, replies sent, deliveries sent, blocks, retries, and failures.
  • Provide admin monitoring for active jobs, paused automations, and error counts.
  • Preserve existing scheduled DMs, media delivery, and account monitoring behavior without regression.

Reel Automation Manager Onboarding

  • Open the existing Telegram bot and choose Reel Automation Manager from the main menu.
  • Select one connected Instagram account if the user has multiple accounts.
  • Tap Refresh Reels to fetch the latest Reels and display them with media ID, thumbnail, caption preview, and date.
  • Choose a Reel and create a new automation with default trigger set to every comment.
  • Set delivery content, follow requirement, public reply, and non-follower instructions.
  • Activate the automation and see a confirmation with the expected first-run status.
  • Target time to value: under 2 minutes from menu entry to enabled automation.

1. Browse Reels

  • The user opens My Reels and sees a paginated list of fetched Reels for the selected Instagram account.
  • Show caption preview truncated to a safe length with a clear Reel identifier.
  • Handle missing thumbnail or media metadata with fallback text.
  • Prevent selection of Reels from the wrong account by showing the active account badge.

2. Create Automation

  • The user chooses a Reel and creates a new automation scope for that exact media item.
  • Pre-fill the automation name with the Reel caption or media ID for convenience.
  • Default trigger mode to every eligible comment.
  • Validate that the Reel has not already reached a configured per-user automation limit.

3. Configure Delivery

  • The user sets the text, URL, media, reply template, and follow gating for that Reel.
  • Allow optional keyword filtering but keep it off by default.
  • Show a clear preview of what followers and non-followers will receive.
  • Warn if the configured media or link is empty while delivery is expected.

4. Activate and Monitor

  • The user enables the automation and sees its status, counters, and last processed events.
  • Show active, paused, blocked, or error states with plain-language reasons.
  • Provide event history for recent comments, replies, deliveries, and verification outcomes.
  • Allow the user to pause or disable without deleting historical data.

5. Edit or Delete Safely

  • The user can update rules later or delete an automation with confirmation.
  • Require a confirmation step before deletion and explain what history will remain.
  • Preserve historic statistics even when an automation is disabled.
  • Block edits that would break stored identifiers unless the user explicitly confirms the change.

Power User and Edge-Case Features

  • Per-Reel statistics dashboard with reply rate, delivery success rate, and follower-gated conversion rate.
  • Manual refresh of Reels and explicit re-scan of recent comments for a selected automation.
  • Safe retry queue for transient Instagram or network failures.
  • Account-level pause mode for maintenance or suspected rate-limit pressure.
  • Optional keyword filtering for campaigns that need stricter lead qualification.
  • Audit trail for edits, activation changes, and admin intervention.

Telegram UI Principles

  • Keep the existing inline keyboard style and use concise, predictable action labels.
  • Show account name and Reel media ID on every automation screen to avoid confusion.
  • Use clear status colors or labels such as Active, Paused, Retrying, and Blocked.
  • Minimize taps for the common path: select account, select Reel, create automation, activate.
  • Avoid clutter by collapsing advanced settings behind an Edit Advanced Options action.
  • Keep responses short and readable on small mobile screens.

Maya runs a small digital product business and uses Instagram Reels to attract leads. Before this feature, she could only use one shared comment automation setup, which meant different Reels often sent the wrong message or the wrong file to commenters.

With Reel Automation Manager, Maya opens the Telegram bot, refreshes her Reels, picks one specific Reel, and attaches a unique message, link, and reply template. She sets another Reel to require follow verification before sending a premium guide, while a third Reel sends a different product pitch without any follow gate.

Now each Reel works independently, comments are handled safely, and failed verification never exposes protected material. Maya spends less time correcting mistakes and more time measuring which Reel converts best, while the bot stays aligned with the behavior of her campaign instead of one global rule set.

User-Centric Metrics

  • At least 70% of users who open Reel Automation Manager create one Reel automation within 7 days.
  • At least 90% of created Reel automations remain correctly scoped with zero cross-Reel delivery incidents in test and production monitoring.
  • Reduce median setup time for a new Reel automation to under 2 minutes.
  • Achieve a minimum 85% successful delivery rate on eligible comment workflows where Instagram permits the action.
  • Keep user-reported confusion about reply scope or delivery scope below 5% of support contacts.
  • At least 60% of active users view Reel statistics at least once per week.

Business Metrics

  • Increase weekly active users of the Telegram bot by 15% within 90 days after launch.
  • Increase retention of automation users by 10% over 60 days.
  • Drive a 20% uplift in adoption of advanced automation features among existing paid or power users.
  • Reduce churn caused by setup complexity or mixed delivery settings by 25% within one quarter.

Technical Metrics

  • Maintain 99.5% uptime for the bot service excluding external Instagram outages.
  • Keep median Telegram command response time under 1.5 seconds for configuration actions.
  • Keep comment processing duplicate rate below 0.1% of handled comments.
  • Record 100% of automation state changes and delivery attempts in persistent logs or event history.

Tracking Plan

  • Track reel_manager_opened when a user enters the Reel Automation Manager.
  • Track reel_list_refreshed when the system fetches Reels for an account.
  • Track reel_automation_created when a new Reel automation is saved.
  • Track reel_automation_activated and reel_automation_paused when status changes happen.
  • Track reel_comment_detected for each eligible comment scan result.
  • Track reel_delivery_sent, reel_reply_sent, reel_blocked_follow_required, and reel_verification_failed for workflow outcomes.
  • Track reel_automation_deleted and reel_automation_edit_saved for lifecycle monitoring.

Technical Needs

  • Python 3.11 or compatible runtime with the existing python-telegram-bot and instagrapi stack.
  • A dedicated Reel automation storage layer built on the current JSON persistence model with atomic file writes.
  • Concurrency control around shared data access, including a lock or single-writer pattern for data.json.
  • A background reconciliation loop that rebuilds active Reel jobs from persisted configuration after restart.
  • Idempotent event handling keyed by account ID, media ID, comment ID, and automation ID.
  • Structured logging with event IDs, retry reasons, and status transitions.
  • Backward-compatible migration logic to populate missing fields in older user records.

Integration Points

  • Telegram Bot API for inline keyboards, callback queries, and message delivery.
  • Instagram via instagrapi for Reel listing, comment retrieval, and follower verification where supported.
  • Current encrypted session storage using Fernet for account sessions.
  • Existing JSON runtime storage in data.json for user, account, and automation records.
  • Render deployment environment for persistent service configuration and startup recovery.

Data Storage & Privacy

  • Store only the minimum Instagram data needed for automation, such as media ID, comment ID, and display metadata.
  • Keep encrypted Instagram sessions separate from general automation metadata and never send session data through Telegram.
  • Provide deletion paths for automation history and user-associated stored metadata where required by policy or request.
  • Treat follower verification results and comment content as sensitive operational data and limit admin visibility to necessary fields.
  • Document retention behavior for event history and apply reasonable log hygiene for GDPR/CCPA alignment where applicable.

Scalability & Performance

  • Limit per-scan Reel comment pagination to a safe, configurable window to avoid rate spikes.
  • Use per-account and per-automation locks to prevent concurrent double-processing.
  • Cache recently fetched Reel metadata briefly to reduce repeated API calls during menu navigation.
  • Support restart recovery without reprocessing already-acknowledged comments or losing pending retry work.

Potential Challenges

  • Instagram API may not reliably expose all requested Reel and comment operations; mitigate by labeling unsupported states and using safe fallbacks.
  • Follower verification may return unknown or error states; mitigate by blocking protected sends until verification is explicit.
  • Shared JSON storage can corrupt under concurrent writes; mitigate with atomic write temp files and synchronized access.
  • Background task loss after restart may cause missed jobs; mitigate with persisted schedules and reconciliation on startup.
  • Rate limits or temporary account restrictions may interrupt delivery; mitigate with backoff, retry caps, and admin-visible health alerts.

Team & resourcing - Small team - 2 backend engineers, 1 Telegram UX designer, part-time PM, and shared QA support.

Phase 1: Storage and Safety Foundation · Weeks 1-2

  • Add Reel automation data structures and backward-compatible defaults.
  • Implement atomic JSON writes and synchronized access to persistent data.
  • Introduce strict processing states, duplicate protection, and logging for Reel workflows.
  • Fix render.yaml indentation and startup configuration issues.

Phase 2: Reel Manager MVP · Weeks 3-4

  • Add Reel Automation Manager menu and account-scoped Reel listing.
  • Implement create, edit, pause, resume, and delete flows for a single Reel automation.
  • Support per-Reel delivery text, link, reply template, and default every-comment trigger.
  • Show automation status and recent event history in Telegram.

Phase 3: Protected Delivery and Recovery · Weeks 5-6

  • Implement strict follow verification states and safe protected delivery flow.
  • Add retry queue and restart recovery for active Reel automations.
  • Reconcile active jobs from persisted config after restarts.
  • Add admin monitoring for counts, failures, and paused automations.

Phase 4: Hardening and Rollout · Weeks 7-8

  • Regression test all existing bot features and preserve legacy behavior.
  • Load test comment scanning, duplicate prevention, and retry handling.
  • Document rollback steps and safe disablement of Reel automation features.
  • Ship monitoring dashboards and production readiness checklist.

Paste this into Cursor, Bolt, Lovable, or v0 to start building.

Build an enhancement for an existing Python Telegram bot that manages Instagram automation. The app already uses python-telegram-bot, instagrapi, asyncio background tasks, Fernet-encrypted sessions, and JSON persistence in data.json. Do not rewrite the app; add a new Reel Automation Manager with minimal, targeted changes and preserve all existing features and menus.

Core requirement:
Add independent per-Reel automation rules for connected Instagram accounts. Users must be able to fetch and view Reels, identify each Reel by media ID, caption preview, thumbnail when available, and publication date, then create separate automations per Reel. Each automation needs its own delivery text, URL, media/material attachment, public comment reply template, trigger mode, follow requirement, non-follower instruction, active/paused status, duplicate protection, and event history. Default trigger is every eligible comment. A comment on one Reel must never trigger another Reel’s automation.

Functional scope:
Create Telegram screens for My Reels, Create Automation, Active Automations, Refresh Reels, Statistics, and Back to Main Menu. Support edit, pause, resume, disable, and delete with confirmation. Preserve all existing global comment reply and delivery systems unchanged and independent from the new Reel manager.

Data and architecture:
Extend the existing JSON storage with backward-compatible defaults and migration for old records. Use atomic writes and synchronization to prevent lost updates. Persist automation state and recovery metadata so active automations can be restored after restart. Track comment processing states explicitly, including pending, replied, delivered, blocked, failed, and retryable. Use idempotent keys based on account ID, Reel media ID, comment ID, commenter ID, and automation ID.

Workflow:
For each new eligible comment, identify the exact account, Reel media ID, comment ID, and commenter. Check whether the comment was already processed. Publish the configured public reply when allowed. If follow requirement is off, send only that Reel’s assigned material. If follow requirement is on, verify the commenter with strict states FOLLOWING, NOT_FOLLOWING, UNKNOWN. Only send protected material for FOLLOWING. If NOT_FOLLOWING, send the configured follow-and-comment-again instruction. If UNKNOWN or API error, never send protected material; record the failure and retry safely. Prevent duplicate replies and deliveries.

Instagram feasibility:
Use instagrapi where supported for Reel listing, comment retrieval, and follower verification, but handle unsupported or unreliable operations safely. Never promise guaranteed delivery. Gracefully label unknown, blocked, or rate-limited states and keep protected material from being exposed when verification is not definitive.

UI:
Keep the current Telegram inline keyboard style. Show account name, Reel media ID, and clear status labels. Keep screens concise for mobile use. Add admin monitoring for automation counts, success/failure stats, active jobs, and safe pause controls.

Implementation details:
Use Python 3.11, the existing bot.py as the main integration point, and add new modules only if genuinely useful for Reel management, storage, and handlers. Do not remove or rename existing handlers unless required for compatibility. Add structured logging, retries with backoff, rate-limit handling, and restart recovery. Preserve legacy user records and existing scheduled DMs, comment reply, delivery, admin, and monitoring features. Include rollback support and feature flags or safe disable switches if needed.

Deliver a production-ready scaffold with screens, state management, data models, event tracking, and safe defaults. Prioritize correctness, idempotency, and preserving all current bot behavior.

Business Idea

PRD REQUIREMENT: ADD A REEL AUTOMATION MANAGER TO THE EXISTING INSTAGRAM TELEGRAM BOT Act as a senior software architect, Python backend developer, Telegram bot specialist, and Instagram automation expert. First understand the existing project described below. Create a precise, implementation-ready Product Requirements Document (PRD). Do not write or modify code yet. 1. EXISTING PROJECT OVERVIEW The project is a Python-based Instagram automation Telegram bot. Its main source file is "bot.py" (approximately 1,153 lines). Supporting files are "README.md", "requirements.txt", "render.yaml", and ".gitignore". Current architecture: - Python with "python-telegram-bot" and "instagrapi". - Telegram inline keyboards, callback handlers, and conversation-based configuration. - Asyncio background tasks for automation. - JSON-based persistent storage through "data.json" at runtime. - Instagram sessions encrypted using Fernet. - Media storage and multiple Instagram accounts per user. - Instagram operations frequently run through "asyncio.to_thread()". - Existing account-specific locks and background loops. Important existing integration points: - "ig_comments()": background comment-scanning system. - "_deliver()": existing DM delivery helper. - "_follows_me()": Instagram follower-verification helper. - "r_cr()" and "in_cr_kw()": existing Comment Reply configuration. - "r_dl()", "in_d_text()", and "in_d_media()": existing Link/File Delivery configuration. - "A()": JSON data initialization/access helper. - "render.yaml": deployment configuration. Existing comment scanning checks approximately the latest five media posts and retrieves up to 30 comments per post per scan. It tracks processed comments, supports keyword filtering, can publish configured replies, and can send existing shared Delivery material. An empty keyword list currently allows all new comments. It does not provide independent automation settings for individual Reels. 2. EXISTING FEATURES THAT MUST BE PRESERVED Do not remove, replace, rename, redesign, or break any existing functionality. Preserve: - Telegram registration and user approval. - Instagram login, encrypted sessions, multiple accounts, account selection/removal. - Auto DM to targets and followers, single DM, incoming DM auto-reply. - General Link/File Delivery and keyword-triggered delivery. - Follow-required DM delivery and non-follower instructions. - Photo/video delivery, welcome DMs, story replies. - Existing Comment Reply and comment-triggered DM. - Scheduled DMs, saved templates, username placeholders, spintax. - Delays, daily limits, and user activity/status. - Admin approval/rejection, ban/unban, user search/details. - Admin limits, maintenance mode, broadcasts, statistics, account/job monitoring. The existing General Delivery and Comment Reply systems must remain independent of the new Reel Automation Manager. 3. NEW FEATURE: INDEPENDENT REEL AUTOMATION MANAGER Add a new Telegram menu item called Reel Automation Manager. Users should be able to: 1. Fetch and view Reels from their connected Instagram account. 2. Identify each Reel using its media ID, caption, thumbnail (if available), and publication date. 3. Select an individual Reel and create a separate automation for it. 4. Configure multiple Reels independently (e.g. 10 Reels, each with different messages and rules). 5. Enable, disable, edit, pause, or delete each automation. Each Reel must have its own: - Delivery text/message. - URL or link. - Supported media/material configuration. - Public comment reply template. - Trigger mode (default: every new comment; optional keyword filtering). - Follow requirement ON/OFF. - Non-follower instruction message. - Active/inactive status. - Duplicate protection settings. - Statistics and event history. Example: Reel A promotes a PDF guide and sends its link. Reel B promotes a course and sends a different message. Reel C promotes a product and sends different information. A comment on one Reel must never trigger another Reel's material. Default trigger: every eligible new comment, without requiring a keyword. 4. REQUIRED AUTOMATION WORKFLOW For every new eligible comment: 1. Identify the exact Instagram account, Reel media ID, comment ID, and commenter. 2. Check whether that comment has already been processed. 3. Publish the configured public reply, where permitted. 4. If follow requirement is OFF, send only that Reel's assigned material. 5. If follow requirement is ON, verify whether the commenter follows the connected account. 6. If FOLLOWING, send the assigned material. 7. If NOT FOLLOWING, send the configured instruction asking the user to follow and comment again. 8. When the user comments again, recheck follow status and deliver the correct material if verified. 9. If verification returns UNKNOWN or an API error, never send protected material. Record the failure and retry safely when appropriate. Use strict verification states: FOLLOWING, NOT_FOLLOWING, UNKNOWN. Never treat an API failure as proof that someone follows. Prevent duplicate replies and deliveries using appropriate comment, user, Reel, and account identifiers. 5. TELEGRAM INTERFACE Preserve the existing UI style and navigation. Add the new manager without disturbing existing menus. Suggested menu: - My Reels - Create Automation - Active Automations - Refresh Reels - Statistics - Back to Main Menu Each Reel's settings should be editable individually, with confirmation before deletion. Show useful status and delivery history. 6. ADMIN AND PERMISSIONS Users can manage only their own connected accounts and Reel automations. Admins retain existing permissions and gain suitable system-wide monitoring: - Automation counts and active jobs. - Success/failure statistics. - Per-user and global usage limits. - Error/health monitoring. - Ability to pause problematic automation safely. Check admin authorization on every privileged action. Never expose Instagram session credentials or private user data unnecessarily. 7. EXISTING CODE PROBLEMS TO ADDRESS The PRD must explicitly cover these observed issues and propose targeted fixes: - "_follows_me()" currently fails open by returning True when verification fails. Replace this behavior with strict verification for the new protected workflow. - "ig_comments()" marks comments processed before all operations are confirmed. Design safer processing states and retry handling. - Comment-triggered delivery needs consistent daily-limit accounting. - Concurrent access to "data.json" risks lost updates or corruption. Specify synchronization and atomic writes. - "A()" may not initialize every missing field in existing records. Define backward-compatible defaults and migration. - In-memory background tasks may be lost after restarts. Define safe recovery from persisted configurations. - Scheduled delivery may lose jobs if a schedule is removed before delivery succeeds. - Improve operation-level logging, error handling, duplicate prevention, and retry management. - "render.yaml" currently has an indentation/YAML parsing problem that must be corrected. - Verify persistent storage requirements for JSON data and media during deployment. - Review session security and avoid exposing credentials through Telegram messages or logs. Distinguish confirmed problems from risks requiring further testing. Do not claim unverified behavior is a confirmed bug. 8. ARCHITECTURE AND IMPLEMENTATION RULES This is an enhancement to an existing project, NOT a complete rewrite. - Keep "bot.py" and existing functions wherever practical. - Integrate with existing account management, Telegram handlers, storage, and background tasks. - Add separate modules for Reel management/storage/handlers only where genuinely useful. - Make minimal, targeted changes to existing functions. - Do not duplicate existing functionality unnecessarily. - Preserve existing data and support old user records. - Avoid unnecessary dependencies and database migrations. - Include error handling, logging, rate limits, retries, idempotency, and restart recovery. - Back up original files and data before implementation. - Provide rollback instructions. 9. INSTAGRAM API FEASIBILITY AND COMPLIANCE Do not assume "instagrapi" supports every requested operation reliably. Research and clearly document: - Reel discovery and pagination. - Comment retrieval and identification. - Private comment replies/DM delivery. - Follower verification. - Messaging restrictions and eligibility windows. - Rate limits, account restrictions, and platform policies. Separate supported, partially supported, and unsupported operations. Provide realistic alternatives where necessary. Never promise guaranteed delivery or bypass Instagram restrictions. 10. REQUIRED PRD OUTPUT Produce a professional PRD containing: 1. Executive summary and objectives. 2. Existing architecture and feature inventory. 3. Existing code integration points and exact functions affected. 4. Confirmed bugs, risks, and required fixes. 5. Detailed functional requirements and user workflows. 6. Telegram UI and admin requirements. 7. Data model and backward-compatible storage design. 8. Automation lifecycle, duplicate protection, retries, and recovery. 9. Security, permissions, and privacy. 10. Instagram API feasibility and compliance. 11. Performance, reliability, logging, and deployment. 12. Acceptance criteria and test cases. 13. Regression tests for every existing feature. 14. Phased implementation plan and rollback strategy. For every proposed change, specify WHAT changes, WHERE it changes, WHY it is necessary, HOW it integrates, and WHAT existing functionality must remain untouched. Include concrete examples, edge cases, failure scenarios, and measurable acceptance criteria. Do not use vague statements such as "improve automation." FINAL RESTRICTION This stage is PRD planning only. Do not generate source code, rewrite files, or assume permission to implement. The first priority is preserving the existing bot and adding the new Reel Automation Manager through minimal, controlled changes. If any requested feature is technically impossible or unsupported, state that honestly and propose the safest practical alternative. Wait for approval of the PRD before preparing the technical design and implementation plan.

Make My PRD

Design by The Resonance | Powered by GPC – The AI Transformation Company

    PRD: PRD REQUIREMENT: ADD A REEL AUTOMATION MANAGER TO THE...