Set email frequency by customer stage and purpose
Create a customer-stage communication calendar with explicit priorities, illustrative contact caps and outcome-based review rather than a universal send frequency.
Which message is useful at this stage?
A new customer waiting for setup, an active customer using the product and a dormant customer considering return need different communication. Start with the task each message helps complete. A calendar organized only by internal campaign deadlines can send several competing requests to the same person in a short period.
Google Analytics documents events as interaction measurements. If email frequency is reviewed using downstream actions, define and verify those events rather than relying on a generic engagement label. A delivered activation event remains distinct from customer satisfaction or a sale. [Set up events]
A communication calendar with explicit priorities
| Customer stage | Useful message | Priority and exclusion |
|---|---|---|
| Setup incomplete | Requested next-step guidance | Pause unrelated promotion while a blocking issue is unresolved |
| First value achieved | Relevant workflow education | Coordinate with onboarding sequence to avoid repetition |
| Active customer | A meaningful feature or task update | Send only when relevant to the customer’s use |
| Dormant customer | A bounded return invitation | Respect suppression and active support context |
| Open service issue | Status or resolution information | Do not bury the issue under conflicting promotional requests |
Separate message purposes operationally and verify applicable requirements with the organization’s actual policy. This calendar does not establish legal categories or permission to contact anyone. A message called “educational” can still serve a promotional purpose, so the label should not be used to bypass a preference restriction.
How should a contact cap work?
Illustrative policy: at most two promotional messages in a rolling seven-day period for an eligible contact, with a declared priority order when campaigns collide. The number is a teaching choice. It is not a deliverability benchmark, an optimal frequency or a statement about any platform’s capabilities.
- Count eligible messages across coordinated campaigns, not just within each sequence.
- Check the rolling window immediately before sending, not only when building the audience.
- Define which purposes the cap includes and document any approved exceptions.
- Delay or drop the lower-priority message rather than silently exceeding the rule.
- Preserve suppression and unresolved preference states ahead of the calendar.
A contact who enters onboarding and a product campaign on the same day should not receive both merely because separate teams own the sequences. The shared scheduling rule needs the person’s relevant state and the messages already sent or reserved. Test simultaneous scheduling if the cap is meant to hold under concurrency.
When is silence the useful next action?
A quiet period can prevent a promotion from competing with a task the customer is already trying to complete. For example, pause an unrelated offer while an unresolved setup failure is being investigated. Define the condition and exit rule so the quiet period does not become an invisible permanent exclusion.
How should the policy be evaluated?
Review meaningful completed actions, suppression changes, complaints where measured and the relevance of each message. Keep open signals and unclassified clicks as limited metrics. Compare compatible periods and customer stages; a mixed audience can change the average without any frequency effect.
If testing a frequency change, predefine eligibility, outcomes and the observation window. Account for the content difference as well as the number of sends. A campaign with more valuable material may perform differently for reasons unrelated to its schedule.
The completed calendar should name the owner, stage rule, priority, cap, quiet condition and review date. That makes frequency an operational decision the team can inspect rather than a fixed number copied from an unrelated industry chart.
Sources
AI-assisted writing and an AI-generated editorial cover. Source links and checked dates are listed below; illustrative examples are labeled in the text.
- Set up events — checked 2026-10-18