Overview
Growth Social combines engagement through native inboxes with automation through a social account connected to the gateway. These are separate connections: direct Instagram login, Instagram linked through Facebook, and the Facebook Page use their respective official inboxes. Gateway-based Instagram automation uses its own session and does not silently replace those inboxes.
Engagement posts, comments and rules require the correct inbox. A rule accepted into the queue is not yet a delivered message: follow each operation in the history.
When connecting or reconnecting Instagram with Growth Social enabled, also grant the comment management permission requested by Meta. An older connection may need this new authorization. Both the comment webhook subscription and the account permission must be active for a rule to receive real interactions.
Prerequisites
- Module access and permission to configure the account or its rules.
- For native Engagement, a connected Instagram or Facebook inbox with the permissions required for the desired operation.
- For gateway automation, an enabled module, available service and connected Instagram session. Complete two-factor verification or any requested challenge before running actions.
- For managed proxies, capacity in the administrator's pool. Enter custom proxy credentials only in the appropriate field.
Step by step
- Open Growth Social, select Engagement and choose the inbox. Confirm whether you are using direct Instagram, Instagram linked through Facebook, or the Facebook Page.
- Select a post, open its comments and configure a private-reply or moderation rule. Check keywords, text or template, and additional actions before saving.
- Make a controlled interaction and inspect the history. Private replies, public replies and moderation have separate outcomes; an additional failure does not mean an already-delivered DM was absent.
- In Instagram automation, connect the account and configure its connection route. Check the effective state after saving.
- In Monitors, select account, collection type, target when required and interval. Check collection state, failure category and next retry.
- In Campaigns, choose the audience and order the steps. Set each step's delay, including the first, and DM templates. Activate the campaign and follow its results.
Settings & options
Native inboxes
Both official Instagram connections are supported as separate paths. The Facebook Page also has its own context. Available operations depend on the connection; missing permissions, limits and expired access are shown as failures rather than an empty comments list.
History distinguishes processing, confirmed delivery, failure and uncertain outcomes. Confirmed private replies are recorded in the corresponding conversation; investigate local recording errors without resending a message already confirmed by the provider.
If the same Instagram profile is connected through both paths in one account, the matching rule with the lowest ID, then inbox ID, determines the private-reply context. A comment does not generate two DMs merely because both connections exist. A failure to record an already-confirmed DM in the inbox is retried automatically up to five times without resending to the provider. Interrupted additional actions are identified as uncertain or not completed and are not repeated automatically.
Campaigns and monitors
Campaign steps advance only after their action is confirmed. Repeated DM steps have separate identities. Pausing or archiving prevents new dispatches; resuming also ensures audience enrollment if it had not yet been processed. Operations already started may finish after a pause.
A completed campaign has finished processing its targets; inspect the completed/failed breakdown. You cannot change its sequence or connected account after targets are enrolled. Create a new campaign for a different flow. Step delay is the supported timing setting; unsupported additional schedule or throttle objects are rejected.
Instagram monitors translate profile/post counts into metrics and save collected audiences as prospects. The last page clears its cursor so a new collection cycle can start. The minimum interval is five minutes. Temporary failures use progressive retry delays; after five consecutive failures, or a definitive failure, collection stops. Retry clears that hold so the scheduler can evaluate the monitor again.
Connection route
Choose direct access, a custom proxy or a managed proxy. Proxy failure policy can hold the account, seek a healthy route, or allow direct access when that option has been explicitly selected. Check region and effective state; a saved configuration may still be pending or paused. The pool shares capacity with other platform consumers.
Use cases
- Reply to an Instagram comment through its official inbox and continue support in the correct conversation.
- Run a follow-up sequence with delays and confirmation per step.
- Track metrics and build audiences without repeating a page or duplicating prospects.
Tips, limits & best practices
Test first with dedicated accounts and recipients. An active connection and automated tests do not prove real delivery. Respect each integration's permissions and limits; permanent absence of external failures cannot be guaranteed. TikTok and YouTube availability depends on their own connectors and must not be inferred from an Instagram connection.
Do not copy passwords, cookies, tokens or credential-bearing proxy URLs into screenshots or tickets. Direct access after proxy failure is used only when the configured policy permits it.
Troubleshooting
- Session failure or challenge: reconnect the account and complete the requested verification.
- Stopped monitor: correct the indicated cause and select Retry. Recovery is scheduled; the click does not mean collection has completed.
- Uncertain delivery: check the provider and ask an administrator to reconcile the action with an audit note and, for delivered outcomes, the external ID. Reconciliation records the outcome and does not automatically send another message.
- Campaign failures: inspect the target and associated action. Legacy records that advanced without confirmation may need reconciliation; do not recreate sends indiscriminately.
- Paused or pending proxy: check credentials, health, region and pool capacity. Treat the route as active only after gateway confirmation.
- Error opening comments: check the selected inbox, connection and permissions; do not treat the error as an absence of comments.
If a manual comment reply has an uncertain outcome, it remains blocked after reloading the page. An administrator must check the outcome with the provider and record reconciliation with a note. Confirmed delivery requires the external identifier and never sends again; confirmed non-delivery unlocks a new explicit attempt.
Comment recovery and provider diagnostics
The activity history separates the private message, the public reply and inbox recording. A public reply failure does not cancel a confirmed private message. Open Provider diagnostics on the failed operation to inspect its code, subcode and request ID without exposing credentials.
An administrator can deliberately enable official comment recovery for one verified Instagram inbox, rule and post. Recovery starts with new comments by default; processing older comments requires an explicit cutoff within the permitted reply window. It shares the webhook delivery ledger, so an uncertain delivery is kept for reconciliation instead of being sent again.
If the official response omits the author identity or a reliable timestamp, recovery pauses with a diagnostic and preserves its place. After correcting access or identity information, the administrator can resume that same scan or stop it. A username alone never creates an identity or authorizes an automatic DM.