Formal vs informal tone in customer service has no single right answer for every business, but it has one wrong one: both at once. A customer who gets “Hi! What can we help with?” and, a moment later, “We hereby inform you, Sir” feels they are dealing with two different companies. The register is a team decision that covers every text a customer reads.
Below: a decision grid by audience and channel, when to go formal, what to do when the customer changes tone, and where the register drifts, from greetings and macros to AI drafts. English has no separate polite “you”, so the choice shows in names, phrasing and sign-offs.
What decides between formal and casual
Start with how your customers write to you, not with how the brand would like to sound. Young buyers in a sportswear shop will accept “Hi Sam” without a second thought. A clinic patient or an older customer asking about an invoice is more likely to expect “Dear Ms Taylor”. Read recent conversations and note how customers open them.
Scroll the table sideways to see all columns.
| Situation | Default register | Watch out for |
|---|---|---|
| Lifestyle shop, young customers, Instagram messages | Casual, first names | Keep complaints and payment issues calm, without slang |
| Website chat for a local service, customers of all ages | Neutral or formal | Impersonal phrasing like “Order number required” feels stiff in a longer chat |
| Health, finance, legal, official matters | Formal, title and surname | Do not switch to first names until the customer invites it |
| Business customers, quotes and wholesale enquiries | Formal first, then whatever the contact uses | In a message to several people, address the team, not one person |
The grid is a starting point, not a rule: a fictional neighbourhood florist can stay on first-name terms with regulars. What matters is a one-sentence rule everyone who answers customers knows: “In chat and on Instagram we write casually and use first names; in emails to companies we stay formal.”
The channel shapes expectations, not the brand
An Instagram DM feels like a chat with a friend, so customers often open with “hey”. Website chat is more often used by someone who wants specifics or reports a problem, where a formal register rarely feels out of place. Defaults can differ per channel, as long as one conversation keeps its register. How to bring social messages into the same inbox is covered in the guide to customer service on Facebook and Instagram.
Watch for customers who move between channels. If someone started casually on Instagram and returns via website chat, a sudden “Dear Mr Lee” sounds like distancing yourself. The practical rule: the register follows the conversation with a specific person, not the channel you happen to reply in.
Nielsen Norman Group describes formal versus casual as one of four dimensions of tone and advises keeping a consistent brand personality while adapting tone to the situation and the reader's state. NN/g, Kate Moran. The article does not test support chats and does not show which register sells better.
When to switch to a formal register
Even a team that writes casually needs exceptions. A complaint, a payment dispute, a health issue or a request to delete personal data are moments when a breezy tone can read as dismissive. Drop jokes, filler and exclamation marks. If the customer writes formally and is clearly tense, answer in their register. The complaint process itself is covered in the guide to handling complaints in written channels.
Casual: “Sorry the parcel arrived damaged. Could you send a photo of the box and the item? I'll sort out a replacement today.” Formal: “I am sorry the parcel arrived damaged. Please send a photo of the packaging and the product, and I will decide on a replacement today.”
Both carry the same specifics: what to do and when the decision comes. List the cases that need the calmer register in your guidelines.
What to do when the customer changes register
The customer writes “Please, call me Tom” or switches to “thanks, can you also check…”. In service, the customer usually sets the level of familiarity: an agent should not shorten the distance alone, but can accept the invitation.
- Follow the customer's lead.If the customer has clearly moved to first names, reply the same way until the end of the conversation. Sticking to “Mr Smith” after the offer sounds like a refusal.
- Do not slip back.Once changed, keep the register in every later message, including ones sent from a macro or an AI draft.
- Leave a note.A short internal note such as “prefers first name, casual” lets the next colleague continue in the same register after a handoff.
- Do not change the team rule.One casual customer does not change your default. New conversations still start in the agreed register.
If the customer answers your casual message with “Dear Sir”, switch to formal from your next message without comment.
One register in greetings, macros and AI knowledge
The register drifts because ready-made texts were written by different people. The widget greeting says “Drop us a line”, a quick reply says “Kindly provide your order number” and the refund macro opens with “Dear Customer”. The greeting itself is covered in the guide to live chat greetings, and building reusable replies in the guide to customer service response templates.
- Greeting, start screen and offline mode in every widget language.
- Quick replies the customer sees in the empty chat window.
- Agent name and AI assistant name shown in the widget.
- Team and private macros, including their variables and preview.
- Help articles and manual FAQs used by Meet AI.
- Success screens, the rating request and the callback confirmation.
In Meetlead customer service you can go through these places one by one: widget copy is edited separately for Polish, English and German, and private and team macros show a preview with variables filled in. Meet AI has no setting for formal or casual address. The assistant and Copilot base their answers on your knowledge, so write articles and FAQs in the chosen register rather than in a detached third person. Check the result in private tests first.
If you also serve German-speaking customers: the official rules of the Council for German Orthography (2024 edition) require the polite “Sie” and “Ihr” to be capitalised, while “du” and “ihr” are lowercase, with capitals allowed in letters. Rat fuer deutsche Rechtschreibung, sections 65-66. The rules cover spelling only and do not say whether a company should address customers with “du” or “Sie”.
Check each draft for mixed registers before sending
A Copilot draft is visible only to the agent and nothing is sent without their decision. Use that moment for one check: does the whole message keep the register of the conversation? Typical slips are a switch halfway through, a formal salutation followed by casual instructions, and a stiff macro sign-off pasted under a friendly reply. “Fix text” corrects spelling, punctuation, grammar and awkward phrasing while keeping the tone, so do not count on it to make the register consistent for you.
Scroll the table sideways to see all columns.
| Draft with a slip | Problem | Corrected version |
|---|---|---|
| “Dear Mr Clarke, just pop into your inbox and grab the link.” | Formal salutation, slangy instruction | “Dear Mr Clarke, please check your inbox for the link.” |
| “Hey! Please be advised that your shipment has been dispatched.” | Casual greeting, bureaucratic phrasing | “Hey, your parcel is on its way.” |
| “We'll refund you within 3 days. Yours faithfully, Customer Services.” | Formal macro sign-off after a casual chat | “We'll refund you within 3 days. Cheers, Ola.” |
While fixing the register, do not change the facts. Amounts, dates and promises in the draft must survive editing intact, as explained in the guide to AI proofreading without changing facts. A long or jargon-heavy message can be simplified with the checklist in the guide to plain language in replies.
Questions about addressing customers
Does an impersonal style solve the problem? Partly. Phrases like “Photos can be uploaded here” avoid the choice, but in a longer conversation they sound like a letter from a government office. In the chat itself, pick one register and stick to it.
Should we use the customer's first name? Only if it fits your register and the customer has given it. In a formal chat, title and surname are safer until the customer signs off with a first name. Write the rule into your team guidelines and apply it in macros and the knowledge base, so the customer never sees both styles in one conversation.
