Why some people were skipped

Open a run in the Agent Activity Log and you will often see that some people were skipped. That is the product working, not failing. Every skip is DM Commander refusing to do something that would put your social account at risk, or that would waste a send on someone who cannot receive it.

Two things to settle up front:

  • A run that sends fewer messages than its limit is completely normal. Each run sends at most 5 DMs on any platform, then waits 15 to 30 minutes before the next batch. Your daily number is spread across the day on purpose.
  • Nobody gets messaged twice by accident. When a send cannot be confirmed, the product skips rather than risk a double message.

People who cannot receive your message

  • "X did not list them in the New chat search. They may not accept messages from you." Many accounts keep DMs closed. Nothing to do.
  • "They do not accept messages from you on X, so they were skipped." Their settings, not yours. Nothing to do.
  • "They cannot be messaged (deleted, suspended or not found), so they were skipped." The account is gone. Nothing to do.
  • "The profile has no Message button." On LinkedIn you can only message people you are connected with. Nothing to do: LinkedIn Step 2 sends everyone else a connection request first, and the message goes out once they accept.
  • "LinkedIn wants the email address before you can connect, so they were skipped." LinkedIn asks for an email on some profiles. Nothing to do.

When the platform itself gets in the way

  • "X kept the Send button off for them, even with the message typed in." What to try: "Open X in this Chrome profile and send them a message by hand. If Send stays off there too, X is not letting this account send messages yet, which is common for new accounts and accounts without a verified email." Verifying the email on that account and running Account Warm-Up for a while are the two things that help.
  • "Pressed Send but the platform did not confirm the message went out." What to try: "Look in your sent messages." If it is there, you are fine. If not, that person stays available for a later run.
  • "The platform reloaded the page while sending. It was not sent again, so nobody gets a double message." Nothing to do. They come round again on a future run.
  • "Messenger opened a different chat than the one it wanted, so nothing was sent." What to try: "Do not type or click in the worker window while it runs." Facebook DMs run in the window you are in, so give that run a minute to itself.
  • "The run ran out of time before everyone was messaged. The rest go first next run." Nothing to do. Nobody is lost; they are first in the queue next time.

People you told it to skip

Three rules in User Settings quietly remove people before a run even starts:

  • "Skip people I already know" has a switch per platform: Facebook friends, X accounts I follow, Instagram accounts I follow, LinkedIn 1st-degree connections. Facebook, X and Instagram are on by default. LinkedIn is off by default, because LinkedIn Step 2 is built to message your connections.
  • "Never message these people" takes one name or handle per line, and matches on both the handle and the display name.
  • Anyone you have already contacted is skipped automatically, on every platform. You will never double-message a lead.

If you want more people reaching your Inbox, this is the first place to look: switch off a "Skip people I already know" toggle you do not need, and review your never-message list.

When a whole batch is skipped

If the log says every approved message was for someone already messaged, on your never-message list, or unable to receive DMs, discard those messages in your Inbox. Then widen your targeting, which is the real fix: add another subreddit or keyword, or point the step at a second source group on the Deploy Agents page, and click Save Campaign.

Fresh targeting plus a click of Run Now in the extension popup, and the next batch goes out straight away.

Was this article helpful? Still need help? Submit a ticket