Troubleshooting

Open Better Support Tickets (and Get Faster Fixes)

A 3-minute format that helps support reproduce your issue quickly instead of asking 12 follow-up questions.

Recurring community pattern: users report "it doesn't work" with no exact error, no timestamp, and no destination context. Support has to guess. This tutorial gives you a clean, copy/paste structure that gets faster answers.

Reality check: clear evidence beats long stories. One precise report with exact error text and a tiny repro usually resolves faster than 20 back-and-forth messages.

What to include every time

Expected behavior: What should have happened?
Actual behavior: What happened instead?
Exact error text: Copy/paste, don't paraphrase.
Where it happened: Dashboard, Discord DM, server channel, thread, etc.
When it happened: Include timezone.
Repro steps: 3-5 short steps max.

Copy/paste support packet

Support Packet - Expected: [what should happen] - Actual: [what happened] - Exact error: [paste full error text] - Surface: [dashboard / Discord DM / server / thread] - Time: [YYYY-MM-DD HH:MM timezone] - Repro steps: 1) ... 2) ... 3) ... - What I already tried: - ... - ... - One screenshot/log snippet (optional but helpful): [attach]

High-friction mistakes that slow support

Paraphrased errors: "something about auth" is not actionable.
No destination context: DM works but server fails is a huge clue—include it.
No timestamp/timezone: impossible to line up logs quickly.
Retry spam: 10 retries can hide the original cause. Share the first failing attempt too.

Privacy tip: include enough evidence to debug, but redact secrets (API keys, tokens, personal IDs) before posting.

One-minute self-check before posting

Can someone else reproduce this from your steps?
Did you include exact text, not summaries?
Did you include channel/thread destination?
Did you include your local time + timezone?

Bottom line: short, structured, evidence-first tickets get solved faster and reduce support loops for everyone.