Undo starts at the line in the record that says what happened. A thread Point filed comes back to your feed. A task Point made goes away again. A batch you cleared in one sentence returns as a batch. The reach stops at the edge of your own systems, so a message already sitting on somebody else’s server stays there.
- Custody decides the reach, not how serious the thing was. What’s still inside a system you own comes back. What’s reached somebody else’s stays with them.
- Three things can happen to something Point did. You put it back, you call it off before it runs, or you send a correction.
- A reversal adds a line. The action and the taking back of it both stand in the record, one under the other, each with its time.
- Cheap reversal is a strong argument for handing over your filing. It’s no argument at all for handing over your client replies.
What one click puts back
Everything Point files is safe while it’s away. Filing is a move, so the thread is sitting somewhere, waiting. You press undo on the row that recorded the action. Open the day’s record, find the filing you disagree with, and one click sends the thread back. Rebecca’s message is in your feed again under Other. Deal with it or leave it, as you like.
Where the button lives matters more than it sounds. A strip along the bottom of the screen is a reflex you have to catch. The actions most worth reversing happen while nobody’s watching. That’s the shape of handing work over: the sorting goes on while you’re with a client. So the button hangs off the record instead, and you can use it on Thursday afternoon about something that happened on Tuesday. The strip still appears while you’re there. Clear a task yourself and you get the same quiet offer to change your mind. The record is what lets that offer outlive the minute.
There’s a half of this people don’t expect. Point writes its decisions into your real mailbox. A thread filed in the feed has left your Gmail inbox too, and it’s waiting in all mail with nothing deleted. The reversal travels the same road back. Both places agree about where the thread lives, so your Sunday evening stays yours instead of going on reconciling two inboxes.
Scale comes back the way it went out. Ask in one sentence for three threads from the same sender to be cleared, and Point does three things. The reversal is three things as well, and they come back together in one place.
The three things that can happen to an action
Three categories. Most of the wrong instincts about undo come from being in one and reaching for another.
Put back. Everything Point did to your own inbox. A thread filed. A message ranked into a part of your week where you’d have put it somewhere else. A task built out of an ask in paragraph four. A task ticked off while the work was still open. A preference Point picked up about how you like things written, which sits in plain sentences you can edit or remove. These are moves inside a space you own. Each one has a reverse, and the reverse costs one click.
Called off. Things arranged and still waiting. A standing request to watch for something, set up in passing three weeks ago and firing on its own timing. A chase waiting on a quiet thread to stay quiet a day longer. Work holding at review that you’d rather stopped there, which is a decline and belongs with approving anything new before it acts. Calling something off is always cheaper than unwinding it, because the work is still ahead of you. This is the category owners forget to check. You set a watch once and then put it out of mind, which is what a watch is for. Every watch you’re running sits in the same list as your own tasks, showing what it looks for and what it has caught. One click ends it.
Out of reach. Anything somebody outside your firm has already seen. The reply that went. The proposed slot the other side has opened. The thing itself can sometimes still be moved, since a meeting shifts with one short message. Their having seen it stays, and that’s usually the part that mattered.
The line between the second of those and the third follows who holds the copy, not how serious the thing is. A task wrongly ticked could cost you a client, and it comes back instantly. A meeting invitation is a small courtesy, and it’s already out. Severity tells you how much to care. Custody tells you what you can do. Mix the two and you spend a morning scrolling the record for a button that was never going to be there.
When it is already on somebody else’s server
A sent email stays where it landed. Point doesn’t retrieve it, and no product does, and the why is worth saying out loud. The copy that matters belongs to your client now. It sits on their provider’s hardware, inside their account. Software that could reach in there and take it back could do the same to your mail on a day you hadn’t authorized.
You may be thinking of the undo send button in a mail client. That one is a short pause between your click and the message leaving, and the mail is still yours for the length of it. Real recall works between colleagues whose mailboxes sit inside the same organization’s mail system, where the copy is still on a server your own employer runs. Your client sits outside that system. So the feature people half remember covers a different message than the one they’re actually worried about.
This category has three instruments of its own, and they’re worth knowing before the afternoon you need them.
Knowing early is the first, and it’s what earns the record the tab it occupies. The activity log behind every action is where the news arrives.
The exact words are the second. A correction written with the text in front of you is a better letter than one written from memory of what Point probably said, and the difference shows.
A second message is the third, and this one you send rather than press. So the clock here is the world’s clock. A follow-up in the same hour reads as ordinary correspondence, the sort every firm sends. The same words on Monday read as a discovery, and the client’s question turns from what you wrote to how long it took you to notice.
A reversal adds a line rather than erasing one
Put something back and the record keeps both halves. The reversal lands underneath, with its own time, so the pair sits there afterwards: filed at 8:40, returned at 9:15. People expect an eraser and get a second line. The second line is the better object.
That’s what a record is for. The case for keeping one is the morning an insurer or a professional body wants an account of what happened in March. A record you could tidy with a button answers that with a version of events curated by whoever was quickest to undo. A record that keeps both lines answers with what happened. Every control in this collection is built so you can produce it later, and this is the place that would have leaked.
One more thing about a reversal, because this is where the effort goes astray. Undo works on the thread in front of you. Putting it back restores that thread, and the next one like it arrives the same way it did before. Changing the call in future is a separate move and a much cheaper one. Say it once in passing, and it’s kept as a plain preference you can read back and edit, holding wherever Point acts for you next. Undo fixes this morning. A sentence fixes the pattern. Thirty undos in the hope of one lesson is the most common wasted week in the whole product.
Where undo stops
The dial is its own move. Reversing an action fixes that action, and reversing forty fixes forty. Where a kind of work sits is something you move deliberately, in setting how much your inbox does on its own. That’s the instrument to reach for when the same reversal keeps coming back.
Undo stands behind an action. The instrument in front is the gate. Where a kind of work waits for your yes, the work is still sitting there, and there’s nothing to take back.
Undo answers for actions. Reading is a different thing, and no button anywhere reverses it. If the worry underneath is that a message was seen at all, the honest instrument is a written answer from the supplier. Put it to the company in as many words, using questions to ask any AI tool about your data.
Disconnecting is the far end of the same axis. Ending the grant on your mailbox stops what comes next, and everything already done stays exactly where it is. Where that switch lives, and why it’s the one control Point doesn’t hold, is where your email credentials are kept.
It belongs to one business. An action happens inside one of the businesses you operate, and its reversal happens there too. Both stay on that side of the line. The boundary itself is keeping one business isolated from another.
All of that measures the reach of one instrument, for somebody who wants to know exactly how far it goes before relying on it. The case for starting at all belongs to learning to trust AI with client work, and the benefits page lists what Point would be doing on your behalf in the first place.
Common questions
Can Point unsend an email?
No, and the reason is ownership rather than a missing feature. Once a message is delivered, the copy that matters sits in an account belonging to somebody else. Software that could reach in there and remove it is software you’d want nowhere near your own mail. The pause some mail clients put in front of sending is a different animal, and it works because the mail is still yours while it waits. For a message that’s genuinely gone, the useful moves are knowing quickly, having the exact text, and writing the second message the same hour.
How long do I have to undo something?
As long as you like, for anything still inside your own systems. The button hangs off the line in the record, so Thursday is still soon enough for Tuesday’s filing. That’s deliberate. Work you raised a setting for happens while you’re busy, and a strip that fades in ten seconds would miss exactly the actions undo exists to cover. The clock that does matter is the world’s rather than the product’s. A filing put back on Friday costs you nothing. A message travels in seconds.
Does undoing something remove it from the log?
No. The reversal goes in as its own line underneath the action, both with their times, so what you can produce later is the whole sequence rather than a tidied version of it. That reads like a small design detail, and it’s the reason the record is worth anything. A log you could edit by pressing undo would show you only what its owner hadn’t got round to erasing, which is no use to you on the day the question is asked in earnest.
If I undo a reply, does Point learn not to write that way?
Not from the undo, and teaching is the cheaper move anyway. Reversing puts the draft back and leaves your habits alone. That sounds like a shortcoming until you picture the alternative, where every click quietly rewrites how Point writes for you, by inference. So say in a sentence what should have been different. It’s kept as a plain preference, visible and editable, and it applies the next time Point writes for you. Undo for the instance, a sentence for the pattern.
Is undo enough of a reason to raise a setting?
For filing, yes. For a client reply, no, and the difference is this whole page. Hand over a kind of work where the wrong version comes back with one click, and your worst case costs you a moment. Hand over a kind of work that leaves for somebody else’s server, and your protection has to come from somewhere other than a button. Cheap reversal is one half of the argument for moving a setting up, and it’s never the entire argument.
The short version
Undo is one click from the line that recorded what Point did. The button lives on the record, so a reversal is still there on Thursday for something that happened on Tuesday. What stayed inside your own systems comes back. Threads you filed, tasks made or ticked, a ranking you’d have called differently, a preference you’d rather drop. All of it is written back to your real mailbox as well as to the feed. Work that’s still waiting gets called off instead, which is cheaper, and standing requests are the ones to go looking for. Work that has reached a server belonging to somebody else is out of reach for everyone, so the instrument there is a correction you send, and you send it quickly. Every line stays in the record. Point is where the button sits, one line down from the thing you’d rather it had left alone.