Write a pack of support reply templates for your most common tickets — fast to send, human to receive, with personalisation slots that matter.
Write support macros for our top ticket types: {{ticket_types}} (list them with what resolution usually looks like). Voice: {{voice}}.
Per macro: the reply — answer/solution FIRST sentence, steps numbered if multi-step, {personalisation} slots where it matters (their name, their specific detail — one genuine specific beats five merge fields), and the closing that fits (did-this-fix-it check vs nothing-needed). Include the 4 universal macros done right: 'we broke something' (own it, timeline, no weasel words), 'that's not a bug, but…' (validate, explain, workaround), 'feature request' (honest about likelihood — no fake 'passed to the team'), and 'you're right, refunding' (fast grace). Rule: every macro must sound like our best agent on a good day.
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...
Define when and how support tickets escalate: severity levels with examples, response targets, who g...