A customer DMs you: “My order was supposed to arrive yesterday. Where is it?” An hour later she posts the same question under your latest Reel. Then she finds your manager’s personal WhatsApp in an old Story and writes there, but the manager is on vacation. The reply lands the next day. By then the comments say “they never answer, avoid”, and there is a one-star review on Google.
It’s rarely that the team doesn’t care. Requests are scattered across five apps, nobody knows whose turn it is to answer, and every reply gets written from scratch. Customer service on social media breaks on process, not on politeness.
Below: realistic reply targets, one inbox for every channel, public versus private replies, six reply frames, an escalation map and four metrics worth tracking.
How long you can stay silent: response-time targets
There’s no universal number, but each channel sets expectations. In a messenger, people see “read” and expect a reply as if from a friend. In comments they’ll wait longer, but everyone sees your silence.
| Channel | Working target for first reply | What matters |
|---|---|---|
| Instagram DM, WhatsApp, Messenger | 15–60 minutes in business hours | The clock starts at “read” |
| Question in comments | 2–4 hours | Everyone with the same question will read it |
| Complaint in comments | within 1 hour | First reply acknowledges; the fix can come later |
| Review on Google, Yelp, Trustpilot | within 24 hours | Future customers read it, not just the author |
| Nights and weekends | instant auto-reply | An honest time when a human will answer |
These aren’t research findings. They are targets a team of one or two can hold without heroics. If 15 minutes is out of reach, put the real number in your bio and auto-reply: “We reply within 2 hours, 9 am to 8 pm.” A promise you keep beats an ambitious one you break daily.
Separate two things: time to first reply and time to resolution. “Got it, checking your order, back to you by 3 pm” within five minutes is service, even if the fix comes that evening.
One inbox for every channel
While requests live on the owner’s phone, a manager’s account and a courier group chat, those targets are out of reach. Step one: get everything into one place.
Built-in tools, up to roughly 20–30 conversations a day:
- Meta Business Suite — a shared inbox for Facebook, Instagram and a connected WhatsApp account: messages and comments in one feed, saved replies, labels, and assigning a conversation to a teammate.
- WhatsApp Business app — greeting message, away message, quick replies via ”/”, labels like “new customer” and “pending payment”.
- Telegram Business — business hours, quick replies, greeting and away messages right in a personal account, plus a connected bot. Requires Telegram Premium.
Dedicated tools, once volume grows or two or more people answer: helpdesks and social inboxes such as Zendesk, Freshdesk, Help Scout, Gorgias for online stores, or the inbox in Sprout Social. What you pay for isn’t a prettier interface: you see who picked up a conversation, and the customer’s history survives a switch from Instagram to WhatsApp.
The sign it’s time to switch: two teammates gave one customer different answers, or someone asked in the team chat “did anyone reply to this person?”
DM auto-replies and flows are covered in our guide to Instagram DM automation.
Public reply or DM
If the answer helps others, reply publicly. Anything that needs personal data goes to DMs, after a public acknowledgment.
- Price, shipping times, size availability — answer in the comments. The next ten people with the same question will read it instead of asking.
- Order number, address, phone, payment — DMs only. Never ask for a phone number in the comments: some people will post it, and it stays there forever.
- Complaints — public reply first, then DMs. The public part is for whoever reads the thread tomorrow.
A reply that works:
“Maya, sorry about the delay — that shouldn’t happen. We’ve sent you a DM: once we have your order number, we’ll tell you where the package is by 3 pm.”
The bad version is “Please DM us.” It hands the work to an unhappy person and, from the outside, looks like hiding the problem. Delete negative comments only when they contain abuse, spam or someone’s personal data. When complaints start piling up, switch to our social media crisis playbook.
Templates that don’t read like templates
A template is a frame, not a finished reply. Each one needs four elements: a name, specifics, a time frame and a next step. Rewrite about a fifth of it for the person in front of you, or by the third identical reply in a thread people will notice.
| Situation | Frame |
|---|---|
| Where’s my order | ”[Name], we checked: order [number] is with the courier and arrives [date]. Here’s the tracking link. If it’s not there by [date], message us and we’ll fix it” |
| Price question | ”[Service] is [price], which includes [what]. You can book [how]“ |
| Quality complaint | ”[Name], sorry this happened. Could you send a photo? By [time] we’ll offer a replacement or a refund” |
| After hours | ”We’re offline now and back tomorrow at 9 am. Prices and address are in the pinned post” |
| Need time to check | ”Fair question — we’re checking with [team]. We’ll get back to you by [time], even if we don’t have the full answer yet” |
| Closing | ”Glad we sorted it out. Anything else, just write here” |
What to avoid: “Your inquiry is very important to us”, “We apologize for any inconvenience”, and “Unfortunately, we can’t help” with no reason and no next step. And don’t dispute the customer’s facts before checking them.
Keep templates in a shared doc and update them when prices or policies change. An outdated template quoting last year’s price creates a fresh complaint.
Who answers and when to escalate
In a small team, service fails not from volume but from “I thought you were replying.” You need an on-duty rotation: at any given moment, exactly one person owns the inbox.
Agree in advance what goes up the chain:
| Situation | To whom | When |
|---|---|---|
| Refund above an agreed amount, say $50 | Manager | Same day |
| Legal threat, complaint to a regulator | Owner | Immediately |
| Creator or journalist with a grievance | Owner or PR | Immediately |
| Same complaint for the third time this week | Whoever owns that process | Within the week |
The last row matters more than it looks. Eight messages a week saying “the courier never called” is not a service problem but a delivery problem, and no template fixes it. For tone in public replies, see our guide to community management.
Four metrics to check weekly
- First response time — the median, not the average. One reply after two days wrecks the average without showing how you usually work.
- Unanswered conversations. The target is zero. At the end of each day check every channel, including comments on old posts: people write there too.
- Repeat contacts. A customer writing again about the same issue means the first reply didn’t solve it.
- Top five reasons for contact. The most underrated metric. If people ask about international shipping ten times a week, put it in your bio, a pinned post and a Stories highlight. Good service eventually cuts the number of questions, not just reply time.
When social media is the wrong support channel
- Sensitive data. Banking, healthcare, legal services: ID numbers and diagnoses don’t belong in DMs. Move the customer to a secure channel — an account portal, your website, a call.
- Complex technical issues. If a fix takes three days and five people, the thread gets lost without a ticketing system. Social is the entry point, not the workspace.
- A 24/7 promise nobody can keep. An honest “we reply 9 am to 9 pm” beats “always here for you” followed by silence on Sunday.
- Hundreds of requests a day. At that volume built-in tools stop helping: you need a helpdesk and probably a dedicated person per shift.
Repost21 isn’t a helpdesk and has no shared inbox. It helps with the other side of service: answers to your top five questions can go into the content calendar as FAQ posts, and Luna drafts replies from the prices and policies in your brand knowledge base — the Google Docs or Notion pages you already maintain. Try it free.