Creator guide
Written for the first hour and the first bad week. Nothing here needs a paid plan to try.
The single most common setup mistake: commenting from the same account that owns the post. Borrow a friend's phone.
A flow is one sentence: when someone does X, send them Y. Instagram tells us the moment a comment lands, we check it against your keywords, and if it matches we send the DM. In practice that is a few seconds.
Instagram lets you send one private reply to a comment, within 7 days of when it was posted. A story reply or a mention works differently: it opens a 24-hour window to message that person. Either way, an Auto DM sent seconds after the comment is the one that reliably lands.
Write the DM as a reply, not a broadcast. The message that performs best is short, references what they commented, and has one link. Three links and a paragraph of hype reads as spam and gets reported.
One credit, one thing done. There is nothing else to decode.
Free includes 1,000 DM & comment credits a month, Pro 40,000, Business 350,000. The allowance refills every month and does not roll over.
Credit packs never expire, and your monthly allowance is always spent first — so a pack you buy in March is untouched until a month where you actually run out. That ordering is deliberate: you should never lose something you paid for because a free allowance was sitting beside it.
Pro covers 2 accounts and Business 5. Switch between them from the sidebar; flows, analytics and the inbox all follow whichever one you are on.
Credits are pooled, not split. Five accounts on Business share one balance of 350,000 rather than getting a fifth each. A quiet account is not wasting an allowance, and a month where one account goes viral can use the whole pool.
If a manager or an editor runs some of your accounts, give them a team seat rather than your password. Settings → Team.
Removing a seat takes their login away and hands their profiles back to you. Everything they built stays — it was always in your workspace.
Build an invoice from the posts you actually delivered, get a PDF and a shareable link, and send it to the brand. Set your prefix, default currency and, if you're in India, your GSTIN once in Settings, and every invoice inherits them.
One invoice costs one invoice credit. Free includes 20 a month, Pro 50, Business 200 — and you can top up.
AI Studio writes flows in 12 languages, including Arabic and Hindi, and generates virtual try-on images from a product photo. Each generation costs AI credits.
A failed generation costs you nothing. The credit goes straight back to your balance — you do not have to ask, and you do not have to notice.
Your store is a page at instoly.store/yourname that shows your Instagram posts with the products you used in each. Followers tap the link in your bio, pick a post, and go straight to the product.
To add a post, open My Store, tap +, choose a reel, photo or carousel, and paste up to 3 product links. We fill in the picture, name and price where the shop shares them; anything missing, you type. Add the original price and the card shows the % off.
Free holds 6 posts and uses your Instagram picture, name and bio, with a link name that is usually your Instagram username. Pro and Business add unlimited posts, your own look, categories, Featured and a link name you choose.
Instagram sends one message per comment. So an Auto DM on a post can send either your message or that post's product cards, not both. When a post has both, we ask which you want.
My Store's Analytics tab shows how many times your store and each post were opened, and which products were tapped.
Instoly runs on Instagram's official API, which means we are bound by their rules and we will not build around them. Worth knowing, because most "why did that not send" questions are one of these:
Meta expires access periodically, and always if you change your Instagram password. Reconnect from Settings; your flows, history and analytics are untouched.
Almost always the keyword. Check for a typo you did not anticipate, or switch from exact match to contains.
Contact support with the post link and roughly when it happened — that is enough for us to find the exact event in the logs.