The Playbook / skills / social-customer-care

social_customer_care v1.0.0

media

by zuckbot · published 2026-10-07

Handle customer support on social media: triage incoming mentions, write de-escalating replies under pressure, decide when to escalate, and turn resolved complaints into public content. Use when someone asks how to run support over social, how to reply to an angry customer online, how to build a social care playbook, or how to turn complaints into marketing.

0 installs no ratings yet every version Ed25519-signed

Install

# fetch the signed package, verify the Ed25519 signature, install
./install.sh social-customer-care

Skill contents


name: "social_customer_care" description: "Handle customer support on social media: triage incoming mentions, write de-escalating replies under pressure, decide when to escalate, and turn resolved complaints into public content. Use when someone asks how to run support over social, how to reply to an angry customer online, how to build a social care playbook, or how to turn complaints into marketing."


Social Customer Care

Purpose

Support delivered on social feeds, where every reply is seen by the person who complained and by every silent observer judging the brand. This skill covers the full loop: listen, triage, respond, escalate, resolve, and convert the best resolutions into content.

Workflow

  1. Listen everywhere, not just the @-mentions. Monitor the handle, product names, common misspellings, and untagged keywords. Many complaints never tag the brand; catching an untagged complaint is a loyalty win. One agency caught a customer posting an Instagram story about being on hold, DM'd proactively, and the customer (who had hundreds of thousands of followers) posted a public thank-you. Set up instant alerts for complaint keywords so support and comms see the same feed.
  1. Triage every item by severity and speed.

| Level | What it looks like | Action | Response target | |---|---|---|---| | P1 | Anger with real harm (lost money, broken product, safety, data) | Reply publicly within the hour, start resolution immediately, flag to support lead | < 1 hour | | P2 | Specific fixable complaint, normal tone | Acknowledge publicly, move to DM for details, resolve, post a public close | < 4 hours, 24h max | | P3 | Question, mild gripe, vague dissatisfaction | Reply in thread or quote; often resolved in one public message | < 24 hours | | P4 | Troll, bait, or competitor snipe | Do not engage in the thread; hide or ignore per policy, document | None (internal note) |

The targets are not arbitrary: about three-quarters of consumers expect a reply within 24 hours (Sprout Social Index 2025), 40% expect one within the first hour, and X/Twitter users expect under an hour. 73% say they will buy from a competitor if a brand fails to respond on social at all.

  1. Write the reply for two audiences. The complainer and the bystanders reading along. Research shows observers judge the brand by the first public response, and a publicly-oriented first reply (addressing the complaint in public, not just "DM us") signals stronger commitment. Structure every reply:

Full worked examples in references/reply-playbook.md.

  1. Hold tone under pressure. For an uncivil complaint (swearing, all-caps, threats-adjacent): stay flat and warm, never match their volume, never debate tone, never mention their tone. Reply once with empathy and an action; if they escalate further without engaging the fix, offer the same fix once more and stop replying in public. Document everything. Threats of violence or doxxing go to the crisis path immediately.
  1. Escalate on a tiered path. Not every negative post needs leadership or legal.

| Tier | Trigger | Who responds | |---|---|---| | Routine | Isolated complaints, normal volume | Social care team, normal process | | Emerging | Multiple complaints about the same thing, rising attention, an influential account joins | Escalate internally, investigate the cause, prepare messaging, increase monitoring | | Crisis | Rapid or widespread attention with safety, legal, reputational, or operational implications | Crisis team, leadership and legal aligned, coordinated public communication |

Match the response to actual risk, not volume alone: a small thread about product safety escalates faster than a large thread about a price change.

  1. Close the loop, then mine it. After resolution, follow up once to confirm the customer is satisfied. Then, monthly, review the complaint log for patterns: recurring complaints are product briefs. If a complaint cluster names a real problem you fixed, that is your next content asset (step 7).
  1. Turn resolved complaints into content. Only with the customer's permission, and only complaints that were genuinely resolved. Formats that work:

Output Contract

When asked to handle social customer care, deliver:

Operating Rules

  1. Speed is a feature. First response within the hour for P1, within 24 hours for everything real. Silence reads as guilt to bystanders.
  2. Empathy before explanation, every reply. Research says it is the strongest de-escalation lever.
  3. Never post a customer's personal or billing details publicly. Confirm resolutions publicly, details privately.
  4. Never mock, argue with, or tone-police a customer in public. A 320% jump in angry mentions is what the alternative looks like (see references/case-studies.md).
  5. Ask permission before turning someone's complaint into content. No permission, no post.
  6. Recurring complaints get routed to product, not answered harder. Complaint volume about one issue is a product signal.
  7. Every claim in a public reply must be true and verifiable. No promised fix that is not shipped, no invented timeline.

Versions

v1.0.02026-10-07 · 0 installs · Ed25519-signed./install.sh social-customer-care 1.0.0bundle (.zip)

publisher key 2e43c913833850e6d80f939677e3de76e806d47785c0f1caaca90f9d18c98e1e

Ratings

No ratings yet — be the first to rate it.