--- title: "Choose the Right Formality in Product Interfaces and Support Messages Without Losing Trust" url: "https://linguisticsnews.com/qa/choose-the-right-formality-in-product-interfaces-and-support-messages-without-losing-trust/" author: "Linguistics News" published: "2026-10-05" updated: "2026-10-05" --- # Choose the Right Formality in Product Interfaces and Support Messages Without Losing Trust ## Choose the Right Formality in Product Interfaces and Support Messages Without Losing Trust The right level of formality can build trust, while the wrong one can quickly weaken it. This article shares practical guidance and insights from experts on adapting product interfaces and support messages across languages and markets. Learn how to set clear language rules, read customer cues, and keep every interaction respectful and consistent. ### Anchor Tone in Local Relationships When I'm working across languages, I've learned that formality isn't something you can decide by simply translating the English version and choosing the more formal option. The same level of formality can feel professional in one language and distant or unnatural in another. My decision rule is to start with the relationship, not the translation. I ask: "How would a trusted local company speak to this customer in a normal conversation?" That means looking at the market, audience, product category, and especially whether the interaction is support, onboarding, marketing, or a transactional message. One example that stands out is German. I've found that using the formal "Sie" is generally the safer starting point for customer support and professional software, particularly when the relationship is new. But even then, formality in the pronoun doesn't mean the entire message needs to sound stiff. A small phrasing change can make a major difference. Instead of translating an English command directly into something that sounds like an instruction from a manual, I prefer a more helpful construction such as "You can..." or "Here's how you can..." It gives the user control rather than making the interface sound like it is ordering them around. I've seen this principle matter across different industries. Users tend to push back when localization feels like a literal translation that ignores how people actually communicate. They're not necessarily objecting to the level of formality itself; they're reacting to language that feels unnatural or overly corporate. I also think support teams should pay attention to the language customers naturally use in their replies. If users consistently mirror a certain level of formality, that's useful feedback about the relationship they expect. For me, the goal isn't to make every localized message sound identical. It's to preserve the same feeling of respect, clarity, and usefulness while allowing each language to behave naturally. Good localization should feel like the product was written for that market in the first place, not translated into it afterward. *— [Max Shak](https://www.linkedin.com/in/mojtaba-shakiba-74002263), Founder/CEO, nerD AI* --- ### Start Strict, Then Follow Customer Cues Formal communication in global customer service is not something that can be grasped from market trends, rather it is something that should be understood as a cultural norm. Breaking this norm can lead to a perception of the service provider as incompetent. From my professional experience in managing international business process outsourcing for the clients originating from different regions of the world, I can tell that it is better to approach the communications with the clients from the perspective of their local cultural traditions rather than relying on a corporate style. The tone of messages should be identified based on the nature of the request. If the client asks about payments or security issues, it is always advisable to use the highest level of formality in communication, while in the case of requests related to communities, the tone can be more relaxed. One of the rules that help to resolve any issues at the time of communication is called the Strict-to-Casual Pivot. The rule stipulates that any greeting message is sent out in the formal form. Only if the client accepts using informal language, the support agent can use informal language. The type of expression that helped us to improve customer satisfaction in German speaking regions is the Hybrid Greeting. We replaced the outdated 'Sehr geehrte(r)' with a more modern greeting 'Hallo' along with the first name of the person. *— [Pratik Singh Raguwanshi](https://www.linkedin.com/in/pratiksinghraghuvanshi), Manager, Digital Experience, CXrove* --- ### Open Respectfully, Use Hindi Aap I believe that in all cases I use the rule of thumb: Formal language at the beginning, and then you can start to ease off once the tension in the conversation has eased. When it comes to messages about money, failed payments or transactions or customers accounts, it is better to keep to a formal, respectful tone to avoid implying that you do not care about their loss. Onboarding and offers can be a little more casual. In Hindi, I would use aap throughout, as tum can come across as quite demanding from a business perspective. Not everywhere is it the same, and some younger customers may appreciate the casual tone from some businesses, such as in the use of certain apps. My main test for this would be to read the message as your unhappy customer and imagine their reaction. If they seem offended, it is best to go for a slightly more formal message. *— [Ankit Sarawagi](https://www.linkedin.com/in/ankit-sarawagi), Curator, CFO Matrix* --- ### Map Channels, Choose French Vous Always choose the level of formality that matches the channel and the expected relationship: use formal address for transactional and support messages (order confirmations, refunds, policy changes) and more informal, friendly tone for in-product microcopy when the brand voice is casual. Decide per language by mapping each channel to a formality rule, then validate with a small A/B test or customer feedback in that market. Concrete rule that prevented pushback: for French communications we always use vous in support and transactional messages rather than tu. Switching to vous removed recurring complaints about tone and felt clearly more respectful to our international customers while keeping casual English microcopy for product pages where appropriate. *— [THERY Jean Christophe](https://www.linkedin.com/in/jean-christophe-thery-a8b158112), CEO, MusaArtGallery* --- ### Use Siz, Explain Required Corrections For a Turkish financial interface, I would default to respectful, plain language and use "siz" when a pronoun is needed. Formal address does not require long bureaucratic sentences, and friendliness does not require treating an unfamiliar user as a close friend. I publish calculators and financial explanations through Hesap Cebimde, where the reader needs to understand an input or assumption before trusting the result. My wording rule would be to explain the next action without blaming the person. For example, "Lutfen tutari sifirdan buyuk girin" tells the user what to change more clearly than "Yanlis deger girdiniz." Across languages, I would review the whole task with a native speaker rather than translate the pronoun decision mechanically. A financial error message needs calm clarity more than personality. I cannot claim that this particular phrasing change consistently prevented complaints; it is the decision rule I would use from my Turkish publishing experience. *— [Cem Oner](https://www.linkedin.com/in/cem-oner-670a68408), Founder / Finance & Public Data Publisher, Hesap Cebimde* --- ### Maintain Each Market's Established Voice I'm Charles Liu, founder and Marketing Director of Cubic Promote, a Sydney-based business employing around 30 people across Australia, the Philippines, Vietnam, and India. Our customer communication is mainly in English, but working across different countries has made me very conscious that tone does not translate word for word. In localisation, this is often described as "register," which is how formal, casual or familiar the language feels. I would decide that based on the local audience, the type of message and the relationship the brand already has with its customers. Australia is fairly comfortable with conversational business language, but that same tone can sound too familiar in another market. Support messages also need more care than marketing copy because a customer may already be frustrated when they read them. I would follow the form of address already established for that market and keep it consistent. German is a good example. "Sie" is the formal form of "you", while "du" is informal. If the website, onboarding and previous customer communication use "Sie", I would not suddenly switch to "du" in a support message because an automated translation decided it sounded friendlier. The same applies in reverse. If a brand has deliberately established an informal voice with "du", unexpectedly switching to very formal language can make the message feel cold. I also prefer simple language over translating Australian expressions or humour literally. "We can help you fix this" travels much better than a phrase that relies on slang or local culture. For me, respect comes from sounding natural in the customer's language, not from making every market sound like the Australian version of the brand. *— [Mr Charles Liu](https://www.linkedin.com/in/charles-liu-042b9124), Marketing Director, Cubic Promote* --- ### Remove Direct Address From Errors French nearly broke us. We defaulted to "tu" across the board because our English copy felt casual and we wanted to match that energy. Complaints came in within a week. French users in professional contexts read "tu" from a software product as presumptuous, not friendly. The decision rule we landed on: default to formal address in any language where the formal/informal split carries social status signals, not just politeness signals. German "Sie", French "vous", Dutch "u" in professional contexts. Informal only when the market data shows your user base skews younger and the product category is consumer, not B2B. For Pageloot, most users are marketing managers or agency leads. That pushed us toward formal in French, German, and Japanese by default, with no opt-out needed because nobody complained about being over-respected. The one phrasing change that cut pushback most: removing second-person address entirely in error messages. Instead of "vous n'avez pas" or "Sie haben nicht", we rewrote errors in passive or impersonal constructions. "The file could not be processed" lands softer than "you did something wrong" in any register, any language. It sidesteps the formal/informal question entirely while also removing blame from the user. Two problems solved with one structural change. *— [Siim Kostabi](https://www.linkedin.com/in/siim-kostabi), CEO, Pageloot* --- ### Define Persona Before Russian Translation Pick the register from who the product is speaking as, not from what the source English does, because English has no choice to make here and most other languages do. Russian is the case I know firsthand. English "you" splits into ty and vy, and the split isn't really formal versus casual, it's a claim about the relationship. A product using ty asserts a familiarity the user never agreed to, which lands as presumptuous from a company and as warm from a peer. Translators handed English strings with no guidance pick differently from screen to screen, and users notice the inconsistency long before they notice the register itself. The rule that stopped the complaints was writing the persona into the string guide before translation, in one sentence, and enforcing it in review. Ours was roughly: the product is a competent colleague, not a friend and not an institution. That settles ty versus vy, and it also settles the downstream questions nobody thinks to ask, like whether an error message apologizes. The phrasing change that did the most work was rewriting imperatives as impersonal constructions wherever the language allows it. Russian lets you state what needs to happen without addressing anyone, which sidesteps the choice entirely on exactly the screens where getting it wrong is most likely. That trick is language-specific, though. Japanese keigo isn't a two-way switch and I wouldn't pretend this rule covers it. *— [Nick Sawinyh](https://www.linkedin.com/in/sawinyh), Head of Product & GTM, Veodyn* --- ### Shift Spanish Address by Moment Spanish isn't one formality setting. Mexico and Argentina default to tu, Colombia leans more usted in service contexts, and Argentina uses vos, not tu, its own voseo. Comi runs in 9 countries, so I can't write one register and ship it everywhere. The rule I use: formality follows the moment, not the whole app. Daily logging screens stay tu, closer to how a friend checks in on you. Anything touching billing, deleted data, or an error switches to usted, because that's when someone wants distance and respect, not closeness. What I see over and over in food and health apps localized from English is tu used everywhere, including error messages, and it reads as flippant right when something's gone wrong. Dropping to usted in support and error copy, even inside an app that's tu by default, is the phrasing change that keeps that friction down. It's a small switch, but it changes who the app sounds like it thinks it's talking to. *— [Jose Gaviria](https://www.linkedin.com/in/jgaviriacol), AI Food Tech Specialist, Comi AI* --- ### Document Language Rules, Prevent Drift Pick one register per language, write it into the style guide, and don't let it drift. The pushback rarely comes from the choice itself. It comes from mixing, like a formal error message after a friendly welcome screen. In languages with a formal and informal split, such as German or Spanish, I settle it by looking at the relationship the product has with its users and at what the closest local products do, then ask a native reviewer to confirm before anything ships. I write the decision into the style guide with a handful of real strings as examples, so every new writer and translator makes the same call. Where I can, I also phrase labels and buttons to skip direct address altogether. "Save" and "Continue" don't force a choice, which takes a lot of the debate off the table. Vlad Kuzin Founder of Pact *— [Vlad Kuzin](https://www.linkedin.com/in/vlad-kuzin), Founder* --- ### Related Articles - [How to Pick the Right Level of Formality in Customer Support Messages](https://linguisticsnews.com/qa/how-to-pick-the-right-level-of-formality-in-customer-support-messages) - [Get Tone Right Across Cultures in App Error Messages and Customer Support](https://linguisticsnews.com/qa/get-tone-right-across-cultures-in-app-error-messages-and-customer-support) - [Make Multilingual Chatbots Sound Natural Without Losing Brand Voice](https://linguisticsnews.com/qa/make-multilingual-chatbots-sound-natural-without-losing-brand-voice)