How CommentLink Paces DMs When a Reel Goes Viral

When a Reel goes viral, the constraint is not your copy. It is how many automated Instagram DMs Meta will accept in an hour. CommentLink’s Smart Send Queue paces sends at about 200 Instagram DMs per hour per account in a rolling one-hour window, exposes remaining slots, and refuses to pretend we sold you extra quota. That 200 is CommentLink’s product pace — not a published Meta SLA.

This page is the product view: rolling window, remaining slots, what counts as a send. The campaign view — captions, staffing, what commenters see — is rate limits and viral Reels. Native Business Suite Custom Keywords typically drop later matches once the cap is hit; that contrast is the reason a queue exists.

The cap we pace to

CommentLink treats Instagram as 200 DMs per hour for pacing. The window is rolling: 3600 seconds, not “reset at midnight.” Each successful send is recorded. Remaining is limit minus how many sends sit inside the current window.

200 is a conservative product number aligned with how operators discuss Instagram’s automated messaging cap. It is not a Meta SLA, and Meta can tighten or change enforcement. The queue does not unlock a private higher ceiling. If Instagram rejects a send, we cannot invent a successful delivery.

What “pace” means in practice

Before a DM goes out, the automation asks the queue whether a slot is free. If yes, it sends and records the send. If not, it waits for a slot to open as older timestamps fall out of the rolling hour. That is pacing: later commenters are not blasted through the cap in the same second.

Native Comment to Message, as described in public 2026 write-ups of the built-in tool, does not give you that waiting line. Extra matching comments are dropped. People who commented “LINK” at minute 61 of a spike simply never get the DM. CommentLink’s design goal is that those people still get in line instead of disappearing.

Waiting is not magic capacity. If 2,000 people comment in ten minutes, you still only send on the order of 200 automated DMs in the next hour, then more as the window rolls. The last commenters wait longer. Tell them in the public reply that DMs can take time when a Reel is busy — honest copy, not a fake “instant for everyone.”

Remaining slots

The queue can report sent_this_hour, limit_per_hour, and remaining. Remaining is how many paced sends you can still fire before the window is full. It is not a customer-facing “credits” pack. CommentLink does not sell extra Instagram DMs. Remaining going to zero means wait, not pay.

WhatsApp has a separate, more conservative paced number in the same service and a totally different Meta billing model (conversation fees). Do not mix the two. A viral Instagram Reel does not spend WhatsApp conversation charges unless you also ran WhatsApp sends.

What the queue does not do

• It does not raise Meta’s cap.
• It does not let you cold-DM a purchased list faster.
• It does not replace a Professional account or OAuth.
• It does not pause Instagram itself — you can still get other API errors.
• It does not apply if someone turns safety queue off on an automation (default on templates is on; leaving it on is the point).

Campaign advice lives on the operator article

Keyword choice, catch-all, public-reply copy, and how to staff the hour are campaign problems. They are covered in rate limits and viral Reels. This page stays on the mechanism: remaining slots, the rolling window, and the fact that we do not sell extra Instagram quota.

Free, still capped

CommentLink not invoicing you does not mean unlimited Graph sends. The free lander says the same: free Instagram DM automation. Native is also free and typically drops. Paid ManyChat still sits under Meta’s hour cap. The vendor bill and the Graph cap are different meters.

A rolling hour, with numbers

At 12:00 you send 200 paced DMs. Remaining is 0. At 12:10, nothing extra goes unless some of those 200 timestamps have aged out — they have not, because the window is 60 minutes. At 13:00 those sends start falling out and remaining climbs. A burst at 12:00 and another at 12:30 share the same crowded window. This is why “it worked at 11:50 and died at 12:05” is usually math, not a disconnected token.

Follow-gate adds sends: the gate card is a DM, the unlock is another. A viral gated Reel consumes slots faster than a one-bubble LINK. Public replies are a different API action; still do not assume they are free of all limits, but the number you should plan around for this article is CommentLink’s Instagram DM pace of ~200/hour — a product ceiling, not a Meta SLA.

Order of delivery

Pacing is meant to keep sends inside the cap rather than firing a thundering herd. Later commenters wait. We do not promise a visible customer-facing ticket number in Instagram. If you need to set expectations, say in the public reply that DMs may take time when the Reel is busy. Do not promise “everyone gets it in 8 seconds” on a boosted giveaway.

Turning the queue off

Automations can disable the safety queue. That is how you shoot yourself in the foot. Templates default it on. Leave it on. Disabling it does not grant extra Meta quota; it only stops CommentLink from waiting for a slot before it tries. Instagram can still reject or throttle. Native drop behaviour is the thing you were trying to avoid.

How this article differs from the viral Reel playbook

The playbook is campaign advice: keywords to use, when to boost, what to tell the audience. This page is the mechanism: rolling window, remaining slots, no extra quota, gate cards counting as sends, native typically dropping. If you are about to pay for ads on a comment-to-DM Reel, read the operator article first. If you are debugging remaining slots at zero, you are already on this page.

Worked numbers: 800 matching comments in 20 minutes. You will not send 800 DMs in 20 minutes on official APIs. CommentLink will send on the order of 200 in the first rolling hour, then more as the window moves. That 200 is our pace. Native typically drops the rest. A follow-gate would have doubled slot use per person who unlocks.

Disabling the queue does not buy Meta capacity. It only stops CommentLink from waiting. Instagram can still refuse. WhatsApp numbers in the same pacing service are a different channel and a different Meta bill. A viral Instagram hour does not spend WhatsApp conversation fees unless you also sent WhatsApp. Remaining going to zero is the Instagram meter, not a CommentLink invoice.

FAQ

Is 200 a guarantee from Meta?

No. It is CommentLink’s paced Instagram limit, aligned with common discussion of the cap. It is not a published Meta SLA. Meta can enforce differently. We do not sell a higher number.

Does native Instagram queue?

Public descriptions of Custom Keywords / Comment to Message say later comments drop at the cap. That is the gap the Smart Send Queue is built for.

Will everyone on a 10,000-comment Reel get a DM?

Not in the first hour. They get paced. Some will wait a long time. Some will leave. That is the honest viral math.

Is this the same as WhatsApp’s 80/hour number in code?

Different channel, different limit in the same queue service. Instagram comment-to-DM uses the Instagram limit.

Do follow-gate cards count toward the 200?

Yes. The gate DM is a send. The unlock DM is another send. Plan viral gated Reels as two-slot conversations, not one. That is why remaining goes to zero faster on gated giveaways than on a single LINK bubble.

If remaining is zero, did CommentLink crash?

Usually not. The rolling hour is full. Wait for timestamps to age out or stop using catch-all. Check you did not also run Story mention thank-yous into the same cap. Reconnecting OAuth will not mint extra quota.

Can I buy extra Instagram DMs from CommentLink?

No. There is no extra quota product. Free does not mean uncapped Graph. Native does not sell extra either; it typically drops. Anyone selling “unlimited official DMs” is mixing categories.

Should I disable the queue to go faster during a boost?

No. Faster means hitting Instagram’s wall without waiting. You wanted the opposite of native drop. Leave safety queue on. Shorten the DM. Narrow the keyword. Tell the audience that DMs may take time.

Related reading

• Native comment-to-DM versus CommentLink
• Viral Reel DM queue (campaign view)