Working social media managers who need professional community responses written fast. Copy these prompts into ChatGPT, fill in the variables, and get polished replies you can post immediately.
These prompts pair well with Jasper AI for Social Media Managers-specific tone control, or Copy.ai for fast iteration.
Crisis Response and Damage Control
You are a community manager responding to a product failure complaint that’s getting traction in comments.
Brand: {brand_name} Platform: {facebook / instagram / twitter / linkedin} Original complaint: {customer_complaint_in_their_words} What actually happened: {internal_explanation_of_issue} Resolution offered: {refund / replacement / credit / investigation} Timeline for fix: {specific_timeframe} Brand voice: {professional / friendly / empathetic / corporate} Complaint severity: {low / medium / high / viral_risk}
Write a 150 to 200 word public response that acknowledges the issue without admitting legal fault, shows you’re taking action, and moves the conversation to DMs for resolution details. Include a clear next step for the customer.
When to use it: When a product complaint is getting multiple reactions or replies and you need to respond publicly before it spreads.
Pro tip: Always reference their specific issue, not generic “we value your feedback” language. Customers can tell when responses are templated.
You are handling a viral negative post about your brand that’s spreading across social platforms.
Brand: {brand_name} Platform where it started: {original_platform} Core accusation: {main_claim_against_brand} Your investigation findings: {what_you_discovered_internally} Legal guidance: {can_dispute / must_not_dispute / partial_accuracy} CEO involvement: {ceo_aware / ceo_will_respond / ceo_unavailable} Media attention: {none / some_pickup / major_coverage} Response urgency: {within_1_hour / within_4_hours / end_of_day}
Write a 300 to 400 word statement addressing the viral post. Lead with facts, avoid defensive language, outline specific steps you’re taking, and include a timeline. End with contact information for media or affected customers.
When to use it: When a negative post about your brand hits 100+ shares or gets picked up by news outlets or industry accounts.
Pro tip: Post the same statement across all platforms simultaneously. Inconsistent messaging between channels makes crisis situations worse.
You need to respond to an influencer who posted criticism of your brand to their 50K+ followers.
Influencer name: {influencer_handle} Their follower count: {follower_number} Their specific criticism: {what_they_said} Your relationship history: {never_worked_together / past_collaboration / ongoing_partnership} Criticism validity: {completely_wrong / partially_accurate / mostly_fair} Internal stakeholders involved: {just_you / marketing_director / legal_team} Desired outcome: {public_correction / private_resolution / relationship_repair} Response timeline: {immediate / within_24_hours / coordinated_timing}
Write a 200 to 250 word response that addresses their concerns professionally, provides factual corrections where needed, and suggests moving to a private conversation. Match their communication style while maintaining brand voice.
When to use it: When someone with significant reach posts criticism and their audience is engaging heavily with the negative content.
Pro tip: Check if the influencer has criticized other brands recently. Serial complainers need different handling than one-off situations.
You’re responding to a customer service failure that’s been escalated to social media after poor phone/email support.
Customer name: {customer_first_name} Original issue: {initial_problem_description} Previous touchpoints: {phone / email / chat / store} What went wrong in service: {missed_callbacks / rude_agent / wrong_information / delays} Customer’s emotional state: {frustrated / angry / disappointed / threatening_to_leave} Resolution available: {full_refund / partial_credit / free_service / policy_exception} Public visibility: {few_likes / getting_shares / comment_thread_growing} Account value: {new_customer / loyal_customer / high_value_customer}
Write a 175 to 225 word response that acknowledges the service breakdown specifically, takes ownership without blaming team members, and provides immediate next steps. Include your direct contact information.
When to use it: When customers post about bad service experiences and tag your brand or post on your page.
Pro tip: Never defend your team’s actions in public, even if the customer is exaggerating. Save explanations for private conversations.
You need to address multiple customers complaining about the same technical issue in a single response.
Technical issue: {specific_problem_description} Platforms affected: {website / app / payment_system / login} Number of complaints: {approximate_count} Engineering team status: {investigating / identified_cause / pushing_fix / resolved} Estimated fix time: {specific_timeframe_or_unknown} Workaround available: {yes_describe / no / partial_solution} Business impact: {minor_inconvenience / major_disruption / revenue_affecting} Communication channels: {just_social / email_blast / website_banner / all_channels}
Write a 250 to 300 word update post that explains the situation clearly, provides realistic timelines, offers workarounds if available, and commits to follow-up updates. Use technical language appropriately for your audience.
When to use it: When the same technical problem generates 5+ separate complaints across your social channels within a few hours.
Pro tip: Pin this post to the top of your page and reference it when responding to individual complaints to avoid repeating yourself.
Customer Service Recovery
You’re responding to a customer who received a damaged product and shared photos of the damage.
Customer name: {customer_first_name} Product damaged: {specific_product_name} Damage type: {broken / wrong_item / missing_parts / defective} Order number: {order_reference} Purchase date: {when_they_bought} Shipping carrier: {ups / fedex / usps / dhl} Customer tone: {calm / frustrated / disappointed / demanding_refund} Photos provided: {yes / no / partial_documentation}
Write a 125 to 175 word response that expresses genuine concern about the damage, requests any missing information you need, and outlines the replacement process with specific timelines. Include a gesture of goodwill.
When to use it: When customers post images of damaged products on your social media pages or tag you in damage posts.
Pro tip: Always ask for the order number in your response, even if they didn’t provide it. This moves the conversation toward resolution faster.
You’re handling a billing dispute where the customer claims they were charged incorrectly.
Customer handle: {social_media_handle} Billing issue: {duplicate_charge / wrong_amount / unauthorized_charge / failed_refund} Amount disputed: {dollar_amount} Account status: {active / cancelled / suspended / new} Previous resolution attempts: {none / phone_call / email_exchange / chat_session} Charge date: {when_transaction_occurred} Payment method: {credit_card / paypal / bank_transfer / digital_wallet} Urgency level: {standard / threatening_chargeback / legal_threats / media_attention}
Write a 150 to 200 word response that acknowledges their billing concern, explains the immediate steps you’ll take to investigate, and provides a realistic timeline for resolution. Include specific contact information for faster resolution.
When to use it: When customers post about unexpected charges or failed refunds on your social media accounts.
Pro tip: For billing issues, always move to private channels immediately. Financial details should never be discussed in public comments.
A customer received poor service at your physical location and posted about it online.
Location: {store_city_and_state} Service issue: {rude_staff / long_wait / wrong_order / dirty_location / policy_dispute} Staff member involved: {yes_named / yes_described / not_specified} Date of visit: {specific_date_or_timeframe} Customer expectation: {apology / staff_discipline / policy_change / compensation} Location manager awareness: {informed / needs_notification / investigating} Franchise vs corporate: {company_owned / franchise / licensing_partner} Review platform: {google / yelp / facebook / instagram}
Write a 175 to 225 word response that addresses the specific service failure, explains how you’ll follow up with the location, and offers to make things right. Include contact information for the local manager if appropriate.
When to use it: When customers tag your location or post negative reviews about in-person service experiences.
Pro tip: Always loop in the local manager before you respond. They need to know complaints are public and may get follow-up contact.
You’re responding to a customer who can’t get through to customer service by phone or email.
Customer name: {customer_first_name} Contact attempts: {phone_calls / emails_sent / chat_attempts} Original issue: {account_problem / order_question / technical_support / billing} Time trying to reach you: {hours / days / weeks} Customer emotional state: {patient / frustrated / angry / threatening_to_leave} Contact center status: {high_volume / staffing_shortage / system_down / normal_operations} Alternative channels: {live_chat / email_form / callback_request / appointment_booking} Account priority: {vip / long_term / new / at_risk}
Write a 150 to 200 word response apologizing for the contact difficulty, providing alternative ways to reach support, and offering to personally ensure their issue gets priority attention. Include specific next steps and timing.
When to use it: When customers post frustration about not being able to reach your support team through normal channels.
Pro tip: Get their contact information in your first response and actually follow up. Customers remember when social media promises don’t happen.
A subscription customer is trying to cancel but claims they can’t figure out how or it’s not working.
Customer handle: {customer_username} Subscription type: {monthly / annual / trial / premium} Cancellation method tried: {website / app / phone / email} Error or obstacle: {technical_error / can’t_find_option / billing_cycle_confusion / retention_offer} Account tenure: {new / 6_months / 1_year / longtime_customer} Cancellation urgency: {end_of_trial / before_next_billing / immediate / end_of_contract} Customer tone: {neutral / frustrated / suspicious_of_dark_patterns} Retention interest: {yes_try_to_save / no_process_immediately}
Write a 125 to 175 word response providing clear step-by-step cancellation instructions, offering direct assistance, and respecting their decision to leave. If retention is appropriate, mention one alternative option without being pushy.
When to use it: When customers publicly complain about difficulty cancelling subscriptions or memberships.
Pro tip: Be extra helpful with cancellation requests. Customers share screenshots of good and bad cancellation experiences widely on social media.
Engagement and Community Building
You’re responding to a customer who shared a creative use of your product that impressed you.
Customer name: {customer_first_name} Product used: {specific_product} Creative application: {how_they_used_it_differently} Platform posted on: {instagram / tiktok / twitter / facebook} Content type: {photo / video / story / text_post} Engagement on their post: {likes / comments / shares_approximate} Repost potential: {yes_ask_permission / yes_already_tagged_you / no_keep_private} Brand campaign relevance: {fits_current_campaign / good_for_future / no_campaign_fit}
Write a 100 to 150 word response celebrating their creativity, asking relevant follow-up questions about their experience, and building community connection. If appropriate, ask permission to share their content.
When to use it: When customers post impressive or unexpected ways they’ve used your products.
Pro tip: Always ask permission before reposting customer content, even if they tagged you. It shows respect and often leads to better ongoing relationships.
A customer posted a before-and-after transformation using your product with impressive results.
Customer handle: {customer_social_handle} Product used: {specific_product_or_service} Timeframe of results: {weeks / months / specific_duration} Type of transformation: {fitness / home_improvement / skill_development / business_results} Documentation quality: {excellent_photos / good_description / video_content / detailed_metrics} Customer followers: {approximate_follower_count} Hashtags used: {your_brand_hashtags / industry_hashtags / personal_tags} Testimonial value: {high / medium / low}
Write a 125 to 175 word congratulatory response that celebrates their achievement, highlights specific impressive details, and encourages community engagement. Ask one thoughtful follow-up question about their journey.
When to use it: When customers share dramatic before-and-after results from using your products or services.
Pro tip: Focus more on congratulating their hard work than promoting your product. Authentic celebration performs better than sales-focused responses.
You’re responding to a customer who asked a detailed technical question about your product.
Customer question: {specific_technical_question} Product involved: {exact_product_model} Customer expertise level: {beginner / intermediate / advanced / professional} Question complexity: {simple_answer / requires_research / need_expert_input} Other customers interested: {solo_question / others_commenting / recurring_question} Documentation available: {user_manual / video_tutorial / knowledge_base / no_existing_resource} Response urgency: {standard / customer_deadline / business_critical} Follow_up_likely: {one_time_question / ongoing_project / relationship_building}
Write a 200 to 250 word response that thoroughly answers their technical question, provides additional helpful context, and positions you as a knowledgeable resource. Include links to relevant documentation if available.
When to use it: When customers ask detailed technical questions that show they’re serious users of your product.
Pro tip: Tag subject matter experts from your team when answering complex technical questions. Customers appreciate access to real expertise.
A customer shared feedback about a feature they love and suggested an improvement.
Customer name: {customer_first_name} Feature they love: {specific_feature} Improvement suggested: {their_enhancement_idea} Suggestion quality: {very_feasible / interesting_but_complex / not_technically_possible} Product team status: {already_considering / worth_proposing / outside_roadmap} Customer type: {power_user / casual_user / new_customer / enterprise_client} Implementation timeline: {next_release / long_term_roadmap / unlikely / unknown} Similar requests: {first_time_hearing_this / occasional_request / frequent_request}
Write a 150 to 200 word response thanking them for both the positive feedback and suggestion, explaining how product feedback gets reviewed, and setting appropriate expectations about implementation without making promises.
When to use it: When engaged customers offer specific feature suggestions or product improvements.
Pro tip: Never promise features will be built, even if they’re already planned. Product timelines change and customers remember specific commitments.
You’re responding to a long-time customer who posted appreciation for your customer service or company.
Customer name: {customer_first_name} Customer tenure: {years_or_months_as_customer} Specific praise: {what_they_appreciated} Team members mentioned: {specific_people / department / general_service} Platform posted: {linkedin / twitter / facebook / google_reviews} Audience reach: {personal_network / business_network / public_review} Relationship value: {high_lifetime_value / vocal_advocate / industry_influence} Sharing potential: {good_testimonial_material / already_public / keep_private}
Write a 100 to 150 word response expressing genuine gratitude, acknowledging specific team members if mentioned, and reinforcing the relationship. Include a forward-looking statement about continuing to serve them well.
When to use it: When loyal customers post unsolicited praise or positive reviews about your service.
Pro tip: Screenshot these positive mentions and share them with the specific team members mentioned. Internal recognition is as important as the public response.
Product Launch and Announcements
You’re responding to early feedback on a product you just launched yesterday.
Product launched: {new_product_name} Customer feedback type: {positive_excitement / concerns_raised / feature_questions / pricing_reaction} Specific feedback: {their_exact_comment_or_concern} Feedback validity: {on_target / misunderstands_product / based_on_old_info} Launch momentum: {going_well / mixed_reception / facing_criticism} Team availability: {product_manager_available / engineers_monitoring / standard_support} Customer influence: {industry_expert / key_account / vocal_community_member / general_customer} Response timing: {immediate / within_hours / coordinated_with_team}
Write a 175 to 225 word response addressing their specific feedback, providing additional context about the product, and encouraging continued dialogue. Include information about where they can learn more or provide additional input.
When to use it: During the first week after launching a new product when early adopters are sharing first impressions.
Pro tip: Respond faster than usual during launch weeks. Early feedback shapes other customers’ decisions about trying new products.
A customer is comparing your new product to a competitor and asking for clarification on differences.
Your product: {your_product_name} Competitor mentioned: {competitor_name} Comparison points: {price / features / performance / support} Customer decision stage: {researching / ready_to_buy / existing_customer_considering_upgrade} Competitive advantage: {your_stronger_areas} Competitor strengths: {where_they_excel} Information needed: {feature_details / pricing_clarification / trial_options} Sales involvement: {handle_in_community / escalate_to_sales / provide_resources}
Write a 200 to 250 word response that honestly addresses the comparison, highlights your differentiators without disparaging competitors, and provides helpful decision-making information. Include next steps for getting more detailed information.
When to use it: When prospects publicly ask about how your products compare to specific competitors.
Pro tip: Never badmouth competitors in public responses. Focus on your strengths and let customers draw their own conclusions about trade-offs.
You’re announcing a significant product update and responding to the first wave of customer reactions.
Update type: {new_features / interface_redesign / pricing_change / policy_update} Customer reaction: {mostly_positive / mixed_feedback / significant_complaints} Specific concerns raised: {usability / cost / missing_features / change_resistance} Implementation timeline: {live_now / rolling_out / coming_next_month} Rollback possibility: {can_revert / limited_changes / permanent_change} Training available: {help_docs / video_tutorials / live_training / self_service} Support preparation: {team_briefed / expecting_high_volume / normal_capacity} Communication plan: {this_response_only / series_of_updates / ongoing_dialogue}
Write a 250 to 300 word response acknowledging the range of reactions, explaining the reasoning behind changes, addressing common concerns, and providing resources for adaptation. Include channels for ongoing feedback.
When to use it: Within 24 hours of announcing major product changes when customer reactions are pouring in.
Pro tip: Address the most common concerns in your main announcement response, then reference back to it when replying to individual comments.
A customer is excited about your announcement but asking when specific features will be available.
Announced feature: {what_you_revealed} Customer excitement level: {very_enthusiastic / cautiously_optimistic / specifically_interested} Availability timeline: {specific_date / quarter / this_year / timeline_uncertain} Development status: {in_testing / in_development / planning_phase / researching} Customer segment: {enterprise / small_business / individual / developer} Beta program: {available / planned / not_offering / by_invitation} Competitive pressure: {racing_to_market / comfortable_timeline / first_to_market} Communication clearance: {can_share_timeline / keep_vague / redirect_to_roadmap}
Write a 150 to 200 word response that matches their enthusiasm, provides as much timeline information as you’re cleared to share, and offers ways for them to stay updated or get early access if available.
When to use it: When customers express strong interest in announced features and want specific availability dates.
Pro tip: Always err on the side of longer timelines in public communications. Delayed features disappoint customers more than conservative initial estimates.
You’re responding to concerns about a price increase you just announced.
Price change details: {percentage_increase / new_pricing_structure / affected_products} Effective date: {immediate / 30_days / renewal_date / new_customers_only} Customer segment affected: {all_customers / new_signups / enterprise / specific_plan} Justification: {increased_costs / new_features / market_positioning / inflation} Grandfathering policy: {existing_rates_protected / limited_time_protection / no_protection} Alternative options: {downgrade_available / competitor_recommendations / payment_plans} Customer tone: {disappointed / angry / understanding / threatening_to_leave} Decision authority: {final_decision / input_being_considered / executive_decision}
Write a 200 to 250 word response explaining the reasoning behind the price change, acknowledging customer concerns, outlining any options available to them, and reaffirming the value they receive. Be empathetic but clear about the business necessity.
When to use it: When customers express frustration or concern about announced price increases.
Pro tip: Acknowledge that price increases are never welcome news before explaining your reasoning. Empathy first, justification second.
Frequently Asked Questions
What makes ChatGPT prompts effective for community management responses?
Effective prompts include specific scenarios, real input variables for customization, clear constraints like word count and tone, and produce finished responses ready to post. Generic prompts that ask for “templates” waste time because you still have to write the actual response.
How quickly can I generate responses using these ChatGPT prompts?
Most responses take 30-60 seconds to generate after filling in the variables. The key is having the customer information and context ready before you start the prompt. These prompts work best when you can quickly copy customer details and paste them into the variables.
Should I edit ChatGPT responses before posting them publicly?
Always review AI-generated responses for accuracy, tone, and brand voice before posting. Check that any specific details like timelines or policies are correct, and adjust language to match your brand’s communication style. The prompts create strong drafts, but human review catches important nuances.