One client payment failed on Tuesday. By Wednesday morning six systems had written to you about it, in six different voices. Only one of them told you something you could act on: the two-line note from the client. Point brings that down to a single telling. The first move happens at the sending end.
- Ten alerts is rarely ten events. Tally what landed yesterday. The pile usually collapses into three or four things that really happened.
- Volume comes down at the sending end. That’s the only place it comes down. Everything you do inside your own mail arranges a stream that keeps arriving at the same rate.
- The senders of the notices you most want gone are exempt from the opt-out rule. Hunting for an unsubscribe link is the wrong hour to spend.
- Aim one standing request at the event rather than at the senders. Aimed at a sender, it hands you the same pile back with a chime on top.
Count them for a week before you change anything
The pile is real and the irritation is earned. Give it a week before you cut anything.
The morning you finally lose patience is the morning you want to start cutting. Annoyance is a poor guide to which notice was carrying the information. The loudest one is often the authoritative one. The bland ones you skim past are often pure repetition.
So spend a week measuring. Keep two columns. On the left, the thing that actually happened in the world. On the right, a mark for every message that announced it. Everything stays switched on that week.
Two numbers come out. The gap between them is the whole problem. A small business generates a handful of real events on an ordinary day. A client pays, or fails to pay. A document gets signed. A filing is accepted. A file syncs, or fails to. Against that, the mail arrives in double figures, because a single event travels.
Here’s how the six in that opening paragraph came to exist. Every firm’s version is the same shape with different names. The card processor declined the charge and mailed you, because that’s where the thing physically happened. The accounting system mailed you, because the processor told it and the invoice reopened. The client relationship tool mailed you, because the accounting system told it. Your bookkeeper’s software mailed you, because you’re listed on the account as a person who should know. The client’s own portal mailed you, because it mails on any status change. And the client emailed you, because they saw a message at their end and wanted to know what to do.
Six announcements. One event. Five of them echo the first. The sixth is the only one that needed a reply.
There’s a second pile that feels identical from the inside and has a different cause, so separate it now. One system writes to you about ten trivial things: every login, every uploaded file, every comment somebody left on a document. Same sense of being pestered, different cause underneath. That one is a single afternoon’s work in one place. It’s the easiest win of the week, so do it first and put it out of your mind.
Four kinds of machine mail, and one of them needs you
The pile looks uniform. It’s four different things wearing the same clothes. Treat them as one and you either drown or miss something.
The receipt. Confirms an action you took and already know about. Your return was submitted. The payment is scheduled. The invoice went out. You were the cause, so the message hands you something you already have. The record lives permanently inside the system that sent it, and you can look it up on the day you need it. This is usually the largest share of the pile, and the safest thing to stop.
The heartbeat. Backup completed. Sync successful. Nothing to report. A heartbeat carries its meaning in the gap. It becomes information on the day it stops arriving, which makes it the one kind of alert that does its job by going silent. Catching that silence means reading every one that comes, and most people stop by the second week. Read one and you learn what you already assumed. Skip one and the silence passes you by.
The echo. The same fact, announced again by a system that heard it from another system. Connected software means one event travels, and each hop is reasonable on its own. That’s why it takes a count to see. Echoes are the single biggest contributor to ten messages about one thing, and they show up the moment you tally.
The one that needs a decision. A card expired. A filing came back rejected. A deadline moved. A client did something in a portal, and that notice is the only word you’ll get about it. This is the entire reason you keep the stream running at all. It arrives from the same no-reply address, in the same template, with the same tone of mild administrative cheer as the other three.
Name which kind a message is and the treatment follows. The rest of this page is mostly bookkeeping. Receipts and echoes get stopped. Heartbeats get honestly reconsidered. The fourth kind gets protected, and protecting it is its own job.
The only place the volume actually goes down
Every system that mails you has a preferences page governing how much it mails you. That page is the only lever in this whole business that reduces the number of messages arriving. Everything else, Point included, arranges a stream flowing at the rate somebody else set. Arranging is worth a great deal. It’s also the reason to spend one hour at the sending end before you spend any at yours.
Do it in the order the four kinds suggest. Echoes first, because the count is high and you keep the fact either way. You lose the repetition and hold on to the news. Receipts second. Heartbeats and decisions last, and slowly, because those are the two you can get wrong expensively.
When several systems announce the same event, two questions settle which one you keep.
Which one knows first? Usually the system where the thing physically happened rather than the one that was told about it afterward. The processor knows before the ledger does.
Which one would you act from? The message that gives you enough to do something: the amount, the client, the reason, and ideally a way straight to the record.
When the same system answers both, keep it and stop the other five. When they differ, keep the one you’d act from and accept the delay. A notice that arrives ninety seconds earlier with nothing usable in it buys you an earlier interruption. You’ll open the useful one anyway.
Now the thing everybody goes looking for, and the reason it’s missing is worth knowing. On the alerts that bother you most, the unsubscribe link is absent, and that’s lawful. The US CAN-SPAM Act attaches its opt-out obligations to commercial messages. The Federal Trade Commission’s compliance guide is direct about a message carrying only transactional or relationship content: “it may not contain false or misleading routing information, but is otherwise exempt from most provisions of the CAN-SPAM Act” (checked September 6, 2026). The guide describes that content as, among other things, anything that “facilitates, completes, or confirms a commercial transaction that the recipient already has agreed to” (checked September 6, 2026). That covers almost every notice in the pile you’re trying to reduce. The mail you most want to stop is exactly the mail a sender is free to keep sending.
Those same vendors also send you marketing. That half does carry an unsubscribe link, and a deadline sits behind it: the same guide gives a sender 10 business days to act on an opt-out request (checked September 6, 2026). Worth an afternoon when you have the patience. The operational half is the one causing this problem, and its only route is the sending system’s own notification preferences, one system at a time. That part happens in their settings, under your own login, and it stays a manual job.
One honest note on heartbeats before you leave this section. If a heartbeat is genuinely guarding something, put it somewhere other than an inbox. The event you care about is a message that stays away, and mail is very bad at absence. So either stop the notice and accept that the watching was only ever on paper, or move the job to a service built to raise an alarm when a signal goes quiet. Where the thing you want to keep an eye on sits on a page rather than arriving as mail, watching things outside your inbox is the arrangement that fits. It runs on a clock rather than on an arrival.
Why a folder for the alerts makes it worse
Almost everybody tries this at some point: a rule that sweeps mail from no-reply addresses into a folder called Alerts. The inbox looks dramatically better within the hour. That’s what makes it so persuasive.
What you’ve built is a standing decision to skip a stream that carries, perhaps four times a year, something you needed the same day. The folder gets opened conscientiously for two weeks. Then the unread count becomes a number you scroll past on the way to something else. Then a rejected filing sits in there for eleven days, and you hear about it from the client.
The deeper trouble is that a folder is one bucket and the pile is four things. All four kinds go in and all four come out, side by side, an echo sitting level with the notice that needed a reply. The sorting problem simply moved somewhere with worse lighting. The buried email you never hear about is what that looks like from the far end.
The obvious follow-up is whether the rule could tell you about the important ones instead of merely filing them, which would fix all of this. A rule acts on the message, and that’s where its reach ends. The reasons are laid out properly under telling your inbox to notify you when something arrives.
What replaces the folder is the ordinary stream. The machine mail stays in it, and the stream carries an order.
What happens to the ones you cannot stop
Some of the pile survives every cut, and that’s fine. Those vendors decided long ago what they mail their customers, and that decision stays theirs. The question becomes where the survivors sit.
Your feed arrives sorted into three sections, now, later and other, with a count on each. Machine mail almost always lands in other, which is exactly where a receipt belongs. The whole section folds out of view with one click. The count stays visible, so you know it’s there. The section remembers your choice, so tomorrow it opens folded. The mail still arrives. Your eye just lands somewhere else first. How the ranking is arrived at is how email triage works.
Three things follow, and each one does a specific piece of this job.
People outrank machines when you say so. Star a client and their mail scores higher for you from then on. An ordinary two-line message from them sits at the top of later, marked important, clear of the section where the noise goes. On our failed payment, that puts the client’s question above the six system notices rather than somewhere in the middle of them. VIP mail that never gets buried is that one setting.
The copies get drawn together. When several emails, a task and a meeting are about the same matter, Point holds them as one concept. You get a single summary card, with every source listed underneath. That’s the literal version of ten into one. Six announcements of a failed payment read as one thing that happened, and the messages behind it sit a click away. One summary for an email thread, its files and tasks is where that lives.
Your mailbox stays in step. Point creates the same three labels in your Gmail when you connect the account. Every message Point triages carries its label there too. Open your mailbox directly and you get the same sorting rather than the raw pile. Filing an alert away files it in both places at once, and the message waits in All Mail like any other.
The arrivals stay the same. What the arrivals cost you changes, and for the share of the pile you can’t stop, that’s the whole of the available win.
One standing request aimed at the event
Now the part that actually collapses ten into one.
Stop reading senders. Describe the event.
The mistake is easy to make and easy to see once it’s named. Tell me when Brightside Billing writes is a request pointed at an announcer. It fires six times if Brightside sends six messages. It stays quiet on the day the news arrives from the processor instead. You’ve rebuilt the pile with a chime attached. Tell me if a client payment fails is pointed at the event. It fires once, whichever of the six systems happened to say it first, and the other five copies stay in the section where they belong.
Machine mail turns out to be good raw material for this, which is the pleasant surprise. Alert mail comes from a system that knows exactly what happened, so it says so plainly in the first line, in a way a person writing at speed often manages less well. What defeats a keyword rule here is six vendors using six different templates and six different subject lines for one fact. A description of the fact holds up across all six. Phrasing one so that it catches what you meant has a page of its own, telling your inbox to notify you when something arrives, and all of it applies here unchanged.
Two rules keep the pile from coming back.
One request per event, not one per system. If you find yourself writing the sixth, the pile has moved rather than shrunk. The sixth is the one still running next year for a vendor you left.
Only for events you would leave a meeting for. Everything else stays in the stream and gets ranked, which is cheap and quiet. Why a short list of standing requests beats a long one is worked out next door.
If the event you’re catching always starts the same job, the request can line that job up as well as tell you. A Friday evening notice becomes something already prepared on Monday. Your settings for that kind of work govern what the prepared work does next, rather than the request itself. Both halves are in when an email watch lines up the next piece of work.
Two weeks in, check the request’s own record for what it’s been catching. If all six copies fired it, the description is still aimed at the shape of the mail. Aim it at the fact instead, and one sentence fixes it. Where that record lives, and how to end a request you’re done with, is seeing and stopping every watch you have running.
What gets to interrupt you
Cutting and ordering still leave one decision, and it’s the one people skip. That’s why the survivors feel loud even after the pile is half the size. Of the things you kept, which ones get to interrupt you, and which ones wait?
Almost everything you kept matters, or you’d have cut it. So use a different test. Does the news change what you do in the next hour? A failed payment on the morning of a closing changes the next hour. A vendor’s quarterly rate change is genuinely important and keeps until tomorrow, so it can be read at 8:30 with everything else. Important versus urgent, and why your inbox confuses them is that distinction at full length, and it’s the one most alert piles get backwards.
Everything in the second category has a natural destination. Your day arrives as one briefing. One line holds what needs you and what the schedule holds, counted rather than guessed at. That’s the batch. A notice that lands there has reached you and left your morning alone. The briefing is yours to keep or switch off, in one toggle.
For the first category, on a phone, the shape is a quiet device that lights up the moment a watch matches and takes you to the message in one tap. The alternative buzzes all day and gets silenced by Thursday. How loudly Point speaks in general is a set of separate switches: email copies, the briefing, sound, vibration and system banners. Choosing between quieting something and ending it is covered in seeing and stopping every watch you have running.
How you know it worked
An emptier inbox is the wrong measure. The folder trick empties an inbox too, and the folder trick is the version of this that fails.
Two measures, both countable.
Did the one that needed a decision reach you the day it landed? Over a quarter you can answer that from memory, and the answer is the only real score. A quiet quarter with a missed rejection in the middle of it is a worse quarter than a noisy one where everything landed.
Run the same tally you ran in week one. Same two columns, same week’s length. The count of events comes out roughly where it was, because your business stayed the same. The count of announcements is the number you were working on.
One failure mode arrives in silence. You cut a category in September, the category quietly held something you needed, and March brings the surprise. The defense is cheap, and it happens at the moment you cut: keep a dated line somewhere saying what you turned off and in which system. Six months later, that line is the only thing that remembers you switched off the payment-failure notice. Skip it and the way back is a reconstruction from scratch.
Two boundaries are worth naming plainly. If the noise comes from infrastructure that has to reach a human being within minutes at three in the morning, the answer is a paging service that rings a phone whether or not anyone is reading mail. And if the volume comes from one system’s settings, the fix is the twenty minutes of work at their end, and any arrangement at yours is second best.
The full range of what you can hand over sits on the benefits page. And if you’d rather watch a first standing request get written than read about writing one, day six of a first two weeks follows one person through it.
Common questions
How do I stop getting ten emails about the same thing?
Count first, then cut at the sending end. A week of tallying which real event each message announced usually shows three or four things happening and a dozen messages announcing them. Most of the extras are one system repeating what another already said. Turn the repetitions off in the systems that send them. Keep the one notice you’d actually act from, and let Point rank whatever survives, so the leftovers sit under other rather than at the top of your day.
Can I just filter all the notification emails into a folder?
You can, and the inbox looks better the same afternoon. What you’ve also made is a standing decision to skip a stream that occasionally carries a rejected filing or an expired card. Machine mail is four different things, and a folder treats all four alike. Leave the mail in the ordinary feed and let it be ranked, and the rare one that needs a decision stays within reach, rather than behind a count you stopped reading in week three.
Why is there no unsubscribe link on the alerts I most want to stop?
Because the law that requires one stops short of them. The Federal Trade Commission’s CAN-SPAM guide says a message carrying only transactional or relationship content “may not contain false or misleading routing information, but is otherwise exempt from most provisions of the CAN-SPAM Act” (checked September 6, 2026). It describes such content as including anything that “facilitates, completes, or confirms a commercial transaction that the recipient already has agreed to” (checked September 6, 2026). That’s most operational alert mail. The lever for those sits in the sending system’s own notification preferences, one system at a time.
Which of the six systems should I keep the alert from?
The one that knows first and gives you enough to act. When those are two different systems, keep the one you’d act from. An earlier message that says only that something happened leaves you opening the slower one anyway, for the what, the who and the how much. Whichever you keep, aim your standing request at the event rather than at that sender, so it still fires when the news comes from somewhere unexpected.
Will Point stop the alerts from arriving at all?
No, and the line is worth drawing exactly. Those messages come from other companies’ systems, and the settings of those systems are the only place to stop them. What changes at Point’s end is what the arrivals cost you. They sort into other rather than now. The section folds away with the count kept. Copies about one matter draw into a single card. And you’re told once about the event you asked about, rather than six times about six senders.
What about all the “completed successfully” notices I never read?
They become information on the day they stop, and that’s the day that slips past you, because catching it means having read all the ones before. So either switch them off and let the reading go, or move that job to something built to raise an alarm when a signal goes quiet. Of the three, leaving them to arrive unread is the one that only looks like monitoring.
The short version
Ten alerts is almost never ten events. Count for a week before you cut anything, and sort what you find into receipts, heartbeats, echoes and the rare notice that needs a decision. Volume falls at the sending end, one system’s preferences at a time. The notices you most want gone are the ones a sender is free to keep sending, so the unsubscribe link you’re hunting for is often absent by design. Let the rest stay in the ordinary feed, because a folder is a decision to stop reading a stream that occasionally matters. Let the survivors be ranked into other and folded away, star the people so they outrank the machines, and write exactly one standing request aimed at the event rather than at any of the senders, so that six announcements produce one telling. Then judge it on whether the message that needed a reply reached you the day it landed. That’s the only number in this that was ever really the point.