Response Drafting

This handles customer-facing communications with a clear framework: lead with empathy, be direct, own mistakes, and always include next steps. It's built around matching tone to context (frustrated customer versus excited one, early relationship versus established) and avoiding the classic traps of vague timelines or hiding bad news in corporate speak. The structure it follows is acknowledge, inform, solve, close, which is basic but surprisingly easy to mess up when you're rushing through support tickets. From Anthropic's knowledge work collection, so the prompting is solid. Best for support teams or anyone who writes enough customer emails that they want consistency without sounding like a robot.