Undo starts from the line in the record that says what happened. A thread Point filed away comes back to your feed, a task Point created goes away again, a batch cleared by one sentence returns as a batch. What undo cannot do is reach a message that has already landed on somebody else’s server.
- The reach is decided by custody rather than by seriousness. What is still inside a system you own comes back. What has gone to somebody else’s does not.
- Three things can happen to something Point did: put it back, call it off before it runs, or accept that the instrument is now a correction rather than a reversal.
- A reversal rubs nothing out. 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 and no argument whatsoever for handing over your client replies.
What one click puts back
The place you press it is 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 the feed again under Other, where you can deal with it or ignore it as you please, and nothing Point files away is lost while it is away, because filing is a move rather than a disposal.
Where the button lives matters more than it sounds. An undo that exists only in a strip along the bottom of the screen is a reflex you have to catch, and the actions most worth reversing are the ones nobody was watching when they happened. That is the whole shape of handing work over: the sorting goes on while you are with a client. An undo attached to the record rather than to the moment is one you can use on Thursday afternoon about something that happened on Tuesday. The strip still appears when you are there, and clearing a task yourself comes with the same quiet offer to change your mind. The record is what lets the offer outlive the minute.
Then there is the half people do not expect. Point writes its decisions into your real mailbox rather than into a private view of one, so a thread filed away in the feed has left the Gmail inbox too, waiting safely in all mail with nothing deleted. A reversal therefore has to travel the same road back, and does. The alternative would be the exact mess a connected client exists to prevent, which is two inboxes holding different opinions about where a thread lives and a Sunday evening spent reconciling them.
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, so the reversal is three things as well, offered together rather than as three separate hunts through the day.
The three things that can happen to an action
Three categories, and most of the wrong instincts about undo come from being in one and reaching for another.
Put back. Everything Point did to the state of your own inbox. A thread filed away. A message ranked into a part of your week where you would not have put it. A task built out of an ask in paragraph four. A task ticked off that was not really finished. 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, so each has a reverse, and the reverse costs one click.
Called off. Things arranged but not yet done. 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 would rather did not go at all, which is a decline rather than an undo and belongs with approving anything new before it acts. Nothing here needs reversing because nothing has happened, and calling something off is always cheaper than unwinding it. This is the category owners forget to check, since the nature of a standing request is that you stop thinking about it. Every watch you have running sits in the same list as your own tasks, showing what it looks for and what it has caught, and one click ends it.
Out of reach. Anything already seen by somebody outside your firm. The reply that went. The proposed slot the other side has opened. The artefact is sometimes still movable, since a meeting can be shifted with one short message, but the fact of having been seen is not movable at all, and that is usually the part that mattered.
Notice that the line between the second and third of those does not follow how serious the thing is. It follows who is holding the copy. A task wrongly marked done could cost you a client and comes back instantly. A meeting invitation is a small courtesy and is already out. Severity is a fair guide to how much you should care and a poor guide to what you can do, and mixing the two produces the person who scrolls the record looking for a button that was never going to be there.
When it is already on somebody else’s server
Point does not retrieve sent mail, no product does, and it is better to say why than to leave a gap where an explanation should be. The copy that matters is no longer yours. It is on hardware belonging to your client’s provider, inside their account, and any software that could reach in and remove it could do the same to your mail on a day you had not authorised.
The undo send button in a mail client is not a counter-example. That one works by not having sent yet: a short pause between your click and the message leaving, in which there is nothing to retrieve from anywhere. Where a real recall exists at all, it operates between colleagues whose mailboxes sit inside the same organisation’s mail system, which is the one arrangement where the copy is still on a server your own employer runs. A client is never on that system, which is why the feature people half remember never applies to the message they are actually worried about.
So for the category with no undo, you have three things instead, and it is worth knowing them before the afternoon you need them.
Knowing early is the first, and it is the reason the record is worth the tab it occupies rather than a compliance ornament. The activity log behind every action is where the news arrives.
The exact words are the second. A correction written from memory of what Point probably said is a worse letter than one written with the text in front of you, and the difference shows.
A second message is the third, and it is a thing you send rather than a thing you press. Which is why the clock on this category is not Point’s clock. A follow-up in the same hour reads as ordinary correspondence, the sort every firm sends. The identical words on Monday read as a discovery, and the client’s question stops being about the content and becomes about how long you did not know.
A reversal adds a line rather than erasing one
Putting something back does not remove it from the record. The reversal is added underneath, with its own time, so the pair sits there afterwards: filed at eight forty, returned at nine fifteen. People expect a rubber and get a second entry, and the second entry is the better object.
The reason is what a record is for. One you could tidy with a button is not evidence of anything, and the case for keeping one at all is the morning an insurer or a professional body wants an account of what happened in March. If reversals quietly disappeared, the answer would be a version of events curated by whoever was quickest to undo, which is no answer. Every control in this collection is built so that you can produce it later, and a reversible record would be the one place the whole arrangement leaked.
Then be exact about what a reversal is not, because this is where the effort goes astray. Undo is not an instruction. Putting a thread back restores that thread and says nothing at all about the next one like it. If you want the same call made differently in future, that is a separate and much cheaper move: one sentence said in passing, 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. Doing the first thirty times in the hope of achieving the second is the most common wasted week in the whole product.
Where undo stops
It is not a setting. Reversing an action changes nothing about what happens next, and reversing forty does not either. The position a kind of work sits at is something you move deliberately, in setting how much your inbox does on its own, and that is the instrument to reach for when the same reversal keeps recurring.
It does not run ahead of anything. Undo is the instrument behind an action. The one in front is the gate, and where a kind of work waits for your yes there is nothing to take back, because nothing has gone.
It does not un-read. Undo answers for actions, and reading is not an action with a reverse. If the worry underneath is that a message was seen at all rather than that something was done with it, no button anywhere addresses that, and 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.
It is not what disconnecting does. Ending the grant on your mailbox stops what comes next and leaves everything already done sitting exactly where it is, which is the opposite end of the same axis. Where that switch lives, and why it is the one control not held by Point, is where your email credentials are kept.
It belongs to one business. An action happened inside one of the businesses you operate, so its reversal happens there too, and neither reaches across. The boundary itself is keeping one business isolated from another.
None of the above is a case for delegating anything. It describes 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 has been delivered, the copy that matters is sitting in an account belonging to somebody else, and software that could reach in there to remove it would be software you should want nowhere near your own mail. What exists instead is the pause some mail clients put in front of sending, which works precisely because nothing has left yet. For a message that has 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?
There is no window you have to catch, because the button hangs off the line in the record rather than off a strip that fades while you are looking elsewhere. That is deliberate: work you raised a setting for happens when you are busy, and an undo you can only use in the ten seconds afterwards would be useless for exactly the actions it exists to cover. The clock that does matter is the world’s rather than the product’s. A filing put back on Friday costs nothing. A message went in seconds.
Does undoing something remove it from the log?
No. The reversal is added 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 is the reason the record is worth anything: a log you could edit by pressing undo would tell you only what its owner had not 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. Reversing puts the thing back and grants no lesson, which sounds like a shortcoming until you consider the alternative, where every click quietly rewrites your assistant’s habits by inference. Teaching is a separate move and a cheaper one: say in a sentence what should have been different, and it is kept as a plain preference, visible and editable, applied 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, and for a client reply, no, and the difference is this whole page. Handing over a kind of work where the wrong version comes back with one click means your worst case costs you a moment. Handing over a kind of work that leaves for somebody else’s server means undo is not on the table, so whatever protection you have has to come from somewhere other than a button. Cheap reversal is one half of the argument for moving a setting up, never the entire argument.
The short version
Undo is one click from the line that recorded what Point did, and the record is where the button lives so that a reversal is still available on Thursday for something that happened on Tuesday. What comes back is what stayed inside your own systems: threads filed away, tasks made or ticked, a ranking you disagree with, a preference you would rather not keep, written back to your real mailbox as well as to the feed. What has not happened yet is called off instead, which is cheaper, and standing requests are the ones to go looking for. What has reached a server belonging to somebody else is out of reach for everyone, so the instrument there stops being a reversal and becomes a correction you send, and quickly. Nothing gets rubbed out along the way. Point is where the button sits, one line down from the thing you would rather it had not done.