Scheduled Morning Email Triage
The Scene
Before my first coffee cools, I face 40+ unread emails accumulated overnight from clients, internal teams, and partners across time zones. Each requires a different tone—formal for external clients, casual for my core team. Manual drafting would consume my first productive hour.
Friction Point
Manually reading, prioritizing, and drafting responses to overnight emails takes 45+ minutes. Context from previous conversations gets lost, and important client communications risk a delayed or inconsistent response.
The Prompt
Draft a two-paragraph response for each of my unread emails received yesterday. Refer to previous email threads, Teams chats, and meeting notes for context. Use clear, professional, and engaging language avoiding the phrase: I hope you are well. For client communications (@basf.com), maintain a formal tone (e.g.,"Dear Mr. [Surname]", "Liebe Frau [Nachname], 'We appreciate your inquiry about...'), and for internal updates (Martin Schmidt, Frederik Jelden, Susana Alcalde), use a casual but respectful tone (e.g., 'Hey team, just a quick follow-up on...'). Prioritize addressing any action items, next steps, or key updates. Use this structure: 1) Greet and acknowledge, 2) Provide the response, and 3) Conclude with an offer of assistance or next steps. 4) Greeting (for client communication write "Best, Michael" or "Liebe Grüße, Michael" (if German) | for team communication "Cheers with Beers, Michael". Always answer in the language of the original mail. Avoid drafts to mail from general newsletters like e.g. LinkedIn or so. In the end, provide a summary table and give also a prioritization for me (use also emojis or icons), such that I don't forget any urgent mail replies (e.g. business impact, team communication etc.). Focus only on unread E-Mails, please.
Value Case
Why This Matters
- •Reduce email response drafting time by 70%
- •Maintain consistent professional tone across all communications
- •Never miss an urgent client request
- •Preserve context from previous threads automatically
💡 Consistent, context-aware responses that reflect relationship history