Lesson 6 of 87 min read

Community management at scale

Answer comments, messages and reviews for many clients with response rules, an escalation path and a reply library, without sounding like a template.

In this lesson you will

  • Write response rules per client: what you answer, how fast, and in what voice
  • Set an escalation path for complaints, legal risk and anything you should not answer
  • Build a reply library that speeds you up without making every reply sound the same

Clients rarely judge an agency by its best post. They judge it by the comment that sat unanswered for four days, the angry review that got a cheerful template reply, or the private message from a big customer that nobody saw. For the people who write to a brand, the inbox is the brand. And for many clients, it is the part of your work they notice most, because their own customers mention it to them.

Community management also scales worse than publishing. You can batch a month of posts into one day. You cannot batch replies to comments that arrive on Saturday night. So this lesson is about the system around the inbox: rules you agree with each client, an escalation path, a reply library, and a daily routine that keeps many clients' inboxes under control without living in them.

Response rules per client

Before you answer anything on a client's behalf, agree on the rules in writing. Five questions cover it:

  1. What do we answer? Comments on the client's posts, mentions, direct messages, reviews. Many agencies answer comments and reviews but route private messages to the client's support team. Decide explicitly.
  2. How fast? A target per channel, during agreed hours. "Comments within one business day, reviews within two, messages forwarded within four hours" is a realistic starting point. Write the hours: if you do not cover weekends, say so.
  3. In what voice? Usually the brand's voice from the onboarding guide, with a few reply-specific notes: first names or not, how to sign off, whether to use the customer's name.
  4. What do we never answer? Pricing negotiations, legal claims, medical or financial advice, anything about a named employee, refunds. These go to the escalation path.
  5. What do we hide or report? Spam, abuse, scams impersonating the brand. Agree that you act on these immediately and tell the client after.

Agree, too, who signs replies when a person at the client wants to be visible, for example a founder who answers some comments personally. Mark those threads so your team stays out of them.

Put the rules on one page per client next to the voice guide. Review them every quarter; new product lines and new problems change them.

The escalation path

Some messages you should not answer at all, or not before someone at the client has seen them. An escalation path says who sees what, and how fast:

SignalExampleRoute toYour public step
Complaint with detailsOrder number, account issueClient supportShort acknowledgement, move to private
Legal or safety riskInjury, threat of legal action, data leakNamed client contact, same dayNothing public until they reply
Press or partnerA journalist or a large account askingClient's marketing leadThank them, say someone will follow up
Repeated angry customerThird public complaint this weekAccount lead and clientPause and agree a single response
Praise worth sharingA detailed positive commentClient, for permission to reuseA real thank-you reply

The important column is the last one. For anything risky, your public step should be either nothing or a short acknowledgement that moves the conversation to a private channel. The worst replies in agency history are long public ones written fast by someone who did not know the full story.

When a thread turns hostile

Sometimes one comment becomes a pile-on: a complaint that others join, or a post that attracts an argument between strangers. Speed matters, but so does restraint. The sequence we would follow:

  1. Stop scheduled posts for that client that could look tone-deaf next to the thread, such as a cheerful promotion an hour later.
  2. Tell the client within the hour with a link and a one-line summary. Do not wait for the daily log.
  3. Post one reply, agreed with the client, that acknowledges the issue and says what happens next. Do not answer every comment individually; that keeps the thread alive.
  4. Hide or report only what breaks the network's rules or the client's written policy: abuse, spam, personal data. Hiding fair criticism makes it worse when someone notices.
  5. Write down what happened for the monthly report, including what you would change next time.

A reply library that does not sound canned

You will write many similar replies: thanks for the kind words, sorry for the trouble, here is the link, we will pass this on. A reply library saves time, but pasted templates are obvious, especially when three customers in the same thread get the identical sentence.

Build the library as structures, not sentences:

Thanks reply
  1. Mention the specific thing they said (not "thanks for the comment")
  2. One sentence that adds something: a tip, a link, what is coming next
  3. Optional: a question back if the brand voice allows it

Problem reply (public)
  1. Acknowledge the specific problem in their words
  2. Say what happens next and who does it
  3. Move it private: where to write, and what to include

Then add a few approved phrases per client for things that must be worded carefully, such as the line about refunds or the sentence that moves someone to support. Those can be identical every time; the rest of the reply should not be.

