Most instructions recommend "responding quickly" without clarifying where to respond. This is an error that costs the brand its reputation. The rule is simple: if the question is standard and the answer demonstrates competence — respond publicly, in comments or under the post. If the question includes an order number, passport details, personal complaint, or emotional conflict — transfer it to direct messages or private messages in the first reply, not after three public exchanges.
A public response to a standard question is not a waste of time, but a showcase. It is read by dozens of potential clients who would never write on their own but will draw conclusions about the brand based on how it responds to others. This is how community self-support is built: if a brand has accumulated a pool of quality public answers to frequent questions, part of the audience solves their problem simply by reading someone else's conversation before reaching out to support themselves.
The rule for transferring to private is formulated as follows:
Channels are not equal to each other, and measuring them with one metric is the second typical mistake. Facebook remains the global leader by volume of support traffic, but in individual countries the picture is different: in Germany, India, Italy, and the Netherlands, WhatsApp leads, while among younger audiences Instagram is growing fastest. Relying on 'market average' figures without tying them to your own geography and audience is a guaranteed miss in planning support resources.
| Channel | Strength | Key KPI |
|---|---|---|
| Mass reach, convenience of chat history | Response rate, time to first response, CSAT after ticket closure | |
| Young audience, visual complaints (product photos) | Speed of response in Stories/Direct, share of resolved inquiries without escalation | |
| Personal, 'friendly' tone, leader in several countries | Time to first response (critical — expectations are higher than in other channels), NPS | |
| X (Twitter) | Publicity, speed of complaint spread | Time to public reaction, reduction of negative tone, reach of public response |
A pure marketing model is good for brand image, but does not solve customer problems. Pure support responds according to schedule, but loses brand tone. The working scheme is hybrid, with clear separation by content type, not by channel as a whole.
The case of OBI and SkyNet shows that with a properly configured process, it is possible to redirect up to 15% of calls from the call center to social networks — and halve the negative feedback simply by improving response speed. This is not theoretical benefit, but a direct reduction of the load on the expensive channel (phone) in favor of a cheaper and faster one.
Response speed is not the only metric and certainly not the main one. CSAT depends directly on response time: with responses within 5 minutes, satisfaction holds at 92%, within an hour it drops to 78%, after a day it falls to 51%, and after more than a day it drops below 40%. This gives a clear benchmark: teams that respond in their own communities within 5–10 minutes, and on external platforms within an hour, achieve maximum CSAT.
But speed should be tracked together with three things that are usually overlooked:
Case of S7 Airlines — a clear illustration of scale: the company processed 85 thousand questions through social media in a year, of which 67 thousand were during quarantine. This proves that social networks can become the primary support channel, not a secondary addition to phone and email.
It's easy to make mistakes in both directions here. 67% of consumers prefer a live person to a chatbot — this is a fact that is often used as an argument against automation in general. But a significant portion of people are open to automation if it actually solves a problem quickly. There is no contradiction here: customers are not irritated by the bot per se, it's the bot that doesn't know how to admit its uselessness and transfer the conversation to a human.
A working automation scheme in support via social networks:
73,3% of consumers prefer messaging to traditional communication channels, and most are annoyed if a brand has no such option at all. 77% of customers expect an immediate response when contacting a company through any channel—social networks, where communication happens in real time in front of other users, set this standard faster than email or phone.
Originally, social networks were a content distribution channel, and customer inquiries in comments were perceived as a side effect. This has now reversed: for part of the audience, especially the young, social networks are the first and only channel of contact with a brand. Hence, three models of operation that are found in companies: marketing-oriented (social networks are managed by marketing, and complex issues are transferred to email or phone), support-oriented (a separate team with SLA, but without brand tone), and hybrid, described above—only it simultaneously covers speed, tone, and systemacity.
Most instructions recommend "responding quickly" without clarifying where to respond. This is an error that costs the brand its reputation. The rule is simple: if the question is standard and the answer demonstrates competence — respond publicly, in comments or under the post. If the question includes an order number, passport details, personal complaint, or emotional conflict — transfer it to direct messages or private messages in the first reply, not after three public exchanges.
A public response to a standard question is not a waste of time, but a showcase. It is read by dozens of potential clients who would never write on their own but will draw conclusions about the brand based on how it responds to others. This is how community self-support is built: if a brand has accumulated a pool of quality public answers to frequent questions, part of the audience solves their problem simply by reading someone else's conversation before reaching out to support themselves.
The rule for transferring to private is formulated as follows:
Channels are not equal to each other, and measuring them with one metric is the second typical mistake. Facebook remains the global leader by volume of support traffic, but in individual countries the picture is different: in Germany, India, Italy, and the Netherlands, WhatsApp leads, while among younger audiences Instagram is growing fastest. Relying on 'market average' figures without tying them to your own geography and audience is a guaranteed miss in planning support resources.
| Channel | Strength | Key KPI |
|---|---|---|
| Mass reach, convenience of chat history | Response rate, time to first response, CSAT after ticket closure | |
| Young audience, visual complaints (product photos) | Speed of response in Stories/Direct, share of resolved inquiries without escalation | |
| Personal, 'friendly' tone, leader in several countries | Time to first response (critical — expectations are higher than in other channels), NPS | |
| X (Twitter) | Publicity, speed of complaint spread | Time to public reaction, reduction of negative tone, reach of public response |
A pure marketing model is good for brand image, but does not solve customer problems. Pure support responds according to schedule, but loses brand tone. The working scheme is hybrid, with clear separation by content type, not by channel as a whole.
The case of OBI and SkyNet shows that with a properly configured process, it is possible to redirect up to 15% of calls from the call center to social networks — and halve the negative feedback simply by improving response speed. This is not theoretical benefit, but a direct reduction of the load on the expensive channel (phone) in favor of a cheaper and faster one.
Response speed is not the only metric and certainly not the main one. CSAT depends directly on response time: with responses within 5 minutes, satisfaction holds at 92%, within an hour it drops to 78%, after a day it falls to 51%, and after more than a day it drops below 40%. This gives a clear benchmark: teams that respond in their own communities within 5–10 minutes, and on external platforms within an hour, achieve maximum CSAT.
But speed should be tracked together with three things that are usually overlooked:
Case of S7 Airlines — a clear illustration of scale: the company processed 85 thousand questions through social media in a year, of which 67 thousand were during quarantine. This proves that social networks can become the primary support channel, not a secondary addition to phone and email.
It's easy to make mistakes in both directions here. 67% of consumers prefer a live person to a chatbot — this is a fact that is often used as an argument against automation in general. But a significant portion of people are open to automation if it actually solves a problem quickly. There is no contradiction here: customers are not irritated by the bot per se, it's the bot that doesn't know how to admit its uselessness and transfer the conversation to a human.
A working automation scheme in support via social networks:
73,3% of consumers prefer messaging to traditional communication channels, and most are annoyed if a brand has no such option at all. 77% of customers expect an immediate response when contacting a company through any channel—social networks, where communication happens in real time in front of other users, set this standard faster than email or phone.
Originally, social networks were a content distribution channel, and customer inquiries in comments were perceived as a side effect. This has now reversed: for part of the audience, especially the young, social networks are the first and only channel of contact with a brand. Hence, three models of operation that are found in companies: marketing-oriented (social networks are managed by marketing, and complex issues are transferred to email or phone), support-oriented (a separate team with SLA, but without brand tone), and hybrid, described above—only it simultaneously covers speed, tone, and systemacity.