How can we help?

InstaLoop turns the replies you would otherwise send by hand into automations that run on their own. Setting up takes about five minutes.

• Create your account and confirm your email address.
• Connect the social account you want to automate.
• Start from a ready-made template or build a workflow from scratch.
• Activate the automation and watch the results in your dashboard.

Open Settings → Connected accounts and choose the platform you want to add. You'll be sent to that platform's own login screen to approve the permissions InstaLoop needs, then returned to your dashboard.

You always sign in on the platform's site, never inside InstaLoop — we never see or store your social media password.

Go to Automations → New automation. Pick a trigger (what starts the workflow, such as a comment containing a keyword), then add the action that should follow (such as sending a DM).

Test it once before you activate it, so you can see the exact message a follower will receive.

The dashboard is the summary view of everything running on your account: active automations, recent activity, messages sent, leads captured and any errors that need your attention.

Anything showing a warning icon needs action from you — usually a reconnection or a workflow that stopped.

From Settings → Connected accounts, select Add account, choose your platform and complete the login and permission screens shown by that platform. Once you're redirected back, the account appears in your list and is ready to use in automations.

InstaLoop works with the platforms that offer an official automation API, and Instagram Professional accounts (Business or Creator) are the primary supported integration.

The current list is always shown on the Add account screen — if a platform isn't listed there, it isn't supported yet.

Open Settings → Connected accounts, find the account marked as disconnected or expired, and select Reconnect. You'll go through the same approval screen as the first time.

Your automations and their history stay intact — reconnecting only refreshes the authorisation.

Select the account in Settings → Connected accounts and choose Disconnect. InstaLoop immediately stops sending and receiving anything for that account, and any automation that depends on it will pause.

You can also revoke access from the social platform's own security settings.

The connected accounts screen shows each account's status, when it was connected, which permissions were granted and which automations currently use it. Use it to check health before you launch a campaign.

You can connect more than one social account and choose which one each automation runs on. Automations never cross accounts unless you set them up that way.

How many accounts you can connect depends on your plan — see Subscription & Billing.

The exact permissions are listed on the platform's approval screen before you accept. In general InstaLoop asks for access to read your profile and account details, read comments and mentions, read and send messages, and publish or schedule content — but only for the features you use.

Each permission maps to something you asked the product to do. Reading comments is what lets a trigger fire; sending messages is what delivers the reply; publishing access is what allows scheduled posts to go out.

Without a permission, the matching feature simply won't run. We request only what the enabled features need.

Most connection failures come down to one of these:

• The account is a personal profile rather than a Professional (Business or Creator) account.
• A required permission was skipped or denied on the approval screen.
• You were signed into a different account in the same browser.
• The platform is having a temporary outage.

Sign in to the correct account, accept every requested permission, and try again.

Social platforms issue access tokens that expire after a set period, and they also expire early if you change your password or revoke access. When that happens, InstaLoop can no longer act on your behalf and the account is flagged as expired.

This is normal and expected — it just needs a reconnection.

Go to Settings → Connected accounts and select Reconnect next to the expired account. Once it's authorised again, paused automations resume automatically.

Anything that was triggered while the token was expired is not retroactively sent.

An automation is a rule that says "when this happens, do that." It has a trigger (the event that starts it), optional conditions (checks that decide whether to continue) and one or more actions (what InstaLoop does in response).

Once activated, it runs on its own, 24/7, without you being online.

Go to Automations → New automation, then either pick a template for a common use case or start from scratch. Choose the account it runs on, set the trigger, add your actions, and save.

Starting from scratch gives you an empty canvas. Add a trigger block first — nothing can be saved without one — then chain actions and conditions beneath it in the order they should run.

Give the automation a clear name so you can find it later once you have several.

A trigger is the event that starts the workflow. Common triggers include:

• Someone comments on a post, or on a specific post.
• A comment or message contains a keyword you chose.
• You receive a new direct message.
• Someone mentions or replies to your account.
• A schedule you set (for time-based workflows).

Actions are what InstaLoop does once a trigger fires — send a DM, reply to a comment, save the person as a lead, tag a contact, add a delay, or move them into another step of the workflow.

An automation can contain several actions that run in sequence.

Conditions sit between a trigger and an action and decide whether the workflow should continue. For example: only continue if the message contains "price", or only if this person hasn't already received this message.

Conditions are the main tool for keeping automated replies relevant.

Add steps one after another to build a longer journey — reply to the comment, wait a few minutes, send a DM, then ask for an email address. Each step runs only after the previous one succeeds.

Keep the first message short; long automated openers get ignored.

