Team chat is noisy by default. Every message is a small request for attention, and most tools make sure you notice each one. That is what happens when a room never closes.
Most of the noise comes from a handful of habits, and each has a fix. Some are settings; most are agreements between people. Here are the ones that matter most, with how to do each in any tool and, briefly, how Tandly helps.
Set working hours, then respect them
Why it helps. If nobody knows when you work, everyone assumes you might be working now. Stated hours give colleagues a reason to wait and give you permission to be offline.
How to do it anywhere. Put your hours and timezone in your profile or status. Agree as a team that messages outside someone's hours are fine to send but not expected to be answered. Say it out loud once.
In Tandly. Each person has working hours, defaulting to Monday to Friday, 09:00 to 17:00 in their own timezone. Overnight ranges work for people on late shifts.
Let messages wait until they are back
Why it helps. Writing at 23:00 is fine. Delivering at 23:00 is the problem. A notification late in the evening says "this is urgent" even when you meant "whenever".
How to do it anywhere. Use scheduled messages if your tool has them. If it does not, keep a draft and send it in the morning. For genuinely urgent things, agree on one channel or one method that is allowed to interrupt.
In Tandly. When you message someone outside their working hours, you can choose to send it when they are back. It is held and delivered at the start of their day. This is on every plan.
Use threads for anything longer than one reply
Why it helps. A channel with five conversations interleaved is hard to follow and pings everyone for all of them. Threads keep each discussion in one place and only notify the people involved.
How to do it anywhere. Reply in a thread by default. Post the conclusion back to the channel if others need it.
In Tandly. Threads have an "also send to channel" option for the reply that everyone should see.
Mute by folder, not by channel
Why it helps. Muting channels one at a time is a losing game. New ones keep appearing. Grouping channels by what they are for, then setting notifications per group, is quicker and survives change.
How to do it anywhere. Organise your sidebar into sections: your team, projects, clients, social, announcements. Decide a notification level for each section rather than each channel.
In Tandly. The sidebar has nested folders, up to four levels, with unread counts rolled up. Each folder has a notification mode (all, mentions, or nothing), and muting a folder quiets everything inside it. Personal auto-filing rules put new channels that match a pattern, such as client-*, into the right folder automatically.
Catch up instead of scrolling everything
Why it helps. After a day off, opening every channel in turn is slow and mostly pointless. You read chatter to find the three things that mattered.
How to do it anywhere. Start with mentions and DMs. Then threads you are part of. Then channels in order of importance. Mark the rest as read without guilt.
In Tandly. After you have been away for eight hours (configurable), a quiet banner offers a catch-up page. It groups what you missed: mentions, DMs, channels, threads you follow, decisions and open questions. You can look at since your last visit, today, the last three days or the last week. It is a straightforward summary built from what you have and have not read, not an AI digest. Opening a conversation clears its section.
Hand over before a holiday
Why it helps. An out-of-office note stops people waiting, but it does not get anything done. A named stand-in means questions go somewhere useful, and you do not return to a pile of "any update?".
How to do it anywhere. Agree a stand-in before you leave. Put their name in your status with your return date. Mute notifications on your phone, or remove the app for the week. When you are back, ask the stand-in for a short summary rather than reading everything.
In Tandly. On Team and Business, you set an end date and a stand-in, with your manager or a peer suggested. Mentions and DMs are forwarded to the stand-in or answered with an auto-reply note, and your notifications are muted. When you return, you get a summary of what was handled.
Give events and incidents their own short-lived channel
Why it helps. An incident or an event produces a burst of messages that matter intensely for a week and then not at all. Keeping them separate spares everyone else, and closing the channel afterwards stops sidebar clutter.
How to do it anywhere. Create a dedicated channel with an obvious name and date. When it is over, post a short summary and archive it.
In Tandly. Temporary channels can archive themselves at the end of the week, in two weeks, at the end of the month or on a custom date. The creator gets a reminder 24 hours before, with options to extend a week, keep it, or archive now. Tandly Bot can post an optional wrap-up.
Replace the daily stand-up meeting with an async one
Why it helps. A daily call interrupts everyone at the same moment, which is rarely a good moment for anyone across timezones. Written updates can be read when convenient and kept for reference.
How to do it anywhere. Agree three short questions, for example: what did you finish, what are you doing next, is anything blocking you. Everyone posts answers in one thread per day. Someone reads the blockers and follows up.
In Tandly. On Team and Business, Tandly Bot asks each participant the questions at stand-up time in their own timezone, only on their working days. It then posts one summary card to the channel instead of a stream of separate replies.
Tame notifications on your phone
Why it helps. The phone is where noise does the most damage, because it follows you out of work. A few minutes of setup changes the whole experience.
How to do it anywhere.
- Turn on Do Not Disturb with a schedule that matches your working hours.
- Set notifications to mentions and DMs only, then add back the channels that truly need more.
- Turn off sounds and badges for anything that is not a mention.
- Use a status with an expiry when you are focusing, so it clears itself.
In Tandly. Web push notifications respect Do Not Disturb and your per-channel settings. Statuses can expire on their own.
Agree the rules as a team
These habits only work if everyone knows about them. A calm chat is less a feature than a shared agreement: we use threads, we do not expect replies after hours, we hand over when away. Pin it and point new people to it.
If your current tool makes some of this hard, the features overview shows what Tandly does and the pricing page shows which plan includes what. If your team lives in Google Workspace, team chat for Google Workspace covers sign-in and directory sync.
Questions people ask
Won't people feel ignored if replies wait until morning?
Only if nobody has said that waiting is normal. Once the team agrees that working hours are real, a reply the next morning reads as ordinary rather than rude.
Is muting a folder risky? What if I miss something?
Muting to "mentions" rather than "nothing" is the safe middle ground. Anything addressed to you still gets through. For the rest, a catch-up or a quick look at unread counts once or twice a day is usually enough.
Do async stand-ups actually get read?
They get read when someone owns the blockers. The rest of the update is reference material, and that is fine.
Which of these should we start with?
Threads and working hours. They cost nothing, work in any tool, and remove a surprising share of the noise on their own. Add the rest as the team gets used to it.