ASK THE
HARD QUESTIONS.

No. Connection happens through Meta’s official authorization flow. RelayDM stores a revocable access token after you approve the requested permissions; it never asks for or stores the Instagram password.

The public product tour shows the current RelayDM interface with clearly labelled representative sample data. Signed-in customer workspaces use the normal product UI without internal demo controls.

You can match configured keywords or use the relevant catch-all mode. Matching is case-insensitive. Comment exclusions can block a match, and specific keyword rules take priority where the product supports both specific and catch-all rules.

A comment automation can target selected media or operate across the connected account’s content, depending on its configuration.

Yes. A Story rule can listen to any Story or a specific Story ID, then apply keyword or any-text-reply matching.

No. Live Instagram output is configured text plus labelled tracked URLs. RelayDM does not claim native button, card or delivered sub-label UI.

Tracked destinations can live in the reusable link library with stored UTM defaults. DM Templates save reusable message text; they do not save an entire trigger, flow or automation.

The current public product does not advertise live {{handle}} personalization. Configure the text that should be sent without relying on an unsupported merge field.

RelayDM evaluates the configured condition before sending. A tracked click or recipient response can stop the relevant pending follow-up. Sending also remains subject to Meta’s messaging window, account eligibility, quota access and configured background processing.

No. The gate advances when the person sends the configured self-attested confirmation phrase. Instagram does not expose an individual follower relationship to RelayDM.

Yes. A Lead Gate can collect an email, email + name, or one qualifying answer before the configured resource is revealed. You can also choose no gate. Any optional user-confirmed follow step is self-attested, not follower verification.

No. Uniqueness is estimated from request fingerprints. It is not an authenticated Instagram identity, read receipt or open event.

No. Conversations is a recent automated-delivery ledger with trigger, status and tracked-link outcomes. It is not a manual reply CRM or full Instagram inbox.

Yes. Audience exports respect the current workspace and filters: CSV provides protected raw lead fields, while PDF creates a branded printable report. RelayDM never exports provider credentials or cross-workspace records.

Signup and workspace creation grant no live access. RelayDM is currently available for paid subscriptions in India, where INR checkout uses Razorpay. International billing is coming later. An eligible workspace can receive one payment-backed trial only after verified authorization. Checkout shows the exact first-charge date, amount and billing interval before approval. The selected cadence bills automatically unless canceled. RelayDM charges zero at setup, though a provider or bank may show a separate temporary authorization. Plan changes never restart a trial.

Monthly subscriptions are charged monthly on the provider billing renewal date. Yearly subscriptions are charged once per year on the annual provider renewal date. Separately, automated-DM quotas reset monthly from the subscription start date for both billing intervals.

RelayDM resolves the billing country server-side before checkout. For launch, only India is available for new paid subscriptions: pricing is INR and checkout uses Razorpay. International billing is coming later. Final billable amounts, currency, provider and plan identity remain server-authoritative.

No. RelayDM automates and measures parts of the path from supported Instagram intent to a tracked destination. Content, audience response and outcomes after the click remain outside that guarantee.