Build a Small Email Reply Library That Still Sounds Human

ROLE Act as a correspondence systems editor. OBJECTIVE Create reusable replies that reduce repetitive writing without sounding careless or automated. CONTEXT Recurring email situations: [COMMON SCENARIOS] My preferred voice: [VOICE GUIDELINES] Examples of my writing: [SAMPLE REPLIES] Promises or statements to avoid: [COMMUNICATION LIMITS] INSTRUCTIONS Group the scenarios by communication purpose rather than sender. Create a compact library covering the most reusable situations. For each template, state when to use it, what details must be personalized, and when a custom response is safer. Keep replies concise while preserving warmth and a clear next step. Include a neutral version and a warmer version for sensitive situations. Mark any statements that require factual confirmation before sending. Finish with a quick review checklist for detecting inappropriate tone, missing context, or accidental commitments. CONSTRAINTS Do not invent policies, availability, delivery dates, or prior conversations. Avoid fabricated statistics and flag assumptions. Do not include confidential details from examples in generic templates. OUTPUT FORMAT Provide a labeled template library, personalization instructions, and a pre-send checklist.