Customers who contact a business on social media are doing it in public, on a screen they already have open, and they expect a reply from a person. What they get depends far less on which software you buy than on a handful of decisions you make once: how fast you commit to answer, how you sound, and what happens when you cannot fix the problem yourself.
This is a playbook for making those decisions. It deliberately does not rank tools. If you want a list of platforms, we compare them in our roundup of social media customer service software, and the playbook below works with any of them, or with a shared inbox and a spreadsheet.
One honest caution before we start. You will see confident numbers online about how quickly brands “should” reply on each network. I do not quote any here, because they vary by industry, by audience and by what you promise. Every target in this article is a policy choice that belongs to you. The job is to pick one you can keep, write it down and tell your customers.
What counts as social customer service
Customers reach you in several places, and each carries different expectations.
| Channel | Visibility | What customers usually expect |
|---|---|---|
| Comments on your posts and ads | Public | A visible reply, often a short one |
| Mentions and tags | Public | Acknowledgement, because they tagged you on purpose |
| Direct messages | Private | A conversation, closer to chat than email |
| Reviews and ratings | Public, long-lived | A considered reply that others will read later |
| Groups and communities you run | Semi-public | Staff presence and consistent answers |
| Posts that do not tag you | Public, hard to find | Nothing, unless you monitor for them |
Decide up front which of these you will serve. Saying “we answer comments and messages but do not monitor untagged mentions” is a perfectly legitimate scope. What causes harm is an unspoken scope, where customers assume you are watching a channel you are not.
Set response targets as your own policy
A response target is a promise. The only good one is a promise you can keep on a normal day and on a bad one.
How to choose a target
- Look at your own history. If you have any records of past messages and replies, see how long answers actually took, and what the slowest ordinary cases looked like.
- Count the people who answer. A target set for a team of four does not survive a holiday with a team of one.
- Separate acknowledging from resolving. Saying “we have seen this and are looking into it” is a different job from fixing it, and you can promise the first much faster than the second.
- Match the channel’s feel. Direct messages usually carry an expectation of conversation, while a comment on a month-old post does not. Your targets can differ for that reason.
- Publish your hours. If nobody answers overnight or at weekends, say so on your profile. A clear “we reply during these hours” is better than a silent gap that looks like neglect.
A target table to fill in
Copy this and replace the blanks with numbers you will actually honour.
| Type of message | First reply target | Update target | Who owns it |
|---|---|---|---|
| Urgent: outage, safety, account locked | ____ | ____ | ____ |
| Complaint or problem | ____ | ____ | ____ |
| Question | ____ | ____ | ____ |
| Praise or general comment | ____ | n/a | ____ |
| Spam or abuse | ____ | n/a | ____ |
The blanks are the point. They force a conversation about staffing that is better had now than during a crisis.
What to do when you will miss the target
Misses happen. Handle them openly.
- Post a short holding reply the moment you know. “We have your message. This one needs another team, and we will update you by [day].”
- Make sure the update arrives when you said it would, even if the update is “still working on it”.
- Never let a public thread sit with the customer’s last message unanswered while the real work happens elsewhere. A thread with no reply reads as no response.
Triage: sort before you answer
Reading a message and replying straight away is how simple questions get slow answers and serious problems get glib ones. Triage takes seconds and changes the reply.
Sort by type and by risk
| Type | Examples | Default handling |
|---|---|---|
| Question | How do I, where is, does it work with | Answer directly, link to the help page |
| Problem | It broke, I was charged twice, it is not arriving | Acknowledge, gather details privately, resolve or escalate |
| Complaint | Anger about experience or policy | Acknowledge, take it private, escalate if it involves a decision you cannot make |
| Praise | Thanks, shout-outs | Reply briefly and genuinely |
| Feature request | I wish it could | Thank, record it, do not promise |
| Abuse or spam | Harassment, scams, bait | Follow your moderation policy |
| Sensitive | Legal threats, safety, personal data, press | Escalate immediately |
Risk matters as much as type. Ask three questions of every message: Is anyone harmed or about to be? Is money, data or legal exposure involved? Is the audience large or influential? A yes to any of them moves it up the queue and usually to someone senior.
Tone: sound like a person who can help
Tone is not decoration. In a public thread, your reply is read by the customer and by everyone who scrolls past later, so you are writing for both.
Principles that hold up
- Lead with what you will do, not with an apology ritual. “Sorry for any inconvenience” tells the customer nothing. “I have flagged your order with the shipping team and will message you tomorrow” does.
- Apologise for the specific thing, and only when something went wrong on your side. A vague apology reads as a script.
- Use plain words. Avoid internal jargon, policy codes and phrases like “per our terms”.
- Match their register, not their anger. Be a little warmer than formal and a little calmer than the customer. Do not mirror hostility.
- Be short in public, fuller in private. The public reply shows you responded. The details can follow in a message.
- Write as a named person where your brand allows it. Signing a reply with a first name or initials makes it easier for the customer to follow up.
- Do not argue. You can disagree with a claim without winning the thread. Correct facts once, politely, then move to resolution.
Before and after
These are illustrations of the style, not quotes from real customers.
| Situation | Weak reply | Better reply |
|---|---|---|
| Delay complaint | “We apologise for any inconvenience caused.” | “That is a long wait, and I am sorry. I am checking where your order is and will message you by the end of today.” |
| Confused question | “Please refer to our FAQ.” | “Good question. The short answer is yes. Here is the page that walks through it, and I can help if anything is unclear.” |
| Public criticism of a policy | “Our policy is clear.” | “I can see why this is frustrating. Here is why the rule exists, and I would like to look at your case. Can you message us?” |
| Error on your side | “Mistakes can happen.” | “That was our mistake. We have fixed it and I am confirming it with you in a message.” |
| Praise | “Thank you for your feedback.” | “That made our day. Thank you for saying so.” |
Where humour and emoji fit
Humour works when the customer is already relaxed, and it backfires with someone who is upset. As a rule, mirror the customer’s mood only when it is positive. Use emoji sparingly and only if they fit your brand voice, and never in a reply to a complaint about money, safety or a serious failure.
Write a voice note for the team
A one-page voice guide prevents most tone problems. Include how formal you are, words you use and avoid, how you sign off, and two or three examples of replies the team admires. New staff and part-timers can then match the voice without guessing.
Move to private the right way
Some conversations belong in public, and some do not. The line is usually personal information.
Take it private when:
- You need an order number, an email address, an account detail or a phone number.
- The customer is describing a problem that involves their data.
- The conversation is turning heated.
- The fix needs back-and-forth that would clutter a thread.
Keep it public when:
- It is a general question other people probably have.
- It is praise.
- You are correcting a public factual error.
The handoff reply
Make the move simple and non-defensive.
Thanks for flagging this, and I am sorry for the trouble.
I would like to sort it out properly. I have sent you a
private message, so please check there. We will not need
anything sensitive in this thread.
Never ask customers to post personal or payment details in a public comment. If one posts them anyway, follow your moderation policy for hiding or removing the comment, and tell them why.
Close the loop in public
When it is fixed, return to the original thread and say so briefly, if the customer is happy for you to. Other readers see that you resolve problems, which does more for your reputation than a hundred polished posts. If the customer has not replied, a short “we have resolved this by message, and please contact us if anything changes” is enough.
Each platform sets its own rules on messaging, automated replies and how long you can contact someone after their last message. Read the current rules for every channel you serve before building automated flows, since they change and a flow that breaks them can cost you access.
Escalation: deciding who handles what
Escalation is not a sign that front-line staff failed. It is the design that lets them handle ordinary cases confidently, because they know exactly when to hand something over.
A four-level ladder
| Level | Who | What belongs here |
|---|---|---|
| 0 | Front-line agent | Questions, standard problems, praise, routine complaints |
| 1 | Support lead or senior agent | Repeat contacts, refund or exception decisions, upset customers who are not calming down |
| 2 | Product, engineering or operations | Bugs, outages, shipping or billing failures with a systemic cause |
| 3 | Leadership, legal or communications | Legal threats, safety, regulators, press, security or data incidents |
Rename the levels to match your organisation. What matters is that every level has a named person or role, a way to reach them, and a clear definition of what they decide.
Triggers that should escalate immediately
- Any mention of a lawyer, a regulator or a legal claim.
- Anything involving safety or harm to a person.
- A suspected breach of personal data or a security issue.
- A journalist, a very large account or a viral thread.
- A threat or targeted harassment of your staff.
- A customer who has contacted you several times about the same unresolved problem.
- A request outside the agent’s authority, such as an exception to a refund rule.
Write this list down and keep it short enough to remember. Add to it after real incidents.
A handoff note that does not make people repeat themselves
Customers dislike explaining the same thing twice. Use a standard note when you escalate.
Channel and link:
Customer handle:
Issue in one sentence:
What the customer wants:
What we have already told them:
Steps taken so far:
Deadline or promise made:
Why it is escalated:
Include the link to the original thread and attach any screenshots. The person receiving it should be able to act without reading the entire history.
Keep ownership clear
One person owns the customer relationship at any given time, even when others work on the fix. Tell the customer who that is and what they should expect next. When ownership changes, tell them again.
Handling difficult situations
Angry customers
Anger is usually about a specific failure plus a feeling of being ignored. Respond to both. Acknowledge the failure plainly, show that a person is on it, and give a next step with a time. Do not tell someone to calm down. If a customer is abusive, apply your moderation policy consistently and keep your replies factual.
Public criticism you believe is wrong
Reply once, calmly, with facts, and offer to look into it privately. Resist the urge to rebut every point. Readers judge you by your manner more than by who wins.
Review sites
A reply to a review is read by future customers. Thank the reviewer, address the specifics, say what you have done or will do, and offer a way to continue by message. Avoid defensive replies and never reveal personal details about a customer in a public response.
Spam, scams and impersonators
Customers often get scam messages from fake support accounts. Say publicly that you will never ask for passwords or payment details in comments, hide or report impersonators according to the platform’s tools, and make your verified channels easy to find.
Reduce the volume of repeat questions
A large part of social support is the same few questions. Cut them at the source.
- Pin an FAQ or link a help page on your profile and in your bio.
- Keep a saved-reply library, with each reply written as a starting point to personalise, never to paste unchanged.
- Fix the cause. If a question keeps arriving, the product, the checkout or the page is unclear, and no reply policy replaces fixing that.
- Give people somewhere to help each other. A customer community lets members answer common questions and gives you a searchable record. If you run your site on WordPress, our guide to building a customer support community on WordPress covers how to set up spaces, accepted answers and staff roles. That is a longer-term option, but for products with many repeat questions it can take pressure off the social inbox.
Tools: what you actually need
You can run a small social support operation with the native inbox of each platform, a shared document for saved replies and a simple log of escalations. A dedicated tool starts to pay off when several people share the work, when you need a single queue across channels, or when you want assignment, internal notes and reporting. Choose it after you have written the policies above, since the policy tells you which features matter. For scheduling and publishing tools, which are a different job, see our list of tools for social media managers. If you are weighing AI assistance for drafting replies, see best AI customer service tools, and keep a person responsible for anything customer-facing.
Measuring without fooling yourself
Pick a small number of measures and compare them to your own past, not to someone else’s average.
| Measure | What it tells you | Watch out for |
|---|---|---|
| First reply time against your target | Whether you keep your promise | Averages hide slow outliers, so also look at the slowest cases |
| Time to resolution | Whether problems actually end | Closing threads early inflates it |
| Handoffs per case | Whether front-line staff have the authority they need | Too many suggests unclear rules |
| Repeat contacts | Whether the first answer worked | Same customer, same issue is the signal |
| Themes | What to fix upstream | Needs tagging discipline |
| Customer comments | Whether tone is landing | Qualitative, so read a sample each week |
Review a sample of conversations each week as a team. Reading real threads together teaches more about tone and judgement than any metric.
Your one-page playbook
Write these on a single page and keep it where the team works.
- Scope: channels we serve and channels we do not.
- Hours: when we reply, published on every profile.
- Targets: our first reply and update commitments, by message type.
- Triage: the types and the risk questions.
- Voice: a short guide with examples.
- Privacy rules: what we never ask for in public, and when we move to private.
- Escalation ladder: levels, owners and triggers.
- Handoff note: the standard template.
- Moderation policy: what we hide, remove or report.
- Review: a weekly look at sample threads and a monthly look at themes.
Frequently asked questions
How fast should we reply on social media?
As fast as you can reliably keep, and no faster. Choose targets from your own history and staffing, separate acknowledging from resolving, and publish your hours. A promise you keep builds more trust than an ambitious one you miss.
Should we reply to every comment?
Not necessarily. Reply to questions, problems, complaints and meaningful praise. For low-value comments, such as a single emoji, a reaction may be enough. State your approach in your scope so customers know what to expect.
When should a conversation move to direct messages?
Whenever you need personal or account details, when the issue is specific to one customer, or when the conversation is heating up. Tell the customer you are moving it, why, and where to look, and close the loop in the public thread afterwards.
What should I do with a viral complaint?
Escalate immediately to whoever handles communications, reply once in public with a calm acknowledgement and a next step, and move specifics to private. Do not delete criticism unless it breaks your published rules.
Do we need a social media customer service tool?
Not at the start. A small team can use each platform’s inbox, a document of saved replies and an escalation log. Consider a tool when several people share the work or when you need one queue across channels, and decide on policies before comparing features.
How do we keep tone consistent across a team?
Write a one-page voice guide with examples, review sample threads together every week and give new staff a set of approved replies to adapt. Consistency comes from shared habits more than from rules.