A community management agency is bought for coverage, not for creativity. The deliverable is that somebody competent is reading your comments, your reviews, your Discord or your subreddit at the hours your audience is awake, answering in your voice, and knowing which messages to escalate rather than answer. That sounds simple until you price it: coverage is a staffing problem, and staffing is the only line item that cannot be made cheaper by being clever. Most disappointing engagements in this category come from buying a content calendar when what the business needed was a rota, or from buying a rota with no agreed rule for what happens when a comment turns into a complaint. Before you compare proposals, decide which of those two things you are actually short of.
The job is a rota, and the rota is the price
Ask any candidate to describe a normal Tuesday and you will learn more than a deck will tell you. A real community operation has named people, defined shift hours, a target first response time, a macro library that is reviewed rather than frozen, and a written rule for when a moderator stops replying and hands the thread to somebody with authority. Price follows directly from that: weekday business hours across two channels in one language is a fraction of the cost of near round the clock cover across five channels and two languages, and no amount of tooling closes that gap because the tooling does not decide whether a refund is warranted. When you read a proposal, translate every promise back into hours of human attention. If the numbers do not add up to a person being present when your customers are complaining, you are buying a scheduler and calling it community management.
Moderation, disclosure and the things that become legal problems
Community work touches rules that ordinary social posting does not. Staff and contractors who talk about your product in your own community are endorsers in the FTC's sense, and the FTC's Endorsement Guides make clear that a material connection between a reviewer or commenter and the brand needs to be disclosed clearly. That covers agency moderators who join a thread as enthusiastic customers, employee advocacy programmes, and seeded reviews of any kind. It also covers what you delete: removing negative comments while leaving positive ones can turn your community page into a misleading advertisement. A serious agency will already have a written moderation policy, a disclosure standard for anyone posting on the brand's behalf, and a retention rule for what gets hidden versus removed. Ask to see all three before you sign, not after an incident.
Where community work meets reputation management
The two are sold separately and overlap constantly. Community management is the daily presence; reputation management is what you do when the daily presence is not enough and a bad review, a viral thread or an old news story is shaping what people find. Buyers routinely discover mid engagement that their community contract covers replies but not review recovery, or covers reviews but not the search results those reviews sit inside, and end up shortlisting reputation management companies separately at exactly the moment they have the least time to compare them. Decide the boundary in advance. Write into the scope whether responding to public reviews, requesting removals, and coordinating with legal are inside the retainer or billed as incident work, and get the incident rate in writing while nothing is on fire.
How to vet a shortlist in three questions
First, who is doing the work and where do they sit. Named individuals with a stated shift pattern beat a generic pod every time, and an agency that will not name them is usually reselling. Second, show me the escalation matrix: which message types go to the client, which go to legal, which the moderator answers alone, and what the target response window is for each. Third, what happens at the end. Community accounts, moderator tooling, macro libraries and the archive of past conversations should be yours, in your own accounts, with agency staff added as users rather than owners. Every one of those questions is answerable in writing in a day. Candidates who need a call to answer them are telling you the process does not exist yet.
Questions people ask about community management agency
Is community management the same as social media management?
No. Social media management is outbound: planning, producing and scheduling posts. Community management is inbound: reading and answering what people say in comments, groups, forums, reviews and chat servers. Many agencies sell both, some sell one and quietly subcontract the other, and the two have different cost drivers. Outbound scales with volume of content, inbound scales with hours of coverage.
What hours of coverage do I actually need?
Look at when your inbound messages arrive rather than when your team works. For most consumer brands the peak is evenings and weekends, which is exactly when business hours cover fails. A practical starting point is coverage across your two busiest days and your two busiest hours, with a defined out of hours acknowledgement, then widening once you can see the response time data.
Who owns the accounts and the conversation history?
You should. Insist that every platform account, moderation tool and analytics property is created under your organisation with agency staff added as users. The archive of past conversations is a genuine asset: it is your record of what customers complained about and how it was resolved, and losing it at the end of a contract is a real cost that never appears in the proposal.
How is it usually priced?
Monthly retainers dominated by staffed hours, sometimes with a per channel component and an incident or surge rate on top. Ask for the retainer to be expressed as hours of coverage per week and the surge rate to be written down separately. Pricing that is quoted only as a flat monthly figure with no hours attached is impossible to compare across candidates.