How-To Guide
What response time promise should a brand make on social media?
Promise a tiered first reply: one hour for complaints and buyers, four business hours for questions, one business day for feedback, and measure the median.
By the Superdirector editorial team. Platform documentation and seven response-time benchmark guides read November 15, 2026.
At a glance
What response time promise should a brand make on social media?
A brand should promise a tiered first response instead of a single deadline: within one hour during covered hours for public complaints and direct messages from buyers, within four business hours for ordinary questions, and within one business day for general feedback. Publish the hours the promise covers, say what happens after hours, and measure the median time to a human first reply. The three tiers sit inside the ranges published benchmark studies report, and they are a working standard for one brand rather than a platform rule.
- Tier the promise by what the message needs, not by platform alone.
- Cover one hour for complaints and buyer messages, four hours for questions, one business day for feedback.
- Measure the median first reply inside published hours and report it monthly.
The tiered promise the article recommends, with a shorter clock for complaints and buyer messages than for ordinary questions. Original diagram, drawn from Hootsuite, Supp and the article's three-tier table read November 15, 2026.
Make it work for your brand
Find it. Remake it. Post it. Superdirector turns the viral formats in your niche into your brand's carousels, X posts and video scripts, and keeps the calendar full.
The promise a brand can keep
The promise worth making is a tiered first-response time. Answer public complaints and direct messages from people ready to buy within one hour during the hours you cover. Answer ordinary product, price and opening-hours questions within four business hours. Answer general comments and feedback within one business day. Publish those three numbers, the timezone and the days they apply to, and report the median each month.
This shape follows what the evidence actually shows. Hootsuite's customer service guide calls a reply within the first hour the modern standard and reports that leading brands aim for 15 to 60 minutes. Supp's channel benchmarks report that social media customers expect an answer within 30 to 60 minutes while the observed median is 3 to 5 hours. The expectation and the delivery are far apart, which is why one blanket promise either disappoints the urgent messages or overstates what the team can hold.
Every promise is a service decision with a cost. One hour needs someone watching the inbox during covered hours and a path to escalate. Four hours can survive two or three checks a day. A full day can wait for the next working morning. Deciding which messages belong in each tier is the work; writing the sentence on the profile is the easy part.
- One hour: public complaints, refund or order problems, safety issues and direct messages from someone asking how to buy.
- Four business hours: product questions, pricing, stock, delivery times and booking requests.
- One business day: praise, general feedback, tags and comments that need no answer to move a purchase forward.
Why one number fails
A single line such as "we reply within 24 hours" sounds responsible and measures almost nothing. That line sets the same clock for a refund request and a heart emoji, so the team spends its attention on the wrong messages and the customer with an open order learns nothing about when help will arrive.
Published numbers show how wide the spread is. HubSpot reports that 39% of social media users expect a response within 60 minutes while the average business response time is about five hours. Nectar's statistics roundup reports academic findings of expected windows of 1 to 3 hours on Twitter and 3 to 6 hours on Facebook. Twenty-four hours sits outside the windows those studies report for time-sensitive messages.
Speed also hides coverage. Nectar reports that Arizona State University's research found 49% of complainants never received responses to their social media complaints, and that an academic analysis of airlines found companies answered fewer than half of customer complaint tweets. Plenty of brands hold a beautiful median over the messages they answer and still leave half their complaints unanswered. That is why the promise needs a response-rate measure beside the clock.
Arithmetic gives the last reason to avoid one number. Presly's benchmark guide shows how one outlier can drag a mean response time from 45 minutes to 4 hours. Judged on the mean, the promise punishes the team for one holiday message. The median version describes what most customers actually experience, while the 90th percentile tells you how bad the tail is.
Set three tiers by message type
Sort messages by what the person needs, then set a target and an owner for each tier. Platform matters too: CampaignSwift's 2026 benchmarks report typical ranges of under 30 minutes on X, 1 to 3 hours for Instagram DMs and 1 to 2 hours on Facebook Messages. Oppira reports usual targets under 1 hour for support questions on Twitter/X and under 4 hours on Instagram. Those ranges fit a three-tier promise without copying any one vendor's number.
| Tier | What belongs here | Target in covered hours | Owner |
|---|---|---|---|
| Urgent | Public complaints, refunds, order problems, safety issues, buyer DMs | 1 hour | Named person on shift |
| Standard | Product, price, stock, delivery and booking questions | 4 business hours | Inbox queue |
| General | Praise, feedback, tags, comments with no purchase question | 1 business day | Batch check |
The tiers should bend to the channel where the evidence supports it. CampaignSwift reports that X carries the highest escalation risk and that Instagram DMs from ads often carry purchase intent, so a brand can promise one hour on X and four hours on Instagram during covered hours without breaking the logic. What it should not do is promise a fast clock on a channel nobody watches.
Write down the boundary cases before launch. Complaints that arrive as DMs are urgent. Price questions from a returning customer are standard unless the message says they are ready to order. Tags from customers who already bought are general. The team needs one rule for moving a message up a tier, and one person who can move it down when the queue is full.
Measure the median, not the average
Three measures carry the promise. First response time is the gap between the message arriving and a person replying; an automatic acknowledgement is not a first response. Response rate is the share of eligible conversations that received any reply. Overdue count is the number of messages that have passed their tier target and are still open.
Oppira defines response rate as replies sent divided by inbound messages received, times 100. Use that formula because it keeps the denominator visible. Answering 90% of direct questions inside the tiers beats answering 60% quickly, and the rate shows that difference where a median alone hides it.
Report the median and the 90th percentile for each tier. Presly calls median first-reply time by platform the single most reliable metric for benchmarking, and its worked example shows why: a mean pulled upward by one slow message makes the team look slower than it is on most interactions, while the median describes the typical customer and the 90th percentile names the worst experience one customer in ten receives. Vida also recommends setting internal targets tighter than the public promise, so a 24-hour public promise might run on a 12-hour internal goal.
Measure from the same clock you published. If the promise covers 9 AM to 6 PM on weekdays, the report should count only those hours. Include the channel and the tier in every row, because a single blended number lets a fast general-comment queue flatter a slow complaint queue.
Presly's worked example as the article reports it: one outlier drags the mean from 45 minutes to four hours while the median describes the typical customer. Original diagram, drawn from Presly's benchmark guide and the article's measurement section read November 15, 2026.
State the hours the promise covers
Every promise needs an edge. Write the timezone, the weekdays and the after-hours rule next to the three targets. Wording such as "we answer complaints within one hour from 9 AM to 6 PM Pacific, Monday to Friday" is checkable. The same promise without the window is not.
The after-hours rule can be simple and still honest. DM Desk suggests promising a reply within an hour while open and by the next morning when closed, and recommends an away message that gives your hours and says when you will reply. Ooctal makes the same point: an automatic acknowledgement outside working hours should say when a person will reply.
Weekend and holiday hours belong in the same place. If Saturday messages wait until Monday, say so rather than letting a customer infer the office hours from silence. The promise can be generous or modest; it cannot be silent about the hours when nobody is there.
Staff the promise before you publish it
Count a normal week before you choose the numbers. Add the comments, mentions, story replies and DMs that need a human answer, then divide by the days the inbox is covered. Oppira estimates one community manager can handle around 100 to 200 meaningful interactions per day before quality drops. Forty messages a day fits one person comfortably; 300 needs either more people, tighter automation for routine questions, or a wider promise.
Escalation is the second staffing question. With a one-hour tier, a message that reaches 45 minutes has to become someone else's problem. CampaignSwift reports that a response within 30 minutes usually keeps a complaint situation private, which is one reason the urgent tier earns its cost. Decide who receives the alert and what they are allowed to promise when they take over.
If the brand wants a visible responsiveness signal, know what the platform measures. Presly notes that Facebook awards a Very Responsive to Messages badge to pages that reply to 90% of messages within 15 minutes, and HubSpot describes the badge appearing when average response time stays under five minutes over the past seven days. The badge is a bonus, not a reason to publish a promise the team cannot hold.
Write the promise in words customers can check
Put the promise where a customer looks before sending a message: the profile bio or contact area, a pinned post, the after-hours auto-reply and the contact page on the website. Use the same sentence in all four places. If the profile says one hour and the auto-reply says 24, the promise is already broken.
Plain wording works better than a slogan: name the tier, the clock and the hours. "Complaints and order questions: a reply within one hour, 9 AM to 6 PM Pacific, Monday to Friday. Other questions: within four business hours. After hours we reply by the next working morning." That wording is specific enough for a customer to check and short enough for a bio.
Keep quality inside the promise. Vida observes that a two-minute reply that does not address the customer's question creates more frustration than a 30-minute wait for a comprehensive solution. Speed with the wrong price or the wrong opening hours creates a second problem on top of the first, so the urgent tier should buy a human answer, not a rushed one.
Avoid absolute language. Words such as always and guaranteed invite a dispute the brand cannot win. Say what the team aims to do, publish the measure, and let the monthly report carry the proof. Sprout Social's 2025 Index found that 73% of social users say they will buy from a competitor if a brand does not respond, which is a reason to answer, not a reason to overpromise.
Review the promise every month
Read the three measures weekly and change the promise monthly. The weekly reading catches a broken queue: overdue messages climbing, a channel with no replies, or one tier absorbing the whole day. The monthly reading is the decision point. If the urgent tier held its one hour for four weeks, keep it. If it missed more than one week in four, either add coverage or widen the promise and say so.
Use the report to defend the promise internally as well. A manager with the median, the 90th percentile and the response rate for each tier can decide whether to hire, automate routine questions or narrow the promise. A single average cannot tell which of those decisions is right.
Change the published sentence when the measure changes. Quietly widening the promise while the profile still says one hour is worse than keeping a modest one. The monthly review is also the moment to check that the after-hours message, the pinned post and the website still match the current hours.
What a response promise should not claim
A published reply target is not a legal service level, a sales guarantee or a platform rule. None of the stored sources reports a legal deadline for social media replies. The only platform mechanism the sources describe is Facebook's voluntary responsiveness badge, which reflects the page's own recent average. Do not tell customers that a platform requires an answer in a set time, because it does not.
Do not claim that answering quickly guarantees a sale, loyalty or a recovered review. The percentages in the research describe expectations and stated intent, not the outcome of one brand's promise. The honest claim is narrower and still useful: a published tier, a measured median and a response rate let a customer know when help will arrive.
Small brands can start with one tier. Promise one business day for everything, measure it for a month, then split out complaints and buyer messages into a faster tier when the volume shows they deserve it. That path keeps the promise true while the team learns its own capacity.
If the account is run by a service, the same rule applies. The $199 plan is one AI-run operated account that creates and posts under the account's own standing posting permission, which means no one approves each post before it goes out; posting can be turned off. The $29 plan is MCP access plus hands-on creation, with no posting. Neither plan changes the response promise: the brand still decides the tiers, the covered hours and the escalation owner.