Sending Limits and Deliverability Standards

These are the deliverability thresholds Members agree to maintain when sending email through the Platform. They exist to protect the deliverability of every Member sharing the Platform's sending infrastructure, and they are referenced in our Mass Email and Anti-Spam Policy §5(a).

Going over a threshold does not automatically suspend an account. Suspension is the last step in a notice-and-remediation conversation, not the first.

Per-plan send allowances

Each plan includes a monthly send allowance (resets on the 1st of each month) and a daily send cap (resets at 00:00 UTC). The daily cap protects the shared sending infrastructure from bursts that would jeopardize deliverability for everyone; the daily caps are sized so you can email your full contact list in a single day.

• Professional. Up to 50,000 messages per month, capped at 10,000 per day.
• Enterprise. Up to 200,000 messages per month, capped at 50,000 per day.
• Enterprise Plus. Up to 500,000 messages per month, capped at 100,000 per day.

Need more headroom? Capacity add-ons let you raise either limit independently. Contact support to add capacity to your plan.

Thresholds

• Spam complaint rate. Sustained complaint rates above 0.1% (one complaint per one thousand delivered messages) across any rolling thirty-day period trigger review.
• Hard-bounce rate. Hard bounces above 5% on any single send trigger review.
• Other patterns. Behavioral signals that indicate deliverability risk, such as rapid list growth without corresponding consent provenance, unusual open-or-click distributions consistent with list quality issues, or repeated sends to addresses that have already unsubscribed across the Platform.

Remediation, not surprise suspension

When usage trips a threshold, we will notify the affected Member, explain the signal we are seeing, and provide remediation guidance before suspending sends. Common remediation steps include pausing further sends to a specific list segment, re-confirming consent for a subset of contacts, cleaning hard bounces and unsubscribes out of an upcoming send, or moving high-risk segments onto a slower send pace.

We reserve the right to suspend sending immediately, without prior notice, in cases of severe or ongoing risk to the Platform's deliverability infrastructure (for example, when continuing a send would jeopardize delivery for every other Member sharing the sending lane). When that happens, we will still explain what we saw and what remediation looks like as soon as it is practical.

How to maintain healthy deliverability

• List hygiene. Remove hard bounces and unsubscribes promptly. The Platform handles cross-Member suppression automatically, but list-level hygiene is the Member's responsibility.
• Consent quality. Send only to contacts who actively asked to hear from you. Re-permission stale segments before mailing them. CASL considers consent older than twenty-four (24) months stale without separate documentation.
• Content quality. Match subject lines and preheaders to the message inside. Avoid all-caps and excessive punctuation. Maintain a clear physical-postal-address footer and a one-click unsubscribe that actually works.
• Sending cadence. Warm new segments gradually. A list that has not received Platform email in months should be re-engaged in slower waves, not as a single mass send.

References

These thresholds are referenced in Member Terms of Service §19 (Member Mailing List Practices) and incorporated by reference into the Mass Email and Anti-Spam Policy. The Platform's sub-processor list is at /subprocessors.