Bounce and suppression handling

Elastic Email records every hard bounce, soft bounce, and spam complaint against each contact after a send. A Beam agent checks this delivery data once a campaign finishes, applies the sender's approved bounce threshold, and adds contacts that fail repeatedly to the suppression list so later campaigns skip them without manual cleanup. A single soft bounce, like a temporarily full inbox, is left alone for the next attempt rather than suppressed outright. Contacts with mixed signals, several bounces alongside a recent open, go to a person to decide whether the address still belongs on the list.

Contact list segmentation

Elastic Email stores contact activity, opens, clicks, and unsubscribes, against list and segment fields. A Beam agent reads this activity after each send and moves contacts into the segment the account owner already approved, such as inactive after a set number of unopened campaigns. Segment membership updates without a person re-checking every record by hand. New segment rules, or a contact whose activity contradicts the existing tags, such as a click on a supposedly inactive address, are routed to a person before the account owner's segmentation logic is applied more broadly.

Transactional delivery alerts

Elastic Email separates transactional sends, receipts and password resets, from marketing campaigns in its delivery reports. A Beam agent watches transactional delivery rates and flags a drop against the account's normal baseline, checking the API logs for the affected message type. Where the connector and account permissions allow it, the agent can pause a failing transactional stream and notify the account owner rather than let messages queue silently. Any change to how a transactional message is set up, or a sustained failure with no clear cause in the logs, is left for a person to investigate directly.