You can restrict when an automation is allowed to run — specific days, business hours, or a fixed start and end date for a promotion. Outside that window the automation stays idle rather than firing.

A new automation stays inactive until you switch it on. Toggle it to Active from the automation list or the editor, and it starts responding to matching events straight away.

Switch the automation to Paused to stop it firing while keeping its setup and history. Anything already in progress finishes, but no new runs start.

Pausing is the safe way to stop something mid-campaign — use it instead of deleting.

Open the automation and change any step, then save. Edits apply to runs that start after you save; runs already in progress finish on the previous version.

For anything more than a wording tweak, pause first, edit, test, then reactivate.

Use Duplicate from the automation's menu to make a copy with all steps intact. The copy is created paused so you can adjust it safely — this is the quickest way to run the same workflow on a different post, keyword or account.

Deleting removes the automation and its configuration permanently and cannot be undone. If you only want it to stop running, pause it instead.

Use the test option in the editor, or trigger the workflow yourself from a second account, to see exactly what a follower receives. Always test before promoting a post that depends on the automation.

Every automation keeps a log of its runs — when it fired, what triggered it, which actions ran and whether each one succeeded. Open the automation and select History to review it.

Open the run in the history log and read the error on the failed step. The usual causes are:

• The connected account's authorisation expired — reconnect it.
• The platform blocks messaging that person (for example, they must message you first).
• You hit a platform rate limit or a plan usage limit.
• The post or content the automation refers to was deleted.

Fix the cause and the next trigger will run normally.

Active — running and responding to events. Paused — set up but not firing. Draft — incomplete and never run. Error — something is blocking it, usually a disconnected account, and it needs your attention.

A campaign is a container for the automations and content that share one objective and one time period — a product launch, a festive offer, a lead-generation push. It lets you start, pause and measure everything together instead of automation by automation.

Go to Campaigns → New campaign, give it a name, set the objective and the dates, then add the automations and content it should include.

The objective tells InstaLoop what to measure as success — replies, leads captured, link clicks or conversions. Campaign reporting is built around whichever objective you pick, so choose it before you launch.

From inside the campaign, choose Add automation to attach an existing workflow or build a new one. An automation can belong to a campaign and still be managed on its own.

Set a start and end date and the campaign's automations activate and stop on their own. This is the safest way to run a limited-time offer — nothing keeps replying about a promotion that has ended.

The campaigns list shows what is live, what is scheduled and what has finished, along with each campaign's headline numbers. Open one to adjust its automations while it runs.

Pausing a campaign pauses every automation inside it in one action, and resuming reactivates them. Use this when you need to stop a promotion immediately.

You can rename a campaign, change its dates, and add or remove automations at any time. Changing the objective after launch affects how results are reported from that point on, so it's best set at the start.

Each campaign has its own report showing conversations started, messages delivered, leads captured and progress against the objective, plus a breakdown by automation so you can see which one is doing the work.

Finished campaigns stay in your account with their full results, so you can compare this month's offer against the last one and reuse whatever performed.

If a campaign shows an error, one of its automations is failing — a disconnected account, a deleted post or a usage limit. Open the campaign, find the automation flagged with an error and check its run history for the specific step that failed.

Open Content → Create, choose the account to publish to, add your media and caption, then either publish immediately, schedule it, or save it as a draft.

Drag your image or video into the composer or select it from your device. The composer shows the size, format and aspect-ratio requirements for the platform you're posting to — files outside those limits are rejected by the platform, not by InstaLoop.

Write the caption in the composer, with hashtags and mentions as you'd type them natively. You can also generate a first draft with AI and edit it — see AI Features.

Choose Schedule in the composer and pick a date and time. Scheduled posts publish automatically as long as the account stays connected — a post scheduled against an expired connection will fail.

All upcoming posts are listed under Content → Scheduled, where you can reschedule, edit or cancel them before they go out.

Open the scheduled post and change the caption, media or time, then save. Edits are only possible before the publish time — once a post is live, edit it on the platform itself.

Select the post in the scheduled list and choose Cancel. It won't be published; you can keep it as a draft or delete it entirely.

The calendar view shows everything published and scheduled across your connected accounts, so you can spot gaps and avoid posting twice in the same slot. Switch between week and month views.

Saving without scheduling keeps a post in Content → Drafts with its media and caption intact. Drafts are never published until you schedule or publish them yourself.

A post marked as failed did not reach the platform. The reason is shown on the post — commonly an expired connection, an unsupported file, a caption over the platform's character limit, or a platform outage.

Fix the cause and republish; InstaLoop does not retry automatically.

