Messaging is work too
Budgets and allow lists instead of bans: the LINE, Slack and WhatsApp problem.
Your clients are on LINE. Your team is on Slack. Your family is on WhatsApp, and so is the supplier who only ever replies at four. Ban chat and you miss the client. Allow it and you lose the afternoon.
A plain blocklist makes you pick one. That’s the mistake: “is this work?” and “is this too much?” are different questions, and chat needs both asked.
Why a chat ban doesn’t last
A ban works until the first message that matters. The client’s “quick question” sits unread for two hours, you find out at five, and the next morning the blocker stays off. Chat isn’t like a feed you scroll. Some of it is the job.
Allowing all of it fails the other way. A reply turns into a thread, the thread into a group, the group into a sticker war, and it’s been forty minutes. Nothing about the app changed. How long you stayed did.
Two questions, two answers
- Is this work? Some apps are, whatever you’re doing. Slack, for most teams, is where the work is discussed.
- Is this too much? Some apps are fine in small doses and a problem in large ones. LINE and WhatsApp, for most people, are both.
A good setup answers the first with a list and the second with a clock.
How SqwarkSelf splits them
The list. Chat is one of the five kinds of thing you can rule out, next to social, video, news and shopping. The built-in rules know the usual apps and their web versions. If your drift happens to be Slack, add it under Messaging in Settings, and it’s treated like the rest.
The clock. Tap Messaging in Settings and give it a budget: 5, 10, 15 or 20 minutes an hour. Inside the budget, chat is let through, and the popover says so. The second the budget runs out, the veil comes down on whichever chat window you’re in.
The hour is a rolling one, not the clock’s. Ten minutes an hour means ten minutes in any sixty, so you can’t get twenty by starting at 9:55. And time you spent in chat just before the watch started counts too.
For the one conversation that is the job
Budgets handle the everyday. For the times when one chat is the work, there are two ways through:
- This is work, on the card. Press it once and that app is let through for the rest of the watch. It’s logged, so the end of the day shows it.
- Always allowed. An app, a site, or words in a window title, added in Settings. It beats every rule, for every watch.
Being wrong costs one click, so there’s no reason to switch the whole thing off.
A setup that holds up
- Chat: blocked on a watch, with a 10-minute budget.
- Social: a house rule, so it’s blocked all day, watch or not.
- Slack: left as work. If it’s your drift, add it under Messaging.
- The one client you answer at once: on the always-allowed list.
What it won’t do
It won’t read your messages. It knows which app is in front and the window’s title, and in a browser the site and page. It never records what you type, and never reads the page itself. For Messages and mail, it doesn’t even keep the window titles. And it won’t follow you to your phone, which is where a lot of chat lives. That’s a Mac app’s limit, and worth knowing before you buy one.
