How to use Bulk DM Queue

One message, several recipients, one result per person. Learn how the queue is trimmed, how failures are contained, and where it stops for you.

Applies to Ins Autopilot 3.22 and later · Updated 2026-10-17

What this helps you do

Bulk DM Queue lets you write one message and work through a chosen list of recipients in a single pass, with a randomized delay between sends instead of a burst. It exists because the alternative — repeating the Direct Message flow by hand — is where consistency quietly collapses.

Everything you would review in a single Direct DM is still reviewed here, once, before the queue starts: the list, the text, and the fact that you are the one pressing the button.

What this is not

A queue is not a campaign engine and not a schedule. It works through your list at a human pace while you are there, and it stops when the allowance or the list runs out.

Nothing in the queue retries an unknown result, and nothing in the queue sends follow-ups. Each recipient gets one attempt, and you deal with the outcomes yourself.

What queued does not mean

Three distinctions matter more than anything else about this feature, and each one causes a different kind of surprise.

• Queued is not delivered. Adding a recipient reserves a slot, nothing more. The outcome is decided one send at a time, and every row gets its own status.
• Sent is not replied. A confirmed send means the message reached Instagram's send path. It says nothing about whether the person read it, cared, or will answer. Reply detection is a separate, read-only step.
• The queue is bounded by what you actually have. If your plan has room for fewer contacts than you selected, only as many as fit are queued — with two Trial contacts left, two go in. The server still decides each send, so a queued row can still come back blocked.

Before you start

• You are signed in to Instagram in the same browser, and the extension shows your account ID in the footer.
• You have a message written and a list of handles to send it to.
• Free plan: the queue draws on the Outreach Trial — 5 unique confirmed contacts per sender account, at most 3 new contacts per UTC day, 7 days from the first confirmed delivery.
• Direct Message and Bulk DM Queue share that same allowance.
• Pro raises the daily ceiling to 30 (Monthly) or 50 (Annual).

Step by step

1. Open Outreach and choose Bulk DM Queue — the panel shows your remaining allowance for today.
2. Add recipients — select contacts from Relationships or type handles in. The list you build is the queue, so check every row before continuing.
3. Write the message once — the same text goes to everyone in the run. Write something you would be comfortable sending to each of these people separately.
4. Review the list and the text — this is the last moment where the whole batch is visible together. Remove anyone you are not sure about rather than hoping it reads well.
5. Start the queue — the extension works through the list one recipient at a time with a randomized delay between sends. The delay avoids a mechanical burst; it does not guarantee anything.
6. Watch each row resolve — every recipient gets its own outcome — sent, blocked, failed, skipped or unknown. One row failing does not stop the rest of the queue.
7. Handle anything marked unknown — the queue stops on a review item instead of guessing. Open the Instagram thread, confirm whether the message arrived, then resolve it by hand. See Sent, blocked, unknown and Needs Review explained.
8. Check History — the full run is recorded with a status per recipient, and each contact picks up the matching entry on the Activity timeline.

How the queue handles limits and failures

• When the queue is built it is trimmed to the allowance you actually have. Selecting ten recipients with two contacts left queues two.
• The Trial counts unique confirmed contacts, not messages, so a second message to somebody already contacted does not fit.
• Because each send is decided individually, the trimmed queue is a projection rather than a promise. A queued row can still come back blocked.
• A failed or blocked row is set aside and the queue moves on to the next recipient. One bad row never cancels the run.
• An unknown row is held for review and is never retried by the queue, because a retry could deliver a duplicate of a message that already arrived.
• Daily DM allowance: 0 on Free outside the Trial, 30 on Monthly Pro, 50 on Annual.

Limits and important behavior

• The queue sends at a human pace with randomized intervals. It is not built for volume, and raising the list size does not change that.
• Sends run in your browser from your signed-in session, not through an official platform API. Instagram can refuse an action at any time.
• Whether Instagram restricts an account depends on the account's state and on the platform's current limits, which are not published. Modest volume is the only real control you have.
• On the Trial, outreach covers 5 unique confirmed contacts in total. After that, new sends need Pro, although earlier History stays readable.

Troubleshooting

Only part of my list was queued.

The queue was trimmed to the allowance you actually have. Direct and Bulk draw from the same pool, and the daily cap still applies.

A row came back blocked.

Nothing left your browser for that row. The contact may already be used on the Trial, or the daily cap may have been reached. Correct the cause and retry.

The queue stopped at one recipient.

Either that row came back unknown, or the allowance ran out. Unknown rows wait for you to check the Instagram thread; an exhausted allowance stops the run until it refreshes.

Can the queue keep going on its own?

No. The queue runs in your browser session while you are using it, one row at a time, at a human pace.