Suppression

The rule

A client is suppressed only for the products they already buy (their scope) and only in the markets where they are a client. Everywhere else they are a legitimate target: an Atlas subscriber is fair game for PiGen, and a UAE-only client is fair game in India. When an out-of-scope client IS targeted, the contact carries a relationship note so the rep coordinates with the account owner. Every excluded contact gets a written reason in the run's suppressed.csv - suppression is auditable, never silent. Names match at two levels (Jul 23): a client's own division names and brands suppress within the scope above, while a parent company name (the corporate umbrella) never suppresses on its own - contact data does not show divisions, so those contacts stay normal targets and carry a note to confirm the division with the account owner before outreach.

The clients (49)

Sourced from the client and contact repository (newsletter send list, Jul 17). Owned brands and email domains listed as aliases match too, with word boundaries (Brita never matches Britannia).

Corrections raised by the team

Spotted a wrong suppression - a client who left, a market that opened, a brand matching the wrong owner? Flag it from the client's row above. Corrections are applied to the client repository by the admin and take effect at the next engine run; nothing on this page changes until then.

R14 expansion leftovers

Existing-client names not in the repository yet. Their contacts are never cold-touched: they route to the account owner as expansion signals, in the regions listed.