Unsubscribe must be reachable from the notice

What it is

When someone no longer wants this stream, the exit must be on this notice: turn this type off, leave this campaign, stop this sender. Leaving the exit only in deep settings asks for a wayfinding task at the moment of peak annoyance. When it cannot be found, people take master-off or revoke permission. In-place unsubscribe keeps the channel and gives up only the current stream.

This is the escape hatch before the global threshold. It is not how category subscriptions should be designed (grain, default on or off, sync with settings), and not when OS permission should be requested.

Why it happens

The disable decision happens in the few seconds of being bothered. Working memory holds this card, not the settings IA. An exit that requires "open app → find settings → find notifications → find this type" outlasts the half-life of annoyance, so people take the system switch—which lives in Control Center and takes fewer steps. Unsubscribe on the notice scopes the object to the current type or sender. It satisfies "stop this stream," not "stop this app," and so it is a fuse for the channel.

The exit also has to be honest. "Manage" that lands on home, "off" that only mutes this one card, and a type that still arrives after unsubscribe will cause the next exit to skip straight to revoking permission.

Studying it

Compare "off only in settings" with "off this type from the notice." Watch the split between master-off / permission revoke and single-type unsubscribe.

Independent variables: exit on the notice, object = this type vs whole app, residual arrivals after unsubscribe. Dependent variables: single-type unsubscribe rate, master-off rate, complaints of post-unsubscribe arrivals, later re-grant of permission.

Lab "please turn off what you dislike" turns wayfinding into the task and overstates settings success. Harder: after a run of arrivals, give no prompt and see whether the first action lands on the notice menu, in-app settings, or OS permission. A high unsubscribe rate is not failure—high single-type off with low master-off means the fuse is working.

Where it stops holding

Safety, billing, and legally required delivery should not offer an unsubscribe as prominent as marketing, to prevent mis-off; the card must still lead to an explanation of that type rather than offering no exit. Legal unsubscribe links in email are not the same channel as system notices and cannot substitute. On child or managed devices the right may sit with an admin; the card should say "controlled by admin" rather than present a switch that does nothing.

Applying it

• Put "stop this type" on the notice menu or the foot of the card, with the same object name as settings, in one step.
• After unsubscribe, that type must stop immediately and show as off in settings; do not merely mute this one card.
• Do not disguise "stop this type" as "turn off all notifications."
• Verify by sending the same type until people say they are done, and watch where the first exit lands. If most go to OS permission and the card has no "stop this type," the fuse is not on site. Sample 72 hours after unsubscribe: that type should not arrive.

Related

• Within the group: H5.07.1 Crossing a frequency threshold shuts the whole channel · H5.07.2 Send timing must follow timezone and sleep
• Adjacent: H5.09 Category subscriptions · H4.05 Notification permission · H5.10 Push frequency and quiet hours
• Search terms: in-notice unsubscribe · stop this type · disable funnel