Which Language Does the CRM Answer In? Interface, Invoice, E-mail and the AI
Most small firms do not work in one language. The owner reads the interface in German, the accountant prefers Ukrainian, one customer writes in English, and the tax adviser will not accept anything but German. Firmspace keeps these layers apart on purpose, and the AI assistant follows the same rules. This article is about which layer chooses which language — and where the choice must stay with a person.
Two questions hide behind the word “language”. “In which language do I see the CRM?” is a preference: the interface exists in German, English, Ukrainian and Uzbek, and the person in front of the screen decides. “In which language does this invoice go to the customer?” is a tax and legal question. Mixing the two is how a firm ends up sending German customers a document that looks foreign.
Firmspace answers the second question from a single place: the country the firm registered in Finance. A German firm issues invoices in German, a Ukrainian firm in Ukrainian, an Uzbek firm in Uzbek. The rule lives in one function, and the interface of the person who clicks “send” has no vote in it. One source of truth means an invoice and a quote cannot drift into different languages depending on which screen they were opened from.
When an invoice is e-mailed, the language is resolved in a fixed order: a language chosen explicitly for this send, then the firm’s market language, then English as the last resort. The comment in the code tells its own story — until this rule existed, the letter always went out in English. Today a German customer receives a German PDF by default, and an explicit choice remains possible for the one-off English invoice.
The AI assistant follows a different rule. Its default is the interface language, but a message in another language wins: the system prompt asks for a reply in the interface language unless the user writes in another one. A Ukrainian accountant working in the German interface who asks in Ukrainian gets Ukrainian back; the German owner who types German gets German. There is no separate “assistant language” switch to forget — the answer follows the message, not the profile.
Voice input changes the rule once more. In voice mode the answer is read aloud, so the assistant answers in the language the person just spoke — explicitly not the interface language. The prompt also warns that speech recognition may return words in another script or with errors, especially in Uzbek, and instructs the model to interpret them by sound and intent using CRM vocabulary such as mijoz, hisob-faktura, buyurtma and shartnoma. That is guidance, not a guarantee: with a heavy accent or a noisy room the transcript can still be wrong, and then the assistant is expected to ask one short question instead of guessing.
For four frequent requests — open a page, list invoices, give the finance overview, check stock — the CRM does not wait for a second model round. The server composes the spoken summary itself, and it needs the language before the model is involved. It reads the alphabet: і, ї, є or ґ without ы, э or ъ means Ukrainian; other Cyrillic means Russian; German letters or common German words mean German; anything else is English. Counts, sums and days overdue are then pronounced in that language, with the right plural form. Everything outside these four requests still goes to the model.
The e-mail language follows the recipient, not the author. When the assistant is asked to reply to a message or write a new letter, it reads the thread first and writes in the language of the other person, showing the draft in the chat. The send tool carries the same sentence: write the body in the recipient’s language. Nothing leaves the mailbox until the owner confirms the text, so a wrong language is caught before it becomes a customer’s first impression.
The chat widget on the public website is a different assistant with a smaller job. It has no CRM data and no tools, only the platform knowledge base, and it answers in the language the visitor writes in, using the page language as a hint. Its hand-over sentence exists in German, Ukrainian, Russian and English, and prices in the chat are converted to the currency of the visitor’s language so the number in the bubble matches the pricing page. A German visitor asking about plans should not receive an English answer with dollars.
Automation messages stay exactly as the firm wrote them. A rule’s e-mail, notification or note is a template with variables; the CRM substitutes names, numbers and dates but does not translate the sentence. That is deliberate: a text that goes to customers should be read by a human before a machine sends it to a list. If you serve a German and a Ukrainian market, keep two templates instead of hoping for automatic translation between them.
Mixed messages are the normal case in a multilingual team — “Hallo, можно счёт?” is a real sentence, not an edge case — and the model resolves them by intent rather than by a strict rule. Names transliterated in two scripts may be found differently in search. A document language chosen explicitly can contradict the market: useful for a one-off English invoice, risky as a habit. And a document with legal weight should still be read by a person before it leaves the firm.
A short checklist. Set the firm’s country in Finance, because it decides the default language of customer documents. Write customer e-mails in the customer’s language, even when the rest of the team works in another one. Review the templates of automation rules once per market. Use the explicit document language as an exception and remember which invoice received it. In voice mode, speak the language you want the answer in.
A language setting looks like a detail until a German tax adviser receives an invoice with English labels, or a Ukrainian customer gets a letter in a language they never used with you. Firmspace CRM keeps four layers apart — interface, assistant, document, correspondence — because each of them answers to a different authority: a person, a model, a tax office and a customer.