> For the complete documentation index, see [llms.txt](https://docs.zipchat.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zipchat.ai/help-center/translating-the-welcome-message-based-on-geolocation.md).

# Translating the welcome message based on geolocation

Zipchat can translate your chatbot’s **welcome message based on the user’s geolocation**, but this feature is currently available **only for Shopify customers**.

If you are using Shopify and would like to enable this functionality, please reach out to our support team — we’ll be happy to configure it for you.

Please note:

* The geolocation-based translation applies **only to the welcome message**.
* It does **not** apply to prefilled messages (quick reply buttons).
* At this time, quick reply buttons cannot be translated automatically based on geolocation.

***

#### If You’re Not Using Shopify

Unfortunately, geolocation-based translation of the welcome message is not available for non-Shopify platforms.

As an alternative, you can:

* Create a separate bot for each language.
* Assign each bot to the corresponding language subdomain of your website.

This approach allows you to fully customize the content and language experience for each audience.


---

# 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.zipchat.ai/help-center/translating-the-welcome-message-based-on-geolocation.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.