Alignment of tone between marketing, PR and support
Why tone diverges and how this hurts the brand
Marketing's task is to engage and sell, so the tone is lively, emotional, sometimes playful. PR's task is to manage reputation, so the tone is measured, legally safe, sometimes formal. Support's task is to quickly resolve issues, so the tone is utilitarian, sometimes dry due to macros written five years ago. Each department optimizes the tone for their own metrics, and that's normal, as long as the customer doesn't encounter all three channels in a row.
The problem is not that tones are different — but that the difference is perceived as brand inconsistency, not as contextual adaptation. A customer who read a friendly post in social media and then received a bureaucratic response from support on a complaint concludes: 'friendliness is only for advertising, and that's really how they are.' This destroys trust faster than any single error in the text.
Who decides: responsibility matrix instead of negotiations
The most common mistake when implementing a consistent tone is creating a committee that meets once a month and discusses disputed cases. This doesn't work: each agreement turns into reopened negotiations, and decisions are made slower than conflicts arise. A working solution is a pre-defined matrix such as RACI, where for each type of decision it is specified who approves, who advises, and within what timeframe.
| Type of decision | Who approves | Who advises | Duration |
|---|---|---|---|
| New support macro | Support manager | Brand manager | 15 minutes for review |
| Crisis comment for media | PR director | Marketing, lawyer | until 1 o'clock |
| The tone of the advertising campaign | Brand manager | PR | alignment at the briefing stage |
| Updating the overall tone guideline | Brand owner (brand director) | Marketing, PR, support | once per quarter |
Without such a matrix, every dispute over formulation goes to the management level, and the decision depends on who insisted more loudly. With a matrix, the conflict is resolved in minutes, because it is already clear in advance whose word is final.
How to check that the tone is really working, and not just declared
A guideline can be written perfectly and still encounter divergence in practice. This is verified through audits of actual communications, not through re-reading the document. Support audits often apply the 70/20/10 pattern: approximately 70% of responses are neutral and do not raise questions, 20% subtly drift away from positioning— not rudely, but already not the 'right' brand, and 10% clearly contradict the guideline. It is precisely on these 10% that main attention should be focused, not on completely rewriting the entire body of text.
For spot checking, the quick metric voice review works well: 15-minute check of each new macro against two questions — whether it uses a brand categorical noun and whether it contradicts positioning. According to practitioners' assessment, such simple checking reduces the number of tone errors by 80%. This is cheaper and faster than manual monthly audit of hundreds of dialogs.
One ton, different channels: a table instead of abstractions
Abstract formulations such as 'we are friendly but professional' do not solve anything at the level of a specific letter or chat response. A table with examples of phrases for each channel works — phone, email, chat, social networks, status page — where you can see that the same value sounds different but not contradictorily.
| Channel | Example of a phrase | What is preserved |
|---|---|---|
| Phone | "I understand, the situation is unpleasant, we'll sort it out together" | empathy, live speech |
| Email support | "Thank you for your inquiry. We are looking into it and will get back to you before 18:00" | empathy + specificity regarding timeframes |
| Chat | "I'm looking at it, one second" | the same empathy, but shorter and faster |
| Social Media | "We hear you, looking into it, will write in direct" | public empathy without disclosure of details |
| Status page | "We are observing a failure, working on resolving it" | the same honesty, but more formal |
Such a table eliminates the main source of disputes between departments — not 'what our tone is,' but 'how exactly it sounds in my channel.' PR gets a formal, but not impersonal, variant; support gets a quick, but not rude, one.
How to embed tone into working systems, not check manually
A guideline that lives in a PDF file does not scale — nobody opens it after the first week. The agreed tone must be embedded where employees actually work: in CMS templates, in CRM macros, in email signatures.
- Identify the 20 most frequently used support macros — according to the Pareto principle, revising just these will resolve approximately 60% of all tone-related issues; afterward, proceed with the residual principle.
- Run every new or modified macro through a 15-minute voice review before publication, not after customer complaints.
- Embed the table of phrases by channels directly into the systems — as hints in CRM, not in a separate document.
- Introduce regular audits with feedback, not one-time training. The case of MTS is telling: to align the tone of support among more than 8000 employees, a three-layer approach was required — practical sessions on typical errors, a video course with live examples, and regular audits with feedback. One guideline mailing was insufficient.
The point of this entire mechanism is simple: tone alignment is not a one-time project of the brand department, but a recurring process with responsible persons, metrics, and control points within the systems where people write to clients every day. The document is important as a base, but it is precisely the verification process and the decision matrix that determine whether the brand will sound the same six months after it was written.
Why tone diverges and how this hurts the brand
Marketing's task is to engage and sell, so the tone is lively, emotional, sometimes playful. PR's task is to manage reputation, so the tone is measured, legally safe, sometimes formal. Support's task is to quickly resolve issues, so the tone is utilitarian, sometimes dry due to macros written five years ago. Each department optimizes the tone for their own metrics, and that's normal, as long as the customer doesn't encounter all three channels in a row.
The problem is not that tones are different — but that the difference is perceived as brand inconsistency, not as contextual adaptation. A customer who read a friendly post in social media and then received a bureaucratic response from support on a complaint concludes: 'friendliness is only for advertising, and that's really how they are.' This destroys trust faster than any single error in the text.
Who decides: responsibility matrix instead of negotiations
The most common mistake when implementing a consistent tone is creating a committee that meets once a month and discusses disputed cases. This doesn't work: each agreement turns into reopened negotiations, and decisions are made slower than conflicts arise. A working solution is a pre-defined matrix such as RACI, where for each type of decision it is specified who approves, who advises, and within what timeframe.
| Type of decision | Who approves | Who advises | Duration |
|---|---|---|---|
| New support macro | Support manager | Brand manager | 15 minutes for review |
| Crisis comment for media | PR director | Marketing, lawyer | until 1 o'clock |
| The tone of the advertising campaign | Brand manager | PR | alignment at the briefing stage |
| Updating the overall tone guideline | Brand owner (brand director) | Marketing, PR, support | once per quarter |
Without such a matrix, every dispute over formulation goes to the management level, and the decision depends on who insisted more loudly. With a matrix, the conflict is resolved in minutes, because it is already clear in advance whose word is final.
How to check that the tone is really working, and not just declared
A guideline can be written perfectly and still encounter divergence in practice. This is verified through audits of actual communications, not through re-reading the document. Support audits often apply the 70/20/10 pattern: approximately 70% of responses are neutral and do not raise questions, 20% subtly drift away from positioning— not rudely, but already not the 'right' brand, and 10% clearly contradict the guideline. It is precisely on these 10% that main attention should be focused, not on completely rewriting the entire body of text.
For spot checking, the quick metric voice review works well: 15-minute check of each new macro against two questions — whether it uses a brand categorical noun and whether it contradicts positioning. According to practitioners' assessment, such simple checking reduces the number of tone errors by 80%. This is cheaper and faster than manual monthly audit of hundreds of dialogs.
One ton, different channels: a table instead of abstractions
Abstract formulations such as 'we are friendly but professional' do not solve anything at the level of a specific letter or chat response. A table with examples of phrases for each channel works — phone, email, chat, social networks, status page — where you can see that the same value sounds different but not contradictorily.
| Channel | Example of a phrase | What is preserved |
|---|---|---|
| Phone | "I understand, the situation is unpleasant, we'll sort it out together" | empathy, live speech |
| Email support | "Thank you for your inquiry. We are looking into it and will get back to you before 18:00" | empathy + specificity regarding timeframes |
| Chat | "I'm looking at it, one second" | the same empathy, but shorter and faster |
| Social Media | "We hear you, looking into it, will write in direct" | public empathy without disclosure of details |
| Status page | "We are observing a failure, working on resolving it" | the same honesty, but more formal |
Such a table eliminates the main source of disputes between departments — not 'what our tone is,' but 'how exactly it sounds in my channel.' PR gets a formal, but not impersonal, variant; support gets a quick, but not rude, one.
How to embed tone into working systems, not check manually
A guideline that lives in a PDF file does not scale — nobody opens it after the first week. The agreed tone must be embedded where employees actually work: in CMS templates, in CRM macros, in email signatures.
- Identify the 20 most frequently used support macros — according to the Pareto principle, revising just these will resolve approximately 60% of all tone-related issues; afterward, proceed with the residual principle.
- Run every new or modified macro through a 15-minute voice review before publication, not after customer complaints.
- Embed the table of phrases by channels directly into the systems — as hints in CRM, not in a separate document.
- Introduce regular audits with feedback, not one-time training. The case of MTS is telling: to align the tone of support among more than 8000 employees, a three-layer approach was required — practical sessions on typical errors, a video course with live examples, and regular audits with feedback. One guideline mailing was insufficient.
The point of this entire mechanism is simple: tone alignment is not a one-time project of the brand department, but a recurring process with responsible persons, metrics, and control points within the systems where people write to clients every day. The document is important as a base, but it is precisely the verification process and the decision matrix that determine whether the brand will sound the same six months after it was written.
Recent articles
MegaFon, BMW, VTB and more 240+ companies. See how it looks in the showcase reel:
Our branding agency is approached to order:
Branding agency services
