A useful Instagram auto-reply delivers what the person requested, explains the next step, and leaves room for a real question. The 25 examples below cover common resource, product, booking, and support situations. They are message templates, not permission to send each message to any account or chain them into an unrestricted sequence.
Replace bracketed details with the actual resource, link, date, or service before use. Choose a matching eligible trigger and check the Instagram automation rules, especially when a reply would follow an earlier comment-triggered message.
What makes an auto-reply feel useful?
Be specific about the request. “Here’s the size guide from the linen-shirt post” gives more context than “Thanks for your interest.” If someone interacted with several accounts, that context helps them recognize why your message arrived.
Use one main next step. A message carrying a worksheet, a course promotion, a newsletter signup, three affiliate links, and a calendar makes it hard to know what to do first. Deliver the promised item, then let subsequent conversation develop from eligible responses.
Keep commitments accurate. Do not say someone is booked, entered in a draw, approved for a program, or guaranteed a discount if your system has not established it. Link delivery is useful even without inflating what it proves.
Resource delivery examples
1. A checklist requested through a comment
“Here’s the [topic] checklist from the post: [resource link]. Start with the first section. If anything is unclear, reply with your question.”
Use it when the post names a specific checklist. Keep the linked resource aligned with the promise rather than redirecting to a general homepage.
2. A recipe from a Reel
“Here’s the ingredient list and method for the recipe you asked about: [recipe link]. The page also includes the serving size and substitutions.”
Only mention substitutions if the page contains them. Specific copy should describe the real destination, not embellish it.
3. A beginner worksheet
“This is the beginner worksheet I mentioned: [worksheet link]. You can use it without booking a call. Start with the section marked [section name].”
Use the reassurance only when it is true. A worksheet hidden behind a mandatory appointment would contradict the message.
4. A sample lesson
“Here’s the sample lesson from [course]: [preview link]. It shows the format and starting level so you can decide whether the full course fits.”
This is a preview invitation, not a claim that the lesson produces a guaranteed learning or earnings outcome.
5. A channel invitation
“Here’s the [channel name] invitation: [channel link]. I share [actual update type] there. Join if those updates would be useful.”
Sending the invitation does not add the person automatically. See broadcast-channel invitations.
Product inquiry examples
6. A product link
“Here’s the [product name] from the post: [product link]. The page has the current price, options, and availability.”
Keep changing prices on the destination when possible, rather than letting an old message quote an outdated amount.
7. A sizing guide
“Here’s the size guide for [item]: [guide link]. Compare the listed measurements with an item that fits you before choosing.”
This gives a practical next step without guaranteeing fit for a person the business has not assessed.
8. Shipping information
“Shipping options and estimated times are listed here: [shipping page]. If you have an existing order question, reply with [appropriate reference].”
Ask for a reference only if your support process uses it. Do not request payment credentials in DM.
9. A restock information page
“The latest availability for [item] is here: [product link]. If a restock signup is available, the page explains how to request updates.”
Do not promise a restock notification if no notification process exists. The DM link and the signup are separate steps.
10. An affiliate product request
“Here’s the [item] link you asked for: [link]. This is an affiliate link; I may earn a commission if you buy through it.”
Use the disclosure that fits your actual relationship and applicable requirements. Do not call a paid recommendation independent.
Booking and coaching examples
11. A discovery-call page
“Here’s the information and booking page for [service]: [calendar link]. It explains who the call is for and what to prepare.”
The link does not reserve a slot. Let the calendar handle actual availability and confirmation.
12. Appointment formats
“You can see the current online and in-person options here: [service page]. If your situation needs a different arrangement, reply and a person will review it.”
Only promise human review if someone owns that task. A handoff without an owner becomes an unanswered request.
13. A program application
“Here’s the application for [program]: [application link]. Submitting it requests a fit review; it does not confirm admission.”
Use this when acceptance actually depends on review. Avoid copy that implies a place is secured before assessment.
14. Workshop registration
“The [workshop] registration page is here: [event link]. It lists the date, timezone, price, and replay details.”
Check every listed detail. If the event has ended, revise or pause the automation instead of sending expired registration information.
15. A service pricing page
“The current [service] packages and prices are here: [pricing link]. Reply if you need clarification about what a package includes.”
Useful pricing information reduces repetitive questions without forcing the person into a sales call just to learn the price.
Lead capture and entry examples
16. A disclosed email request
“To continue with the [resource] request, what email should I save? The post explains how the address will be used.”
The referenced explanation must exist. Do not use this sentence as a substitute for a clear signup and privacy process.
17. Delivery after the capture step
“Thanks—here’s the [resource] access link: [URL]. If the link does not open, reply with the problem you see.”
Do not say “I emailed it” unless an email service actually performs that delivery. AutomateDM capture is separate from email sending.
18. A giveaway entry page
“Here’s the entry page for [giveaway]: [URL]. It explains eligibility and the closing time. Requesting the link alone does not complete entry.”
Use this for a form-based giveaway. A different entry method needs different wording; see the giveaway workflow.
19. A free event information request
“The details for [event] are here: [URL]. Check the location, date, and any registration requirement before attending.”
A link to directions should not imply admission is guaranteed when the event has capacity or registration rules.
20. A waitlist request
“Here’s the [offer] waitlist page: [URL]. It explains what updates you can request and whether joining guarantees anything.”
Do not promise priority access or a reserved place unless the waitlist process actually provides it.
Clarification and human handoff examples
21. A first-message orientation
“Thanks for contacting [business]. Product details are at [URL]. If your question is about an existing order or another issue, describe it here.”
Use a supported first-message workflow. Keep the destination helpful, and do not trap every question in a link-only response.
22. A message outside working hours
“Thanks for the message. Our usual reply hours are [hours and timezone]. Please describe your question here so we can review it when available.”
Only configure this for a trigger and schedule the product supports. Writing an out-of-hours script does not create a scheduling feature.
23. An individual review handoff
“This needs a person to review it. Please describe the issue without sharing passwords or payment details. Our team will respond through the usual support process.”
Use it when the team actually monitors the resulting conversation. Avoid promising a response deadline you cannot meet.
24. A broken resource fallback
“If the resource link is not opening, you can also find [resource name] at [public fallback URL]. Reply with the error you see if that does not work.”
Make the fallback a maintained destination, not a second copy of the same broken link.
25. A clearer public comment reply
“Check your DMs and requests for the [resource] link.”
This sets an expectation without claiming confirmed main-inbox delivery. Use it as a public reply where your configured workflow supports that step.
How do you turn these scripts into a working automation?
Choose one script and one matching interaction. In AutomateDM, connect the professional account, create the appropriate trigger, select the intended media if needed, and add the actual link. The comment-to-DM guide covers the common keyword-comment flow.
Test from a separate account, then inspect both the message and the destination. Verify optional gates separately. A script can be well written while the selected post, keyword, or link is wrong.
Free supports basic text-and-link campaigns. Media messages, tracked links, CSV export, and some other features require a paid plan. Check pricing before assuming a script’s surrounding workflow is available on your subscription.
The template catalog and Instagram automation overview help connect the message to a supported recipe. Choose a template for the actual job, rather than chaining all 25 examples into one campaign.
Frequently asked questions
Can I copy these messages directly?
Replace every illustrative placeholder and verify every commitment first. A generic example is not ready for your campaign until it matches the offer and process.
Will changing words prevent spam restrictions?
No wording trick guarantees safety. Relevance, eligibility, behavior, and platform rules matter; variation is not permission to send unwanted messages.
Should I pretend the message is typed personally?
Use clear, natural wording without creating a false impression about individual review. Deliver the request and provide a real handoff when needed.
Are public replies proof that the DM arrived?
No. A public reply should direct the person where to look without overstating delivery evidence.