You Are Sending Too Many New Direct Messages: Why Discord Paused You

The full message reads: "You are sending too many new direct messages. Hold off for a few minutes before trying to message this person again." It is one limit, on your account. The person you were writing to did nothing to cause it.

What does "you are sending too many new direct messages" mean?

Discord thinks you are opening new conversations faster than a person normally does, and it has stopped you opening more for a while. The word that matters is "new": conversations you already have are not what it counts.

Discord's developer documentation describes the same idea in plainer words, for apps: "You are opening direct messages too fast." Opening, not sending.

What Discord does not publish is the number. Its safety pages say it runs a proactive spam filter and enforces rate limits against bulk activity, and stop there. Figures on forums are what one person ran into once, not a rule.

It is also easy to confuse with three other Discord messages that look alike:

The second row is covered in cannot send messages to this user. The last two are heavier. Discord lists messaging several people who are not your friends among the reasons it asks for verification, and Limited Access follows what it calls suspicious account behaviour.

Why does Discord say you are sending too many DMs?

Because what you did looks, to an automatic filter, like what spam accounts do. Discord's spam guidance names unsolicited messages and adverts, mass server invites, and the same message sent many times in a short period. Its verification page adds messaging several users who are not your friends.

Discord does not say what its filter weighs, so read this as the usual pattern rather than the rule:

Ordinary people hit it too: a giveaway host messaging winners, a team captain messaging a roster, a member messaging every moderator about one problem. A filter sees the pattern, not the reason. Discord's own spam page says even invitations people did not mind receiving can be flagged.

How long do you have to wait?

Take the message at its word: a few minutes, with no new conversations in between. Discord publishes no exact time, and it does not say whether trying again restarts the wait. Assume it does.

What you do in those minutes matters more than the clock:

If it keeps coming back, or turns into "Verification Required" or the red bar, the pattern is the problem, not the timing. Spread your messages out, write to people who expect to hear from you, and leave links for the second message.

If you believe Limited Access is a mistake, the notice has a Regain Access Here button that asks Discord to review it.

Who should you message instead?

If you were writing to a server's staff, stop DMing them one by one and open the server's ticket. It is an easy way to hit the limit: something goes wrong, the moderator list is right there, and you message five moderators hoping one answers.

A ticket simply works better:

• Your DM may never be seen. For many people, Discord sends a message from someone who is not a friend to a separate requests inbox, unless the two share a friend or a small server.
• One moderator is one person. They may be asleep. A ticket reaches the whole team.
• A DM leaves no record in the server. A ticket is saved when it ends.
• It keeps you away from fake staff. In a ticket you know who you are talking to. In DMs, anyone can copy a moderator's name and picture.

To find the ticket, look for a channel called support, tickets or help with a button that opens one, and check the rules channel. What is a ticket in Discord walks through it. Reporting another member works the same way, through a report ticket.

One exception: anything on your Discord account itself, this limit included, is Discord's alone. No server's staff, role or bot can lift it. If waiting does not clear it, that is a question for Discord's own support.

Why do members DM your mods instead of opening a ticket?

For server admins: because they could not see another way. A member who DMs five moderators is telling you the support path is missing, hidden, or looks slower than a DM.

Make it one place. A Discord ticket bot gives every member a button in a channel they can see. With AI Ticket Bot, the AI replies to the first message in seconds, from what your staff taught it, including when no moderator is online. When a person is needed, it hands the ticket over and pings the one staff role you chose, inside the ticket. Staff are never sent a DM about a ticket, so nobody's inbox becomes the queue.

Then say it. Paste this into your rules, your panel or a pinned message, with your own channel name:

**Need staff?** Please do not DM moderators.
Open a ticket in #support and the whole team will see it.
Staff will never DM you first. If someone claiming to be staff messages you, tell us in a ticket.

The last line also protects members: when your team never starts a DM, a DM from "staff" is plainly fake. Stopping spam tickets covers the rest of that.

Will a ticket bot DM people for you?

No, and it should not. AI Ticket Bot only messages a member about a ticket they opened or were added to: the closing message with the transcript link, and a few notices about that same ticket. Members who never open or join a ticket never hear from it, and it has no bulk or announcement message of any kind.

When a member's DMs are closed, the closing message simply does not arrive. The transcript is still saved, and the member can read it any time with /mytickets. Ticket bot DMs lists every message it can send.

What a ticket bot cannot do about it

The honest list.

If you hit the limit messaging a member list to promote a server, a ticket bot is the wrong tool, and so is any bot that offers to do it for you. Discord's spam rules cover bots as well as people. Post it in your own server's announcement channel instead.