Notifications and Digests Print

  • email, spam, security, billing, guide, howto, solution, zillionkinghost
  • 0

Telling users what happened.

WHAT TO NOTIFY ABOUT

Things requiring action Things affecting them directly Things they asked to hear about

WHAT NOT TO NOTIFY ABOUT

Everything that occurs.

WHY

Excessive notification is disabled entirely, including the important ones.

WHAT CONTROLS TO PROVIDE

Per category, not a single switch.

WHY

An all-or-nothing choice results in nothing.

WHAT CHANNELS TO SUPPORT

In-product Email Whatever messaging platform your customers use

WHAT MATTERS LOCALLY

That messaging platforms are checked far more reliably than email.

WHAT DIGESTS PROVIDE

Several events in one message.

WHEN TO PREFER THEM

For anything frequent but not urgent.

WHAT TO BATCH

Activity in a workspace Summaries of progress

WHAT NEVER TO BATCH

Security alerts Payment failures Anything time-critical

WHAT EVERY NOTIFICATION SHOULD CONTAIN

What happened Who did it A link to the exact place How to stop receiving it

WHY THAT LAST ITEM

Its absence produces complaints and spam reports.

WHAT TO RESPECT

Time zones, for anything scheduled.

WHAT TO MEASURE

Which notifications are opened, and which are disabled.


Was this answer helpful?
Back

Are you happy with your experience? Leave us a review on Trustpilot.


Trustpilot