Almost nothing Point does leaves your building. Ranking, summarizing, filing, lifting a task out of a thread, writing a reply and holding it: all of that happens inside the account you own, and all of it can be put back. What reaches another person is a short list, and out of the box every item on it waits for you.
Both halves of that need saying, because the worry at this stage is not shaped like the thing it is about. What people picture is a machine holding a send button and a client list, and the picture has no edges, which is why no amount of reassurance touches it. The set of ways something can actually get out of your mailbox is small enough to write down in a paragraph, and writing it down is most of the work.
The second half is where this has to be careful. Out of the box is not forever and was never meant to be. The arrangement is built so that you move it, one kind of work at a time, and at the far end of any one of those settings Point does that work without checking with you first. So the question worth your afternoon is not whether it sends. It is which of these you would ever raise, and what it costs if you are wrong about one of them.
Writing and sending are two directions
Point writes in two directions, and only one of them points out.
Most of what happens is a write into your own account. The ranking that lifts a thread to the top of the morning. The summary sitting above it. The label that lands in Gmail so the judgment is legible in your ordinary mailbox as well as in Point. The archive, the snooze, the task with a date on it, the reply parked underneath a message. Every one of those changes something, none of them is visible to a single person outside your firm, and every one can be turned back round, because what was changed is still sitting in a place you administer.
Then the short list that leaves: a reply or a new message going out under your address, a calendar invitation landing in other people’s diaries, the messages that make up a scheduling exchange, and the confirmation that goes back when somebody picks a slot on a booking page. That is the perimeter, and it is four items long. Everything Point does with a mailbox is a list many times longer than that, and the ratio between the two is the plain answer to the question this chapter is named after.
The intuition runs the other way, which is why it is worth stating slowly. Software that reads your mail and acts on what it read sounds like software whose every action is an emission. Almost none of them are. The reading has consequences all over your own account and, with four exceptions, stops at the edge of it.
A draft is not a send
The distinction the whole subject turns on is one your practice makes every day without ever naming it.
Composing a reply and releasing it are two separate acts. They happen a second apart when you do them yourself, which is why they feel like one act, and everything expensive about email lives in the first. The empty box on a Tuesday with eleven of them waiting. Working out how to say the thing about the unpaid invoice without making it worse. Getting from what you mean to a version you would put your name on.
That first act is what Point can do while you are elsewhere, and it is the recoverable one. A draft that came out wrong costs you the twenty seconds of reading it and the movement that throws it away. Nobody was affected. Nothing has to be explained to anybody. On the settings a new account arrives with, that is where the work stops for anything addressed to a human being: the words are ready and going ahead is a separate decision, still yours.
Which is the thing to understand about review being the default. It is not the product with its good part switched off, waiting for you to be brave enough to turn it on. It is most of the good part. Whether the writing is any good to begin with is a different question and whether the judgment can be trusted takes that one on properly, but the shape holds either way: the half that costs you your week is the half that leaves no mark outside your own walls.
The first setting most people raise
Scheduling is where nearly everyone moves first, and it repays understanding before you meet it, because it is the moment the perimeter starts being used in earnest.
Finding an hour that suits four people is five messages, and not one of them is a judgment about anything. Point runs that back-and-forth itself once you have raised that setting: proposing, reading what comes back, proposing again, and writing the event into the diary when a time holds. Real messages, with your name at the top, arriving in other people’s mail without your having seen them first. That is not a gap in the design. It is exactly what you asked for when you moved the setting, and it is the clearest example in this series of a decision you made once going on working while you are not watching.
The reason it is the usual first move is that the stakes are readable from outside. Would Thursday at three suit you? commits to no work, quotes no figure, concedes no deadline and takes no position on anybody’s affairs. When it is wrong the repair is one more message, and the repair costs nothing to make. Which gives you the beginning of a way to sort that four-item list, because the other things on it are not like that at all.
Weight, not volume
Sort what can leave by how much of you is in it, and the list stops being one category.
At one end sit the arrangements. Times, rooms, confirmations, the diary. Wrong is inconvenient and the correction is free. At the other end sit the commitments: a figure confirmed, a date agreed, a position taken on a client’s treatment of something, an answer to a question the client will act on. Wrong there is not one more message. It is a thing that has been said, on your headed paper, to somebody who is entitled to rely on it.
The setting is held per kind of action for precisely this reason. Not as a nicety, but because a single dial across everything would force you to price the invitation and the tax opinion the same way, and you would either lose the benefit or take the risk, depending on which way you flinched.
And the reason to keep the commitment end on review is not the one you would expect. It is not that the drafting is unreliable. It is what the mailbox does not contain: a reply can be flawless against the written record and still wrong, because the written record is not the relationship. You know the client’s father died in March. You know the last time this supplier was chased it went badly. You know the thing you are not going to put in an email. A reply built from the correspondence alone is built from a partial document, and the parts it is missing are the parts you were never willing to type. In a practice, deciding who may commit the firm to what is a written policy rather than a feeling, which is what a firm’s own AI policy is for.
What comes back, and what does not
Every mail product you have used has already taught you this, quietly, and it is worth making explicit before you raise anything.
Gmail’s undo send is a pause before the message leaves rather than a way of fetching it home, and the longest cancellation period on offer is thirty seconds (Gmail Help, checked 19 August 2026). Outlook’s recall is narrower than the word suggests. Microsoft’s own page makes the condition plain: “if you and your recipients are all on Microsoft Exchange or Microsoft 365 and in the same organization, you can recall or replace an email message” (Microsoft Support, checked 19 August 2026). A firm and its clients are not one organisation. For the mail that actually worries you, recall has never once applied.
So the asymmetry is not a shortcoming anybody could design away. Undo in Point covers what Point did, which is a real and large territory: the filing, the label, the task, the draft, the thread it tidied away while you were out, all of it in a place you control and all of it recoverable. It reaches exactly as far as your own boundary and no further, which is the same edge the withdrawal in the last chapter ran into from the other side. A message on somebody else’s server is past everything you administer.
That changes what a check is for, depending on which side of the send it sits. Before, a check can prevent. After, a check can only tell you. Both are worth having and they are not substitutes, and confusing the two is how people end up with a lot of monitoring and no brakes.
Being told quickly is the whole thing
Which leaves the outbound question in a particular condition, and it is not the condition the six questions started in.
The first chapter sorted a lump of unease into things a supplier could be held to. Two of them have answers now. Reading is broad and revocable. Sending is narrow, sorted by weight, and the narrow part that matters is not revocable by anyone. What remains is not a setting. It is a timescale.
A message that went out wrong and reached you within the hour is a phone call you make slightly sheepishly. The same message found three weeks later is a different conversation, with a different client, about a different subject, which is now whether you know what is happening in your own firm. Nothing about the message changed. The gap did.
And a standing decision you cannot see the results of is not a decision you are supervising. You raised scheduling in March for good reasons, and the only way to find out whether those reasons still hold in November is to be able to read what it has been doing since. Which is the next question, and the one that makes every setting in this series worth having: what happened, in order, in language you can read without help, close enough to the event to still be worth something.