Troubleshooting
“I couldn't send you a DM” in #help?
Fix Discord DM privacy settings so Whambulance can open your support flow and your ticket doesn't stall.
If you see this in #help:
❌ I couldn't send you a DM. Please enable DMs from server members, then post again.
your setup is usually fine — Discord is just blocking the bot's direct message.
Why this matters: if DMs are blocked, support automation can't start your thread correctly, and your issue can sit unresolved longer.
2026 update: some users now see a “this channel has moved” banner in #help. If that appears, use heyron.ai/support instead of repeatedly reposting in #help.
Quick fix (2 minutes)
1) Enable DMs from server members
In Discord, open User Settings → Privacy & Safety and turn on:
- Allow direct messages from server members
If you're on mobile, open server settings and check the server-level privacy toggle too.
2) Check per-server overrides
Discord lets each server override DM behavior. In the heyron server:
- Open server name → Privacy Settings
- Ensure DMs are allowed for this server
3) Use the active support entry point
If #help is active, post one fresh message there after enabling DMs. If #help shows a “this channel moved” banner, open a ticket directly at heyron.ai/support.
4) If prompted, provide your signup email
For server-side checks (like 502/container issues), support may ask for the signup email tied to your Heyron account.
If it still fails
- Close/reopen Discord (desktop and mobile can cache privacy changes)
- Leave and re-enter the support flow with a new message
- Confirm you didn't block the bot account
- Temporarily disable strict DM filters if enabled
- If #help is archived/moved, skip retries and open a fresh ticket at heyron.ai/support
Ticket keeps opening/closing? Use this reset
If you see repeated open/close behavior or no visible ticket thread, it's usually the DM handshake failing mid-flow.
- Enable DMs globally and for the heyron server (steps above).
- Wait 15–30 seconds so Discord applies the privacy change.
- Use one active support entry point only: either one clean retry in #help (if active) or one fresh web ticket at heyron.ai/support.
- If Whambulance asks for your signup email for a 502/container fix, reply in the thread it opens.
Can’t find your support thread? Scroll for a bot mention with a thread link, or post once in #help: "I enabled DMs — please reopen my support thread."
Advanced edge cases (when DMs are ON but it still fails)
- DM toggle is on, but bot is blocked: open the bot profile and confirm it is not blocked.
- Server DM override still off: global privacy can be ON while the heyron server-level setting is OFF.
- Mobile/desktop mismatch: one client applies the toggle late; test from the other client after a full restart.
- Safety filters/intermediate apps: strict filters or bridge-style repost flows can strip message content. If triage shows your message as blank, repost plain text directly in #help.
- Repeated retries causing noise: send one clean retry after settings changes, then wait for the bot response instead of rapid reposting.
Seeing a blank triage snapshot? Do this exact recovery
Some users complete the DM step, but support receives an empty/blank issue body. That usually means the message payload was stripped by client formatting, relay behavior, or a failed first handshake.
- Stop repost spam. One clean retry is better than 5 partial retries.
- Post plain text only (no screenshots-only, no embeds-only) with 3 lines: issue, exact error, what you already tried.
- Include destination context: DM, #help, thread, or web ticket — say where the failure happened.
- If the relay still appears blank, bypass #help and submit at heyron.ai/support with the same 3-line summary.
Copy/paste plain-text triage packet
Support packet (Discord DM handoff)
Issue:
Exact error text:
Where it failed (DM/#help/thread/web):
What I already tried:
Timezone + time observed:
Can support continue via ticket if DM handoff fails again?
Known-good test message
Paste this in #help after changing settings (if that channel is still active):
Test: I enabled DMs from server members. Please reopen my support thread if needed.
If #help is moved/archived, use this as your support ticket summary instead:
Discord DM handoff failed with “couldn't send DM” even after enabling global + server DMs. I restarted Discord and retried once. Please continue via ticket.
Don't post secrets publicly: API keys, tokens, and passwords should never go in #help. Share only what support asks for, and prefer ticket threads/DM when available.
Why this keeps happening
Discord privacy defaults are different across desktop/mobile and can be overridden per server. Many users think DMs are on globally, but they're still off for one server.
Bottom line: turn on DMs, retrigger #help, and your support flow should recover quickly.