Sourcing Compliance: Geography and Off-Limits

PlacementFlow builds compliance guardrails directly into campaigns: some geographies can't be cold-emailed, your clients' domains are filtered out of every send, and a multi-layer off-limits check stops you from accidentally poaching from your own client base.

Geography: Why Germany Is Excluded

German law (UWG §7) prohibits unsolicited B2B email — sending cold outreach there exposes the sender to formal legal warnings and costs. PlacementFlow therefore blocks Germany-targeted cold campaigns outright:

• The campaign wizard rejects German locations at creation — the country, major cities, and federal states are all recognised.
• The same check re-runs at launch, so a draft can't slip through later.
• Matching is deliberately generous: a rare false positive (a similarly named non-German place) is a better outcome than a legal exposure.

This isn't a preference toggle; it's a legal constraint enforced in the product. If your candidate market includes Germany, use channels where the candidate initiates contact instead.

The Client-Domain Blocklist

The blocklist is your first line of client protection for cold outreach:

1. Go to Settings → Client Domains
2. Add the email domains of your client companies (e.g. acmecorp.com)
3. Any sourced prospect whose enriched email matches a blocklisted domain is dropped before a single email is sent

Every campaign carries a snapshot of your blocklist, and the snapshot is refreshed at launch — clients you added after saving a draft are still protected when the draft goes live.

Off-Limits: The Deeper Check

Domains alone aren't enough — a candidate at one of your clients may reply from a personal address, or work at a subsidiary with a different domain. So a second, deeper off-limits check runs where cold leads enter your warm pipeline (the Qualified queue) and again on warm sends:

1. Email domain — direct match against your protected companies
2. Company identity — the employer's LinkedIn company record
3. Fuzzy company name — near-match name comparison that catches spelling variants and subsidiaries

The result shows on each qualified lead: a hard match blocks the handoff entirely (server-side, not just a greyed-out button), and a soft signal — such as employer data being unavailable — shows a warning for your manual judgment. The check fails closed: if it can't run, the handoff is refused rather than risked.

Manage your protected companies in Settings → Off-Limits; the domain blocklist and the off-limits list work together, covering the cold and warm sides respectively.

No Double-Contacting

PlacementFlow also guards against the same person being hit twice:

• A candidate already in an active outreach for one role isn't cold-messaged again for another.
• A cross-channel guard prevents duplicate outreach to the same candidate across email, WhatsApp, and portal touchpoints.

What the AI does here

• Enforces the geography rules and blocklist filtering automatically on every campaign.
• Runs the full off-limits check on every qualified lead and every warm send — and refuses, rather than guesses, when the data is missing.
• You decide what to do with warned leads; hard blocks exist precisely so no one — human or AI — can make that mistake in a hurry.

Related articles

• Reviewing warm replies and handoff
• Create a sourcing campaign
• How sourcing campaigns work