KoltrixWriting support emails people actually read
How to write support replies customers read to the end: answer first, short paragraphs, numbered steps, one question at a time, and a before-and-after rewrite.
On this page(7 sections)
Customers don't read support emails the way you write them. They skim on a phone, between meetings, looking for one thing: the answer. If it's in paragraph four, a good share of them will reply asking the question again.
The good news is that readable support email is a learnable format, not a talent. This post walks through the principles and then applies them to a real-feeling reply, before and after.
The principles
Answer first
Put the answer, or the status, in the first one or two sentences. Context, apologies and explanations come after.
- Weak opening: "Thanks so much for reaching out, and sorry for the trouble you've been having with exports. I've looked into this with our team..."
- Strong opening: "Your export is fixed. You can run it again from Settings > Data > Export."
If you can't give the answer yet, the status is the answer: "I don't have a fix yet, but I've reproduced the problem and our engineers are on it. I'll update you by Thursday."
Short paragraphs
Two to three sentences per paragraph, max. Long blocks look like work on a phone screen, and people skip them.
Numbered steps for anything sequential
If the customer has to do things in order, number them. Bullets are for unordered lists; numbers are for instructions.
One question per email, when you can
If you need information from the customer, ask for the most important thing first. Five questions at once often get one answered. If you truly need several details, number them so the customer can reply in kind.
Plain links
Link the exact page, with descriptive text: "the export guide" rather than "click here". Avoid three links when one will do.
Bold sparingly
Bold one or two things that the customer must not miss: a deadline, a setting name, a warning. If everything is bold, nothing is.
End with the next step
Close with what happens next and who does it. "Reply with the file and I'll check it today" beats "Let me know if you have any other questions."
The before
Here's a reply to a customer who asked why teammates aren't receiving invitation emails, and whether they can bulk-invite people.
Hi Sam,
Thank you so much for reaching out to us and I'm really sorry to hear that you've been having trouble getting your teammates into your workspace, I know how frustrating that can be especially when you're trying to get everyone set up quickly. I took a look at your account and it looks like the invitations were sent successfully from our side, so there are a few things that could be going on. Sometimes invitation emails end up in spam or a promotions tab, so it would be worth asking your teammates to check there. It's also possible that your company's email system is filtering messages from new senders, in which case your IT team might need to allow our sending domain. Another thing is that invitations expire after a period of time so if they were sent a while ago they might need to be resent, which you can do from the members page. Regarding your question about bulk invites, yes that is possible, you can go to the members page and click invite and then paste in a list of emails separated by commas, and they will all be sent at once. Let me know if any of this helps or if you have any other questions!
Best, Alex
Everything in it is correct and kind. It's also one paragraph, the bulk-invite answer is buried at the end, and Sam has to dig to find out what to do.
The after
Hi Sam,
The invitations went out successfully from our side, so they're likely being caught on the receiving end. Here's what to check, in order:
- Spam or promotions folders. Ask your teammates to search for "invitation" there.
- Expired invites. Invites expire after a while. You can resend them from Members > Pending.
- Company email filters. If nobody at your company received one, your IT team may need to allow our sending domain. I can send them the details if that helps.
And yes, you can bulk-invite: on the Members page, click Invite and paste a list of addresses separated by commas.
If your teammates still don't see anything after a resend, reply with one of their email addresses and I'll trace that specific message.
Alex
What changed, line by line
| Change | Why it helps |
|---|---|
| Opening states the finding | Sam knows immediately it's not a problem with their account |
| Apology and "I know how frustrating" removed | It read as filler; the fix shows care better |
| Three causes became numbered checks | Sam can work through them and report back by number |
| Setting names in bold | They're the things Sam will look for on screen |
| Bulk-invite answer got its own short paragraph | The second question isn't lost |
| Ending asks for one specific thing | Clear next step; no vague "let me know" |
| Word count dropped noticeably | Less to read, nothing important lost |
Notice what didn't change: the facts, the friendliness, and the offer to help further. Readable doesn't mean cold.
When longer is right
Some replies need length: a detailed explanation of a billing correction, an incident summary, a complex migration. The same principles still apply:
- Lead with a two-line summary.
- Use H3-style labels or bold lead-ins to break the email into sections.
- Put reference detail (logs, full timelines) at the bottom, clearly separated.
The customer who only reads the top should still get the point.
Habits that keep replies readable
- Re-read the customer's email before sending yours. Check that you answered every question they asked, in the order they care about.
- Read your reply on a phone. If it looks like a wall, break it up.
- Cut your first sentence. Often it's warm-up. Try deleting it and see if the email gets better.
- Watch for repeat questions. If customers keep replying "so what should I do?", your answers are buried.
Bottom line
- Put the answer or status in the first two sentences.
- Keep paragraphs short and number any steps.
- Ask for one thing at a time where you can, or number your questions.
- Bold only what the customer must not miss, and link exact pages with descriptive text.
- End with a specific next step, not a generic invitation to ask more.
Start with Koltrix
Your domain, one inbox, and an API that sends.
A team inbox where AI sorts and drafts (nothing is sent without your click), plus the transactional API and SMTP relay your product sends with. 7 days free, no card.
