Not all messages are equal
A security alert and a marketing tip should not flow through the same pipe at the same speed. Tagging each notification with a priority lets the system treat them differently.
How priority shapes flow
- Critical messages use a separate high priority queue and bypass rate limits and digests.
- Normal messages follow standard preferences, limits, and batching.
- Low messages are good candidates for digests and can be dropped under pressure.
Queue separation
Using distinct queues per priority prevents a flood of low priority work from delaying urgent sends, a form of head of line protection.
Channel choice by urgency
Urgency also drives channel: a critical alert may use SMS or push for speed, while a low priority note waits for email or a digest.
Key idea
Priority tags route notifications into separate queues so urgent messages bypass limits and batching and reach users fast.