TL;DR
Concepts pages explain one idea at a time. This section does the opposite: each page takes a real business situation and walks it end to end — what triggers it, what gets sent and when, and what makes it stop.- Written for Marketing and Product first. No code is required to follow along.
- Every case names the exact settings to pick in the dashboard.
- Each ends with a troubleshooting accordion for the things that usually go wrong.
What a case contains
The channels row is rarely a matter of taste. A billing contact who never opens the product will never see a message in the in-app Notification Center; a shop whose customers are mostly on iPhone cannot rely on web push alone. Each case says which channel it picked, and what forced the choice.
The cases
Migration deadline
A bank retires a savings product. Every holder must act themselves before a fixed date. Five reminders, stopped the moment they do.
Abandoned checkout
A shopper fills a basket and closes the tab. Nobody clicks I give up, so the silence itself is the trigger — and the basket is read again before each message leaves.
Failed payment recovery
A subscription charge is declined. Four reminders chase that invoice and stop the moment it is paid — then start again, from the first message, at next month’s failure.
Product announcement
A SaaS announces a new plan to its whole base: Tuesday it rehearses, Thursday at 9 a.m. it ships — and twelve minutes in, someone spots the wrong price.