Publishing errors come from the social platform rather than from InstaLoop. The most frequent causes are missing publishing permissions, media that doesn't meet the platform's specifications, and rate limits from posting too frequently in a short window.

Pick the target account at the top of the composer before you write. The calendar can be filtered per account, and each account keeps its own drafts and scheduled queue.

You give InstaLoop context — what your business does, your tone, and what a reply should achieve — and it drafts content and replies from that. It suggests; you decide what actually gets sent or published.

In the composer, describe the post you want and generate a draft, then edit it before scheduling. The more specific your description — audience, offer, tone, length — the less editing you'll do afterwards.

Generate a caption from your media or from a short brief, and regenerate until one fits. Captions are drafts, not final copy — always read them before they publish.

InstaLoop can suggest content ideas and reply variations based on your recent posts and the questions your audience actually asks. Treat these as a starting point to adapt, not a schedule to publish blindly.

Inside an automation you can use AI to interpret an incoming message and pick the right response, rather than matching one fixed keyword. This handles the many ways people phrase the same question.

Keep a plain fallback reply for anything the AI can't confidently handle.

A prompt is the instruction that shapes AI output inside a workflow. Good prompts state the role, the goal and the limits — for example: "Reply as a friendly bakery owner, answer only questions about menu and timings, keep it under 200 characters, and never quote prices."

• Read every generated message before it goes live.
• Never let AI state prices, stock, delivery dates or policies without checking.
• Give it your real brand voice, including words you'd never use.
• Keep automated replies short — long AI replies read as automated.
• Hand off to a human for complaints, refunds and anything sensitive.

AI generation is included up to a monthly allowance that depends on your plan. Your current usage is shown in Settings → Usage; once the allowance is reached, AI steps pause until the next cycle or until you upgrade, while your non-AI automations keep running.

If generation fails or returns something unusable, try again with a more specific prompt. AI output can be inaccurate or incomplete, so you remain responsible for reviewing anything published or sent from your account.

The dashboard summarises the current period: automations running, conversations handled, messages sent, leads captured and errors outstanding. Change the date range at the top to compare periods.

Each automation reports how often it triggered, how many actions completed successfully and how many failed. A high trigger count with few completions usually means a condition is filtering people out or an action is being blocked.

Campaign reports roll up every automation in the campaign and measure them against the objective you set, with a per-automation breakdown so you can see which part is carrying the result.

Account-level metrics such as reach, impressions, profile activity and follower change come directly from the platform's API. Figures can lag the platform's own app by a few hours.

Engagement covers comments, replies, mentions and message activity — the interactions your automations respond to. Rising engagement alongside a steady automation success rate is the sign that a workflow is working.

Reach is the number of unique accounts that saw your content; impressions is the total number of views, including repeat views by the same person. Impressions are therefore always equal to or higher than reach.

Conversions count the people who completed the goal you set — shared contact details, clicked your link, or reached the final step of a workflow. Set the objective at the campaign level for these to be tracked.

Reports combine automation, campaign and account metrics for a date range you choose. Build one per campaign or per month, depending on how you review performance.

Use Export on any report to download the underlying data as a file you can open in a spreadsheet. Exports cover the date range currently selected.

The log is the run-by-run record of an automation: the event that triggered it, each step attempted, and the result of each step. It's the fastest way to answer "why did this person get that message?"

Filter the log by status to isolate failures. Each failed action shows the error returned by the platform, which tells you whether the problem is a permission, a limit or the content itself.

A workspace holds a set of connected accounts, automations and team members. Your first workspace is created with your account; add more from the workspace switcher to keep separate brands or clients apart.

Go to Settings → Team → Invite, enter the person's email address and choose their role. They'll get an invitation link and join once they accept and sign in.

The team screen lists everyone with access, their role and their invitation status. From there you can change a role or revoke access at any time.

Roles decide what each person can do — for example an admin who manages billing and connections, an editor who builds and runs automations, and a viewer who can only see results. Assign the lowest role that lets someone do their job.

Permissions follow the role and cover connecting or disconnecting accounts, editing and activating automations, publishing content, viewing analytics, and managing billing and team members.

Admins manage the workspace: connected accounts, team membership and roles, subscription and billing, and workspace-wide settings. Keep at least two admins so you're never locked out.

Use the workspace switcher to move between workspaces. Automations, connected accounts and analytics are kept entirely separate — nothing is shared across workspaces unless you set it up in both.

Select the person in Settings → Team and choose Remove. Their access ends immediately, while the automations and content they created stay in the workspace.

Workspace settings cover the workspace name, time zone, default connected account, notification preferences and defaults applied to new automations. The time zone matters most — scheduling follows it.

