Instagram Comment Auto Reply With DM Follow-Up

In 2026, most Instagram automation tools handle one step. Someone comments a keyword, and they get a DM. That's it. Conversation over. But the real value isn't in the first message — it's in the follow-up. The second message. The third. The one that actually converts a curious commenter into a paying customer.

Instagram comment auto-reply with a DM follow-up is a two-stage automation. Stage one: detect a keyword in a comment, send an instant DM with the information requested. Stage two: send a follow-up DM hours or days later with a case study, testimonial, or limited-time offer. The first message captures the lead. The second message closes the deal.

This post covers the technical architecture behind this two-stage pipeline, the rate limit constraints that shape how you space follow-ups, the webhook payload structure that makes it work, and how to integrate the whole thing into your existing stack.

Why One-Stage Automation Isn't Enough in 2026

A single DM response to a comment is a conversation starter. It's not a sales pipeline. Someone comments "PRICE" on your Reel, gets your pricing link, and that's the end of the interaction. They have the information. They might buy. They might not. You have no mechanism to nudge them.

The follow-up changes this. The first DM delivers what they asked for. The second DM — sent two hours later — asks if they have questions. The third DM — sent two days later — shares a case study or testimonial. The fourth DM — sent a week later — offers a limited-time discount.

Each message moves the conversation forward. Each message keeps your brand in their inbox. And each message is timed to arrive when they're most likely to act, not when you happen to have time to type a response.

The challenge is that Instagram enforces a 24-hour messaging window. Once a user messages you, you have 24 hours to reply freely. After that, you need special tags. Your follow-up sequence has to respect this constraint — or the messages get blocked.

The Technical Architecture

Stage 1: Comment Detection and First DM

The first stage is a webhook-driven pipeline. Instagram fires a webhook event when a new comment lands on your post. Your server receives the event, classifies the intent, and sends a DM response through the Graph API.

Here's the minimal webhook handler:

app.post('/webhook', (req, res) => {
  const { object, entry } = req.body;
  if (object !== 'instagram') return res.sendStatus(404);

  entry.forEach(event => {
    event.changes.forEach(change => {
      if (change.field === 'comments') {
        const { text, id: commentId, username } = change.value;
        const mediaId = event.id;

        // Classify intent
        const intent = classifyIntent(text);

        if (intent.isAutoReply) {
          // Send first DM
          sendDM({
            recipientId: change.value.from.id,
            text: intent.replyTemplate,
            mediaId: mediaId
          });

          // Queue follow-up
          queueFollowUp({
            userId: change.value.from.id,
            username: username,
            followUpStep: 1,
            scheduledAt: Date.now() + (2 * 60 * 60 * 1000) // 2 hours
          });
        }
      }
    });
  });

  res.sendStatus(200);
});

The queueFollowUp function pushes a follow-up task into a delayed queue — Redis, Bull, or a cron-based scheduler. The task sits there until the scheduled time, then fires.

Stage 2: Timed Follow-Up Sequence

The follow-up worker pulls tasks from the queue and sends messages through the Graph API. Each follow-up message checks the 24-hour window before sending. If the window has closed, the worker uses the HUMAN_AGENT tag (extends to 7 days) or skips the message.

async function processFollowUp(task) {
  // Check 24-hour window
  const lastInteraction = await getLastInteraction(task.userId);
  const hoursSince = (Date.now() - lastInteraction) / (1000 * 60 * 60);

  if (hoursSince > 24) {
    // Window closed — use HUMAN_AGENT tag or skip
    if (task.supportsHumanAgent) {
      await sendDMWithTag(task.userId, task.message, 'HUMAN_AGENT');
    } else {
      console.log(`Skipping follow-up for ${task.username} — window closed`);
      return;
    }
  } else {
    await sendDM(task.userId, task.message);
  }

  // Schedule next follow-up if exists
  if (task.nextStep) {
    queueFollowUp({
      ...task,
      followUpStep: task.nextStep,
      scheduledAt: Date.now() + task.nextDelay
    });
  }
}

The Follow-Up Sequence Pattern

A typical sequence looks like this:

• Message 1 (immediate): "Hey! Here's the pricing guide you asked for: [link]"
• Message 2 (+2 hours): "Did you get a chance to look at the pricing? Happy to answer any questions."
• Message 3 (+2 days): "Here's how [customer name] used this to [result]: [case study link]"
• Message 4 (+7 days): "Quick heads up — we're running a 15% discount this week. Use code SAVE15 at checkout."

Each message is spaced to respect the 24-hour window while maintaining momentum. The key is that each follow-up adds value — it doesn't just repeat the first message.

