Custom Support Responses

BugSplat's Custom Support Responses let you communicate directly with your users the moment a crash happens. Instead of digging through forums or DMing support, they see a clean, branded message from your team: what happened, what to do next, and when it'll be fixed. Instant peace of mind.

Why it matters

• Keep players in the loop: Let users know you're already on the case—or give them a quick fix so they can jump back in.
• Reduce support tickets: When users get answers in real time, they stop flooding Discord, forums, and email with the same report.
• Look pro: A sleek, branded message in your crash dialog sends the signal that your team knows what it's doing—even when things go wrong.

How it works

Custom Support Responses are tied to crash groups, which BugSplat organizes using grouping rules. That way, when a specific crash type hits, users see a specific message tailored to that issue.

You can define fallback messages for all crashes, or target them by localization, platform, or any attribute you choose. Want to show a different message to German users running version 1.1.4? No problem.

And yes—markdown is fully supported. Toss in links, code blocks, whatever your support team needs to get the point across.

No extra portals. No added steps.

You configure and preview responses right inside your BugSplat dashboard. No extra tools, no uploading HTML, no weird configs. Just click, write, and go.

Want to see it in action?

Check out our full implementation guide and code walkthrough in this blog post. It's got everything you need to get up and running fast.