InstaLoop is sold as a monthly subscription. The current Growth plan is ₹199 per month, and you can cancel at any time.

Up-to-date pricing is always shown on the pricing section of our site.

Paid plans unlock the full set of automation, AI and analytics features along with higher usage limits. Where a free tier is available it is limited in the number of connected accounts, active automations and monthly actions.

Every plan lists its connected-account limit, active-automation limit, monthly action allowance, AI allowance and team seats. The comparison on the pricing page is the authoritative version.

Upgrade from Settings → Billing. The new limits apply immediately and your billing is adjusted from the change onwards.

Downgrades take effect at the end of your current billing period, so you keep what you've paid for until then. If your usage is above the lower plan's limits, reduce it first — connected accounts or automations over the limit will be paused.

Settings → Billing shows your current plan, renewal date, payment method and invoice history, and is where you upgrade, downgrade or cancel.

Payments are processed by our payment provider and support the usual Indian methods, including credit and debit cards, UPI and net banking. InstaLoop does not store your full card number or CVV — see our Privacy Policy.

Your cycle starts on the day you subscribe and renews on the same date each month unless you cancel first. Your next renewal date is shown in Settings → Billing.

An invoice is generated for every successful payment and stored in your billing history for download. Add your business name and GSTIN in billing settings before your next payment if you need them on the invoice.

If a payment fails we'll email you and retry. Access to paid features may be restricted until the outstanding amount is settled — update your payment method in Settings → Billing to resolve it.

All paid plans include a 14-day money-back guarantee on your first subscription payment. Email helloinstaloop.ai@gmail.com with the subject "Refund Request".

Full details are in our Refund Policy.

Cancel any time from Settings → Billing. You keep access to paid features until the end of the period you've already paid for, and you won't be charged again.

Cancel before the renewal date — cancelling after a renewal doesn't refund that month.

Each plan includes monthly allowances for actions, AI generations and connected accounts, tracked in Settings → Usage. When a limit is reached the related features pause until the next cycle or until you upgrade.

Check you're using the email address you signed up with, and reset your password if you're unsure. If the page won't load at all, try a private window or another browser to rule out a cached session or an extension.

Verification emails can take a few minutes and often land in spam or promotions. Search your inbox for "InstaLoop", and request a new link if the old one has expired — only the most recent link works.

Use Forgot password on the login screen and follow the emailed link. The link is single-use and expires, so request a fresh one if it doesn't work.

Confirm the account is a Professional (Business or Creator) account, that you're signed into the right account in that browser, and that you accepted every permission on the approval screen. Then try connecting again.

This means the platform rejected the authorisation. Sign out of the platform, sign back into the correct account, and start the connection from InstaLoop again rather than from a stale browser tab.

Access tokens expire on a schedule, and immediately if you change your password or revoke access. Reconnect from Settings → Connected accounts and your automations resume.

A permission the feature needs wasn't granted. Disconnect the account, reconnect it, and accept every requested permission — declining one silently disables the feature that depends on it.

Check that it's set to Active, that its account is still connected, that you're inside any schedule window you set, and that you haven't hit a plan usage limit. Those four cover almost every case.

Open the run in the automation's history and read the error on the failing step — it names the cause, usually an expired connection, a platform messaging restriction or a rate limit.

Confirm the trigger is watching the right account and the right post, and check keyword matching — keywords must appear as you configured them. Test by triggering it yourself from another account.

If the trigger fires but the action doesn't run, a condition above it is filtering the person out, or the platform is blocking the action — for example, a DM to someone who has never messaged you first.

A workflow stops mid-way when a step fails or a condition isn't met. The history log shows the last completed step, which tells you exactly where it ended and why.

Check the post's status in Content. Failures are almost always an expired connection, missing publishing permission, or media the platform rejected. Fix the cause and publish again — there's no automatic retry.

The most common reason is that the account's authorisation expired between scheduling and publishing. Reconnect the account and reschedule, and check connections before scheduling far ahead.

Check the file against the format, size, duration and aspect-ratio limits shown in the composer. Very large videos can also time out on a slow connection — re-export smaller and try again.

Platform metrics are fetched on a schedule and can lag by a few hours, so recent activity may not appear immediately. If figures are more than a day stale, check the account is still connected.

First check the selected date range and account filter. Data from before an account was connected is never available, and some metrics depend on permissions that must be granted at connection time.

Refresh, then try a private window to rule out cached files or a browser extension. If it still won't load, email us with your browser, the time it happened and a screenshot — see Contact Support.

