Message Prioritization
An optional layer on frequency capping that uses categories and ranked rules to decide which of several competing sends goes out, holding back lower-priority messages and retrying them later.
Entries on this page are generated by AI from vendor sources. How AI is used
Limits and rules on how often and when messages go out.
| Month | Changes |
|---|---|
| 2026-01 | 5 |
| 2026-02 | 3 |
| 2026-03 | 0 |
| 2026-04 | 3 |
| 2026-05 | 1 |
| 2026-06 | 2 |
| 2026-07 | 1 |
| 2026-08 | 6 |
| 2026-09 | 2 |
| 2026-10 | 2 |
Select a month to view the whole-record timeline. This clears timeline filters.
Platforms with at least one feature state classified in this capability (primary or secondary, minor updates included), in the site's fixed order. Select one to filter the timeline. Counts are not shown side by side: they reflect how finely each vendor documents, not how much it offers.
Filters apply to the timeline. The chart and platform totals describe the whole record. Selecting a chart month clears timeline filters to show that same whole-record scope.
Matches the Release Matrix evidence: latest state reached in the selected period, entries under review excluded, primary and secondary capabilities included.
No recorded changes match these filters.
Within each period: major updates as cards, then notable ones as rows; newest first in each group. Minor updates below.
An optional layer on frequency capping that uses categories and ranked rules to decide which of several competing sends goes out, holding back lower-priority messages and retrying them later.
AI Decisioning lets you choose the exact send time within each three-hour best-time-of-day window, applied per user's time zone to new recommendations.
Journey Builder can deduplicate recipient email addresses within a journey to stop redundant sends.
Text campaigns can now be delayed or skipped automatically to avoid sending during recipient quiet hours.
Sets a default quiet hours window per channel across the whole workspace, respected by every campaign and Canvas in each recipient's local time zone unless overridden.
Caps how many times a user can receive a specific periodic or event-triggered campaign within a defined sliding time window.
Decisioning frequency capping can now be scoped to individual placements, with per-placement or placement-specific modes.
Orchestrated campaigns can now define Quiet Hours windows that block sends during set time periods.
Orchestrated campaigns can now schedule outbound sends in controlled waves over time instead of all at once.
Campaign sends can now be paced in batches as small as 1% per minute instead of only hourly intervals.
Banner campaigns can re-admit users who dismissed a Banner after a configurable cooldown window instead of excluding them permanently.
New SMS campaigns now default to Quiet Hours pausing sends 8pm-9am local time, for both marketing and transactional messages.
Workspace-level messaging rate limits regulate outgoing send speed per workspace; the setting is rolling out gradually.
Journey arbitration ranking formulas can now use AI models to boost priority scores from profile and contextual data, in Limited Availability.
Guardrails can restrict AI Decisioning message delivery to specific time windows per channel.
Ranking formulas can now boost journey priority scores from profile and contextual factors, in Limited Availability.
Audience-based and event-based journeys gain more granular entry controls to limit how often members enter and prevent repeated sends.
Extends Frequency Capping to inbound In-App and On-Site Messaging, limiting repetitive in-session messages by trigger type and tag.
Quiet hours rule sets block sends across Email, SMS, Push, and WhatsApp during defined periods, now GA with queueing and rule preview.
Promotional texts are now automatically capped at three per 24 hours in regulated US states including Oregon, Florida, Oklahoma and Maryland.
A campaign or Canvas can set a distinct send-rate limit per channel instead of one limit shared across the whole send.
Orchestrated campaigns can now use rate control to pace deliveries against volume constraints.