In this article

Your launch email has a sensible schedule. So does the weekly digest, the feature reminder and the invitation to a webinar. Then all four reach the same person on Tuesday.

Campaign calendars describe what each team wants to send. A notification policy decides what a customer should receive when those intentions collide. The policy needs a shared limit, a way to choose between eligible messages and a rule for messages that become irrelevant while waiting. A cap alone cannot make those decisions.

Give each message a job and an expiry

Start with an inventory of messages reaching established customers. Include product-generated email, push and SMS as well as marketing automations. Record the recipient, triggering event, intended action, relevant preference, expiry and what would make the message unnecessary. A customer who completed the task should leave the reminder audience even if the original campaign still exists.

Use a small priority scheme that someone outside the messaging team can understand. This is a proposed operating policy, not a claim about the best frequency for every product.

ClassExampleScheduling ruleExpiry or stop condition
Task-critical service noticeAccount-security alert or a failure requiring actionDedicated route with its own duplicate and escalation controlsResolved incident, replaced instructions or invalid action
Requested updateA report the person asked to receive or a reminder they setDeliver at the agreed time; combine compatible updates where possibleRequest withdrawn, task completed or reminder time passed
Discretionary product messageFeature tip, event promotion or upgrade suggestionCompete for a shared attention budgetCampaign deadline, changed eligibility or a fresher message serving the same purpose

The classification should follow the customer’s need. Calling an upgrade campaign “important” does not make it a service notice. Give one person responsibility for exceptions and record the reason. Otherwise every campaign owner can escape the limit by choosing a more urgent label.

Keep preferences ahead of priority. A message that is not eligible under the person’s applicable preferences never enters the competition. Customer.io’s subscription center distinguishes content topics from delivery channels and requires the applicable subscriptions for sending. That is a useful separation: wanting product news does not mean wanting it by every available channel.

Put the competing campaigns on one calendar

Consider a fictional reporting product. An established customer receives requested reports, occasional product education and service notices. For this example, discretionary email and push share two rules: at most one sent message in a rolling 24-hour window and at most two in a rolling seven-day window. Neither number is an industry benchmark. Requested updates and critical notices have separate policies and remain visible in the same customer history.

The following week assumes an empty discretionary history before Monday. Times are in the customer’s local time zone.

DayMessages that become eligibleDecision
MondayRequested digest at 9 a.m.; feature tip at 10 a.m.Send the digest, then the tip. The tip uses the first discretionary slot.
TuesdayWebinar promotion at 9 a.m., expiring at 9:30 a.m.Drop it. The 24-hour limit does not clear before its expiry.
WednesdayFeature announcement at 11 a.m.Send it. The second discretionary slot is used.
ThursdayTask reminder at 3 p.m.; requested export ready at 4 p.m.Drop the reminder because the task finished at 2 p.m. Deliver the requested export notice.
FridaySecurity alert at 8 a.m.; upgrade campaign at noonSend the security alert through its service route. The campaign cannot fit before its Sunday expiry.
SaturdayNo new eligible messageSend nothing. Unused time does not require another campaign.
SundayCustomer-requested reminder at 10 a.m.Send under the requested-update policy. Do not revive the expired webinar promotion.

This calendar exposes decisions that a campaign-by-campaign review misses. Tuesday’s promotion is still blocked even though it falls on a different date from Monday’s tip. Friday’s campaign cannot borrow a fresh weekly allowance simply because the calendar is approaching a weekend.

The example also makes the exceptions visible. Requested and critical messages still interrupt the person, even when they do not consume the discretionary allowance. Review their combined volume rather than congratulating the team for meeting a narrow marketing cap.

Choose the winner before the sending window opens

If two discretionary messages qualify at the same time, use an explicit tie-break rule. Prefer the message connected to the person’s current work, then consider whether its useful window closes sooner. If neither has a stronger claim, use a stable campaign priority agreed before launch. Do not allow whichever job happens to run first to become the editorial decision.

For example, a relevant explanation of a feature the customer has just attempted may deserve the next slot ahead of a broad product-news roundup. That judgment depends on context; an error in the attempted feature may instead mean the correct action is support. Record the chosen message and the reason alternatives were delayed or dropped.

Give delayed messages a maximum waiting period. A retry should recheck the customer’s preferences, task completion, account state and expiry. A message that no longer helps should end quietly. “We have room now” is insufficient reason to send Thursday’s instruction on Sunday.

Check the platform’s actual behavior

The scheduling policy and the platform configuration need separate reviews. Customer.io supports channel-specific and shared limits, but workflows do not count toward a limit by default; they must be assigned. Its automatic retries apply to automations and API-triggered broadcasts, with a maximum retry window of 48 hours. One-time sends and transactional messages do not receive automatic retries.

There is another consequential detail: Customer.io says a blocked message can be retried after the person has exited its automation. Do not assume an exit cancels queued communication. For a message whose relevance changes quickly, choose a sending design that can enforce the final eligibility check; otherwise leave automatic retry off. The seven-day calendar above is a policy example, not a promise that a vendor will hold and reprioritize that queue for you.

Test the rules with deliberate collisions. Send two eligible campaigns toward the same test identity. Change a preference while another message waits. Complete the triggering task before a retry. Repeat the test across channels and around the exact rolling-window boundary. The expected result should name which message sends, which stops and why.

Review what the policy withholds

A useful weekly report includes sent, delayed, expired, suppressed and superseded messages by purpose. Look for requested updates being crowded out, discretionary campaigns repeatedly expiring, and campaigns that avoid the shared limit. Inspect a few complete customer histories alongside totals.

Use meaningful product activity to judge whether reminders are connected to useful work. Opens and clicks can help diagnose a message, but a cleaner calendar should ultimately support the task the customer came to complete. When a campaign consistently loses the priority decision, revisit its purpose before asking for a larger allowance.

Sources

Something we should clarify?

Suggest a correction