Sourcing Compliance: Geography and Confidentiality

3 min read

PlacementFlow builds compliance directly into campaigns: cold email runs only in jurisdictions where it's legally viable, and every cold send goes out under a neutral platform identity — your agency stays confidential until you personally review a warm reply and approve the handoff.

Geography: An Allowlist, Not a Blocklist

The list depends on the campaign type. Candidate sourcing campaigns email personal addresses and run in the United States only. Business development campaigns email work addresses and are supported in the United States, United Kingdom, France, Ireland, Singapore and the United Arab Emirates. Each country was checked on its own before it was added. PlacementFlow does not send cold email anywhere else.

The enforcement is deliberately strict:

The campaign wizard accepts only verified allowed countries — anything not on the allowlist is rejected, rather than PlacementFlow maintaining a list of "bad" places.
Umbrella regions ("Europe", "EMEA") and city- or region-level locations ("London", "Paris, France") are rejected too — target at country level so every send is unambiguously inside an allowed jurisdiction.
The same check re-runs at launch, so a draft can't slip through later.

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

Confidential Search: How Your Agency Stays Protected

Cold outreach never carries your agency's name. Every cold email goes out under a neutral platform identity from managed sending domains — the classic executive-search "confidential client" pattern. That has two practical consequences:

Cold volume can't touch your brand. Nobody can connect a cold email to your agency, because the agency isn't in it.
Nothing is exposed to anyone at a client company before a human decides. A cold email reaching someone who happens to work at one of your clients reveals nothing about you. Your agency is only introduced when you review the warm reply and approve the handoff — and the intro then goes from your own mailbox.

You Own the "Is This My Client's Employee?" Call

There is no automated client-protection filter — deliberately. Fuzzy company matching is unreliable in both directions: it misses subsidiaries and personal email addresses, and it silently drops good candidates over name coincidences. The reliable check is you.

Every lead in Today, under Decide, shows the candidate's current employer alongside the reply. Before you hand off, that's your moment to ask: is this person at one of my clients, and do I want to proceed? Until you click Hand off to me, the candidate has seen nothing that identifies your agency — so a "no" costs you nothing.

Opt-Outs and Suppression

Consent signals are honored durably across the cold engine:

Opt-outs and unsubscribes stop outreach to that person permanently — not just for one campaign.
Hard bounces and spam complaints trigger suppression automatically, protecting deliverability for everyone.
The kill switch pauses all cold campaigns immediately, including those running on managed infrastructure.

What the AI does here

Enforces the geography allowlist automatically at creation and again at launch.
Sends every cold email under the neutral platform identity — it never names your agency in cold outreach.
Honors opt-outs, bounces, and the kill switch without exception.
You decide every handoff — the moment your agency's identity enters the conversation is always a human decision.

Back to Sourcing & Campaigns