Writing an email reply worth sending
A generated draft gets you most of the way. The rest is knowing what the reply has to do, the habits that close the gap, and where a general-purpose generator stops and a real AI agent takes over.
Start with what the reply has to do
The fastest way to a draft that lands is to name the job before you worry about tone. A reply that answers a question reads nothing like one that buys time or says no, and the generator writes a sharper draft when it knows which it is.
Lead with the direct answer before anything else. If you don't have it yet, say so plainly rather than burying it in qualifiers.
Move it forward without nagging. Make the one thing you need from them impossible to miss, and give them an easy out on timing.
Say it clearly and early, give one honest reason, and keep it warm enough that the relationship outlasts the no.
Own the specific mistake without excuses, then move straight to what you'll do about it and by when.
Acknowledge the email now, set a clear expectation for when the real answer lands, and own the follow-up yourself.
Confirm or propose specific times and end on a clear next step, so it gets booked instead of bouncing back.
What a good email reply looks like
Same frustrated email, 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 email
“This is the second time I've asked and still nothing. I need an answer today or I'm escalating this.”
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 annoyed — asking twice and hearing nothing back is on us, not you. Here's where it actually stands: [the real status]. I'll have a firm answer to you by [specific time today], and I'll come to you rather than the other way around. Sorry it took a second email to get here. [your name]
Six habits that make an email reply land
A generated draft gets you about 80% of the way. These are the habits that close the gap, whoever you're replying to.
Acknowledge what they asked or how they feel in the first line before you explain anything. Someone who feels heard reads the rest differently.
If the answer is no, or not yet, say so plainly and early. A clear no beats a warm maybe that wastes everyone's week.
Be honest about what you can and can't do. Over-promising means under-delivering later, and that's what erodes trust.
End every reply knowing exactly what happens next and who does it. Vague replies generate more replies.
A reply to a client reads nothing like a note to a coworker. Set the right register and the draft earns its formality instead of faking it.
AI sounds confident even when it's wrong about your details. You're the editor on every reply, not the rubber stamp.
If most of your replies go to customers, the best ones are worth reusing. Turn them into help center articles customers can find on their own, or let an AI agent reply to the repeat questions for you.
A generator vs a real AI agent
A general-purpose generator drafts an email reply fast, but it can't see your product, reply on its own, or get the draft into your inbox without you pasting it across. For customer email specifically, here's where the two diverge.
| Capability | Generator | Selvo agent |
|---|---|---|
| Drafting a reply | ||
| Drafts a complete email reply | ||
| Knows your product and policies | Only what you paste in | Trained on your help center |
| Applies your voice | Re-describe it every time | Set once |
| Cites a source the customer can verify | ||
| Getting it to the customer | ||
| Copy-paste each reply into your inbox | Every single one | Never |
| Replies to customer email 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 reply | ||
| Price | Free / $20-mo per person | $0.10 per resolved chat |
