Community and the inbox
The inbox is where the money actually is
Posts create attention; DMs convert it. For most SMB clients, the entire point of social media is that someone eventually sends a message — "how much for a deep clean?", "is the Saturday slot open?" — and what happens in the next hour decides whether that's revenue or a ghost. This is also the layer AI can't fake: a real human, on brand voice, moving a conversation toward a booking. It's precisely why community management sits in the strategist tier while posting sits on the floor.
DMs as a revenue pipeline
Treat every inbound DM like a lead form submission: acknowledge fast (inside an hour during coverage), answer the actual question, then move one step toward the business outcome — a booking link, a phone number, a quote request. Log anything warm in the client's tracker or CRM so it can't evaporate. And know your limits in advance: you answer questions the FAQ covers; the client answers custom pricing.
Anatomy of that reply: answered within the SLA, mirrored her situation, offered two next steps (low-commitment first), and stayed in Sarah's warm-professional voice. That DM goes in the tracker as a lead with a follow-up date — DMs with no follow-up date are how "posting VAs" lose clients money.
Comment SLAs and escalation rules
Agree on service levels with the client in writing, then hit them. A workable default: comments and DMs answered within 1-2 hours during agreed coverage windows, everything else first thing next window. Since most engagement happens on US time, be honest about coverage — 9am-6pm EST is 9pm-6am in Manila. Many VAs cover an evening block (US morning) plus a PH-morning block (US evening) rather than pretending to be awake 24/7.
| Situation | You do | Escalate? |
|---|---|---|
| FAQ question (hours, price list, location) | Answer from the approved FAQ doc | No |
| Warm lead ("how much for X?") | Reply, send booking link, log in tracker | FYI in daily summary |
| Complaint about service/refund | Acknowledge publicly, move to DM, no promises | Yes — owner, same day |
| Troll or hate comment | Hide (not delete), don't engage, screenshot | Only if it escalates |
| Legal threat, press, safety issue | Nothing public. Screenshot everything | Immediately — call/text, don't just Slack |
Handling the ugly ones
Complaints in public comments are a test the whole audience watches. The pattern: acknowledge fast, take it private, never argue, never promise compensation you're not authorized to give.
"Hi Marco — I'm really sorry this was your experience, and it's not the standard we hold ourselves to. I've sent you a DM so we can get the details and make it right."
Crisis basics: know when to stop the machine
If something blows up — a bad review going viral, a local tragedy, an offensive post that slipped through — the first move is always the same: pause the scheduler. A cheerful pre-scheduled promo landing mid-crisis reads as tone-deaf and becomes its own screenshot. Then escalate per the matrix and wait for the owner's call. Knowing when not to post is a strategist skill clients remember.
Do this now
Twenty minutes, on your mock brand from lesson 2. Add a section titled Community Playbook: (1) rebuild the five-row escalation matrix above, adapted to your brand — what's an FAQ, what's a lead, who gets called at 3am; (2) write five on-voice replies: one FAQ answer, one warm-lead DM reply that offers a next step, one public complaint response, one troll decision (state the action, not a reply), and one "thank you" to a glowing comment that invites a review or referral.
Read the five replies in a row — they should sound like one consistent person who happens to be the brand. That consistency is exactly what clients mean when they say someone "gets our voice," and it's page two of your portfolio.
Tip: use your ← → arrow keys.