The reply you’re worried about is probably fine. Somebody wrote, the answer is yes, and you’re about to spend four minutes turning six words into a paragraph because six words looks abrupt sitting there on the screen. From the other end it reads as an answer. What actually reads as cold is narrower than length, and one clause repairs it while the reply stays short.
Coldness in a reply is a ratio. Your reader is comparing, without meaning to, what they spent against what you spent. Three things feed that: the work that went into the message they sent you, how much of your answer could have gone to anybody, and how long it sat there before those six words arrived. Bring any one of the three back into proportion and two lines read as attentive. Miss all three and the padding just makes it longer.
- Short is the norm. In the largest study of real replying behavior anyone has published, the single most common reply length is five words.
- Your reader notices whether one thing in your reply could only have been written to them. The word count passes them by.
- Speed is the part of your tone the reader can measure exactly, and the only part that survives the trip intact.
- The cheapest repair in professional email is one concrete noun lifted out of their message. It costs a clause and buys back everything the brevity spent.
This page is about the ordinary reply, the forty or fifty small answers a week that are easy in themselves. What happens to tone on the way across is taken apart in the polite reminder email, which treats courtesy as a question of imposition rather than of wording. If the short answer you owe is a refusal, that message has its own shape in how to say no in an email. If something went wrong, it’s how to apologize by email. And if the first message went quiet and you’re writing a second time, that’s the follow-up email that gets answered.
Short is what email already is
Start with what you’re actually being compared against. Most people picture a normal email as longer than it is, and the picture is what makes them anxious.
Farshad Kooti, Luca Maria Aiello, Mihajlo Grbovic, Kristina Lerman and Amin Mantrach reported a study to the 2015 World Wide Web Conference built on “more than 2 million users exchanging 16 billion emails over several months”. It’s still the largest published look at how people actually reply. Their finding on length: “the most likely reply length is only five words, with half of the replies being shorter than 43 words.” Thirty percent of replies run past a hundred words, which is where the mean of 153 comes from. The median reply is 43 words, and the modal reply is a sentence fragment.
Timing goes the same way. “More than 90% happen within a day of receiving the message, and the most likely reply time is just two minutes. Also, half of the replies are within 47 minutes of receiving the message.” And most exchanges end after one round: “more than 30% of threads have only one step, which means, it’s an email and a single reply to it.”
Read that with its limits attached, because they matter. This is Yahoo Mail, so it’s consumer webmail with personal correspondence mixed into the business, and it’s a decade old. Your own client mail runs longer and slower than the median in that corpus, and it should. What transfers is the shape. A five-word reply that arrives in ten minutes is the most ordinary thing that happens in email. The paragraph you were about to write to avoid looking curt is the unusual object.
So the anxiety is real and the diagnosis behind it is wrong. Something does make a short reply land badly. It isn’t the shortness.
Three ways a short reply goes wrong
The effort is visibly out of proportion. Somebody spent forty minutes on a message. It has structure, three questions, a paragraph explaining the awkward part. You answer the whole thing with “Sounds good.” The information may be complete, and the trade is still lopsided. Your reader can feel exactly how much of their forty minutes you were prepared to match. This is the one that damages relationships, and the one that asks for a real judgment from you rather than a rule.
Every line of it could have gone to anybody. “Thanks, will do” fits every thread in your sent folder. So does “Received, appreciate it.” A reply built entirely from interchangeable parts tells your reader you processed their message rather than read it. That’s a smaller insult than rudeness and a more corrosive one, because it’s about whether you were there at all. The repair is one specific noun, and it’s the whole trick of this piece.
It arrives late and it’s still tiny. Six words on Tuesday afternoon reads as efficient. The same six words on Friday, after four days of silence, sends a message about your priorities you never meant to send. The delay sets your reader up to expect something proportionate to the wait. The brevity then answers the question they’d started asking, which is whether this matters to you. Of the three, this one has the easiest fix: send it now.
Notice what the list leaves out. The pleasantries, the exclamation mark, their question restated back to them. Those are the things people add under pressure. The three above stay exactly where they are.
One noun out of their message
Here’s the mechanic, and it’s almost embarrassingly small. Lift one concrete detail out of their message and put it in your reply. One noun that only exists in this conversation.
Yes, Thursday works.
Yes, Thursday works. I will bring the Ellsworth numbers so we can settle that in the same hour.
A dozen words added, and the second version belongs to this conversation alone. That’s what your reader is checking for. It works the same with people you’re fond of and people you merely deal with. It asks you to have read the message, which you did, and to prove it in one clause, which takes six seconds.
The details that work are the ones you’d have to have read the message to know. A file name. Their project’s internal name. A date they mentioned in passing. The specific thing they were worried about. The person on their side who is actually waiting. The ones that fall flat are the ones anybody could supply: their company name, the day of the week, the fact that they have been busy.
Three more pairs, same move:
- “Got it, thanks.” becomes “Got the trial balance, and it opens fine. Nothing missing that I can see.”
- “Will do.” becomes “Will do, and it will be with you Thursday morning rather than tonight.”
- “No problem at all.” becomes “No problem. The layouts can sit until you are back, and I will move the print date myself.”
Each of those is still a short reply. Each one now carries something your reader has to have been in this conversation to receive. And each has picked up a second useful property: your reader knows what happens next, which is the thing they opened the message for.
That’s the whole of it. If you take one thing from this page, take the noun.
The clock is the honest part
Speed is the one element of tone that arrives undistorted. Everything else about your message gets read through whatever mood your reader is in. The gap between their message and yours is a number, and they can compute it exactly.
That cuts both ways, and the generous direction is the useful one. A fast short reply reads as attention at any length, because promptness is the one thing you have to actually do, and your reader knows it. So the two-line answer sent within the hour lands warmer than the careful paragraph sent on Thursday. And the instinct to save a message up until you can “do it properly” makes almost every reply worse than the version you’d have fired off on the spot.
One corollary is worth being honest about. Your shortest replies come on your worst weeks, which is exactly when you can least afford them. The same study found that as email load rises “users reply to a smaller fraction of their emails, from about 25% of all emails received in a day at low load to less than 5% of emails at high load (about 100 emails a day)”. Under pressure people write fewer replies, and shorter ones. The ones that get dropped are picked by accident rather than by importance. If your clients feel a difference in March, that’s what they’re feeling, and the wider version of that problem is worth its own read.
One practical note on the clock. When a reply is genuinely going to be slow, the two-line holding message is the reply. More on the wording of that below. And where the delay is structural rather than personal, what resolves it is a stated turnaround your clients can plan against, which is an email response time policy rather than better wording on any individual message.
The shape of a two-line reply
Almost every short reply worth sending has the same three parts, in this order. The whole thing runs under forty words.
The answer, first. Ahead of the greeting, ahead of the context, ahead of the run-up. The word your reader opened the message to find goes in the first line: yes, Thursday, six days, not yet, done. Make somebody read to the end to find it and the brevity costs them time instead of saving it.
The anchor. One detail from their message, as above. This is the part that makes it a reply to them rather than a receipt.
The next state. What happens now, and when. “Invite sent.” “With you Thursday morning.” “Nothing needed from you until then.” That last one is the most under-used sentence in professional email, because it’s the only kind that ends somebody’s obligation rather than moving it around.
Then stop. Leave the closing question out unless you want a reply. A question is an instruction to write back, and half the value of a short reply is that it ends the thread cleanly.
Two small things around the edges. Keep the greeting and the sign-off, or at least the name at one end. Four words of “Hi Grace” and “Sam” are the difference between a message and a system notification, particularly for anybody outside your own building. And reply on the thread rather than starting fresh, so their message stays quoted below yours and the details stay to hand.
Sixteen short replies, written out
Every one of these is under fifty words. Each has an answer in the first line, one detail that could only have been written to that person, and a plain statement of what happens next.
One. Confirming a time.
Hi Grace,
Thursday at 2 works. Invite sent.
I will bring the Ellsworth numbers so we can settle that in the same hour rather than trading emails about it afterwards.
Two. A time you have to turn down. The alternatives go in the same message, so the next mail can be a yes.
Hi Dan,
Thursday is out at my end. Any time Friday works, or Monday after 11.
If neither is good, this moves it to whatever is open and you do not need to write back: [link]
Three. Answering a question with a number. The condition attached to the number is what stops the second email.
Hi Priya,
About six days, and it can start the week of the 14th.
That is the two US entities only. Adding Canada puts another three on it, so tell me if that is still in.
Four. Acknowledging something they sent.
Hi Tom,
Trial balance is here and it opens fine. Nothing obviously missing.
I will come back Thursday if I have questions. Nothing needed from you until then.
Five. Confirming receipt before you’ve looked. Saying so outright is warmer than implying you’ve read it.
Hi Tom,
Got the file, not opened it yet. It is first on Thursday morning.
If anything in it is time-sensitive, say so today and I will look sooner.
Six. A status update that says the same as last week. The whole message exists so they can stop wondering.
Hi Rachel,
Still with the reviewer, and nothing has changed since Tuesday.
Nothing is needed from you. You will hear from me by Friday either way.
Seven. The holding reply. This is the reply in its own right.
Hi Marcus,
Read it, and I do not want to answer this one in two minutes between other things.
Thursday morning you will have a proper answer on the pricing question. If Thursday is too late, tell me and I will do it today instead.
Eight. Thanking somebody for a referral. The specific outcome is what makes it worth reading.
Hi Sofia,
Nadia wrote this morning and said you had sent her. Thank you.
It looks like a real fit rather than a polite one, which is rarer than it should be. I will tell you how it goes.
Nine. Replying to praise. Naming who did the work is the whole message.
Hi Grace,
Thank you, that is good to hear.
The turnaround on the second round was Dev’s doing rather than mine, and I will make sure he sees this.
Ten. Somebody has told you bad news. Skip the advice and the silver lining, and name one concrete thing you’ll absorb at your end.
Hi Ben,
Sorry to hear it. Take whatever time you need.
Nothing here is urgent. The layouts can sit, and I will move the print date myself so it is not one more thing on your list.
Eleven. Somebody has told you good news.
Hi Elise,
Congratulations. That is a better reason to move a deadline than most.
Everything at this end can shift two weeks. Tell me when you are back and I will rebuild the schedule around it.
Twelve. A long message you can only half answer. Answer the answerable part today rather than saving the whole thing up.
Hi Elena,
Three things in there and I can settle one now: the survey goes out on the 9th as planned.
The pricing question and the second market need a conversation rather than an email. Twenty minutes Thursday, or I write it up properly Friday. Your call.
Thirteen. A first message from somebody new to you. Short works here as long as it reads unmistakably as an answer.
Hi Nadia,
Thank you for writing, and yes, annual reporting is exactly what we do.
The next step is half an hour on the phone. Here is what is open: [link]. If nothing there works, send me a couple of times and I will make one of them work.
Fourteen. Passing it to the right person. The introduction goes in the same message, so the handover happens once.
Hi Chris,
This one is Dev’s rather than mine and I have put him on the thread.
Dev, Chris is asking about the November invoice and whether the retainer covered the extra day. You will have a better answer than I would.
Fifteen. A reply that’s genuinely late. Name the length of the delay in a clause, skip the explanation, and put the answer immediately underneath.
Hi Rachel,
Eight days, which is longer than this deserved. Short answer is yes, the March scope is fine as written.
The reporting change needs a bit more thought and it will be with you tomorrow morning.
Sixteen. Ending a thread on purpose.
Hi Dan,
That settles it at my end, so nothing further needed from either of us.
Thanks for turning it around as fast as you did. It made the Friday deadline a lot less interesting than it was going to be.
Read across the sixteen and three things hold every time. The answer is in the first line. Every one carries at least one detail that belongs to that person alone. And four of the sixteen say outright that nothing is needed in reply, which is the most generous thing a short message can do.
The words that land as cold
These are the standard acknowledgment vocabulary, and each one is doing less than the sender thinks.
“Noted.” The coldest word in business email, and it earns the title. It confirms that you read something, agrees to nothing, and closes the thread. People send it to be efficient and it arrives as displeasure. If you mean yes, write yes.
“Received.” and “Acknowledged.” Receipts rather than replies. Your mail server can send those. Say what arrived and what you’re going to do with it.
“Fine.” and “OK.” In speech, tone carries these entirely, and tone is the one thing that stays behind. On the page they’re a shrug, and your reader supplies whatever mood they’re already in. Why that happens, and the research on it, is in the polite reminder email.
“Will do.” on its own. It commits to the task and leaves the timing open, so your reader is left holding an open item. Three words more and it settles: “Will do, Thursday.”
“Sure.” Reads as reluctant agreement far more often in writing than out loud. “Yes” is the same length and lands as agreement.
“Per below.” “As discussed.” “See attached.” Each one hands your reader a search. If the answer is in the thread underneath, say the answer.
“Thanks.” as an entire message. Between two people who trade twenty a day, it’s fine and everybody knows what it is. From somebody a client is paying, arriving four days after they sent something over, it reads as the smallest possible acknowledgment of their effort, which is what it is.
“Let me know if you have any questions.” It appears at the bottom of every email ever written, so it carries nothing. If you have an actual open question, ask it. Otherwise end on a statement.
The bare forward. A forward with an empty top line leaves your reader working out why they got it, what you think about it, and what’s expected of them. One line above the fold answers all three.
Stripped of the greeting and the name. Fine between colleagues. Reliably cold to anybody outside, where the words on the page are all your reader has to go on.
The pattern across all of them is the one from earlier. Each of these could have been sent to anybody. That’s what your reader is registering.
The signature that apologizes for you
Phone replies are shorter and faster, and the difference is bigger than most people would guess. The same 16-billion-email study picked mobile messages out of the corpus by the signatures phones append by default, “Sent from my iPhone” among them. It found that “replies from phones have a median length of 20 words, and tablets have a median length of 27 words, while desktops have median of 60 words.” Phone replies also landed at a median of 28 minutes against 62 minutes from a desktop.
So the phone reply is a third of the length and arrives in half the time. On the ratio from the top of this piece, that trade is usually a good one. Speed is the part your reader can measure, and length is the part they leave alone.
The signature doing the explaining is the part worth reconsidering. The stock version is a bare line naming the device, and a great many people extend it into an apology: please excuse brevity, please excuse typos, sent on the move. That attaches a small disclaimer to every message you send from the phone, including the clean ones and the long ones. Over a year it says, several hundred times, that your messages come with a disclaimer. When the brevity genuinely needs explaining on a particular message, one true clause inside the message does it better: “on the road, so this is short.” That reads as a person. The automatic version reads as a setting.
The one case for keeping it is a real one. If your reader is a client you’ve only ever emailed and the reply is four words, a phone signature does supply a reason. Weigh that against the three hundred messages a year where it supplies an excuse to a reader who was happy with the message.
When two lines are the wrong instrument
Six cases that call for something other than two lines.
The message took them real effort and the answer is complicated. Some proportions are too big to buy back with a noun. Somebody who wrote you a considered page about a decision they’re struggling with is owed a real answer, or an honest holding reply with a date on it. The thing to avoid is the cheerful two-liner that answers the easiest of their three questions.
It’s bad news, criticism, or a mistake. A short message about something that went wrong reads as indifference to what it cost. Those have their own structure in how to apologize by email.
It’s a no. A refusal compressed into two lines often reads as a maybe. Your reader looks for the answer, finds half of it, and picks the reading they prefer. Refusals are short in a particular shape, which is in how to say no in an email.
You’re the second or third person to reply and the thread is still stuck. At that point it needs somebody to say what’s actually blocking it, or a phone call.
The shortness is avoidance. This is the honest one. Some two-line replies are short because the answer is easy. Some are short because the real answer would commit you to something you’re still weighing. The second kind reads exactly as what it is, and it buys you about a week.
They wrote to you as a person rather than a correspondent. Somebody who has just told you their father is ill, or that they’re leaving the firm, is having a conversation with you. Two lines are fine there, as long as they’re warm rather than efficient. And if you know them at all, the phone beats any wording on this page.
Worth saying the opposite too, since people get this backwards. The high-volume, low-stakes reply is the one thing email does better than any other channel, and answering it in two lines the same day is the entire job. Saving those up to do properly later is how forty of them come to be sitting in a mailbox on a Friday, each one now late as well as small.
What Point does with the small replies
Point replaces the client you read your mail in, on the Gmail or Microsoft 365 mailbox you already have. What it lifts here is the volume rather than the wording.
Most of what makes a short reply land badly is the clock, and the clock is a sorting problem. Point orders what arrives by what it’s waiting on rather than by when it turned up. Forty small answers stay in view while one long thread sits beside them. Anything still waiting on you comes back up the feed as it ages, which is the whole distance between a reply that’s short and one that’s short and four days old.
The wording is the other half. Say what you want in a line on the thread, “yes to Thursday, mention the Ellsworth numbers”, and a draft comes back phrased the way you phrase things. The conversation stays underneath it, and it’s usually one edit from being sent. Which habits of yours a draft has to reproduce before it passes as yours is replies in your voice.
What happens to that draft next is yours to set. The dial is per action type and has three positions: suggest only, prepare it and hold it for you, or handle it outright. Every action type arrives on the middle one, so a drafted reply waits with you until you move that particular kind of work up. The three settings, and what each looks like on a Tuesday, are on the autonomy dial. There’s an ordered record of everything Point did, and undo reads back from it. The one repair undo can’t make is an email already delivered to somebody else’s server. The wider list of what a mailbox gains is on the benefits page.
Common questions
Is a short email reply rude?
Shortness by itself reads as ordinary, and the data says so plainly. In a study of 16 billion emails, the most common reply length was five words and half of all replies came in under 43 words. A two-line answer is the everyday shape of email. What reads as rude is narrower: a reply that took a fraction of the effort the message took, a reply that could have been sent to anybody, or a short reply that arrived four days late. Fix the proportion and the length looks after itself.
What is a good short email reply example?
The shape is the same every time. Answer in the first line, one detail that could only have been written to this person in the second, and what happens next in the third. “Hi Grace. Thursday at 2 works, invite sent. I will bring the Ellsworth numbers so we can settle that in the same hour.” Under thirty words, and your reader has the answer, the proof you read their message, and the fact that nothing else is needed from them.
How do I make a short reply sound warm without adding fluff?
Lift one concrete noun out of their message and put it in yours. A file name, the date they mentioned, the person on their side who is waiting, the thing they said they were worried about. That single clause proves you read the message, which is the only thing warmth in email actually means, and it costs a dozen words at most. A pleasantry does something else: “hope you’re well” fits every message you will ever send, which is exactly why it registers as nothing.
Should I apologize for a short reply?
Almost never. “Sorry for the brief reply” tells your reader there is something wrong with the message they’re holding, which they’d taken as fine until you said so. If the brevity genuinely needs a reason, give the reason once, inside the message, as a clause: “on the road, so this is short.” Skip the standing version at the bottom of everything.
How quickly should I reply to be polite?
Sooner beats better on almost everything small. Most replies people send arrive fast. The most likely reply time in that same study was two minutes, and more than 90 percent landed inside a day, so a reader’s sense of normal sits well below where most people imagine it. A two-line answer within the hour reads as more attentive than a careful paragraph on Thursday. Speed is the one part of tone you have to actually deliver, and your reader can measure it exactly.
Is it OK to reply with just “Thanks” or “Noted”?
Between people who trade twenty messages a day, yes. Outside that, both are weaker than they feel. “Noted” confirms that you read something, agrees to nothing, and closes the thread, which is why it so often reads as displeasure. “Thanks” on its own, in answer to something that took the other person real work, is the smallest available acknowledgment of that work. Two or three more words fix both: what you’re thanking them for, or what you’re going to do next.
Do I still need a greeting and a sign-off on a two-line reply?
Keep at least one end of it. “Hi Grace” costs two words and turns a fragment into a message addressed to a person. That matters most with anybody outside your own team, where the words on the page are all your reader has to read your tone from. Inside a fast thread with a colleague, dropping both is ordinary. If you’re keeping one, the name at the bottom is worth more than the greeting at the top.
Should I write a longer reply if they wrote a long one?
Match the effort rather than the word count. A long message usually contains one real question and a lot of context supporting it. The right reply answers the question, names the specific thing that shows you read the rest, and says what happens to the parts you left. Where today’s answer is out of reach, say so, with a date. The failure mode is answering the easy part and silently dropping the two hard parts, which the sender will spot immediately.
The short version
Two lines is an ordinary reply. In the biggest study of real replying behavior we have, five words is the most common reply anybody sends, and half of all replies come in under 43. Whatever you’re worried about, the length is fine.
What actually goes wrong is a ratio. Their effort against yours, when somebody spent forty minutes and got a shrug. Specificity, when your reply is built from parts that fit any thread in your sent folder. And time, when six words show up on Friday after four days of silence. The first asks for a judgment. The third asks you to send it now. The second is the one with the trick attached: one concrete noun out of their message, one clause, and the reply becomes something that could only have been written to them.
So the shape is the answer in the first line, one detail from theirs in the second, and what happens next in the third. Cut “Noted”, cut “Per below”, cut the standing apology at the bottom of everything. Add “nothing needed from you until then” whenever it’s true, because that’s the only sentence that ends somebody’s obligation rather than moving it.
What you’re replying to changes the emphasis. An accounting practice answering a client mid-season is mostly confirming that a document arrived and naming the day it gets looked at, which is two lines and a date. A design studio replying about a round of layouts owes the page number more than it owes the pleasantry. A coaching practice is often replying to something personal, where the short version has to be warm rather than efficient, and the phone is frequently better than any of this. And a consultancy fielding a long stakeholder message is usually answering one question out of four, which works as long as it says so. The other trades this was built for sit somewhere among the four.