Writing a reply worth sending
A generated draft gets you most of the way. Here's what a reply that actually lands looks like, the habits that close the gap, and where a general-purpose generator stops and a real AI agent takes over.
What a good reply looks like
Same angry customer, two very different replies. The first is fast and forgettable. The second acknowledges the frustration, owns the problem, and gives one clear next step.
The message
“This is the second time I've been double-charged and nobody has gotten back to me. Refund both charges today or I'm cancelling.”
A rushed reply
“Sorry for the inconvenience. We're looking into it and will get back to you soon.”
A reply worth sending
Hi [name], you're right to be frustrated, and I'm sorry — being charged twice and then waiting on a reply is not the experience we want for you. I can see the duplicate charge from [date], and I've refunded it to your original card just now; it'll clear in 3–5 business days. I've also flagged the slow response internally so it doesn't happen again. Is there anything else I can put right while I have you? [your name]
Six habits that make a reply land
A generated draft gets you about 80% of the way. These are the habits that close the gap, drawn from how the best support teams write.
Acknowledge how they feel in the first line before you explain what you can do. A customer who feels heard reads the rest differently.
Be honest about what you can and can't do. Over-promising means under-delivering later, and that's what erodes trust.
If a customer can't find something, the product made it hard, not them. Apologize for the friction and point the way without blame.
Every question sits inside a workflow of follow-ups. Reply to the one they'll ask next, and you turn two tickets into one.
Close by inviting them to reply if anything's still unresolved, so they never feel shut down or rushed off the thread.
AI sounds confident even when it's wrong about your product. You're the editor on every reply, not the rubber stamp.
Once you've written a reply this good, it's worth reusing. Turn your best answers into help center articles customers can find on their own, or let an AI agent answer the repeat questions for you.
A generator vs a real AI agent
A general-purpose generator drafts a reply fast — but it can't see your product, answer on its own, or get the reply to the customer without you pasting it across. Here's where the two diverge.
| Capability | Generator | Selvo agent |
|---|---|---|
| Drafting a reply | ||
| Generates a written response | ||
| Knows your product and policies | Only what you paste in | Trained on your help center |
| Applies your brand voice | Re-describe it every time | Set once |
| Cites a source customers can verify | ||
| Getting it to the customer | ||
| Copy-paste each reply by hand | Every single one | Never |
| Answers customers 24/7 on its own | ||
| Lives inside your support inbox | ||
| Hands off to a human when unsure | ||
| Trust & cost | ||
| Guardrails against made-up answers | ||
| Audit log of every answer | ||
| Price | Free / $20-mo per person | $0.10 per resolved chat |
