Document Type: Framework
Status: Active
Version: v1.0
Authority: MWMS HeadOffice
Parent: Ecommerce Brain Canon
Slug: ecommerce-brain-communication-frequency-framework
Purpose
Defines how MWMS determines optimal communication frequency across Email and SMS channels in order to maximise engagement persistence, protect deliverability health, and sustain long-term lifecycle revenue performance.
Communication frequency directly influences:
engagement durability
message responsiveness
unsubscribe rates
spam complaint risk
long-term list value
lifecycle conversion efficiency
Excessive communication reduces engagement quality.
Insufficient communication reduces lifecycle leverage.
Optimal frequency balances visibility with relevance.
Core Principle
More messages do not necessarily produce more revenue.
Communication effectiveness depends on:
relevance
timing
frequency tolerance
behavioural responsiveness
Customer attention is limited.
Communication must respect attention constraints.
Sustained engagement produces higher long-term revenue than short-term messaging intensity.
Engagement Sensitivity Model
Customers exhibit different tolerance levels for communication frequency.
common engagement patterns:
high engagement subscribers tolerate higher frequency
moderate engagement subscribers tolerate moderate frequency
low engagement subscribers require reduced frequency
frequency calibration improves engagement persistence.
engagement persistence supports lifecycle revenue stability.
Frequency Impact Risks
Over-communication risks
list fatigue
declining open rates
declining click rates
increased unsubscribe rates
increased spam complaints
declining engagement reduces future message effectiveness.
fatigued audiences reduce long-term monetisation potential.
Under-communication risks
reduced brand recall
reduced repeat purchase prompting
missed lifecycle intervention opportunities
lower customer lifetime value realisation
insufficient communication reduces lifecycle leverage.
reduced lifecycle leverage limits revenue expansion potential.
Channel Role Differences
Email and SMS serve different frequency roles.
Email supports:
structured content delivery
educational messaging
promotional sequencing
Email frequency tolerance generally higher than SMS.
SMS supports:
time-sensitive messaging
urgency reinforcement
concise prompts
SMS frequency tolerance generally lower than email.
excessive SMS frequency may increase opt-out rates.
balanced channel coordination improves engagement stability.
Behaviour-Based Frequency Adjustment
communication frequency should adapt to behavioural responsiveness.
example signals:
recent engagement activity
recent purchase behaviour
declining open behaviour
declining click behaviour
high engagement behaviour may justify increased messaging frequency.
low engagement behaviour may require frequency reduction.
behaviour-responsive frequency improves long-term list value.
Lifecycle Stage Frequency Variation
different lifecycle stages support different communication frequency structures.
example patterns:
new subscribers often tolerate higher onboarding frequency
repeat buyers tolerate regular engagement messaging
inactive customers require cautious reactivation pacing
frequency must align with lifecycle relevance.
misaligned frequency reduces engagement probability.
Relationship to Segmentation Framework
segmentation logic enables differentiated frequency calibration.
example:
high engagement segment → higher frequency tolerance
low engagement segment → reduced frequency tolerance
segment-informed frequency improves engagement durability.
engagement durability supports lifecycle monetisation stability.
Relationship to Behaviour-Based Automation Framework
automation triggers should consider communication recency.
trigger logic must prevent message clustering.
clustered communication increases fatigue risk.
frequency-aware automation improves message effectiveness.
Relationship to List Growth Asset Framework
list health influences long-term revenue capacity.
communication frequency influences list health.
healthy list supports consistent lifecycle revenue contribution.
over-messaging degrades asset value.
owned audience must be protected as long-term infrastructure.
Frequency Calibration Signals
key signals indicating frequency misalignment:
declining open rate trend
declining click rate trend
increasing unsubscribe rate
increasing spam complaint rate
declining engagement persistence
frequency adjustments should respond to signal deterioration.
signal responsiveness protects list value.
Drift Protection
system must prevent:
maximising short-term campaign volume at expense of long-term engagement
ignoring declining engagement signals
applying identical frequency across all segments
increasing messaging frequency without behavioural justification
prioritising message volume over message relevance
sustained engagement supports long-term revenue stability.
Architectural Intent
Ecommerce Brain Communication Frequency Framework ensures MWMS balances communication visibility with engagement durability.
sustained engagement improves lifecycle efficiency.
lifecycle efficiency improves realised customer lifetime value.
stable lifetime value improves growth predictability.
Future Expansion
adaptive frequency optimisation models
predictive engagement fatigue scoring
reinforcement learning send cadence models
cross-channel frequency coordination engines
dynamic engagement decay modelling
future models improve frequency precision.
Final Rule
Attention is limited.
MWMS protects engagement durability by aligning communication frequency with behavioural responsiveness.
Change Log
Version: v1.0
Date: 2026-04-12
Author: MWMS HeadOffice
Change:
Initial creation of framework defining lifecycle communication cadence logic protecting engagement persistence and long-term list value.
CHANGE IMPACT
Pages Created:
Ecommerce Brain Communication Frequency Framework
Pages Updated:
None
Pages Deprecated:
None
Registries Requiring Update:
MWMS Architecture Registry
MWMS Brain Registry
MWMS Lifecycle Map
MWMS Canon Hierarchy Map
Canon Version Update Required: No
Change Log Entry Required: Yes