Nobody chooses DM-based support. It happens: your community grows, moderators become recognisable, and people start messaging them directly because it works. By the time it stops working, the habit is established and undoing it takes a plan rather than an announcement.

The failure mode of DM support is not volume, it is invisibility. Nobody can see the queue, nobody can cover for a moderator who is asleep, and nothing that happens in a DM helps anyone answer the same question tomorrow.

Before you switch anything

Spend a week writing down what people actually ask. Not categories you imagine: the real questions, in the words they use. That list decides your panel buttons, your forms, and your first knowledge-base articles, and guessing at it is the most common reason a migration produces a panel nobody clicks.

Week one: set it up quietly

  1. Add the bot and create a support channel, or reuse the one you have.
  2. Build one panel with three to five buttons based on your list of real questions.
  3. Attach a short form to the buttons where context genuinely helps. Skip forms entirely on the simple ones.
  4. Set up routing so each button assigns the right role. This is what makes the new system visibly faster than a DM.
  5. Run it with your moderators only for a few days. They will find the confusing labels before your members do.

Week two: make it the obvious path

Announce it once, pin the panel, and link it wherever people currently ask: your rules channel, your FAQ, your welcome message, your server description. The goal is that anyone looking for help finds the panel before they find a moderator’s profile.

Do not announce it three times. A migration that is announced repeatedly reads as a rule being enforced, and people push back on rules in a way they do not push back on convenience.

Week three: redirect gently

When somebody DMs a moderator, the moderator answers, and then adds one line: "for next time, opening a ticket gets you an answer faster because the whole team sees it." Answering the question first is the part that makes this work. Refusing to help until someone uses the correct channel trains people to stop asking, not to open tickets.

Within a few weeks the DMs thin out on their own, because the ticket genuinely is faster. If it is not faster, that is the actual problem, and no amount of redirecting will fix it.

What to watch afterwards

  • First response time. If it is worse than DMs were, your routing is not doing its job.
  • Which panel buttons go unused. An unused button is a label problem, not a demand problem.
  • Questions that keep recurring. Those belong in a knowledge-base article, not a ticket.
  • Whether moderators are still being DM’d. Usually it is one or two well-known people, and usually one conversation fixes it.