Reply to a Public Social Media Complaint and Move It to DM
Get a 280-character public social media reply that de-escalates a complaint, plus a matching direct-message follow-up script to resolve it privately.
You getPublic Reply, private DM Follow-Up and internal Handoff Note
Prompt
Act as a senior customer support specialist skilled in social media de-escalation. I will paste a public customer complaint and any relevant context below.
Your job is to write a calm public reply that moves the conversation to direct messages, followed by a private DM script to resolve the issue.
Rules:
1. Keep the public reply under 280 characters, including spaces.
2. Acknowledge the customer's frustration without being defensive, making excuses, or blaming the customer.
3. Do not ask for sensitive details (order numbers, emails, or account IDs) in the public reply.
4. Make the DM script warm, direct, and focused on gathering only the exact information needed to fix the problem.
Output format:
- **Public Reply** (include the exact character count)
- **Private DM Follow-Up** (the opening message to send once they reach out)
- **Internal Handoff Note** (2-3 bullet points on what to check before replying further)
End with one line noting any missing context or policy risks to verify before posting.Example output
Tips and common edits
Why this works
- Enforcing a 280-character limit keeps the public reply concise and prevents over-explaining.
- Banning sensitive data requests in public protects customer privacy and platform compliance.
- Pairing the public reply with a DM script ensures a seamless, non-defensive handoff.
Use this in ChatGPT, Claude, or Gemini when a customer vents publicly on X, Instagram, or LinkedIn. Paste the customer's post and any order or outage context you have.
Common edits
- Add your brand's specific tone of voice (e.g., casual, formal, or playful) to the rules.
- Include your company's exact refund or replacement policy so the DM script reflects it.
Make it repeatable
Keep using this prompt without pasting it in every time.
Prompt details
- By
- Prompts-GPT editors
- Published
Keep exploring
More like this
Reply calmly to a negative public customer review
Draft composed, professional public responses to critical reviews that acknowledge mistakes, de-escalate tension, and move resolution offline.
Score a Support Agent Reply Against a Quality Assurance Rubric
Get a four-criteria QA scorecard table grading tone, accuracy, completeness, and next steps, plus a ready-to-send rewrite of your support agent's reply.
Reply to an Angry Customer Complaint Without Blame or Vague Promises
Paste an angry customer message and get a calm reply that names their exact problem first, skips blame-shifting phrases, and ends with one dated next step.
Write Executive Escalation Email for At-Risk Customers
Generate a professional, high-impact email from a VP to retain a churn-risk customer by offering ownership, a concrete fix, and direct communication.
Draft a Bug Acknowledgment Email Without an ETA
Generate a clear support email that validates a reported bug, provides a safe temporary workaround, and sets realistic follow-up expectations.
Respond to an Abusive Ticket While Solving the Issue
Generates a calm customer support reply that establishes clear conduct boundaries while resolving the underlying technical problem.
- Find Help Center Gaps by Matching Support Tickets to Existing Articles
- Write Help Article Titles and Meta Descriptions in Your Customers' Words
- Build a Yes/No Troubleshooting Decision Tree for a Recurring Product Issue
- Write a Customer Outage Update for Status Page, Email and Social
- Write Saved Replies (Macros) for Your Top Five Support Ticket Types
- Explain browser console logs to everyday users