Rate Limit Constraints

Instagram's Graph API enforces multiple limits that affect your follow-up pipeline.

Per-Hour Limits

750 calls per hour for private replies to comments. 200 calls per hour for general API calls. These are separate budgets per account. If your follow-up sequence sends messages to the same account, you need to track both limits.

The 24-Hour Window

This is the critical constraint for follow-ups. Once a user messages you, you have 24 hours to reply freely. After that, you need the HUMAN_AGENT tag, which extends the window to 7 days but requires special permission from Meta.

For most follow-up sequences, spacing messages within the 24-hour window is sufficient. Two or three follow-ups delivered within 24 hours covers most sales cycles. If you need longer sequences, you'll need HUMAN_AGENT permission.

Monitoring Compliance

Parse the X-Business-Use-Case-Usage header on every API response:

{
  "ig_api_usage": [{
    "acc_id_util_pct": 65,
    "reset_time_duration": 3600
  }]
}

When utilization crosses 80 percent, pause follow-up sends and queue them for the next window. Don't wait for a 429 error — by then your queue is backed up.

The Webhook Payload for Follow-Up Sequences

If you're using a tool like InstantDM instead of building from scratch, the webhook payload includes everything you need for follow-up routing.

{
  "flow_id": "5a0441b5-6589-4452-b8bf-90902c865893",
  "flow_name": "Lead Capture Flow",
  "sender_id": "2031528510825908",
  "sender_username": "__zain_z",
  "completed_at": "2026-05-06 04:46:15.654321",
  "tags": ["hot-lead", "interested"],
  "response_variables": {
    "user_name": "Zain",
    "email": "[e-mail]",
    "interest": "pricing"
  }
}

The tags array tells you which follow-up sequence to trigger. "hot-lead" might trigger an aggressive follow-up (2 hours, 2 days, 7 days). "interested" might trigger a gentler sequence (24 hours, 3 days, 7 days). The response_variables give you the data to personalize each follow-up — "Hey Zain, did you get a chance to look at the pricing?" beats "Hey there, did you get a chance to look at the pricing?"

You route this payload to a scheduler (Make.com, n8n, or your own cron system) that triggers the follow-up sequence based on the tags.

Building the Follow-Up Scheduler in 2026

Option 1: Make.com Scenario

In Make.com, create a scenario with your tool's webhook as the trigger. Add a Router module that routes based on tags. Each tag routes to a different sequence — different delays, different messages.

For each follow-up step, add a Sleep module (2 hours, 2 days, etc.) followed by an HTTP module that sends the follow-up message through your tool's API. The Sleep module handles the timing. The HTTP module handles the delivery.

Option 2: Custom Queue

If you're building from scratch, use a job queue with delayed tasks. Redis with Bull, AWS SQS with delayed messages, or a cron-based scheduler. Each follow-up is a delayed job that fires at the scheduled time, checks the 24-hour window, and sends the message.

Option 3: Database + Cron

The simplest approach. Store follow-up tasks in a database with a scheduled_at timestamp. Run a cron job every minute that queries for tasks where scheduled_at <= now, sends the messages, and marks them complete. Simple, reliable, easy to debug.

The Developer's Decision in 2026

Building the two-stage pipeline from scratch gives you full control. You own the follow-up logic, the timing, the personalization, and the rate limit compliance. The trade-off is engineering time — OAuth token management, webhook verification, error handling, and ongoing maintenance when Instagram's API changes.

Using a tool's API gives you the structured webhook payload, the rate limit compliance, and the follow-up scheduling without building the Instagram layer yourself. You focus on what happens after the data arrives — the routing, the personalization, the integration with your existing systems.

InstantDM (instantdm.com) handles the Instagram layer as an official Meta Business Partner. Their webhook payload gives you the structured data — tags, response variables, timestamps — to trigger follow-up sequences. Their rate limit compliance monitors Meta's headers and throttles at 80 percent utilization. Their Dedicated Safety Queues handle traffic spikes automatically.

The pricing is flat — $9.99 per month for unlimited DMs. No per-contact overages. For developers building follow-up sequences, this means predictable costs regardless of how many leads your comments generate.

The integration options include native Make.com and Zapier support. You can route the webhook payload to your scheduler, CRM, or custom backend without building middleware.

For most development teams, the question is whether the engineering time spent building and maintaining Instagram's API integration is worth more than the $9.99/month the tool costs. For a follow-up sequence that runs for months or years, the math usually favors the tool.

The real engineering value isn't in the first DM. It's in the follow-up — the sequence that turns a curious commenter into a customer. Build that sequence, respect the rate limits, and measure what converts.