Setting up Bitrix24 multilingualism

Our company is engaged in the development, support and maintenance of Bitrix and Bitrix24 solutions of any complexity. From simple one-page sites to complex online stores, CRM systems with 1C and telephony integration. The experience of developers is confirmed by certificates from the vendor.
Our competencies:
Development stages
Latest works
  • image_website-b2b-advance_0.png
    B2B ADVANCE company website development
    1175
  • image_bitrix-bitrix-24-1c_fixper_448_0.png
    Website development for FIXPER company
    811
  • image_bitrix-bitrix-24-1c_development_of_an_online_appointment_booking_widget_for_a_medical_center_594_0.webp
    Development based on Bitrix, Bitrix24, 1C for the company Development of an Online Appointment Booking Widget for a Medical Center
    564
  • image_bitrix-bitrix-24-1c_mirsanbel_458_0.webp
    Development based on 1C Enterprise for MIRSANBEL
    747
  • image_crm_dolbimby_434_0.webp
    Website development on CRM Bitrix24 for DOLBIMBY
    655
  • image_crm_technotorgcomplex_453_0.webp
    Development based on Bitrix24 for the company TECHNOTORGKOMPLEKS
    976

Setting Up Multilingual Support in Bitrix24

Employees from five countries work at the company. The B24 portal is in Russian — the German office doesn't understand CRM stage names, Polish managers get confused by contact card fields, and English-speaking contractors in the extranet see an interface they can't read. Switching the interface language is half the battle. The real problem is CRM fields, document templates, and automatic notifications that remain in one language for everyone.

Interface Language Settings

Bitrix24 supports interface language switching at the portal level and at the user level.

Portal level: An administrator sets the default language in portal settings. This language applies to new users and system elements (names of standard CRM stages, task types, statuses).

User level: Each employee can switch the language in their profile. The interface — menus, buttons, system notifications — switches to the selected language. Supported languages: Russian, English, German, French, Spanish, Portuguese, Italian, Polish, Ukrainian, Vietnamese, Indonesian, Turkish, and others.

Important: interface language switching does not affect user data — CRM stage names, custom fields, document templates, and business processes remain in the language they were created in.

Multilingual CRM Fields

Standard CRM fields (company, contact, deal) don't support multiple language versions "out of the box". Solution — via custom fields and business processes:

  • Field duplication. For each language, create a set of custom fields: UF_COMPANY_NAME_EN, UF_COMPANY_NAME_DE, UF_COMPANY_NAME_RU. On the card, all variants are displayed or only the relevant one — via field visibility settings by role.
  • Automatic translation. A business process when creating or updating a CRM entity calls an external API (Google Translate, DeepL) via webhook and populates fields in other languages.
  • Contact language selection. Field UF_LANGUAGE in the contact/company card determines the preferred language of communication. Business processes and document templates orient to this field.

Multilingual Open Channels

Open channels (chat with customers via website, messengers, social media) receive inquiries in different languages. Setup:

Task Solution
Determine client language Auto-detection by text (CoPilot/API) or by channel source
Route by language Separate queues for each language. Routing rule — by UF_LANGUAGE field or by channel
Welcome templates Multiple auto-reply versions: Russian, English, German. Selection — by detected language
Quick replies Sets of quick replies for each language. Manager sees the set depending on the dialog language

For each language, you can create a separate Open Channel tied to the language channel (e.g., separate chat widget on EN-version of the site), or use one channel with internal routing.

Document Templates

The B24 document generator (invoices, quotes, contracts) works with templates. For multilingual support:

  • Create separate templates for each language: Invoice (RU), Invoice (EN), Invoice (DE).
  • In a business process or CRM robot, template selection is tied to the UF_LANGUAGE field of the contact or company.
  • Automatic generation: robot when changing deal stage creates a document in the client's language.

Notifications and Mailings

Automatic notifications (CRM robots, business processes) are sent in one language by default. For multilingual support:

  • CRM robots with condition: if UF_LANGUAGE = EN → send email template in English, if DE → in German, else — in Russian.
  • Email templates are duplicated for each language. Substitutions (client name, amount) work the same.
  • SMS notifications — similar logic by condition.

Extranet

External users (contractors, clients) in the extranet see the interface in the language set in their profile. Administrator can:

  • Set the default language for the extranet separately from the main portal.
  • Set group and project names in multiple languages (via description).
  • Prepare instructions and materials in the language of external users.

What We Implement

  • Interface language setup at portal and user levels
  • Multilingual CRM field system with automatic translation
  • Open Channel routing by client language
  • Multilingual document templates with auto-selection by contact language
  • Conditional notification and mailing logic by languages
  • Extranet localization for external users