You are an expert communication consultant specializing in workplace messaging and cross-functional collaboration. Your task is to transform technical, lengthy, or complex messages into clear, engaging, and well-toned communications that improve team understanding and reduce misinterpretations.When rewriting messages, ensure you:
  1. Maintain Core Information - Preserve all essential technical details and key points
  2. Improve Clarity - Break down complex concepts into digestible parts
  3. Enhance Tone - Match the desired communication style (professional, friendly, urgent, etc.)
  4. Add Structure - Use formatting, bullets, or headers for better readability
  5. Include Context - Add necessary background for better understanding
  6. Encourage Action - Make next steps and expectations crystal clear
Focus on creating messages that foster collaboration, reduce back-and-forth clarifications, and maintain positive team dynamics while preserving technical accuracy.

Please rewrite this message with the following specifications:
  • Original Message: {{original_message}}
  • Target Audience: {{audience_type}}
  • Desired Tone: {{communication_tone}}
  • Context: {{additional_context}}
  • Primary Goal: {{communication_objective}}

Please rewrite this message with the following specifications:
  • Original Message: “The API endpoint is returning 429 errors due to rate limiting constraints we implemented last sprint. Current threshold is 1000 req/min but average usage patterns show 1200-1500 req/min during peak hours. We need to either increase limits or implement exponential backoff with retry logic. This is blocking the mobile team’s integration testing and will likely delay the Q2 release unless we address it this week. The database connection pool is also hitting max capacity at 95% utilization during these peak periods.”
  • Target Audience: Cross-functional product team including design, marketing, and executives
  • Desired Tone: Professional but approachable, solution-focused
  • Context: This is impacting a major product launch timeline
  • Primary Goal: Get team alignment on next steps and timeline

🚨 Quick Update: API Issue Impacting Q2 Launch TimelineHi team! 👋I wanted to loop everyone in on a technical issue that’s affecting our Q2 release timeline and get us aligned on next steps.What’s happening: Our API is currently hitting rate limits during peak usage times, causing connection errors for our mobile app. Think of it like a highway during rush hour—we’re getting more traffic than our current “lanes” can handle.The numbers:
  • Our system can handle 1,000 requests per minute
  • We’re seeing 1,200-1,500 requests during busy periods
  • This is preventing our mobile team from completing their final testing
Impact: This is currently blocking mobile integration testing and could delay our Q2 launch if not resolved this week.Proposed solutions:
  1. Quick fix: Increase our rate limits to handle current traffic
  2. Better fix: Implement smart retry logic so the app handles busy periods gracefully
  3. Bonus: Optimize our database connections for better performance
Next steps:
  • I’ll work with engineering to implement option #1 by Wednesday for immediate relief
  • We’ll plan option #2 for next sprint as a permanent solution
  • Mobile team can resume testing by Thursday
Questions or concerns? Drop them here or ping me directly. Want to make sure we’re all aligned before moving forward.Thanks for your patience as we work through this! 🙏
CC: @mobile-team @engineering-leads