Unsubscribe and preferences
Making unsubscribing hard does not retain subscribers, it converts them into complainants, which is worse for both the user and the sending reputation. A good preference centre keeps people who would otherwise have left entirely.
Method
- Honour one-click unsubscribe immediately. No login, no confirmation page, no survey. Required by law in several jurisdictions and by good sense everywhere.
- Offer granularity as the alternative to leaving. Type and frequency options mean someone overwhelmed can reduce rather than stop (see notification-fatigue).
- Include a pause. A temporary stop retains people who are busy rather than uninterested, and it is often the option they actually want.
- Apply preferences everywhere, at once. A preference honoured in one system and ignored in another is the most common and most damaging failure (see consent-management).
- Never resubscribe silently. A new feature or a new list must not inherit an old consent, which is both a trust and a compliance failure.
- Confirm the change plainly. What will and will not be received now, so the user knows it worked.
- Keep transactional separate and say so. Explain that receipts and security notices continue, since users expect opting out to be total otherwise.
Boundaries
Preferences govern optional messages; legally required and security notices continue regardless and must be identified as such. Unsubscribe timing requirements are set by law rather than by product preference. A preference centre is only as good as the systems that read it (see notification-strategy).