Marketing email sent through EasyDigz runs behind an automatic protection layer. It stops contacts being over-emailed, blocks addresses that have bounced or opted out, and halts a campaign before a wave of bounces can damage your sending reputation.
These protections are always on. You do not switch them on, tune them, or maintain a suppression list by hand. This page exists so that when one of them acts, you know what happened and why.
#Why a platform limits your own sending
Your sender reputation is a real, measurable thing held by Gmail, Outlook and the rest. It is slow to build and fast to lose, and once lost, your email quietly stops reaching inboxes, including the one-to-one email you send a client about their offer.
Most of the ways to lose it look harmless in the moment: emailing the same person three times in a day, mailing a list you bought, restarting a campaign that bounced. The rules below make those hard to do by accident.
#The rules
| Rule | In short | Detail |
|---|---|---|
| Daily cap | 2 marketing emails per contact per rolling 24 hours, across all your campaigns combined | The daily cap |
| Priority | When only one slot is left, a trigger email beats a drip step | Below |
| More than one campaign | A contact can be in several drips. You choose Enroll in both, Move here or Skip | Contacts in more than one campaign |
| Suppression | Bounced, unsubscribed and closed-account addresses are blocked automatically. A hard bounce for any agent blocks the address for every agent | Bounces and unsubscribes |
| Auto-pause | Two hard bounces pause a campaign; repeats escalate | Auto-pause and lockouts |
| Per-agent unsubscribe | Someone who unsubscribes from you can still hear from other agents | Bounces and unsubscribes |
| Separate trigger pipeline | Triggers are never stuck behind a large drip batch | Below |
| No duplicates | A contact gets each campaign step once, even if you restart it | Below |
#What counts as marketing
The rules apply to marketing email. Not everything EasyDigz sends is marketing, and the distinction decides what is capped.
| Kind of email | Daily cap | Lockout | Suppression |
|---|---|---|---|
| Trigger email | Applies | Applies | Applies |
| Drip campaign step | Applies | Applies | Applies |
| Composer send, now or scheduled | Exempt | Exempt | Applies |
| Welcome and workflow email | Exempt | Exempt | Applies |
| Daily or weekly digest | Exempt | Exempt | Exempt |
| Test send to yourself | Exempt | Exempt | Exempt |
| Emails to you about your own business | Exempt | Exempt | Exempt |
Look down the suppression column: unlike the cap, it applies to manual sends too. If someone has unsubscribed from you, a one-off email typed in the composer will not reach them either. That is deliberate, an opt-out means opt-out, and it is the one rule with no exceptions.
#When two emails compete
If a contact has one slot left in their 24 hours and both a trigger and a drip step are due, the trigger goes. Triggers are tied to something that actually just happened, a price cut, a matching listing, so they are worth more than the next scheduled step in a sequence. Composer sends are not capped, so they go out however many slots remain, but they are still checked against suppression.
#Triggers do not wait behind big drips
Trigger emails and drip or scheduled emails use separate send pipelines. A time-sensitive trigger, a property enquiry, say, is never stuck in the queue behind a 9,000-contact drip batch. The daily cap still applies at send time.
#No duplicate sends
- A contact receives each campaign step once, even if the campaign is restarted.
- If the same address appears twice in an audience, one email is sent.
- Only one pass of the drip sender runs at a time, so a step cannot be sent twice in parallel.
- Pausing stops anything still queued within seconds.
- Large enrolments are staggered and batched safely.
#When something did not send
Nothing is silently dropped, every skip is recorded with a reason. Why an email did not send is the diagnostic, in the order worth checking.