A reply gets written and then nothing happens. The words are there, addressed, sitting under the thread. The message hasn’t gone anywhere. That gap is a setting. Drafting starts at review, so the work is finished and the sending stays with you until you move that setting for drafting yourself. This page is about what happens inside the gap, what it’s worth, and the way it quietly stops being worth anything.
- Sending has always been one keystroke and two decisions: what to say, and whether to say it. Writing the message yourself fuses them. A draft you didn’t write pulls them back apart.
- A default reads as a recommendation, because most people never move one. That’s true of this setting and true of every other setting you were handed.
- The pause is worth exactly what you put into it. A yes you give every time without looking leaves you with a memory of having checked, and nothing else.
- An undo window asks for your attention at a worse moment. For mail leaving your firm, recall mostly doesn’t exist at all.
- The cost is real. Unsent work forms a queue, and a queue is another inbox.
The two decisions inside one button
Sending an email is one keystroke and it has always been two calls. What to say, and whether to say it. Write the message yourself and the two run together with no visible seam. By the time you’ve picked the last word you’ve made both. The button at the end is a formality, attached to a decision you finished three sentences ago.
A drafted reply separates them. The first call happened while you were somewhere else. What’s on the screen is finished work you haven’t agreed with yet. The button that used to close a thought now opens one.
That’s the whole case for the default, and it’s worth putting in terms of what you get. Writing is the slow half of answering an email. Deciding is the fast half. A draft that waits hands you the slow half already done. The fast half stays exactly where it was. Divide the work that way and you’re strictly better off than you were before the software arrived.
The three positions this setting can take, and how to think about which kinds of work belong at which, are setting how much your inbox does on its own. The point here is narrower. For drafting in particular, the two halves of the job differ enormously in how easily they’re taken back. One keystroke used to do both, and that’s no reason to hand them over at the same speed.
What “by default” is doing in that sentence
The phrase carries more than it looks. It means two things at once. This is where the setting sits when you connect your mailbox. It’s also where it will still be sitting in a year, for most of the people reading this.
The best-known demonstration of the second half is about organ donation rather than software. In Do Defaults Save Lives?, published in Science on November 21, 2003, Eric Johnson and Daniel Goldstein reported an online experiment with 161 respondents. Each was asked whether they would be a donor, having been told to assume they had moved to a state where the default was one thing or the other. Consent came out at 42 percent when the default was not to be a donor. It came out at 82 percent when the default was to be one, and 79 percent in a third condition with no default at all. Only the opt-in version came out significantly below the no-default case, and the authors note that opt-in is “the current practice in the United States.”
The detail that makes this useful here is what it cost to disagree. “Respondents could at a mouse click change their choice, largely eliminating effort explanations.” Nobody was trapped by paperwork. The gap of forty points opened up between people who had the same information and the same one-click exit. The authors put one reason first among three: “decision-makers might believe that defaults are suggestions by the policy-maker, which imply a recommended action.”
That was a question about donor cards. What carries over here is the shape, and the shape is enough. Where a product ships a setting reads as advice, and it mostly stays where it shipped.
Two things follow, and they point in opposite directions.
The first is that a vendor is telling you something. Drafting arrives at review, one position below the top, and that’s a statement about which kind of work is worth a look before it leaves. The other way around would be a much easier product to demonstrate.
The second is that the default was chosen for the median mailbox. Yours is a particular mailbox. If almost everything you get drafted is an internal note about a meeting time, the starting position is more careful than your situation calls for, and you’re paying a small tax for somebody else’s risk. If the drafts go to clients about their money, it’s set correctly and the argument for moving it is weak. Both of those are facts about your desk rather than about the software. That’s why the setting is yours.
The pause has to change something
Every arrangement where a machine hands a person finished work for approval has the same failure built into it. People do a shallow check and come away with a memory of a thorough one.
That has been measured on people whose job was supervising automation. Kathleen Mosier, Linda Skitka, Susan Heers and Mark Burdick flew glass-cockpit pilots through scenarios seeded with automation events. Their paper, Automation bias: decision making and performance in high-tech cockpits, was published in The International Journal of Aviation Psychology in 1998. They reported that pilots “were also likely to erroneously ‘remember’ the presence of expected cues when describing their decision-making processes.” A recollection of having looked. The same study found what predicted actual double-checking: whether a pilot held an internalized sense of accountability for the outcome. What happens to a confirmation step when that’s missing is worked through properly in a task list that notices what you already finished, which is the same problem arriving on a different screen.
Cockpits sit a long way from inboxes, and that study is about flying. What carries over is the shape. Reviewing a plausible answer is a weaker act than producing one, and it leaves a trace that feels similar afterwards.
A drafted message is also harder to review than a row you tick, in three specific ways.
There’s no single fact to confirm. A row saying you sent the schedule on Tuesday at 11:12 is one claim, and you either remember it or you don’t. A reply is twenty sentences. Most of them are unremarkable, and the load-bearing part sits somewhere in the middle.
The trouble is in what got added. A draft usually goes wrong by carrying a date, a figure or an agreement that nobody put there. So the check runs against your own knowledge, rather than against anything on the screen.
It arrives in your register. That’s the feature working, and it’s also what disarms you. A message that reads like something you already decided to send goes down easily. A stranger’s phrasing at least keeps your attention switched on.
Which gives the diagnostic. How often you change a draft measures whether the writing is right, and that belongs with getting AI replies that sound like you wrote them. The question here is this one: if something had been wrong in the last ten drafts you approved, would you have seen it? Two things make that a yes, and trying harder is neither of them. The first is giving the reading a fixed shape instead of an amount of care, and that page sets out the shape. The second is the next section.
Not every draft is worth the same look
The pause is the same length on every message. Your attention varies, and it should. Treating every draft alike is exactly how a real review decays into a uniform glance. Sort the drafts into three piles, and do the sorting before you open the draft.
The ones where nothing in them can be expensive. Yes, Thursday works. Got it, thanks. The file came through. No figures, no commitments, no news. Check the reply is going where you think and send it. Reading these carefully spends the attention the other two piles need on the pile with nothing in it.
The ones carrying a specific you didn’t supply. A date, an amount, a document name, a delivery window, a name you haven’t used on this thread before. Any specific that was missing from the thread and missing from what you asked for arrived by inference, and inference is confident. This is the pile the fixed reading is for.
The ones where the honest end of the review is a rewrite. Somebody is unhappy. Money is moving. A deadline is being agreed to. A relationship is starting or ending. Here the draft is a first sentence, and what it did for you was clear the blank screen. Which messages those are, and why, is worked through from the writing side in getting AI replies that sound like you wrote them and, for messages you started yourself, in composing an email from scratch.
The categories are obvious. The discipline is sorting from the thread instead of from the draft. A reply written in your own register argues for the first pile whatever is actually in it, because it reads like something you already decided to send. Decide what kind of message this is while you’re still looking at what they wrote. Then the draft doesn’t get a vote.
Why an undo window is not a substitute
The obvious alternative design is to send straight away and let you take it back. Two mechanisms exist for that in the mail systems most small firms are on. What each one actually reaches is worth pinning down.
Gmail’s is a short hold. Google’s documentation describes choosing “a Send cancellation period of 5, 10, 20, or 30 seconds” (checked September 6, 2026), during which an undo option is offered. It works precisely because the message is still sitting with you.
Outlook’s message recall is a genuine recall, and its reach is narrow. Microsoft’s own page says you can recall a message “only if both you and the recipient have a Microsoft 365 work or school email account in the same organization,” and only where the recipient hasn’t opened it. It also states plainly that “personal email accounts (Gmail, Hotmail, Outlook.com) cannot use message recall” (checked September 6, 2026). This page is about replies leaving your firm for a client on their own domain. For those, recall is not on the table at all.
Set the two designs beside each other and the real difference is timing. An undo window asks you to notice the problem in the seconds after you decided you were finished. That’s the worst moment on offer. The message is closed in your head and you’re already reading the next one. A pause before the send asks while you’re still looking at the thread, with the decision still in your hands.
There’s a second asymmetry, and it runs the wrong way. The window shrinks as the message gets more important, because important messages are opened fastest. A note to a colleague might sit unread for an hour. A reply to a client who has been waiting since Tuesday is open in a minute.
An undo is worth having, and it’s worth having alongside the review rather than in place of it. What a reversal reaches and where it stops is undoing what Point did.
What the wait actually costs
Waving the cost away would make the case for the default weaker. So, honestly.
The writing already happened, usually before you sat down, so the pause adds nothing to how long a draft takes to exist. What it adds is one decision per message, and decisions are the expensive unit in a working day. Two of the costs are real.
Prepared work forms a queue. Drafts written while you were with a client have to wait somewhere. Put them in a list of pending approvals and you’ve acquired a second inbox with all the properties of the first. It fills, it carries a number, and emptying it starts to feel like the job. That’s a design question with a specific answer. A draft that waits under the conversation it belongs to costs you nothing extra, because you were going to open that conversation anyway. A screen you visit only to approve things is a queue.
Some replies are worth less later. An acknowledgment that a document arrived, a confirmation of a time, a one-line answer to a yes-or-no question. The value in those is mostly the speed. One that waits until 8:30 the next morning is worth measurably less than one that went at 9:40 the night before. That’s a real argument for raising the setting on some kinds of work. It’s also exactly why the setting is held per kind of work rather than once for the whole mailbox: setting how much your inbox does on its own is where that gets decided, one kind at a time.
Then a cost people expect and don’t meet. Most drafts belong in the first pile above, and the first pile costs a glance.
What waiting does not do for you
Five things sit outside this. Each one is a different control, or nothing at all.
It doesn’t make the draft right. A wrong date waits as patiently as a right one. The pause creates the opportunity to catch a wrong date, and the catching is yours. That’s why most of this page is about the reading rather than about the setting.
It doesn’t reach past the send. Once a message is delivered it’s sitting on somebody else’s server, and settings in your account stop at your account. Where the line falls is undoing what Point did.
It isn’t the record. What was prepared, what you agreed to and when, is a separate artifact with a separate job. It’s the only place the work is visible at the top of any setting. That’s the activity log behind every action.
It doesn’t govern how the draft is written. Preferences and habits are held apart from this, as plain sentences in a list you can read and change. The list changes the words. The setting changes whether they go. How things get in there is how Point learns your email habits, and reading it back and cutting what has stopped being true is seeing what an AI learned about you.
It doesn’t keep one business’s mail out of another’s. That’s its own boundary, between the businesses you operate, and it’s keeping one business isolated from another.
The blunt version: the wait buys you a place to stand. What you do while standing there is the whole of its value, and that part is yours to supply.
How Point handles a draft that is ready
Point is an email client, and the mailbox underneath it is the Gmail or Microsoft 365 account you already have. Nothing is migrated. Your address stays your address, and a reply that leaves from here leaves from your own account.
You open a conversation that needs an answer and the reply is already under it, written out in full. A gray auto-drafted mark says Point wrote it. Change a line and the mark comes off, because at that point the words are yours. The draft waits in the composer under the thread rather than in a separate approvals list, so it’s ready when you get there instead of piled on a screen you have to go and clear.
How much Point does unprompted is a level, held for each type of work on its own. It runs from suggest-only, through review, to fully handled. Drafting starts on review. The message is prepared and the sending stays with you until you raise that one setting yourself. Raising it is a decision about drafting alone, and it leaves filing, scheduling and everything else where you had them. The reasoning for where each kind of work belongs is in setting how much your inbox does on its own. The first time Point wants to do a kind of thing it has not done for you before is covered in approving anything new before it acts.
Sending hands the message to your own mailbox. The reply leaves from your address, threads under the original, and turns up in your real sent folder alongside everything else you have written. Everything Point has done is written down in plain language as it happens. A reversal reaches what is still yours to reverse, and a message already delivered elsewhere sits outside that.
What you’ve taught Point rides along with each draft, and you say it once. It’s held as ordinary sentences in one list you can read, edit and delete from. Starting a message with no thread underneath changes what there is to work from, and that’s composing an email from scratch. A reply to somebody who wrote to you in their own language raises a question of its own, in drafting emails in another language. The benefits page is the rest of what’s finished by the time you open the inbox. The case for the writing and the waiting happening inside the mail client, rather than in a browser tab alongside it, is set out in what an AI email client is.
Common questions
Will a reply go out before I have looked at it?
Drafting starts on review, and on review the words get prepared while the sending stays with you. That one setting decides it, rather than anything about the draft. At the top of the setting Point completes that kind of work without coming back to you, which is what the top of any setting means. So the honest answer depends on where you have drafting set today, and that’s a thing you can check in a moment rather than take on faith.
Why not just send it and let me undo it?
Because an undo asks for your attention at the worst moment available, in the seconds after you’ve decided you were finished and moved on. It’s also thinner than it sounds. Gmail’s cancellation window is a short hold measured in seconds. Outlook’s recall works only between accounts inside the same Microsoft 365 organization, and only before the recipient opens the message, which rules out almost every reply that leaves your firm. Having an undo is worth it. The review is the part that catches things.
How long should I actually spend on a draft?
Different amounts on different messages, decided from the thread before you open the draft. A confirmation with no figures and no commitments in it needs a look at the recipient and nothing else. A message containing a date, an amount or an agreement gets the real read, because anything specific in it that you didn’t supply arrived by inference. Where somebody is unhappy or money is moving, the honest outcome of the review is often that you write it yourself.
When is it reasonable to raise the setting for drafting?
When you already know the answer from watching, rather than as a way of finding out. Raising a setting leaves the judgment behind the drafts exactly where it was, and takes away the step where you would have caught a bad one. The clearest case for moving it is a kind of reply where speed is most of the value and the content can’t be expensive. The clearest case against is client mail about client money. Those can be different settings, because the level is held per kind of work.
Where do the drafts wait, and do they pile up?
Under the conversations they belong to, which is the design that keeps this from becoming a second inbox. A draft sitting beneath a thread you were going to open anyway costs you nothing to find. A separate screen full of pending approvals is a queue with a number on it, and clearing queues is the work you were hoping to hand over in the first place.
If I approve a draft and it turns out to be wrong, whose message is it?
Yours, in every sense that matters to a client and to your engagement terms. It went from your address, it threads under the original, and it’s in your sent folder. That’s uncomfortable, and it’s also the thing that makes the review work at all. The research on people supervising automated work found that the ones who felt the outcome was theirs were the ones who actually double-checked. The accountability is the condition the feature depends on.
Does a draft that waits mean it is unfinished?
No. What’s waiting is a complete message: addressed, in your register, with a sign-off. The setting decides whether it leaves, and it says nothing about how done it is. Those two are worth keeping straight, because they get confused. What Point has learned about how you write changes the quality of the draft. The level you have set changes whether it goes. Neither one moves the other.
The short version
Sending is one keystroke and two decisions, and writing the message yourself hides the join. A draft you didn’t write shows it. The default splits the two, hands you back the slow half finished, and leaves the fast half where it was. That’s the trade, and it’s a good one as long as you do something with the half you kept.
The half you kept is where the value actually sits, and spending nothing on it is easy and feels like something. Sort the drafts before you open them. Glance at the ones where nothing can be expensive. Read the ones carrying a specific you didn’t supply. Rewrite the ones where the fact that you sat down is part of the message. Keep an undo as an undo, because it asks at the wrong moment and, for mail leaving your firm, mostly doesn’t exist. And keep the drafts under their threads, because an approvals screen is a second inbox wearing a different name.
What ends up in which pile depends on the desk. An accounting practice mostly sorts on whether there’s a figure or a date in the message. A consultancy mostly sorts on how hard a sentence commits. If neither of those is your morning, there are other versions of it.