Most people who message a brand on social expect an answer the same day, and within a few hours if it involves money or a problem. Public comments run on a tighter clock than DMs, because the wait is visible to everyone scrolling past. Reviews run on a looser one — days, not hours — but they stay online forever, which makes them the least urgent and most permanent surface you own.
The useful question isn't "how fast is fast enough?" It's "what's the slowest I can promise and still hit every single time?" A dependable four-hour reply beats an erratic instant one, because consistency is what customers actually notice. This is the operating playbook for picking that number and hitting it without living in your notifications. The measurement side — how to calculate and track it — is covered in social media customer service metrics.
Response time is a promise, not a personal record
Response time is the gap between someone reaching out and your first human reply. Two things about it trip people up.
First, track the median, not the average. One message you answered four days late will drag your mean into fiction while hiding that most replies went out in an hour. The median tells you what a typical customer actually experienced.
Second, response time is worthless without response rate — the share of reply-worthy messages you answered at all. A two-hour median across the 40% of messages you noticed is not a good number; it's a measurement of your notification settings. Speed only counts on messages you actually saw.
What people expect, surface by surface
Expectations are not uniform. The same customer will tolerate a two-day wait on a review reply and feel ignored after ninety minutes on an unanswered comment about a broken order. Here's how the surfaces differ, and what a one-person operation can realistically commit to.
| Surface | What people expect | Realistic solo promise |
|---|---|---|
| Public comment on a live post | Fast — minutes to a couple of hours while the thread is active | Same day; within your post-publish window if it lands in the first hour |
| Public complaint (any surface) | Immediate acknowledgment | Same business day, no exceptions |
| DM from an existing customer | Hours, not days | Same business day during stated hours |
| DM / message request from a stranger | Hours, but tolerance is higher | One business day |
| @-mention or tag | Optional, but noticed when answered | Next sweep; no guarantee |
| Review (Google Business and similar) | Days, not hours | Within 2–3 business days, always |
Three of these deserve unpacking.
Public comments are the urgent ones. People treat DMs as a queue and comments as a conversation. An unanswered question under this morning's post reads as neglect to everyone who scrolls past — and keeps reading that way for years. If you have attention for one surface only, make it comments on your two or three most recent posts.
Message requests are where new customers hide. On most platforms, messages from people who don't follow you land in a separate folder, often with no notification. That's your highest-intent stranger — the person asking whether you ship to their country — sitting where you never look. Checking requests once a day is the highest-return habit on this list.
Reviews are slow but permanent. Nobody expects a review reply within the hour, and rushing one rarely helps — a two-day turnaround with a specific, human reply beats a same-day "Sorry to hear this!" Reviews are also the one surface where you're writing mostly for the audience, not the reviewer.
A one-person SLA that actually holds
An SLA you miss is worse than no SLA, so build it from what a bad week looks like, not a good one. Three tiers, defined by mechanical rules so you're not making judgment calls at 9pm:
- Tier 1 — money or anger. Complaints, order problems, refund requests, purchase and booking questions. Same business day, aiming for four working hours. These are the only messages allowed to interrupt you.
- Tier 2 — routine questions. Pricing, availability, how-it-works, collaboration enquiries without a deadline. One business day.
- Tier 3 — praise and conversation. Compliments, emoji, general chat, most @-mentions. Next sweep, best effort, no promise.
Weekends are explicitly off unless you genuinely trade on weekends. A predictable Monday-morning answer is a better experience than an exhausted Saturday one that trains people to expect Saturdays forever.
Write those three lines down where a future you — or a future contractor — can find them. An SLA belongs in a documented process rather than your head; the social media SOP guide covers capturing it in a form somebody else can follow. The triage mechanics that feed the tiers are laid out in how to manage DMs and comments.
The expectation-setting moves that buy you grace
Here's the part most people skip: a stated response time resets the clock in your favour. Someone who knows you reply within one business day and gets an answer in six hours feels well served. Someone who assumed instant and got six hours feels ignored. Same reply, same speed, opposite outcome.
Four moves, in order of effort:
- Put your hours in the bio. One line: "DMs answered Mon–Fri, usually within a day." It costs nothing, it appears above every message anyone sends you, and it does more expectation management than any tool.
- Pin an FAQ. A pinned post or comment answering your five most common questions deflects the volume that was going to eat your response time. If half your DMs ask about shipping, the fix isn't faster typing — it's answering before it gets asked.
- Use native auto-away where it exists. Meta Business Suite, Meta's free management dashboard, offers away messages for outside your working hours and an instant reply for the first message in a new conversation. Set the instant reply to state your actual SLA: "Thanks — we reply within one business day." Coverage is uneven across networks, so where there's no native away message, the bio line and pinned post do the work.
- Say the number in the reply itself when you can't resolve immediately. "I need to check with the supplier — I'll come back to you by tomorrow lunchtime" converts an open-ended wait into a kept promise.
One rule holds all of this together: automation greets, humans answer. An honest instant reply builds trust. A bot impersonating you burns it, and regulars spot it immediately.
The twice-daily routine
You do not need to be reachable all day to hit a same-business-day SLA. You need two reliable sweeps and a third opportunistic one.
- Morning sweep (15 min). Message requests first, then overnight DMs, then comments on your two most recent posts. Everything Tier 1 gets answered now. Tier 2 gets answered or parked with a holding reply.
- Post-publish window (15–30 min). Whenever today's post goes live. Comments cluster early, and replying while people are still online is the highest-leverage engagement time you get.
- End-of-day sweep (15 min). Tier 2 clean-up from saved replies, comment sweep, plus a weekly slot for reviews.
Between sweeps, turn off everything except the notification channel that carries Tier 1. Notification hygiene is what makes fixed windows survive contact with a busy week.
I should be straight about where our own product sits in this: SocialKit has no unified inbox, no comment-moderation queue, and no social listening. The routine above happens in the native apps, or in something like Meta Business Suite — and for conversations, that's the right place for it. What SocialKit removes is the other half of the workload: compose once, customise caption and media per platform, and let the visual content calendar auto-publish across all 11 platforms, including Google Business, where your reviews live anyway. Publishing stops competing with replying for the same hour. As of June 2026, every plan includes all 11 platforms and unlimited scheduled posts, from €29/month on Solo (€17.40/month billed annually), with a 7-day free trial.
Knowing when the SLA has outgrown you
Review two numbers weekly, per platform: median response time and response rate. Both slip in the same direction and usually at the same moment — when posting volume rises. That's your early warning that the system needs adjusting before you do. The full measurement setup is in the customer service metrics breakdown; the wider service system it sits inside — tone, public-to-DM handoffs, escalation — is in the social media customer service playbook.
When the numbers keep slipping despite a working routine, the fix is a second pair of hands with clearly split ownership, not a faster you. One owner per sweep, never two.
Start here this week
- Pick your three tiers and write the target next to each. Be pessimistic.
- Add one line of hours to every bio. Today, five minutes.
- Set a native instant reply stating your SLA wherever the platform supports one.
- Pin an FAQ post answering the five questions that generate the most DMs.
- Book two 15-minute sweeps in your calendar as recurring events, and check message requests in the first one.
- Tally your median and response rate on Friday for one week before changing anything else.
The goal isn't to be fast. It's to be predictable at a speed you can sustain in a bad week — and to tell people what that speed is before they have to guess.