Key takeaways
- Time is the standard. Name windows by message type — question, lead, complaint, crisis — not "we try to reply."
- Escalate by type, not by panic. Pricing, refunds, legal, and safety have owners before the thread goes public.
- Log the incident. A deleted comment without a record is a lesson you cannot fix.
Someone asked on Instagram if you still install in Pinellas. The post went up at nine. The question sat there until Thursday. They hired the account that answered Tuesday.
Community management is not a tone-of-voice poster on the wall. It is a message taxonomy, response windows, and an escalation tree — written before the angry comment, not after it.
Buyers treat public silence like a closed shop. Tone without time is decoration.
Comments are leads wearing costumes
A question about service area is a lead. A price question in the DMs is a lead. A complaint about a late crew is retention and reputation in one thread. A tagged photo from a happy customer is proof waiting for permission.
Social media tips for small businesses already named the job: answer people. Management scope that includes scheduling but not response is a calendar without the hard part. Generating leads from your website and generating them from comments share one rule: a specific ask, a reason to trust the answer, and a next step that is not a maze.
Pass the SLA test on last month's inbox
Sort thirty recent interactions into types. If you cannot sort them, you cannot staff them.
| Type | Examples | First response window | Owner | Escalate when |
|---|---|---|---|---|
| FAQ / hours / area | "Do you serve…?" "What are your hours?" | 4 business hours | Channel manager | Answer needs policy you do not have |
| Sales / quote | Pricing, availability, "how much for…" | 4 business hours | Sales delegate | Custom scope, legal claim, or angry tone |
| Support / complaint | Late job, billing issue, damaged work | 2 business hours | Operations or owner delegate | Refund, threat, media, or repeat contact |
| Praise / UGC | Tag, review share, testimonial | 1 business day | Channel manager | Repost needs written permission |
| Spam / abuse | Scams, slurs, bot piles | 1 business hour | Channel manager | Coordinated attack or impersonation |
| Crisis | Injury, discrimination, executive tag, viral negative | 30 minutes | Owner + named backup | Legal, PR, or law enforcement |
Run the test honestly. Pick five threads. Did you meet the window? Was the owner pulled in for a FAQ because macros did not exist? Did a complaint vanish without a log entry?
Meta's business guidance for messaging treats response as part of customer care on connected surfaces — slow or absent replies train people to stop asking. Use Meta Business Help — Respond to messages as the platform floor, then tighten windows to match how fast your buyers actually decide.
Write macros that sound human, not hollow
Macros are not auto-replies that pretend to be personal. They are approved sentences for the first touch — hours, area, how to book, what to send for a quote — with a blank for the one detail that matters.
A good macro names the next step. "Send the address and a photo of the space to this link" beats "DM us." A bad macro performs empathy without authority — "Sorry for your experience" with no owner and no clock.
High-risk topics skip macros. Refunds, injuries, legal threats, and discrimination allegations get a human inside the crisis window, plus a log line.
Build the escalation tree before you need it
Escalation is not "I'll ask the boss." It is a path with a maximum wait.
Level 1 — Channel manager acknowledges every public message inside the window, hides spam, applies macros, tags type.
Level 2 — Functional owner joins for sales, support, or partner questions. Sales owns quote shape. Operations owns delivery complaints.
Level 3 — Executive joins for crisis, media, legal, or requests that bind the company.
Level 4 — Legal / PR / platform joins for threats, regulated claims, impersonation, or coordinated abuse.
Write backups for PTO. Write after-hours rules if you serve emergencies. If nobody is on call, say so on the profile and route urgent work to a phone number that rings.
Pair the tree with your content approval workflow. A public reply that changes price or policy is high tier even if the original post was low tier.
Log incidents you intend to learn from
The incident log is not a shame file. It is four fields: date, channel, type, action, outcome.
Log complaints even if you fixed them in DMs. Log near-misses — the spam wave you almost answered, the refund you almost promised in a comment. Log escalations that worked and ones that blew the window.
Deleted comments without a record teach nothing. Screenshots in a private folder beat arguments in the thread.
Monthly, scan the log for patterns. Same FAQ weekly means a pinned post or a page update. Same complaint means operations, not nicer emojis. Patterns belong in reporting that changes a decision, not in a slide that only counts replies.
Connect response to the destination
A perfect reply that sends someone to a homepage with eight services wastes the win. Point area questions at the service-area proof you already publish. Point quote questions at the short form that matches the channel promise.
If the site cannot finish the job, fix the destination before you scale response. Community management amplifies what exists. It does not invent an offer page at 10 p.m.
What you can document in an afternoon
You do not need enterprise software to start. You need typed messages, named owners, windows, macros, and a log template.
CLICK.BLUE has run channels where replies matter since 2014 — twelve-plus years, fifty-plus businesses, a hundred-plus websites. Ongoing response inside a wider cadence is social media management. A channel that needs the first honest scripts and windows is monthly social.
Get started with your last thirty public messages. We will return a taxonomy and SLA your team can keep when the real work gets busy.