Data is encrypted in transit using TLS/HTTPS and at rest where appropriate, passwords are stored using secure hashing, and access to production systems is restricted and logged. Full detail is in our Privacy Policy.

Depending on the platform and the permissions you grant: your profile and account details, post and media metadata, comments, mentions and replies, messages where authorised, and engagement figures. We request only what your enabled features need.

Permissions are granted by you on the platform's own approval screen, and you can review or revoke them there at any time. Revoking a permission disables the InstaLoop feature that relies on it.

Settings → Connected accounts shows every account linked to InstaLoop, what it's authorised for and which automations use it. Disconnect anything you no longer use.

Use a strong, unique password for InstaLoop, don't share your login, and remove team members as soon as they no longer need access. Tell us straight away if you think your account has been accessed by someone else.

Where two-factor authentication is available for your InstaLoop account, enable it in Settings → Security. Separately, keep 2FA switched on for your social accounts — that protects the accounts InstaLoop connects to.

You can request deletion of your account and associated personal information from your account settings, or by emailing helloinstaloop.ai@gmail.com.

Some records, such as billing and transaction history, must be retained where the law requires it — see Data Deletion in our Privacy Policy.

Disconnect from Settings → Connected accounts, or revoke InstaLoop's access from the platform's own settings. Either way, InstaLoop stops sending and receiving for that account immediately.

Our Privacy Policy explains what we collect, how we use it, who we share it with, how long we keep it and what rights you have over it.

Our Terms of Service set out the rules for using InstaLoop, including acceptable use, billing, account termination and liability.

Start from the outcome — a booking, an enquiry, an email address — and work backwards to the fewest steps that get there. Every extra step loses people, so a two-step workflow that completes beats a six-step one that doesn't.

• Sound like a person: short sentences, your normal words.
• Make the first message useful on its own, not just an opener.
• Always leave an obvious way to reach a human.
• Test every workflow from a second account before promoting it.
• Review the logs weekly rather than setting and forgetting.

A loop happens when an automation reacts to something it caused — for example, replying to your own comment and triggering the same rule again. Exclude your own account from triggers, and never let one automation's action match another's trigger.

Specific triggers beat broad ones. Watch one post or a tight keyword set rather than every comment, and account for the variations people actually type, including short forms and common misspellings.

Conditions are what keep automated replies relevant. Use them to check what the person asked, whether they've already had this message, and whether they're an existing contact — then branch instead of sending everyone the same thing.

Name automations for what they do and where they run ("Reel #14 — price enquiry → DM"), and check for overlapping triggers before activating a new one. Two automations watching the same keyword will both fire.

Add a condition that excludes anyone who has already received the message, and avoid running two automations on the same trigger. Duplicate DMs are the fastest way to get muted or reported.

Post when your audience is actually active rather than when it suits you, keep a steady rhythm instead of bursts, and add a short delay before automated replies so they don't arrive suspiciously fast.

Watch the success rate, not just the trigger count. A drop usually means an expired connection, a platform change or a workflow that no longer matches how people are writing to you.

Scale what's already proven: duplicate the automation that works onto more posts or another account, and change one thing at a time so you can tell what caused a change in results.

API access lets you work with your InstaLoop data from your own systems — reading automations and results, and creating or updating records programmatically.

API access isn't enabled on every plan. Email helloinstaloop.ai@gmail.com to check availability for your account.

Requests are authenticated with an API key sent in the request headers, over HTTPS. Requests without a valid key, or over plain HTTP, are rejected.

Keys are generated and revoked from your account settings once API access is enabled. Treat a key like a password: never commit it to a repository or ship it in front-end code, and revoke it immediately if it's exposed.

The reference covering endpoints, parameters, responses and error codes is provided when API access is enabled for your account. Email us if you need a copy before deciding whether to build against it.

Webhooks push events to a URL you host as they happen, so you don't have to poll. Your endpoint should respond quickly, verify each request before trusting it, and handle the same event arriving more than once.

Requests are rate limited to keep the service stable for everyone. Handle a rate-limit response by backing off and retrying rather than repeating the request immediately.

Errors return a standard HTTP status with a message describing the cause — commonly an invalid or revoked key, a missing parameter, a record that doesn't exist, or a rate limit. Log the full response body when reporting a problem to us.

Beyond the API, InstaLoop can be connected to other tools so leads and events flow into the systems you already use. Tell us what you need to connect and we'll confirm what's possible today.

• Is there a sandbox? Use a separate test workspace and a dedicated key.
• Can I use it from the browser? No — keys must stay server-side.
• Are there SDKs? The API is plain HTTPS and JSON, usable from any language.
• Who do I ask? Email helloinstaloop.ai@gmail.com.