In this article
Beside the send control there is a bell. Tapping it sends the message without a sound — it arrives, it appears in the chat list, the unread count moves, and nobody's phone makes a noise.
It is a one-tap decision that people make once and never think about again, in either direction. The channels that use it constantly have made themselves ignorable; the ones that never use it are spending something they cannot see, and Step 072 has the number that shows them the bill.
What you will be able to do after this step
- check_circle Send silently, and say exactly what is suppressed.
- check_circle Decide whether a post is worth interrupting somebody for.
- check_circle Recognise the cost of over-notifying before subscribers leave.
- check_circle Use the same control considerately in ordinary conversations.
notifications_off What silent actually suppresses
A silent message removes the sound, the vibration and the screen waking. Everything else happens normally: the message arrives instantly, the chat moves up the list, the unread count increases, and the person sees it the next time they look at their phone.
Two things follow, and both get misunderstood in opposite directions.
It is not a lesser message. Nothing is hidden, nothing is delayed, and nobody is shown a smaller version. A silent post is exactly as visible to somebody opening the app as a loud one.
It is not secret either. The badge still moves, so a person who checks their phone knows something arrived. Silent is about the interruption, not about concealment — a distinction worth making if you were reaching for it to send something discreetly.
The control exists in every chat, not only in channels. That is the underused half of this step and the section near the end is about it.
Worth a sound, or not
One question, asked once per post: does a person need to know this before they next pick up their phone?
notifications_active Ring them
do_not_disturb Send it quietly
The honest default for a publishing channel is silent unless there is a reason, rather than loud unless you remember. Most channels have it the other way round and lose the difference slowly.
trending_down What over-notifying actually costs
Nobody unsubscribes because of one loud post. What happens is quieter and worse: they mute the channel.
From your side almost nothing changes. The subscriber count is the same, the views hold up for a while, and the channel looks healthy. What has changed is that those people now see your posts only when they open the app and scroll to you — which means the next time something genuinely matters, it does not reach them.
That is why the notification share from Step 072 is the number worth watching. It is the only figure that records this decision, it moves slowly, and it does not recover on its own. A channel that has trained its audience to mute it cannot untrain them by posting less; the setting stays where they put it.
The practical rule is to think of audible notifications as a budget rather than a feature. A few a week, spent on things that were worth it, keeps the channel in the category of "worth hearing from". Several a day spends the budget in a fortnight and buys nothing, because the posts that arrived loudly were not more urgent — they were simply louder.
forum The same control in ordinary conversations
Everything above is about channels, and the bell works identically in a one-to-one chat or a small group, where almost nobody uses it.
The obvious case is the hour. Sending a colleague something at eleven at night with the sound off means the message is waiting in the morning and their evening was not interrupted — which is most of what people are trying to achieve when they apologise for the time in the first line.
The second case is volume. Sending somebody four messages in a row makes four notifications; sending three of them silently and the last one normally makes one. That is a small kindness in a busy group and a considerable one for anybody who works in a room where notifications are already constant.
Two cautions, because the courtesy can go wrong. Do not send urgent things silently — if it needs an answer tonight, a quiet delivery is a way of blaming somebody later for not seeing it. And remember it is per-message, not a setting: the next thing you send is loud again unless you tap the bell again, which is the correct default and occasionally a surprise.
Where the hour is the only problem and the message can simply wait, scheduling from Step 073 is the better instrument. Silence delivers now without noise; scheduling delivers later at a sensible time. The distinction is worth keeping because using the wrong one produces a message that arrives at three in the morning and sits there out of sequence.
touch_app Try it now — five minutes
Four steps, and the second one is a decision you make once and then stop thinking about.
- Find the bell and use it once Beside the send control. Send yourself something silently and something normally, so you know the difference from the receiving side.
- Decide your channel's default For most publishing, silent unless there is a reason. Write the reason down — what would justify a sound — so the decision is not made in the moment every time.
- Write down today's notification share From Step 072's screen, with the date. This change shows up there over months and nowhere else.
- Use it tonight in a personal chat The next message you send after ten in the evening. It costs one tap and it is the most immediately appreciated thing in this step.
notification_important The notifications you are sending without posting
The bell governs your posts. A channel with any structure around it produces several other kinds of interruption, and they come out of the same budget without appearing on the same screen.
The copy in the linked group. As Step 075 explains, every channel post is copied into the discussion group automatically. For members of that group who have not muted it, that is a second notification for the same post — so anybody who both subscribes and joined the group is being told twice. Saying so in the group's description is the fix, since the remedy is theirs and most people never think of it.
Replies to comments. Somebody who comments gets notified when anybody replies to them, which is the mechanism that brings readers back and also the mechanism by which a lively thread becomes a source of interruptions for the twelve people in it. Nothing to configure; worth knowing when a post goes unexpectedly well.
Stories. A channel story puts your channel into the ring at the top of the chat list, which is a visual interruption rather than an audible one. It is cheaper than a notification and it is not free — the same fatigue applies, and Step 076's warning about filler is the same argument in a different currency.
Pinning with the notify option. Pinning a message in a group can notify every member, including people who muted it. That is the loudest thing available anywhere in this curriculum, and Step 021 is the argument for treating it as an emergency measure rather than as a way to highlight something.
The common point is worth stating: your audience does not experience these as separate systems. They experience a number of interruptions per week from you, and they respond by muting whichever one produced the last unnecessary sound. Adding a busy comment section to a channel that already posts loudly is how a carefully managed notification budget gets overspent by a feature nobody counted.
help Common questions at this stage
Does a silent message look different to the recipient?
No. It appears as an ordinary message with no marker of any kind, and there is no way for the recipient to tell how it was sent. The only difference happened at the moment of delivery, on their device, and it has already passed by the time they look.
Does it matter if the person has already muted me?
Not for them — a muted chat is silent regardless. It matters for everybody who has not muted you, which is the audience you are trying to keep. That is the whole argument: the people you would be disturbing are precisely the ones who still trust you not to.
Can I send silently from a bot or a scheduled post?
Yes to both — scheduling and silence are independent choices made on the same menu, and automated posting supports the same option. For a channel publishing on a rhythm, the combination of scheduled and silent is the normal configuration, with the bell reserved for the occasional post that genuinely warrants it.
Will silent posts get fewer views?
Fewer in the first hour, and usually similar within a day or two, because most reading happens when people next open the app rather than at the moment of arrival. Channels that measure this often discover the immediate spike was the only thing the sound bought — and it was paid for with the notification share, which does not come back.
What about mentions and replies in groups?
Those carry through mute settings, as Step 055 describes, which is exactly what makes muting a group safe for members. It also means a silent message that mentions somebody still reaches them — the exception is about who is addressed, not about how the message was sent. Worth knowing before assuming silence covers everything.
Is there a way to make every post silent by default?
Not as a channel setting — it is chosen per message, deliberately. In practice that is manageable because the choice becomes automatic once you have decided the policy, and the friction is useful: the moment of tapping the bell is the moment you ask whether this one is worth it. Automation that posts for you can carry the choice permanently, which is the closest thing to a default.
At a glance
- 1What silent does
No sound or vibration; the badge and order still update.
- 2Worth a ping?
Only interrupt people for posts that need them now.
- 3The cost
Readers mute noisy channels and miss the important posts.
Updated
