AI Replies to Customer Emails: 8 Best Practices
Between June and mid-November 2026, the AI in our customer service case study drafted 204,910 replies to customer emails for an e-bike brand selling in eight languages. Every draft that an agent edited before sending told us something about what a good AI reply looks like. These are the eight practices that came out of that work.
1. Answer the question in the first sentence
Customers read the first line and decide whether the email helped. If they asked for a link, the first sentence gives the link. If they asked what the box contains, the first sentence lists it. Background, apologies and context come after the answer, if at all. Drafts that opened with a summary of the customer's own message were the ones agents rewrote most often.
2. Answer this email, not the whole history
The AI reads the earlier thread as a structured summary so it does not contradict past promises. But the reply answers what the customer asked in this email. Old issues that were already answered are not repeated; open issues that the customer raises again are answered, not skipped.
3. Give the fix before the process
When a customer asks how to solve a problem, the reply leads with what they can do now: the troubleshooting steps, how to free a stuck part, how to keep using the product in the meantime, and the likely cause. Warranty checks, dealer visits and requests for photos come after. A reply that starts with "please contact your dealer" leaves the customer exactly where they were.
4. Give a judgement, even without a final answer
Some questions have no confirmed answer yet. The reply still says what the known facts point to and what the customer should do next. Refusing to give any view, or deferring entirely to "the official position", reads as indifference. The judgement must rest on real facts; it never invents a date, an amount or a status.
5. Keep promises and numbers consistent
An amount, a date or a status that the company has already stated must not change between emails without a reason. The facts given to the model include what was promised before and when, so a new reply builds on the old one. In a review of 400 edited drafts, 53 percent of edits removed promises the agent did not want to make, which is why promises with money attached always wait for a person.
6. Ask only for what is missing, and say why
Before asking for photos, an order number or an invoice, the AI checks what the customer has already sent. When something is genuinely missing, the reply asks for that one thing, says what it is for and how to send it. Asking a customer to resend a video they already sent is one of the fastest ways to lose their patience; we saw a model do exactly that after reading a very long case file.
7. Keep internal wording out
Status codes, team names, internal SKUs and process labels stay inside. The reply describes the result from the customer's side: the parcel has reached the carrier in your country, the replacement part is being packed, the refund has been issued to the original payment method. All of these reply rules live in one shared set of principles that every drafting step reads, so changing the tone of replies is a change in one place.
8. Reply in the thread
A reply belongs under the customer's latest email, with the original subject line, so the customer's mail program keeps the conversation together. Starting a new thread for an existing conversation makes the customer search for context. New threads are only for first contact, such as a reply to a web form.
Measure what agents keep
The test of these practices is how many drafts agents send without changes. In the last 30 days, 3,463 drafts went out unchanged after approval, 19,357 were edited first and 2,756 were sent by the AI on its own. Each recurring edit points to a missing fact or a rule to change in the material the AI receives. For the full drafting flow see AI email reply automation.