Cannot Send Messages to This User on Discord: Why a Bot's DM Fails

Bots show this in different words. Some say "Cannot send messages to this user due to having no mutual guilds", and developers know it as error 50007. On a server with tickets it usually surfaces as a simpler complaint: "I never got the message when my ticket closed."

What does the error mean?

Discord decided the receiver does not accept direct messages from this sender. Nothing was delivered and nothing is waiting.

"Guild" is Discord's own word for a server, so "no mutual guilds" is the first row: the member left, or was removed, and the bot has no server in common with them any more.

The second row is by far the most common. Discord lets every member decide, server by server, whether people and bots from that server may message them. Many switch it off to stop spam, and it stops the ticket bot as well.

How does a member fix it?

Allow direct messages from that server, and unblock the bot if you blocked it. It takes a few seconds.

There is also an account-wide default in User Settings under privacy, which decides what new servers start with. Changing it does not change servers you already joined, so the per-server switch is the one that matters.

If you would rather keep direct messages off, that is a fair choice. You do not lose your ticket. The next section covers how to get what the message would have contained.

Why can an admin not fix it?

Because it is the member's own privacy choice, and no role or permission is above it. Giving the bot Administrator changes nothing. Moving its role higher changes nothing.

That makes this different from almost every other bot problem. A bot that cannot create a ticket is missing a permission an admin can grant. A bot that cannot message a member has every permission it needs and is being told no by that member.

What an admin controls is how much depends on a direct message arriving. Ticket bot permissions covers the problems an admin can fix.

What does a ticket bot do when the DM fails?

It depends on the message. Here is each direct message AI Ticket Bot sends a member, and what happens when Discord refuses it.

In most rows the direct message is a copy of something that also happens inside the server. The close message is the exception, because the channel is gone when a ticket closes. Two things replace it.

/mytickets lists the tickets you opened and has a Read transcript button on each closed one. It works in the server and in a direct message that you start with the bot.

The star rating is the one thing with no second route. It is offered in the close message only, so a member who does not get that message cannot rate the ticket.

The bot does one thing before it sends: for a member who has left the server it skips the close message entirely. Leaving is treated as not wanting to hear from that server again. Ticket bot DMs covers every message and who receives it.

How do you run a server where DMs often fail?

Assume a share of your members will never receive one, and put nothing important only in a direct message.

Staff should also not read a silent member as a rude one. A member who never answered a reminder may never have seen it. On AI Ticket Bot the ticket shows which happened: a small note says whether the member was reminded by direct message or, when that failed, in the ticket itself.

For members who prefer direct messages to channels altogether, tickets and modmail work differently. Ticket bot or modmail compares them. Modmail depends on direct messages working, which is exactly what this error is about.

What nobody can do about it

The honest list, for AI Ticket Bot.

The first limit is the one to know. When a member says they got nothing, the bot has no record to check, and the likely cause is the privacy switch above. Any Discord ticket bot is in the same position, because the rule is Discord's.