Frequently asked questions

You set up a campaign tied to a specific keyword, a specific post or reel, and a message to send. When someone comments that keyword, social.fluxx detects it through Meta's official webhook system and automatically sends them a private DM with whatever you configured: a link, a code, or more information.

You can also enable an optional public reply under the comment itself, so it's visible that a DM is on its way. The whole flow runs through Instagram's own messaging system using the official Graph API, not a workaround.

No. social.fluxx runs on a single Meta application that's been through Meta's App Review process, so all you need to do is connect your Instagram Business account through a standard OAuth authorization, the same kind of "Connect with Instagram" flow used across other apps.

You don't need to register as a Meta developer, submit anything for review yourself, or manage API credentials. That entire layer is handled on social.fluxx's side.

You need an Instagram Business (or Creator) account, since Meta's messaging and comment-management APIs only work with those account types, not personal accounts. If your account is currently personal, Instagram lets you switch to a Business or Creator account for free from within the app before connecting.

Yes. social.fluxx supports multiple connected Instagram accounts within a workspace, and multiple workspaces if you're managing separate clients. Each workspace has its own owner, admin, and member roles, so you can bring team members onto specific accounts without giving them access to everything.

Campaigns, DM logs, and billing are all scoped per workspace, which keeps client accounts cleanly separated from each other.

social.fluxx is priced by how many automations you can have active at once, not by contacts or DM volume, both of which are unlimited on every tier (Meta's own rate limits are the only real cap on send volume). Four tiers: Starter (₹150/$5 per month, 2 automations), Growth (₹550/$13, 5 automations), Pro (₹750/$18, 8 automations), and Scale (₹1,000/$24, unlimited automations), all plus 18% GST.

Every tier includes up to 6 connected Instagram accounts, unlimited contacts and DM sends, tracked links, follow-gated links, and full DM logs — the automation count is the only thing that changes between tiers. Every workspace also gets a 15-day free trial (1 automation, no credit card required) before you need to subscribe.

Billing runs through Razorpay, which supports credit and debit cards, UPI, and netbanking. Razorpay was chosen specifically because it fits an India-based business well and gives Indian customers local payment options rather than relying only on international card processing.

Cancellation is a direct in-app action from Settings > Billing, there's no support ticket or email required. Since Razorpay doesn't offer a hosted billing portal, cancelling is a straightforward button with a confirmation step, and it takes effect immediately rather than at the end of your current billing period.

Every automation you already have keeps running exactly as before — DMs keep sending, nothing gets paused or interrupted. You just can't create a new automation until you either upgrade to a tier with a higher limit or delete an existing one to free up a slot. There's no overage billing; it's a hard cap tied to your current plan.

The same 1-automation limit applies during the 15-day free trial before you've subscribed to a plan at all.

Not currently. social.fluxx v1 runs on its own domain for every customer and doesn't offer a white-label or reseller mode. If that changes in a future release, it'll be announced separately rather than assumed.

social.fluxx connects to Instagram exclusively through Meta's official Graph API, using standard OAuth, the same sanctioned path any legitimate Instagram app uses. It never asks for or stores your Instagram password.

Meta's enforcement is aimed at simulated, password-based automation and cold outreach, not at API-based tools reacting to comments and messages your account actually received. Comment-to-DM automation through the official API is explicitly within Instagram's allowed use of the platform.

Yes. Every connected Instagram account, campaign, and DM log is scoped to a single workspace at the database level. There's no path for one workspace's data, or its team members, to see another workspace's connected accounts or message history, even though everyone runs on the same underlying application.

social.fluxx stores what's necessary to run your campaigns: your connected Instagram account details, campaign configuration, and logs of DMs sent (including delivery status). Data is retained according to the retention practices described in the privacy policy, rather than indefinitely by default.

You can request full deletion of your data separately from simply disconnecting an account, in line with Meta's platform requirements around data deletion.

social.fluxx's approach to data handling is informed by both GDPR and India's Digital Personal Data Protection (DPDP) Act, the more directly applicable regime given the parent company is India-incorporated. That means designing around DPDP's stricter consent standard, explicit, unbundled consent, rather than the more permissive baseline GDPR allows in some cases.

This is general information about our approach, not legal advice. If compliance is a specific requirement for your business, consult your own legal counsel.

Meta caps private replies to comments at 750 per hour, per connected Instagram account. If a campaign gets busy enough to approach that limit, social.fluxx's send queue automatically paces the remaining messages rather than dropping them or retrying aggressively, so a queued DM still goes out, just slightly delayed, without risking the account's standing with Meta.

In normal conditions, a DM goes out within seconds of a matching comment being detected. The only time there's a noticeable delay is during high-volume moments where Instagram's rate limits require pacing, in which case sends are queued and processed in order rather than sent instantly.

Not in v1. social.fluxx is Instagram-only by design, matching the scope of the product it's built on. There's no current support for WhatsApp, Facebook Messenger, or other channels.

DM sending runs through a dedicated background queue with automatic retries on transient failures, rather than a single attempt that either works or silently fails. Every send is recorded in the DM log with its outcome, sent, queued, or failed, so you always have visibility into what actually happened to a specific message.