Free tool
Draft the public reply.
The public reply points to the inbox. The link stays in the DM.
2 minute read
Sent. Check your DMs for LINK.
Done — the link is in your inbox.
On its way. Look for a message from us.
Keep the public reply short. Put the link in the private DM.
How to read the result
Keep it short. A long public reply hides the keyword other people need to see.
The tool runs in your browser. It does not send the numbers to DripDM.
A public acknowledgment should match delivery reality
Enter the keyword and review the public-response drafts. These are template suggestions, not messages posted to Instagram. Their job is to acknowledge the request and tell the person where to look. Keep the resource destination in the private handoff where that is the advertised workflow, and keep personal details out of the public reply. The generator cannot verify whether a DM was actually accepted or reached the recipient.
Using the inputs and result
Choose a line that matches the timing and certainty of your configured flow. If a suggestion says sent, verify how your automation handles private delivery failures before using that wording unconditionally. An acknowledgment can invite the person to check requests without publishing their email or repeating a long sales pitch. Pair the public text with the actual private message and inspect them together from an independent account. The two should refer to the same keyword and offer.
Limits and result checks
A short public reply is not proof of private delivery. If someone says no DM arrived, inspect the account, rule scope, recipient eligibility, requests, and send result rather than posting repeated assurances. Do not use this tool to automate unsolicited comments on other people’s posts. It drafts text for your configured response to an eligible event. Keep wording current when a keyword or resource changes, and test a fresh comment instead of assuming an old already-replied comment can receive another private message.
Coordinate the public and private copy owner
When the private destination changes, have the same review process check the acknowledgment so it still describes what the recipient should expect. Keep support alternatives practical when requests are filtered or delivery is unavailable. Do not publish private contact details as evidence that you replied. A short public line should guide, not pressure, the person. Verify the actual configured delivery path instead of relying on a draft that says done, and preserve the send result when someone reports the promised message is missing.
Questions
No. Copy the result into your caption, bio, or a DripDM rule.
Only when that wording matches the actual configured outcome. The generator cannot verify delivery. Prefer an acknowledgment you can stand behind, and inspect private-send failures separately so the public response does not promise a resource that never became available.
No. It drafts public text only. Inspect the private send result and independent recipient test before claiming delivery. Keep public acknowledgment and private fulfillment as separate checks.