> For the complete documentation index, see [llms.txt](https://docs.bugsplat.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bugsplat.com/education/faq/common-end-user-questions/my-software-just-crashed.-should-i-contact-bugsplat-for-help.md).

# My software just crashed. Should I contact BugSplat for help?

Unfortunately, BugSplat cannot help individual users of an application with specific issues that are causing their software to crash. The BugSplat team does not have any insight into what might be causing application crashes.

BugSplat is something called a[ Crash Reporter](https://docs.bugsplat.com/education/faq/what-is-a-crash-reporter.md) that simply helps developers find and fix application defects, bugs, and crashes.

You can follow [these simple steps](https://github.com/BugSplat-Git/bugsplat-docs/tree/master/education/faq/common-end-user-questions/broken-reference/README.md) to try and find the cause of your application's crashes.

If that doesn't work please try finding and contacting support staff at the company which builds or supports the application which is crashing. Often a company will answer support-related questions from email an email formated as support@\[insert-name-of-company].com.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.bugsplat.com/education/faq/common-end-user-questions/my-software-just-crashed.-should-i-contact-bugsplat-for-help.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
