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 you can put all of it back. What reaches another person is a short list. Out of the box, every item on it waits for you.
Both halves of that need saying. At this stage the worry usually arrives as a picture: a machine holding a send button and a client list. A picture has no edges, so reassurance slides off it. The ways something can actually get out of your mailbox fit in a paragraph. Writing them down does most of the work.
The second half is where this asks for care. Out of the box is a starting position, and it’s built to be moved. You move it one kind of work at a time. At the top of any one of those settings, Point does that work without checking with you first. So the question worth your afternoon is which of them you’d ever raise, and what it costs if you’re wrong about one.
Writing and sending are two directions
Point writes in two directions. One of them points out of your firm.
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 shows up 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. All of it stays inside your firm. And you can turn any of it back round, because what 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. An invitation landing on other people’s calendars. The messages that make up a scheduling exchange. The confirmation that goes back when somebody picks a slot on a booking page. That’s the perimeter, and it’s four items long. Everything Point does with a mailbox runs many times longer, and the ratio between the two answers the question this chapter is named after.
The intuition runs the other way, which is why it’s worth saying slowly. Software that reads your mail and acts on what it read sounds like software that’s always sending something. Mostly it’s writing to your own account. The reading has consequences all over that account, and with four exceptions it stops at the edge of it.
A draft is not a send
The whole subject turns on a distinction your practice already makes every day, without ever naming it.
Writing a reply and releasing it are two separate acts. You do them a second apart, so they feel like one act. 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’d put your name on.
That first act is what Point can do while you’re elsewhere, and it’s 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. There’s nothing to explain to anybody. On the settings a new account arrives with, that’s 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. Review is most of the good part, and it’s working for you from the first day. 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. Either way the shape holds. The half that costs you your week is the half that stays inside your own walls.
The first setting most people raise
Scheduling is where nearly everyone moves first. It’s worth understanding before you meet it, because it’s the moment the perimeter starts being used in earnest.
Finding an hour that suits four people takes five messages, and every one of them is arrangement rather than judgment. Once you’ve raised that setting, Point runs that back-and-forth itself. Proposing, reading what comes back, proposing again. When a time holds, Point writes the event onto the calendar. Real messages, with your name at the top, arriving in other people’s mail before you’ve seen them. That’s exactly what you asked for when you moved the setting. It’s the clearest example in this series of one decision going on working while you’re somewhere else.
The reason it’s the usual first move is that the stakes are readable from outside. Would Thursday at three suit you? is a question about a time. No work committed, no figure quoted, no deadline conceded, no position taken on anybody’s affairs. When it’s wrong, the repair is one more message, and the repair costs nothing to make. That gives you the beginning of a way to sort the four-item list, because the other things on it work differently.
Weight, not volume
Sort what can leave by how much of you is in it, and the list separates into two kinds.
At one end sit the arrangements. Times, rooms, confirmations, the calendar. 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 a thing that has been said, on your letterhead, to somebody who’s entitled to rely on it.
The setting is held per kind of action for precisely this reason. One dial across everything would price the invitation and the tax opinion the same way, and you’d either lose the benefit or take the risk, depending on which way you flinched.
The reason to keep the commitment end on review sits in what the mailbox does not contain, rather than in the quality of the drafting. A reply can be flawless against the written record and still be wrong, because the record holds the correspondence and you hold 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’d never put in an email. A reply built from the correspondence alone is built from a partial document, and the missing parts are the ones 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. That’s what a firm’s own AI policy is for.
What comes back, and what does not
Every mail product you’ve used has already taught you this, quietly. It’s worth saying out loud before you raise anything.
Gmail’s undo send holds the message back for a moment before it leaves, and the longest cancellation period on offer is thirty seconds (Gmail Help, checked August 19, 2026). Outlook’s recall is narrower than the word suggests. Microsoft’s own page makes the condition plain. It reads “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 August 19, 2026). A firm and its clients are not one organization. For the mail that actually worries you, recall has never once applied.
So the asymmetry is something to work with, rather than a shortcoming anybody could design away. Undo in Point covers what Point did, and that’s a real and large territory. The filing, the label, the task, the draft, the thread Point tidied away while you were out. All of it sits in a place you control, and all of it is recoverable. Undo reaches exactly as far as your own boundary, which is the same edge the withdrawal in the last chapter ran into from the other side. A message on somebody else’s server sits past everything you administer.
That changes what a check is for, depending on which side of the send it sits. Before, a check prevents. After, a check tells you. Both are worth having, and they do different jobs. Treat them as one job and you end up with a lot of monitoring and no brakes.
Being told quickly is the whole thing
Which leaves the outbound question somewhere new, a long way from where the six questions started.
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 and sorted by weight, and the narrow part that matters is beyond recall for everyone. What remains is a timescale, rather than a setting.
A message that went out wrong and reached you within the hour is a phone call you make slightly sheepishly. Find the same message three weeks later and it’s a different conversation, with a different client, about a different subject. That subject is now whether you know what’s happening in your own firm. The message didn’t change. The gap did.
Supervising a standing decision means seeing what it produces. You raised scheduling in March for good reasons, and you find out in November whether those reasons still hold by reading what Point 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.