Audience relationships
Invite the conversation before automating it.
A new follower has chosen to see your content. That action alone does not open ordinary API messaging permission. Build growth around useful offers and eligible interactions, not a promise to DM everyone who follows.
4 minute read
A follow and a message are different events
Meta’s Send Messages documentation describes conversations beginning with a message from the Instagram user. Following an account is not that message. Do not treat a follower count, profile visit, or scraped username as evidence that ordinary outbound DMs are permitted. A recipient identifier alone is not sufficient authorization to send.
Comments have a separate private-reply allowance. An eligible comment can receive one private reply within Meta’s documented conditions. That reply is not an unrestricted conversation. Ordinary follow-ups require the recipient to respond. DripDM does not turn a new follow into automatic cold outreach. A clear invitation to message you is more honest than advertising a welcome sequence that ignores these boundaries.
Give people a reason to start
Choose a useful resource that matches the public content. A studio could offer a preparation checklist; a shop could explain a product’s sizing. Tell readers whether they should comment a keyword or send it privately. State what they will receive so the interaction does not become a surprise sales pitch.
An illustrative post instruction is: “Message FIT for the sizing guide.” An illustrative reply is: “Here is the guide. Tell us which measurement needs clarification.” These are sample messages, not evidence of conversion results. Keep the destination usable without demanding unnecessary personal information. A recipient who only wants the resource should not have to navigate unrelated questions or repeated promotional reminders.
Use the growth gate as an explicit step
DripDM’s growth gate is available on paid plans, starting with Pro. It can check the follow relationship within an eligible rule workflow. When the gate applies, the message asks the recipient to follow and reply DONE. The incoming acknowledgment drives a recheck before the configured next step. A follow alone does not send the success message.
Explain that requirement before asking someone to complete it. Do not describe DONE as automatic proof that the person follows. The service checks the relationship, and an unavailable check can prevent release. Existing followers can take a different branch. Test both cases before using the gate publicly. Do not present the gate as a new-follower broadcast or as guaranteed follower retention.
Preserve a useful ungated option
A gate introduces work for the recipient. Decide whether that work fits the offer rather than turning it on everywhere. If the campaign’s purpose is customer support, hiding basic help behind a follow request can create frustration. Keep essential assistance accessible through an appropriate alternative channel.
Review the gate prompt, success destination, and still-not-following message as one experience. Tell recipients to reply DONE rather than to wait for an automatic follower event. If they report a problem, investigate the connected account and conversation instead of requesting repeated comments. Disable an unhelpful rule while correcting it. This is an operational choice, not a claim that every gate increases followers or sales.
Leave unsolicited engagement out of the workflow
Do not confuse responding to your own audience with automatically commenting on unrelated posts, buying followers, or harvesting accounts for outbound contact. Meta Developer Policies prohibit programs facilitating the purchase or exchange of engagement and require appropriate messaging opt-in. DripDM’s messaging workflows are not auto-follow, auto-like, or mass-comment tools.
Respect requests to stop messaging, whether received inside the conversation or elsewhere. Contact deletion and messaging opt-out are separate operational questions; do not assume one action proves every system has stopped. If a recipient no longer wants the interaction, do not push them through a gate. Assign someone to resolve the request and verify the relevant rule and conversation state.
Measure what the workflow actually tells you
Record the offer, trigger, destination, and campaign period before reviewing results. Examine actual deliveries, useful recipient replies, and recorded link taps where available. A link tap does not prove a completed purchase or a lasting follow. Avoid attributing every change in follower count to the automation when content and other campaigns changed too.
Review confused replies alongside successful ones. If people repeatedly ask why they must follow, rewrite the invitation or remove the gate. Keep comparisons tied to observed events, not invented benchmarks. A small workflow with a clear next step is easier to diagnose than several overlapping rules. Growth remains a broader content and relationship problem, not a software guarantee.
Questions
A follow alone does not open ordinary API messaging permission. Use a clearly described eligible interaction instead. This article does not claim DripDM provides new-follower outbound broadcasts.
No. A gated recipient is asked to follow and reply DONE. The acknowledgment leads to a relationship recheck and an eligible next step, rather than an automatic follow-event message.
No. The shared plan configuration enables it on Pro, Growth, and Business. A paid allowance still does not override platform permission, opt-in, or messaging-window requirements.
Keep reading
When a gate helps
Decide whether the extra step fits the resource and audience.
Interpret link activity
Avoid treating a tap as a completed business outcome.
DM limits and permission
Understand why a follower list is not a send list.
Meta: Send Messages
Read the primary description of how conversations begin.