Rewrite real support replies in a better voice: warmer without being fake, clearer without being blunt — with the before/after patterns your team can copy.
Make over our support tone. Here are real replies we've sent: {{samples}}. Our intended voice: {{voice}}. For each sample: the diagnosis (robotic? apologetic-without-helping? blunt? corporate-speak?), the rewrite in our voice, and the pattern name (so the team learns the move, not just the fix — 'lead with the answer', 'own it specifically', 'no policy-quoting: explain the why'). Then the cheat sheet: the 8 phrase swaps that most improve our tone ('as per our policy' → the actual reason; 'unfortunately' → what we CAN do), the empathy-without-grovel formula, and the calibration rule: match the customer's energy, one notch calmer.
Fields like {{ this }} are placeholders — replace them with your own details, or let Aria ask you for them.
This prompt runs with Aria connected to your email, files, CRM and 40+ other services — and you can schedule it to run automatically.
Start Free WeekDraft an empathetic, on-brand reply to a customer ticket.
Turn a solved issue into a reusable help-centre article.
Respond calmly and constructively to an angry customer.
Build a set of reusable saved replies for a common topic — answer-first, personalisation slots where...
Take a customer complaint through five-whys to the process failure behind it: the analysis, the fix...
Write a pack of support reply templates for your most common tickets — fast to send, human to receiv...