> 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/localized-support-responses-for-windows-c++-.net-and-macos.md).

# Localized Support Responses for Windows C++, .NET, and macOS

BugSplat's Support Response feature allows developers to display a localized message to their users at the time of a crash. The Support Response feature is currently supported by our [Windows C++](/integrations/desktop/cplusplus.md), [.NET](/integrations/desktop/bugsplat-for-dot-net.md), and [macOS](/integrations/desktop/macos.md) integrations and support for other platforms is coming soon. The following steps will allow you to create a localized Support Response message for all crashes in your database. These same steps can be applied to create localized [stack key specific Support Response](/guides/production/setting-up-custom-support-responses.md#creating-a-crash-specific-support-response) messages as well.

{% hint style="info" %}
**This is about the support message, not the dialog's own text.** The words on the Windows crash dialog itself — labels, buttons, body copy — come from `BugSplatTheme\strings.<bcp47>.json`, and `BugSplatReporter.exe` picks the file matching the end user's own Windows UI language with no configuration at all. The key described below is a separate thing: it is a value **you** choose and set in code, and it selects which support response your database returns. See [Crash Dialog Branding](/education/how-tos/customize-the-crash-dialog.md#adding-a-language) for translating the dialog.
{% endhint %}

## Step 1

Log in to the web application and navigate to the [Support Response](https://app.bugsplat.com/v2/support?stackKeyId=0\&key=*Default*) page to edit the default support response for your database

## Step 2

Create a new key for the localized version of your support message by typing a value in the key field. You'll want to remember what you typed here for later.

## Step 3

Enter a subject for your support message. This subject is for internal use only and will not be displayed to the customer.

## Step 4

In the code you use to initialize BugSplat, provide the value you used for key from step 2.

![Support Response Editor](https://976110677-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LBMgmIcgkIXSUfnXDSv%2Fuploads%2Fgit-blob-42cd0b6683902f0e4d09a04252d09d239554bf1d%2Fconfigure-custom-support-response-1.png?alt=media)

**Windows C++**

The key is set with `SetKey` after the `BugSplat` instance is constructed.

```cpp
BugSplat g_BugSplat(L"Fred", L"myConsoleCrasher", L"1.0");
g_BugSplat.SetKey(L"es-ES");
```

If you're using the dynamic library and the C API, call `BugSplat_SetKey` instead:

```cpp
BugSplat_Init(L"Fred", L"myConsoleCrasher", L"1.0");
BugSplat_SetKey(L"es-ES");
```

**.NET**

```csharp
var bugsplat = new BugSplat("Fred", "myDotNetCrasher", "1.0");
bugsplat.Key = "es-ES";
```

**Mac OS**

```
- (NSString *)applicationKeyForBugsplatStartupManager:(BugsplatStartupManager *)bugsplatStartupManager signal:(NSString *)signal exceptionName:(NSString *)exceptionName exceptionReason:(NSString *)exceptionReason;
{
    return @"es-ES";
}
```

## **Step 5**

Generate a crash and ensure that the correct support response is loaded, you should see your translated message.

![Support Response Page](https://976110677-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LBMgmIcgkIXSUfnXDSv%2Fuploads%2Fgit-blob-c840fece498c322197f5b6c8896618ed2c901de2%2Fconfigure-custom-support-response-2.png?alt=media)


---

# 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/localized-support-responses-for-windows-c++-.net-and-macos.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.