Community Management Response Templates
Builds a brand-voiced library of social media reply templates for every common interaction and scenario.
// prompt
You are a senior **community manager and social media engagement specialist** with years of experience moderating high-volume brand accounts. Build a reusable library of response templates for **{{brand_name}}**, a **{{business_type}}**, to handle common interactions on **{{platform}}**.
## Context
- **Brand:** {{brand_name}} — offering {{product_or_service}}
- **Voice & tone:** {{brand_voice}} (e.g., warm, witty, polished)
- **Values to reinforce:** {{brand_values}}
- **Audience:** {{target_audience}}
## What to produce
Write **2–3 ready-to-use templates for each category below**. Keep them appropriate in length and style for {{platform}}, reinforce the brand voice, and leave variable details as merge fields like {{customer_name}}, {{order_number}}, or {{link}}.
1. **Positive interactions** — thank-you replies, compliment acknowledgments, reposting user-generated content.
2. **Customer service** — problem resolution (apology + clear move-to-DM path), refund/return questions, information requests.
3. **Engagement** — replies to general comments, questions back to the audience, contest/giveaway entries.
4. **Difficult situations** — constructive criticism, escalation handoff, public complaints, and a calm de-escalation reply for trolling.
## Rules
- Match the norms of {{platform}}; use emojis only if they fit {{brand_voice}}.
- Never promise timelines, refunds, or facts you can't guarantee — keep specifics in {{bracketed}} merge fields the team fills in.
- Always offer a clear next step (DM, link, or follow-up).
- Sound human and on-brand, never scripted or robotic.
## Output format
For each category, present a list or table with three columns: the **scenario**, the **template text**, and a one-line **note on when to use it**. Finish with three quick **do / don't** tips for moderating {{platform}} in {{brand_voice}}.
Fill in the variables
Example run
Generated by Claude Opus 5.5 on September 23, 2026
Inputs used
- Brand name
- Fernweg Coffee Roasters
- Business type
- small-batch, direct-trade coffee roastery with a monthly subscription box
- Platform
- Product or service
- single-origin coffee subscription boxes (whole bean or ground, shipped monthly)
- Brand voice
- warm, witty, polished — like a well-traveled friend who happens to be a coffee nerd
- Brand values
- direct-trade sourcing, sustainability (compostable packaging), transparency with farmers' pay, and building a genuine coffee-curious community
- Target audience
- coffee enthusiasts aged 25–45 who care about ethical sourcing and enjoy discovering new origins each month
- Customer name
- Priya Anand
- Order number
- FW-48213
- Link
- fernwegcoffee.com/support
- Bracketed
- [specific detail, e.g., refund amount, ship date, or replacement timeline]
Fernweg Coffee Roasters: Instagram Response Template Library
How to use this library:
- Replace anything in
[brackets]before posting. - Common merge fields:
[@handle],[First Name],[Order #],[Origin](e.g., "Huila, Colombia"),[Farmer/Co-op Name],[Support Link],[Team Member Name]. - Anything involving money, dates or replacements stays in a merge field until the team confirms it.
- Tweak one or two words every time you post. Identical replies under the same post read as bot-written.
1. Positive Interactions
| Scenario | Template Text | When to Use |
|---|---|---|
| Thank-you reply (customer shares a happy experience) | [@handle] this made our whole roasting crew grin ☕ Thank you for brewing along with us. [Farmer/Co-op Name] put a lot of love into this lot, and we'll make sure they hear it landed well. |
Use when a customer praises a specific box or origin. Passing thanks back to farmers reinforces direct trade. |
| Compliment acknowledgment (praise for packaging, brand or values) | Ah, you noticed the compostable bag! 🌱 [@handle], you're our kind of person. Pop it in the compost when you're done, and it'll finish its journey the way it started: close to the earth. |
Use for comments about packaging, sustainability or brand aesthetics. |
| Compliment acknowledgment (general love) | [@handle] you've officially made our morning better than our first cup did, and that's saying something. Thanks for being part of the Fernweg crew. What origin are you hoping we land on next? |
Use for broad "love this brand" comments. The question keeps the conversation going. |
| UGC repost request | This photo belongs on a postcard, [@handle] 📸 Would you mind if we shared it on our feed (with full credit, of course)? Just reply "yes" here and we'll handle the rest. |
Use before any repost. Always get explicit permission in the comments or DMs first. |
| UGC repost caption (after permission) | Brewed, poured and beautifully captured by [@handle] ✨ This month's [Origin] traveled from [Farmer/Co-op Name] to their kitchen, and we love seeing where our beans end up. Tag us in your brew, and your cup might be next. |
Use as the caption when resharing. Credit the creator in the first line. |
2. Customer Service
| Scenario | Template Text | When to Use |
|---|---|---|
| Problem resolution (damaged, missing or wrong item) | Oh no, [@handle], that's not the welcome we wanted for your box. We're sorry. Could you send us a DM with your order number and a quick photo? We'll look into it personally and figure out the right fix together. |
Use for any fulfillment issue raised publicly. Apologize once, then move to DMs. Never ask for order details in the comments. |
| Problem resolution (delayed shipment) | Totally fair to wonder where your beans are, [@handle]. Let's track it down. DM us your order number and we'll check exactly where your box is and what's happening with it. |
Use for "where's my order?" comments. Don't guess at carrier timing publicly. |
| Refund/return question | Great question, [@handle]. Our full policy lives at [Support Link], but every situation is a little different. Send us a DM with your order number and we'll walk you through your options. |
Use when someone asks about refunds in general. Link the policy and keep specific amounts or eligibility out of public comments. |
| Refund/return follow-up (in DM, after team confirms) | Thanks for your patience, [First Name]. We've confirmed [specific detail, e.g., refund amount / replacement box / credit] for order [Order #], and you can expect it [confirmed timeline]. If anything looks off on your end, just reply here. We've got you. |
Use in DMs only, after the team has approved the resolution. Fill every bracket before sending. |
| Information request (grind, roast, subscription details) | Happy to nerd out on this, [@handle] 🤓 [Answer, e.g., "You can switch between whole bean and ground anytime in your account settings"]. More details live at [Support Link], and if you'd like help picking a grind for your brewer, slide into our DMs. |
Use for FAQs about the product or subscription. Offer a deeper conversation for brew-method questions. |
| Information request (sourcing and farmer pay) | We love this question. This month's [Origin] comes from [Farmer/Co-op Name], and we publish what we pay farmers at [Transparency Link]. Want the full story behind this lot? DM us and we'll share more. |
Use when someone asks about ethics, pricing or sourcing. Link the verified data rather than quoting figures from memory. |
3. Engagement
| Scenario | Template Text | When to Use |
|---|---|---|
| General comment reply (e.g., "Looks delicious!") | It tastes even better than it looks, and we checked. Thoroughly. Several times. For science. ☕ | Use for short, positive drive-by comments. Keep it light and brief. |
| General comment reply (brew-method share) | A [brew method, e.g., Chemex] person! Excellent taste in both beans and equipment, [@handle]. How are you finding [Origin] on it? We're curious whether the [tasting note] comes through. |
Use when followers share how they brew. It invites a longer conversation. |
| Question back to the audience (caption or reply) | Settle a debate in the roastery: are you a "tasting notes on the bag" person or a "just tell me it's good" person? 👇 No wrong answers (okay, maybe one). | Use as a caption or story prompt to spark comments. Keep it easy to answer. |
| Question back to the audience (origin discovery) | If you could get a postcard from any coffee-growing region, where would it come from? We're mapping out future boxes and genuinely want to know. 🗺️ | Use for community input posts. It reinforces the discovery theme. Only say "we're planning" if that's true. |
| Contest/giveaway entry reply | You're in, [@handle]! 🎉 Fingers crossed for you. We'll announce the winner on [announcement date], and full rules are at [Rules Link]. |
Use to acknowledge entries. Only include dates the team has confirmed. |
| Contest/giveaway entry (incomplete entry) | Love the enthusiasm, [@handle]! Quick heads up: to be entered you'll also need to [missing step, e.g., tag a friend]. Full rules are here: [Rules Link]. Good luck! ☕ |
Use when an entry is missing a requirement. Keep it friendly and never scold. |
4. Difficult Situations
| Scenario | Template Text | When to Use |
|---|---|---|
| Constructive criticism (didn't like an origin or roast) | Thank you for being honest, [@handle]. Genuinely. Not every origin will be everyone's cup, and this kind of feedback helps us curate better boxes. Would you DM us what you usually enjoy? We'd love to point you toward something that fits your taste better. |
Use for taste feedback. Validate it and turn it into a personalized next step. |
| Constructive criticism (price, packaging or service) | Fair point, and we appreciate you raising it, [@handle]. We've shared it with the team. If you're open to it, DM us. We'd like to hear more about what would make this work better for you. |
Use for feedback about the business. Don't argue or justify at length in public. |
| Escalation handoff | [@handle], we want to make sure this gets the attention it deserves. I've passed it to [Team Member Name] on our customer care team, who can dig into the details. Keep an eye on your DMs, or reach them directly at [Support Link]. |
Use when an issue needs a manager, billing or ops. Name a real person when possible. |
| Public complaint (frustrated, legitimate) | [@handle], you're right to be frustrated, and we're sorry we let you down. This isn't the experience we want for anyone in our community. We've sent you a DM so we can sort this out properly. We'll see you there. |
Use for visible, emotional complaints. Acknowledge, own it, and move to DMs. Then actually send the DM right away. |
| Public complaint (repeat or unresolved) | [@handle], we hear you, and we're sorry this still isn't fixed. That's on us. [Team Member Name] is personally taking over and will reach out via DM [confirmed timeframe, if any]. |
Use when a previous resolution attempt failed. Show escalation clearly and publicly. |
| Trolling de-escalation | Appreciate you stopping by, [@handle]. If there's something specific we can help with, our DMs are always open. ☕ |
Use once for bad-faith or baiting comments. Stay calm, reply once, and don't engage further. Hide or report per community guidelines if it turns abusive. |
| Trolling de-escalation (misinformation about sourcing) | We hear the skepticism, and we're glad people ask these questions. Transparency is kind of our whole thing. You can see exactly what we pay our farmers at [Transparency Link]. Happy to chat more in DMs anytime. |
Use when someone publicly questions your ethics. Reply once with verifiable facts, not defensiveness. |
Quick Do / Don't Tips for Moderating in the Fernweg Voice
-
✅ Do add one specific, human detail (the origin, the farmer, their brew method) so every reply feels hand-poured. ❌ Don't paste the same template under ten comments. Instagram users notice, and it undermines the "well-traveled friend" feel.
-
✅ Do keep humor for happy and neutral moments, and switch to warm and plain when someone is upset. ❌ Don't crack jokes in a complaint thread. Wit at the wrong moment reads as dismissive.
-
✅ Do move anything involving orders, money or personal details to DMs within the same hour, and follow up publicly once it's resolved (e.g., "All sorted, thanks for your patience! ☕"). ❌ Don't promise refunds, ship dates or fixes in the comments before the team has confirmed them. Keep them in merge fields until they're real.
Related prompts
Social Media & Communication
Telegram Channel Content Plan Builder
Builds a 30-day Telegram channel content plan with pillars, post formats, opening hooks, interactive posts, and CTAs designed around forwards and notifications.
Social Media & Communication
Telegram Bot Conversation Designer
Designs complete Telegram bot conversations: onboarding, scenario flows built on inline keyboards, real message copy, error recovery paths, and a command menu.
Social Media & Communication
YouTube Video Title & Description Optimizer
Generates click-worthy, keyword-optimized YouTube titles, descriptions, tags, and thumbnail ideas to maximize search reach and CTR.
Social Media & Communication
LinkedIn Professional Post Creator
Writes a polished, engagement-optimized LinkedIn thought-leadership post that builds your professional credibility.