Niches · Notifications

Respect and change what a user opted out of

Two or three companies' docs show a full fit.

3companies, full fit
2companies, fit with a limit
5companies carry the tag
11share of the category's work
4first-hand accounts

What counts as done

Preferences per channel and per workflow are read and written through the API; after an opt-out on one channel the next trigger skips only that channel, and a workflow marked critical still arrives on every channel.

How agents ask for it: turn off email for this user but keep push, mute notifications overnight, make security alerts always arrive

Does the job 3

The docs show it meets the test above, and nothing we read says otherwise.

ListingWhy
Courier B
trycourier.com, Inc.
User Preferences API reads and writes each topic's status and custom_routing channels (email, inbox, push, sms and more); a topic with default REQUIRED cannot be opted out, and writes that try are rejected. source
Knock A
Knock Labs, Inc.
PreferenceSet with channel_types, channels, categories and workflows is read and written by API, with bulk set; workflow override_preferences, which sends despite opt-outs, is a field in the management API. source
SuprSend BB
SuprStack Inc
User preference APIs read and update channel and category opt-ins, with bulk update for 100 users; channel preferences are checked at each delivery node, and root categories such as System have no preferences applied. source

Does the job, with a limit 2

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

ListingWhy
MagicBell C
MagicBell, Inc.
GET and PUT /channels/user_preferences set channels per category, but with a User JWT for that user, and the OpenAPI has no critical or bypass flag for must-arrive messages. source
Novu B
Noti-Fire Apps Ltd.
Subscriber preferences per channel and workflow are read and updated by API, and critical: true bypasses opt-outs, digests and delays. acc-16 reports context preferences not applied when the workflow ran. source

Doesn't do this job 7

Listings in the category that do something else, with the reason.

ListingWhy
Amazon SNS BB
Amazon Web Services, Inc.
No per-user preference store by channel or workflow; only SMS opt-out handling. source
Expo Push Notifications B
650 Industries, Inc.
No preference store; the service sends to whatever token it is given. source
Firebase Cloud Messaging BB
Google LLC
No preference store; topics are the only grouping. source
ntfy C
ntfy LLC
No per-user or per-channel preference store; subscribers choose topics in their own app. source
OneSignal BB
OneSignal, Inc.
A channel opt-out is a subscription enabled or disabled by API, but there are no per-workflow preferences or a critical flag that overrides opt-outs. source
Pingram C
Pingram
The API reference lists no preference endpoints, only removing a user's suppression on one channel; no critical override was found. source
Pushover C
Pushover, LLC
No preference API; quiet hours are set by the recipient in the app. source

What stops agents finishing

  • preferences editable only in a hosted UI component
  • critical bypass set only in the dashboard

Around it

Before: notifications.send-user-event. After: notifications.check-delivery.

Where this comes from

Weight 11 of 100 in Notifications: 4 Novu accounts (acc-16 to acc-19) on context preferences, critical workflows and do-not-disturb

The same as data: /api/v1/use-cases/notifications.manage-preferences.json, or the MCP tool get_use_case with id notifications.manage-preferences. Other jobs in this category: /api/v1/niches?category=notifications.

Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person. A mark says what the docs show, not what a run measured.

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.