Yes. Locale detection works on free and paid TranslatePress versions identically because both editions expose the same locale API. The free edition's two-language setup gets the same bot treatment as Pro multi-language sites; the only difference is how many languages your TranslatePress install actually serves. SleekAI does not require Pro features to do its job.

TranslatePress handles front-end translation, including AI-translated strings if you use the AI add-on. SleekAI generates each reply natively in the active language through the LLM, so chat replies are not part of TranslatePress's string database. That means the chat layer never adds to your TranslatePress translation backlog, and AI-translated front-end strings stay separate from the bot's reply generation.

Yes. Bot welcome and placeholder text can be set per language directly in SleekAI's chat configuration. Preset suggested questions support per-language variants too, so an Italian visitor sees Italian presets and a French visitor sees French ones. This bypasses TranslatePress's string translation system entirely; the chat strings are managed inside SleekAI rather than treated as front-end content.

No. Chat replies are not translated by TranslatePress's AI add-on; they are generated natively by the LLM in the active language. TranslatePress's AI quota is for translating front-end strings, which is unrelated to chat. That distinction matters at scale: a high-volume bot generating thousands of replies a month would be expensive if every reply consumed translation credits, but with SleekAI those credits are untouched.

Through TranslatePress's locale API, not browser headers. The visitor's chosen language drives the detection, which is the right behavior for multilingual sites where users explicitly switch languages with the language switcher. Browser-header-based detection is unreliable in practice; users browse in one language while their browser is set to another. The TranslatePress switcher signal is what matters.

OpenAI, Anthropic, and Google models cover every major language well. Italian, French, Spanish, German, and Portuguese are all native-quality on current frontier models. Less common languages may need testing per-model; SleekAI's conversation logs record the active language with each chat, so you can review quality per locale and pick a different provider for languages where one model performs noticeably better than another.

Yes. Translated URL slugs in TranslatePress Pro produce locale-specific URLs, and SleekAI consumes whatever URL TranslatePress renders at request time. Bot replies that link back to articles or product pages land on the right localized URL. That keeps the chat surface consistent with the SEO surface, where each language has its own URL structure indexed by search engines.

Yes. Display conditions filter by the active TranslatePress locale slug, so you can run the bot only on languages you want to support. A small site with five TranslatePress languages might run the chat surface on only the top three for now, expanding as the support team gets comfortable reviewing logs in those languages. The bot simply does not load on excluded locales, which keeps the visitor experience clean.