ManyChat Tells You Who Commented. Zippy Tells You Who Actually Opened the App.
Comment-to-DM automation delivers the message, then the link opens Instagram's in-app browser and the sale dies. Here's the fix that works today, and the native Instagram automations we've built behind it — including the honest bit about Meta approval.
⚡ Zippy: the DM got opened. don't lose it in the last three centimeters.
Comment-to-DM is the best-converting thing on Instagram right now. You write "comment LINK" in the caption, a few hundred people do, and every one of them gets a DM with your link in it. ManyChat built a whole company on this and deserved to.
Then comes the part nobody puts in the case study. They tap the link, and it opens in Instagram's in-app browser.
The in-app browser is eating money you already earned
That webview is a browser, technically. It is also:
- A place nobody is logged in. Your shop, your course platform, YouTube, Spotify — the session that exists in their real app does not exist in here. They're a stranger again.
- A checkout with no Apple Pay. No autofill, no saved cards, no one-tap anything. A buyer who had already decided now has to type a card number with their thumbs, inside a cramped webview, standing on a train.
- A blind spot for your pixel. Webview cookies are sandboxed. The click happened; your retargeting audience, your affiliate attribution, your conversion tracking never saw it.
None of that is ManyChat's fault. Instagram decides where a tap opens, and ManyChat's job ends the moment the message is delivered. But it is your problem, because it lands squarely on the funnel step you paid the most to reach: the person who already read your caption, already commented, already opened the DM, already tapped.
You won every hard step and lost on the last three centimeters.
The number that exposes it — and why nobody shows you
Ask a comment-to-DM tool how a campaign went and you get: comments matched, DMs sent, link clicks. All three can be excellent while your revenue is flat, and none of them tell you why.
The missing number is what happened after the tap. Did the person land in the real native app, where they're logged in and their card is saved? Or did they land in the webview and bounce?
No automation tool can answer that, and it isn't laziness — it's architecture. The tool's knowledge ends at "the link was clicked", because the tool is not the thing the link goes through. A link tool is.
Every DM Zippy sends carries a Zippy link. So the same tap that ManyChat counts as a click, we resolve as an outcome:
- opened — they reached the real app. This is the one that pays.
- browser — the webview won.
- broken — the hand-off went nowhere useful.
"My DM automation gets clicks but no sales" stops being a mystery and becomes a number with a cause.
The fix you can do today, in two minutes
You don't have to leave ManyChat, and you don't have to wait for us.
- Paste your destination at app.zipthe.link and copy the short link.
- In your ManyChat flow, replace the raw URL with that one. Publish.
That's the whole change. When the tap comes from inside Instagram, Zippy detects the webview and springs the real app — YouTube opens YouTube, a product link opens where their card lives. Wrong platform, desktop, or the app isn't installed? It degrades to a normal redirect. A link never breaks.
Works on any ManyChat plan, because a Zippy link is just a URL. Full recipe, including the External Request block for a link per subscriber: the ManyChat docs page, or the deep dive.
And the native version we've been building
Here's where we'd normally sell you the roadmap. Instead, the truth.
We've built Instagram DM automations natively into Zippy — the whole thing. Comment triggers, DM keyword triggers, story replies, story mentions. A rule builder with a live preview of the exact message your follower receives. Public replies under the comment. Tags on everyone who answered. Per-rule stats that show sends and app opens.
And a set of refusals we're prouder of than the features:
- You cannot type a link into the DM text. The link is attached structurally, so every DM we send is measurable and springs the app. Paste a raw URL and the rule won't save.
- Every send is a reply to a specific person who just interacted with you. There is no audience field. You could not build a bulk DM blaster out of these parts without adding one on purpose.
- When Instagram's rules are unclear, we don't send. Comment older than 7 days, DM older than 24 hours, a live-video comment, a missing timestamp — all skipped, each one shown to you with a plain-English reason. A restricted account is not something we can hand back.
What we cannot do is let you use it yet. There is no Meta app to connect to, and App Review hasn't been submitted. Meta requires a working app to review — you record a screencast of it — which is exactly why it gets built first. When a Meta app is approved it goes live; until then the connect button says so in those words rather than pretending.
We're telling you this in the same post where we're pitching you. The setup page has the full built-vs-not table, line by line.
Meanwhile, the ManyChat swap above gets you the entire wedge — the app opens, and the number that proves it — with nothing to approve and nobody to wait for.
What to do with the people who answer
A DM automation isn't the end of a funnel, it's the front of one. Once someone has commented, been DM'd, tapped, and landed in your real app, they're the most qualified person you'll meet this month.
- Audience segments — a saved slice like "US · iPhone · actually opened the app". Filter to opened and that's your true-fan list, not your follower count.
- Email capture — turn a tap into a contact you own. Instagram can throttle your reach tomorrow; an inbox can't be throttled by anyone. We wrote about why that matters in own your audience.
- Webhooks —
app.openedfires the instant a DM tap resolves, so your own stack can react without polling anything.
FAQ
How do I auto-DM people who comment on my Instagram post?
You need a comment-to-DM automation and a Professional Instagram account. Today, the reliable route is ManyChat (or a similar tool) with a Zippy link pasted into the flow instead of a raw URL — that way the DM gets delivered and the link opens the real app rather than Instagram's in-app browser. Zippy's own native comment-to-DM automations are built but not yet connectable, because our Meta app hasn't been through App Review.
Why do my ManyChat links open in the wrong browser?
Because Instagram never hands the tap to your phone's browser. It opens the URL in its own webview inside the Instagram app, and that's Instagram's decision, not your automation tool's. A Zippy link detects the webview and springs the real native app instead.
Why does my DM automation get clicks but no sales?
Almost always because the clicks are landing in the in-app browser, where the buyer is logged out and has no Apple Pay. The click counter still counts them, which is why the numbers look fine while revenue doesn't. Check your link's app-open rate — the share of taps that reached the real app — and you'll usually find the gap there.
Can I see who actually opened the app, not just who clicked?
That's the number Zippy reports and a click counter structurally can't: every tap resolves to opened, browser, or broken. Rates are a sampled estimate and are labelled as such, and a link with no measured taps yet shows no rate at all rather than a misleading 0%.
Do I need a Facebook Page to automate Instagram DMs?
No. Zippy uses Instagram Login, and Meta's documentation for that setup states plainly that it does not require a Facebook Page to be linked to the Instagram professional account. You need two things, both free and both inside the Instagram app: a Professional account (Creator or Business), and "allow access to messages" turned on.
Tools that do demand a Page are using Meta's other flow, Facebook Login for Business — that's an integration choice on their side, not a rule Instagram imposes on you. The setup checklist walks both steps.
Is Zippy's Instagram automation available right now?
No, and we'd rather say it here than in a support ticket. It's built, tested, and dark behind a flag; there is no Meta app to connect to and App Review hasn't been submitted. The ManyChat + Zippy link recipe delivers the same app-open outcome today, on any plan.