If you use AI drafts for replies, the same rule applies as for posts: a draft is a starting point. Nobody sends a reply without a person reading it, and nothing involving a complaint, money or safety goes out from a draft at all.

Reviews are their own channel

Reviews on a business profile, such as a Google Business listing, deserve separate treatment because they stay visible for years and future customers read them before they ever see a social post.

  • Answer every review, positive and negative, within the agreed window. A short, specific thank-you is enough for good ones.
  • Negative reviews get the problem reply structure, never an argument. Assume the next customer is reading your reply, not the reviewer.
  • Never offer compensation in public. Move it private and let the client decide.
  • Watch for patterns. Three reviews mentioning the same problem in a month is information for the client, and worth one line in the monthly report.

A daily routine across clients

The inbox needs a little attention often, not a lot rarely. A routine for a team managing several clients:

  • Twice a day, fixed times, work each client's inbox in turn. One client at a time, never a mixed list, so a reply cannot go out under the wrong brand (the fourth failure from lesson 2).
  • Order within a client: messages and anything escalated first, then reviews, then comments on the newest posts, then older ones.
  • End of each session: log escalations sent, and anything the client should know.
  • Weekly: read the log for patterns and send the client a three-line summary.

Fifteen to thirty minutes per client per day is a typical range for small and mid-size accounts. Measure yours; it is the hardest part of the service to estimate and the easiest to underprice in hours (lesson 8).

Worked example: rules for our own accounts

If an agency managed community for our brand, here is the rule sheet we would give them:

Answer: comments and mentions on X, LinkedIn, Bluesky, Threads
and Instagram; questions in our Discord.
Route to us: anything about billing, an account problem, a bug
report with details, a security concern.
Speed: comments within one business day; Discord questions the
same day during business hours.
Never: quote prices (link the pricing page), promise a feature
or a date, name the services we run on.
Voice: we / you, plain, no emojis, no exclamation marks.

And two example replies, written from the structures above.

A public comment asking how to schedule to several networks:

Write the post once in the composer, then pick the accounts.
Each network gets its own preview, so you can shorten the X
version without touching LinkedIn. Our cross-posting page
walks through it.

A public complaint that a post failed to publish:

Sorry, a failed post is exactly what should not happen.
Could you send us the details through our contact page,
with the network and roughly when it was scheduled?
We will look into it from there.

Neither reply quotes anything we cannot stand behind, and the second moves the conversation to a private channel instead of debugging in public.

Recap

  • Agree per client what you answer, how fast, in what voice, what you never answer, and what you hide.
  • Route risky messages through a written escalation path; the public step is nothing or a short acknowledgement.
  • Build the reply library from structures plus a few approved phrases, and keep a person reading every reply.
  • Treat reviews as their own channel: answer all of them and report patterns.
  • Work the inbox one client at a time, at fixed times, and measure the hours.

Exercise

Write a response playbook

  1. For one client, answer the five response-rule questions in writing.
  2. Fill in the escalation table with the client's real contacts and your public step for each signal.
  3. Write two reply structures (thanks and problem) plus three approved phrases the client must sign off.
  4. Draft replies to three real comments from the client's recent posts using the structures. Check each X reply fits with the free X character counter.
  5. Done looks like: a one-page playbook with rules, escalation table, reply structures and approved phrases, plus three drafted replies.

Go further

Unified inbox and Radar alerts

In FoPost, each brand's comments, messages and reviews arrive in one inbox, filtered to the brand you are working in; replies drafted by an automation or the agent wait for someone to send them. To hear about mentions of a client outside their own posts, set up a Radar tracker and an alert in Radar alerts. See the inbox feature page.

Check yourself

  1. 1What should your public step be for a message with legal or safety risk?

    Nothing public until the named client contact replies, or at most a short acknowledgement that moves it to a private channel.

  2. 2How do you keep a reply library from sounding canned?

    Store structures rather than full sentences, keep only a few approved phrases identical, and always mention the specific thing the person said.

  3. 3Why work the inbox one client at a time?

    So a reply cannot go out under the wrong brand, which is one of the four wrong-client failures.

Academy

Keep reading, free

Tell us a little about you and the rest of this lesson, and every lesson in every course, opens on this device. No account and no card.

What describes you best?
Where do you post today? Pick any that apply.
What do you want most right now?

We use your answers to suggest lessons and to improve the Academy. They are never shown publicly. Read our Privacy Policy.