Deliver your Instagram lead magnet automatically by DM.

Start with a promise people can verify

Imagine a creator publishing a Reel about planning a product launch. The caption promises a one-page checklist and says: “Comment CHECKLIST and I’ll send it in Direct.” That sentence tells the reader what they will receive, how to request it, and where the next step happens.

The automation should preserve that clarity. It is not a substitute for a useful resource or a truthful caption. Its job is to recognize an eligible request and carry the promise into a private conversation without making the person guess what happened.

In levios, the creator chooses the relevant post or Reel, defines the comment trigger, writes an optional public reply, configures the first DM, and checks the phone preview. The reviewed product flow can also save the contact created by the interaction.

A simple message sequence

The public reply can be short and contextual:

Example public reply: “I sent you the next step in Direct.”

The initial private reply should identify the resource and explain any action needed before another automated message can be sent:

Example first DM: “I have the launch checklist ready. Reply CHECKLIST here and I’ll send the access link.”

After the person replies, the follow-up can deliver the promised destination:

Example follow-up: “Here is the checklist: [your reviewed link]. Save it before planning your next launch.”

These are examples, not proof of a customer outcome. Replace the placeholder with a destination you control, verify that it works on mobile, and make sure the page matches the promise in the post.

Meta’s current Instagram API documentation distinguishes a private reply to a comment from an open messaging conversation. It documents one private reply to the commenter; follow-up messages depend on the recipient responding and then fall within the applicable messaging window. That is why the first DM should not conceal a required response.

What to test before publishing

Use a second Instagram account and follow the same path a visitor will take. Comment the exact keyword on the selected post. Confirm whether the public acknowledgement appears, whether the first DM reaches the correct inbox or request folder, and whether its instructions are understandable without the original caption open.

Then perform the requested interaction and confirm that the resource link arrives. Check the link, the resource title, access permissions, and mobile layout. Also test a comment that should not match, so a broad trigger does not turn unrelated discussion into an unsolicited DM.

Watch the operational status rather than assuming every platform call succeeds. A deleted comment, changed permission, disconnected professional account, duplicate event, or platform error can interrupt delivery. The useful response is a visible status and a fix, not a claim of guaranteed delivery.

Keep the use case narrow

One post can promise one concrete resource to one recognizable audience. If a caption offers several unrelated downloads, the trigger and first message become harder to understand. Separate those promises into different posts or explicit keywords.

A good resource-delivery automation feels like a continuation of the post: the public call to action, private message, and destination all say the same thing. That consistency is more valuable than adding branches before the basic path has been tested.

Sources and review dates

• Meta Instagram API documentation
• levios product overview
• Meta Instagram private replies