About

A small team, building one sharp product.

ReplyMagic exists because creators were drowning in DMs and the only "fix" on the market was a keyword bot from 2017.

Why we built it

The DM tab became a full-time job.

"Same five questions. Price. Sizes. Where to buy. When it ships. Is it still in stock."
— Every creator we spoke to

A product launch, a viral reel, a flood of comments and DMs — most of them asking the same handful of questions in slightly different phrasings.

The existing tools tried to solve this with keyword triggers. The result felt exactly like a keyword bot — stiff, off-voice, and useless the moment a customer phrased the question differently. So replies stayed manual, and growth quietly capped at "however many DMs the founder can answer at midnight".

We thought there was a better way: feed the assistant the same context a human team would have — the product, the offer, the voice — and let it answer comments the way you would, in your tone, while you focus on the work that actually needs you.

What we believe

Three things, in order of stubbornness.

01
Context beats cleverness

A model with the right product info will out-perform a more capable model that's guessing — every time.

02
Voice is non-negotiable

Replies that sound like a help desk lose the trust that brought the customer in. The voice profile is the product.

03
Official channels only

We use the official Instagram Graph API. No scraping, no proxies, no risk to your account.

The studio

Built inside ZipLyne.

A small AI product studio. Tight portfolio of vertical AI tools rather than spread thin across a dozen ideas. ReplyMagic gets the lion's share of our attention.

The team is engineering-led, design-obsessed, and customer-close. You'll often hear back from someone who actually wrote the code.

Want to see the context engine on your account?