{"slug":"social-media-strategist-launch-crisis","title":"Social Media Strategist: Product Launch and Crisis Response","tags":["social-strategy","product-launch","crisis-response","campaign","social-media"],"agent_summary":"Two strategic modes: Mode 1 builds a product launch campaign across pre-launch, launch, and post-launch phases. Mode 2 builds a crisis response plan covering immediate response, reputation management, and recovery content.","trigger_phrases":["social media strategy","product launch campaign","crisis response social media","launch campaign","handle negative press","social media crisis","launch strategy"],"runnable":true,"markdown":"\n# Social Media Strategist: Product Launch and Crisis Response\n\nTwo modes for high-stakes social situations. Product launches and crisis moments both require structured strategy — improvised social content in either scenario is expensive.\n\n---\n\n## Mode 1: Product Launch Campaign\n\n### Phase 1: Pre-Launch (4 weeks out)\n\n**Goal:** Build anticipation without revealing everything.\n\n| Week | Content Focus | Platforms | Post Frequency |\n|------|--------------|-----------|----------------|\n| 4 weeks out | Tease the problem being solved | All | 3x/week |\n| 3 weeks out | Behind-the-scenes or \"coming soon\" | All | 3x/week |\n| 2 weeks out | Email list + follower early access offer | Email + social | 4x/week |\n| 1 week out | Countdown + daily reveals | All | Daily |\n\n**Pre-launch content types:**\n- \"We've been working on something...\" post (vague, curiosity-driven)\n- Problem-focused content that seeds the pain point\n- Social proof: beta tester testimonials or early results\n- Waitlist/early access push: scarcity drives signup\n\n---\n\n### Phase 2: Launch Week\n\n**Day 1 (Launch Day):**\n- Announcement post across all platforms (native format per platform)\n- Email blast to full list\n- Stories: real-time updates, founder video, customer reactions\n\n**Days 2-5:**\n- Case study or before/after from early user\n- FAQ content addressing launch objections\n- Social proof amplification (share reviews, testimonials)\n- \"Last X hours at launch price\" urgency content\n\n**Launch post template:**\n```\n[The announcement — one clear sentence]\n\n[What it does for the customer — specific outcome]\n\n[Why now — one sentence on timing or scarcity]\n\n[Link + CTA]\n```\n\n---\n\n### Phase 3: Post-Launch (2 weeks)\n\n**Goal:** Maintain momentum, convert fence-sitters, build social proof.\n\n- Customer success content: real results with real numbers\n- FAQ resolution: address every common objection that appeared during launch\n- Community content: user-generated content amplification\n- FOMO play: \"X people joined in the first 48 hours\"\n\n---\n\n## Mode 2: Crisis Response Plan\n\n### Triage First\n\nBefore responding publicly, answer these internally:\n\n1. What is the actual claim or complaint? (Summarize in one sentence)\n2. Is it factually accurate? (Verify before disputing)\n3. What is the potential reach? (Small complaint vs viral post)\n4. Who is the source? (Customer, competitor, journalist, influencer)\n5. What is the worst-case outcome if handled poorly?\n\n---\n\n### Phase 1: Immediate Response (within 2 hours)\n\n**Do:**\n- Acknowledge the situation without admitting fault before investigation\n- Move detailed resolution to DM or email — not public comment threads\n- Designate one spokesperson; all responses go through them\n\n**Don't:**\n- Delete negative comments (it amplifies the story)\n- Argue facts publicly before internal verification\n- Post \"business as usual\" content during active crisis\n\n**First response template:**\n```\nWe've seen this feedback and we take it seriously. [One sentence acknowledging the concern — no defensiveness]. We're looking into this now and will follow up directly. If you're affected, please DM us or reach us at [contact].\n```\n\n---\n\n### Phase 2: Reputation Management (Days 1-7)\n\n**Content to suppress vs amplify:**\n\n| Action | What |\n|--------|------|\n| Amplify immediately | Positive customer testimonials already on record |\n| Amplify if genuine | Behind-the-scenes transparency content |\n| Hold | Any promotional content |\n| Cancel | Scheduled humor or celebratory posts |\n\n**Week-1 content calendar:**\n- Day 2: Factual update on what happened and what's being done\n- Day 4: Evidence of resolution (if resolved) or progress update\n- Day 7: Return to normal content — crisis mentioned only if asked\n\n---\n\n### Phase 3: Recovery Content (Weeks 2-4)\n\n- Customer stories that reinforce trust\n- Transparent \"what we learned\" post (authentic, not PR-speak)\n- Updated policy or product improvement announcement if applicable\n- Return to full content calendar with crisis tone integrated, not erased\n\n---\n\n## Crisis Tone Rules\n\n- First-person plural: \"We\" not \"the company\" or \"our team\"\n- No passive voice: \"Mistakes were made\" = trust killer\n- Specific action stated: \"We've updated our [policy/product/process]\"\n- Timeline provided: \"By [date] we will [action]\"\n- Never: \"We apologize if anyone was offended\" (conditional apology = not an apology)\n\n#content-sop #social-strategy #product-launch #crisis\n","html":"<h1>Social Media Strategist: Product Launch and Crisis Response</h1>\n<p>Two modes for high-stakes social situations. Product launches and crisis moments both require structured strategy — improvised social content in either scenario is expensive.</p>\n<hr>\n<h2>Mode 1: Product Launch Campaign</h2>\n<h3>Phase 1: Pre-Launch (4 weeks out)</h3>\n<p><strong>Goal:</strong> Build anticipation without revealing everything.</p>\n<p>| Week | Content Focus | Platforms | Post Frequency |\n|------|--------------|-----------|----------------|\n| 4 weeks out | Tease the problem being solved | All | 3x/week |\n| 3 weeks out | Behind-the-scenes or \"coming soon\" | All | 3x/week |\n| 2 weeks out | Email list + follower early access offer | Email + social | 4x/week |\n| 1 week out | Countdown + daily reveals | All | Daily |</p>\n<p><strong>Pre-launch content types:</strong></p>\n<ul>\n<li>\"We've been working on something...\" post (vague, curiosity-driven)</li>\n<li>Problem-focused content that seeds the pain point</li>\n<li>Social proof: beta tester testimonials or early results</li>\n<li>Waitlist/early access push: scarcity drives signup</li>\n</ul>\n<hr>\n<h3>Phase 2: Launch Week</h3>\n<p><strong>Day 1 (Launch Day):</strong></p>\n<ul>\n<li>Announcement post across all platforms (native format per platform)</li>\n<li>Email blast to full list</li>\n<li>Stories: real-time updates, founder video, customer reactions</li>\n</ul>\n<p><strong>Days 2-5:</strong></p>\n<ul>\n<li>Case study or before/after from early user</li>\n<li>FAQ content addressing launch objections</li>\n<li>Social proof amplification (share reviews, testimonials)</li>\n<li>\"Last X hours at launch price\" urgency content</li>\n</ul>\n<p><strong>Launch post template:</strong></p>\n<pre><code>[The announcement — one clear sentence]\n\n[What it does for the customer — specific outcome]\n\n[Why now — one sentence on timing or scarcity]\n\n[Link + CTA]\n</code></pre>\n<hr>\n<h3>Phase 3: Post-Launch (2 weeks)</h3>\n<p><strong>Goal:</strong> Maintain momentum, convert fence-sitters, build social proof.</p>\n<ul>\n<li>Customer success content: real results with real numbers</li>\n<li>FAQ resolution: address every common objection that appeared during launch</li>\n<li>Community content: user-generated content amplification</li>\n<li>FOMO play: \"X people joined in the first 48 hours\"</li>\n</ul>\n<hr>\n<h2>Mode 2: Crisis Response Plan</h2>\n<h3>Triage First</h3>\n<p>Before responding publicly, answer these internally:</p>\n<ol>\n<li>What is the actual claim or complaint? (Summarize in one sentence)</li>\n<li>Is it factually accurate? (Verify before disputing)</li>\n<li>What is the potential reach? (Small complaint vs viral post)</li>\n<li>Who is the source? (Customer, competitor, journalist, influencer)</li>\n<li>What is the worst-case outcome if handled poorly?</li>\n</ol>\n<hr>\n<h3>Phase 1: Immediate Response (within 2 hours)</h3>\n<p><strong>Do:</strong></p>\n<ul>\n<li>Acknowledge the situation without admitting fault before investigation</li>\n<li>Move detailed resolution to DM or email — not public comment threads</li>\n<li>Designate one spokesperson; all responses go through them</li>\n</ul>\n<p><strong>Don't:</strong></p>\n<ul>\n<li>Delete negative comments (it amplifies the story)</li>\n<li>Argue facts publicly before internal verification</li>\n<li>Post \"business as usual\" content during active crisis</li>\n</ul>\n<p><strong>First response template:</strong></p>\n<pre><code>We've seen this feedback and we take it seriously. [One sentence acknowledging the concern — no defensiveness]. We're looking into this now and will follow up directly. If you're affected, please DM us or reach us at [contact].\n</code></pre>\n<hr>\n<h3>Phase 2: Reputation Management (Days 1-7)</h3>\n<p><strong>Content to suppress vs amplify:</strong></p>\n<p>| Action | What |\n|--------|------|\n| Amplify immediately | Positive customer testimonials already on record |\n| Amplify if genuine | Behind-the-scenes transparency content |\n| Hold | Any promotional content |\n| Cancel | Scheduled humor or celebratory posts |</p>\n<p><strong>Week-1 content calendar:</strong></p>\n<ul>\n<li>Day 2: Factual update on what happened and what's being done</li>\n<li>Day 4: Evidence of resolution (if resolved) or progress update</li>\n<li>Day 7: Return to normal content — crisis mentioned only if asked</li>\n</ul>\n<hr>\n<h3>Phase 3: Recovery Content (Weeks 2-4)</h3>\n<ul>\n<li>Customer stories that reinforce trust</li>\n<li>Transparent \"what we learned\" post (authentic, not PR-speak)</li>\n<li>Updated policy or product improvement announcement if applicable</li>\n<li>Return to full content calendar with crisis tone integrated, not erased</li>\n</ul>\n<hr>\n<h2>Crisis Tone Rules</h2>\n<ul>\n<li>First-person plural: \"We\" not \"the company\" or \"our team\"</li>\n<li>No passive voice: \"Mistakes were made\" = trust killer</li>\n<li>Specific action stated: \"We've updated our [policy/product/process]\"</li>\n<li>Timeline provided: \"By [date] we will [action]\"</li>\n<li>Never: \"We apologize if anyone was offended\" (conditional apology = not an apology)</li>\n</ul>\n<p>#content-sop #social-strategy #product-launch #crisis</p>\n"}