How-To Guide
How many community managers does a brand need?
A volume-first way to size community staffing: replies per person per day, response-time targets by tier, coverage hours, and when to hire a second manager.
Size the role by inbound volume and the response time you promise, not by follower count. One common rule of thumb is 60 to 100 standard replies per person per day when saved replies and clear policies exist. Below about 15 messages a day a dedicated hire is hard to justify. Above 100 conversations a day that are complex or emotional, or when one person has no cover for holidays, add a second manager. Then use your response targets to check the ratio, because a 15-minute promise on X needs more people than a same-day promise on LinkedIn.
- Count comments and DMs together per brand for two weeks, then split them into urgent, standard and low before you divide by a planning rate.
- 60 to 100 replies a day is one vendor's rule of thumb, not a platform standard, and complex conversations lower it.
- A second manager is due when one person has no cover, the planning band is exceeded after complexity, a response tier misses two weeks running, or escalation load takes over.
How many community managers a brand needs
Headcount follows message volume and the response time you promise, not follower count. A common rule of thumb is one person for 60 to 100 standard replies a day when saved replies and clear policies exist. Below about 15 messages a day, a dedicated hire is hard to justify. Above 100 conversations a day that are complex or emotional, or when one person has no cover for holidays, add a second manager.
Three quantities decide the number. How many comments and direct messages arrive each day, what response time you promise for each tier of message, and how many hours a day someone is actually watching the inbox.
- Volume. Count comments and DMs together, per brand, over two ordinary weeks.
- Response target. A 15-minute promise on X needs more people than a same-day promise on LinkedIn.
- Coverage. Five business days of one shift is not the same as seven days with evenings covered.
The promised reply time is a staffing decision, not a slogan: a tighter window needs more of the day watched, not someone typing faster. Original diagram, drawn from the response-time benchmarks and the Meta 15-minute badge figure read November 16, 2026; it shows the decision, not a per-platform headcount.
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.
Count the messages before you count heads
Start with the inbox, not the org chart. Count comments and direct messages together for each brand for two weeks, then split them by urgency. MydropAI sorts every message into urgent, standard and low, with a starting target of one hour, eight business hours and 24 hours. Its point is that the tier list matters more than the exact minutes.
Count the tier that hurts, too. A brand can receive 40 messages a day and still overload one person if six of them are public complaints or legal questions. The blend hides the load.
Two details change the count. Pre-sales questions in comments convert directly into revenue, so slow answers cost money as well as goodwill, as AI Networks notes. And a busy day pushes replies into tomorrow when capacity is thin, which is how a queue turns into a backlog.
Never judge the queue by average response time alone. Skycom makes the point that unanswered messages do not appear in an average, so the average flatters any team with a backlog. The same page cites a Sprout Social Index study of retailers in which 83 percent of social customer questions received no reply.
Replies per person per day
The 60 to 100 figure is a rule of thumb from one vendor playbook, not a platform standard. MydropAI words it as one person handling 60 to 100 standard replies per day when they have saved replies and clear policies. Treat it as a planning band and replace it with your own count within a month.
Complex or emotional conversations cut the number a lot. A reply that needs an apology, a refund decision or a product investigation is not a saved reply, and a queue of them is not a queue of 80. The same playbook says so directly: fewer replies are possible when the conversations are hard.
Time is the other way to count. AI Networks splits it by hours instead: thirty minutes a day realistically covers one pass through notifications, replies to direct questions and obvious spam. Once a brand passes about fifty interactions a week, or receives any real volume of DMs, it suggests an hour a day.
For a small business that also creates content, one to three hours a day is a reasonable starting point for the whole social job, not only the inbox. Community work is one part of that day, which is why a single manager can look busy and still leave messages unanswered.
Response time sets the headcount
The promised response time is a staffing decision, not a customer-service slogan. CampaignSwift measures expectations by platform: under 30 minutes on X, one to three hours for Instagram DMs, one to two hours on Facebook, the same business day on LinkedIn, and a first-hour reply on TikTok where reach is at stake.
Its own agency data sets the spread. Across agencies using its platform, the median social message response is about 2 hours 40 minutes, and the top 10 percent answer in under 35 minutes. To hit the fast end you need someone watching more of the day, not someone typing faster.
Platform rules tighten it further. Skycom reports the Meta standard for the Very Responsive badge: a Page needs a 90 percent response rate and a reply time under 15 minutes on Messenger. A brand that wants that badge is buying near-continuous coverage during business hours.
Published expectation figures disagree because they measure different situations and samples. One often-cited line says 88 percent of customers expect a reply within an hour (Vida); a US survey cited by Nectar puts 38 percent at an hour for social comments; Skycom cites about 72 percent expecting an hour on X, but about 76 percent accepting 24 hours for a general social message. Do not merge them into one number. Pick the tier and the platform you promise, then staff to that.
Coverage hours and the weekend gap
Most response targets are written for business hours only. CampaignSwift puts the common window at 8 AM to 6 PM in the client timezone, which is ten hours of attention and fourteen hours of silence if nobody covers the rest.
Weekends and evenings are where a one-person plan breaks. AI Networks lists the three honest choices: accept the gap, pay for weekend monitoring, or publish your response hours on the profile. Publishing them is cheap and removes most of the frustration, because people mind waiting far less when they were told.
Coverage multiplies headcount. One person can hold a single business-hours shift. Twelve hours a day, six days a week, needs at least two people before you count holidays, and a high-volume brand needs a named backup on day one.
The hiring trigger
Hire the second person when one of four things is true, not when the calendar says a year has passed:
- One person has no cover for holidays or sick days. MydropAI warns that the one-hour target slips on the first day of absence.
- The daily volume sits above the planning band after complexity is counted, not just on paper.
- The promised response time misses in the same tier two weeks running.
- Escalations pile up because the same person both answers and decides.
Share the quiet brands before you hire. MydropAI says a brand with 15 messages a day should not own a full-time hire, and suggests pairing three or four of them under one community manager. In an agency setting, CampaignSwift reports that a team of two or three community managers can handle 15 to 25 clients from one inbox.
Protect proactive time as you add people. The same guide reports a workable split of roughly 70 percent reactive replies to 30 percent proactive engagement, and says most agencies run closer to 95 percent reactive because they lack the bandwidth. If you hire only to clear the queue, the 30 percent never returns.
A worked headcount by volume
Here is the arithmetic on a midpoint of the band, not a benchmark. Assume 80 standard replies per person per day, business hours only, and no complex cases. Divide your measured daily volume by 80 to get full-time equivalents.
| Messages per day | Divided by 80 | Planning read |
|---|---|---|
| 15 | 0.2 | Share a manager across several brands |
| 40 | 0.5 | Half a person, or a shared role |
| 100 | 1.25 | One person plus overflow cover |
| 250 | 3.1 | About three to four people |
| 600 | 7.5 | About seven to eight people |
Read the table with two corrections. Complex or emotional conversations lower the 80, so add people before the queue shows it. And the numbers assume business-hours coverage; evenings and weekends sit on top. A 250-message brand that wants a fast X reply and a weekend watch is not a 3.1-person plan.
The worked arithmetic from the headcount section, in order: measured volume divided by a planning rate gives full-time equivalents, then complexity and coverage sit on top. Original diagram, hand-drawn from the article's own method, with 80 as a planning midpoint rather than a benchmark.
Escalation paths and scope
Headcount is not the only staffing answer. Every message that is not a standard reply needs an obvious next step, or the manager becomes a bottleneck. MydropAI documents four routes, each with a named owner and a named backup.
- Customer service: orders, billing and account issues, with a handoff template.
- Legal or compliance: claims, regulated topics, anything that mentions a lawsuit.
- Communications: anything that could become a story.
- Product: repeated feedback, tagged so it can be counted.
Scope boundaries protect the role as much as the person. DBLSEO defines community management as comments and inbox messages with defined response times, escalation rules and scope boundaries, so social does not become a second full-time job. Without an escalation path, AI Networks warns, an agency either bothers you constantly or improvises answers on your behalf.
Where Superdirector fits
Superdirector, the publisher of this guide, does not answer comments or DMs, so it does not reduce the community headcount this page describes. What it takes off the team is the publishing half of the job. Growth costs $199 a month for one AI-run social account, run under account-level standing posting permission: you set the brand and creative direction, name the accounts and competitors to watch, and it builds branded carousels and X text posts from what is working in your niche and publishes them. Starter, at $29 a month, is MCP access plus hands-on creation, with no scheduling.
That matters to a small community team because the same manager often writes the calendar as well as the replies. Handing publishing to a system frees the hours that would otherwise go to making and scheduling posts, which is the time that pays for a second pair of hands on the inbox. It is not a substitute for an inbox tool, a listening tool or a person who can decide how to answer a complaint.
The four numbers to review weekly
Measure per brand, not as one blended average. Sprout Social defines first reply time as the wait for the first reply inside business hours, and groups customer-service metrics into speed, volume and productivity, and sentiment. Skycom adds the warning that response rate deserves more attention than it usually gets: the share of messages that get any reply at all is the honest measure of whether the queue is staffed.
- Median first response time by tier. Urgent, standard and low, reported separately.
- Share answered within the target. The percentage, not the average.
- Repeat contact rate. A fast reply that does not resolve the issue creates a second message.
- Escalation rate. How often a message needs legal, communications or product, because a rising rate points at the product, not the community team.