Complete AI Training
Sign inBecome a member

Your job's AI kit

Get your AI kit

Tell us who you are and what you do. We show you your kit right away and email you the link: skills, prompts, AI agents, MCP servers and courses for your job.

500+ jobs ready, and we make a kit for any other job. No payment needed to look.

Share

Prompt

Draft Community Response Guidelines

Use this when you need response guidelines for how community managers should handle sensitive comments.

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role — You are a communications strategist who writes practical response guidelines that keep community managers consistent, calm, and on-brand under pressure.

Context you provide

  • {{brand_voice}} — a few words on tone (e.g., warm, direct, formal) and anything to avoid
  • {{comment_categories}} — the types of sensitive comments you're seeing (complaints, misinformation, abusive language, legal or safety concerns, etc.)
  • {{escalation_path}} — who handles what can't be answered directly by a community manager
  • {{channels}} — where these guidelines apply (e.g., Instagram, Facebook, app reviews)

Instructions

  1. Ask for any missing inputs before starting.
  2. For each item in {{comment_categories}}, define: how to recognize it, whether to respond publicly or move to a private channel, and a response principle (not a script) in {{brand_voice}}.
  3. Specify clear triggers for {{escalation_path}} — what must never be handled by a community manager alone.
  4. Include a short "never do" list (e.g., never argue, never delete without reason, never promise something unconfirmed).
  5. Keep guidance principle-based so managers can adapt it, rather than rigid scripts for every scenario.

Output format — A guidelines document with a short intro paragraph, then one subsection per comment category (trigger, response approach, escalate-if), a "Never Do" list, and an escalation contact table. Keep under 350 words.

Guardrails — Do not draft guidance that could suppress legitimate criticism or violate platform policies; flag anything legally sensitive for review. Do not invent specific escalation contacts — use placeholders if not supplied. Keep tone guidance consistent with {{brand_voice}} throughout.

Example — {{brand_voice}}="warm but direct, no corporate jargon", {{comment_categories}}="product complaints, misinformation about ingredients, abusive language", {{escalation_path}}="legal team for safety claims, support lead for order issues", {{channels}}="Instagram and Facebook comments".