# The Four Alerts Worth Interrupting You **From Chapter 13.2 of *The 4-Hour Side Hustle*.** Four alerts, the three you'll be tempted to add and shouldn't, and what to actually do when each one fires. The dashboard is what you go to. Alerts are what come to you — and they should be rare enough that a notification means something. **All four go to the single Telegram channel from Chapter 1.2.** Not email, not four different apps. One channel. --- ## The four ### 1. A payment failed Money didn't arrive, or a subscription renewal bounced. Stripe's Smart Retries handle most of these. A failure that persists past retries needs a human email within a day or two, while the customer still remembers wanting the thing. **When it fires:** nothing for 72 hours. Retries are working. Note it, deal with it in the Tuesday window. It only becomes yours if it survives the retries. --- ### 2. A high-severity automation error The test, from Chapter 3.2: **would a customer notice this before I did?** A payment webhook that failed to grant access. An order record that didn't write. Anything where someone paid and is currently sitting in the dark. Everything else — a clip that didn't post, a rate-limited platform, a report that didn't generate — logs quietly and waits for Sunday. **When it fires:** this is the one that genuinely interrupts. And the first move is not to fix the chain. **Fix the customer first.** Manually send them what they bought, with a short apology, within the hour if you're conscious. Then fix the chain, in whatever block comes next. A customer served late by a human doesn't churn. A customer left waiting while you debug does. --- ### 3. A support ticket older than 48 hours Your published support windows are Tuesday and Friday. A ticket that survives both has fallen through something, and 48 hours is where a reasonable wait becomes a person wondering whether anyone is there. One Make scenario checking ticket age daily. Simple, and it catches the thing your deflection stack is structurally blind to. **When it fires:** answer it now, briefly, even if the real answer waits for your window. *"Saw this, I'm on it, full answer Friday"* costs eleven seconds and completely resolves the silence. --- ### 4. A sale above a threshold you set This one looks like indulgence, so it's worth justifying properly. Set an alert for any sale above a number that means something to you — your rung-three offer, or an unusually large order. When it fires, your phone buzzes and tells you someone just paid you real money for something you built once and haven't touched in weeks. **Automation without felt progress burns people out.** That's the whole argument. The better this machine works, the less you experience it working: money arrives in an account you check monthly, from people you never speak to, produced by chains you approved in a queue. It is entirely possible to run a genuinely successful automated business and feel nothing about it — and people who feel nothing about their businesses stop maintaining them. The celebration alert is a deliberate reintroduction of the feedback manual work gave you for free. It isn't sentimentality. It's maintenance on the operator. **Setting the threshold:** high enough to stay meaningful. If it fires four times a week it's noise. If it fires once a month it's a good evening. **When it fires:** nothing. That's the point. Read it, feel it, put the phone down. --- ## The design test Three of the four resolve **in under a minute, from a phone.** Only one needs a laptop. That's the design goal, and it's the test for any alert you're considering: > **If an alert routinely requires you to stop what you're doing and open a computer, it isn't an alert — it's an unscheduled work session.** Automate it further, or demote it to the Sunday review. --- ## The three that aren't You will be tempted to add a fifth. These are the three that tempt hardest, and each one is a number you'd rather see on Sunday, delivered on a Tuesday, at a cost. ### ✗ The new-subscriber ping Pleasant. Fires several times a day once anything is working. Within three weeks you're swiping it away without looking — which means you're practising swiping that channel away without looking. Marcus deleted his after five weeks, for exactly this reason. **Where it belongs:** the Sunday review, as one number. ### ✗ The daily summary Feels responsible. Is actually a report you skim, and skimming is the habit you can't afford in a channel that also carries "a customer paid $340 and got nothing." A daily summary also creates a subtle pressure to act daily on a business designed to be touched weekly. **Where it belongs:** the Sunday review, which is the summary, done properly, once. ### ✗ The content-published notification A clip went out. An article posted. Nothing is wrong, nothing needs doing, and you knew it was scheduled because you scheduled it. This one is worth naming because it feels like monitoring. It isn't — a *successful* publish tells you nothing. A *failed* one is already covered by alert 2 if a customer would notice, and by the Automation Log if they wouldn't. **Where it belongs:** the Automation Log, silently. --- ## The rule that keeps them working **Audit your alerts quarterly, at the same time as the Chapter 11.3 automation audit. Any alert you've started ignoring gets deleted.** Not muted. Deleted. This matters more than it sounds. An alert you routinely dismiss without reading is actively training you to dismiss alerts without reading — and the channel you're being trained to ignore is the same one that will eventually tell you a customer paid and got nothing. **The cost of a tolerated useless alert isn't the interruption. It's the erosion of every other alert's meaning.** --- ## Checklist - [ ] Exactly four alerts built. The fifth resisted - [ ] All four routed to one Telegram channel, not scattered - [ ] Alert 2 filtered by the Chapter 3.2 test — would a customer notice before I did? - [ ] Everything below that severity logs to the Automation Log instead - [ ] Ticket-age scenario running daily - [ ] Celebration threshold set high enough to fire monthly, not weekly - [ ] Response for each of the four decided **now**, before one fires on a train - [ ] High-severity response starts with fixing the customer, not the chain - [ ] Quarterly alert audit in the calendar - [ ] Any alert you've started dismissing without reading: deleted, not muted