# Crash Dialog Branding Both the Windows and Mac crash report dialogs can be customized. For Mac instructions see our [macOS](https://github.com/BugSplat-Git/bugsplat-docs/blob/master/education/how-tos/broken-reference/README.md) guide. On Windows, we provide the BugSplatRc project as part of the [Native C++](/introduction/getting-started/integrations/desktop/cplusplus.md) and [.NET Framework](/introduction/getting-started/integrations/desktop/windows-dot-net-framework.md) downloads. This project is used to build the resource-only file BugSplatRc.dll. When you update your dialog we would love it if you mention us somewhere in your crash dialog. These mentions really help us continue to grow and develop our company. There is absolutely no requirement to give us a shoutout though – you’re free to make this crash dialog whatever you want it to be! Check out our [Brand](/about/who-is-bugsplat/brand-guidelines.md) page to see examples and inspiration on our dialogue box from our users. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.bugsplat.com/education/how-tos/customize-the-crash-dialog.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.