[ 01 ]
Cross-border outreach carries real legal risk
Cold-contacting a lead is not the same legal act everywhere — a pattern that clears one jurisdiction can be blocked outright in another.
CogniLead
ProductWarmed sender poolReputation circuit-breakerJurisdiction routingREST APIMCP serverDNS automationCompliance & suppression
SolutionsDevelopersAgenciesB2B SaaSRecruitersSales teamsSolo foundersSaaSRecruiting & staffingReal estateAgencies & consultingEcommerce & DTCB2B services
CompareAll 12 alternatives →vs. Instantly.aivs. Smartleadvs. Lemlistvs. Apollo.iovs. Woodpecker.coInstantly vs. SmartleadSmartlead vs. LemlistApollo vs. LemlistSee all 8 →
ResourcesBlogDocsMCP serverAPI referenceSPF checkerDMARC checkerBlacklist checkerSpam-word checkerStatus
PricingLog inJurisdiction-aware routing
Every lead, processed in its own region.
Before CogniLead spends a cent verifying or personalizing a lead, it reads that lead’s jurisdiction — to decide whether cold contact has a legal basis there at all, and which region’s AI infrastructure should be the one drafting the outreach.
The problem
Most cold-email pipelines don’t know where a lead is.
[ 02 ]
One-size-fits-all infrastructure ignores where the lead is
Running every lead through the same pipeline regardless of origin treats a recipient in Zurich the same as one in Austin — even though the rules, and the ideal processing path, differ.
[ 03 ]
Compliance teams end up blocking outbound entirely
Without a system that already knows which jurisdictions are off-limits, the safest move for a compliance team is often to pause outbound altogether rather than trust it case by case.
[ 04 ]
No visibility into where a lead was actually processed
When routing is invisible, "we handle data carefully" is a policy statement, not something you can point to for a specific lead.
How it works
Jurisdiction decides the whole path a lead takes.
One field on the lead record drives two decisions: whether cold contact is legally permitted there at all, and which region’s AI infrastructure is the right one to process it.
A lead’s jurisdiction is read first
Every lead carries an ISO country code. A lead with no usable jurisdiction is rejected before any verification spend, not processed as a default case.
The routing decision is made per lead
That country code is checked against a maintained legal-basis table and used to pick an AI provider whose infrastructure actually sits in or near that region.
What changes downstream
Jurisdictions with no permitted basis for cold contact are blocked outright; everywhere else, personalization is drafted through the selected region and provider, logged with the region and jurisdiction that drove it.
The mechanism, live
Four regions, one routing table.
Every recipient jurisdiction resolves to one of four regions this table already knows about — each with its own preferred provider and a fallback chain behind it, not a single global default wearing a compliance label.
Routing table4 regions
- CHRouted 2m ago
Infomaniak — checked first for Swiss recipients
Switzerland
- EURouted 40s ago
Mistral — checked first for EU/EEA recipients
26 EU/EEA jurisdictions, plus the UK
- USRouted 5m ago
OpenAI — checked first for US recipients
United States
- WORLDRouted 1m ago
Gemini — the global default elsewhere
Everywhere without a dedicated regional route
Providers and coverage reflect the real fallback chain in code; the per-row timestamps above are illustrative, not a live feed on this page.
[ 01 ]
35
Jurisdictions with a documented legal basis
[ 02 ]
4
Regions personalization can route to
[ 03 ]
5
Jurisdictions blocked pending a real opt-in flow
Jurisdiction-aware routing
Where a lead lives decides how it’s handled.
No lead is processed through a single default pipeline. Its jurisdiction is read first, checked against a real legal-basis table, and used to route personalization to the region whose infrastructure actually fits.
35 jurisdictions
Documented legal basis
4
Processing regions
Yes
Blocked before spend
FAQ
Questions about jurisdiction routing.
No — this describes a real processing and legal-basis-gating behavior in the pipeline, not a certification. See /legal/privacy and /legal/security for the complete data-handling posture this feature supports.
It is rejected at the legal-basis gate before verification spend — no email is drafted or sent, and no per-lead cost is incurred processing it further.
Not yet — which sending domain carries a send is decided by warmth and health today (see /features/warmed-sender-pool). Jurisdiction currently drives the legal-basis gate and which AI region drafts the personalization.
Every routing decision is logged with the region, the provider, and the jurisdiction that drove it, per lead — not just applied silently.
Read the full data-handling posture this feature supports: /legal/security.
Your leads deserve to reach an inbox.
Every email you send without protection is a gamble on whether it reaches the inbox at all. Bring your leads — CogniLead handles the warmup, the safety checks, and the cleanup, so you don't have to think about deliverability again.
100 sends a month, free forever · no credit card · cancel any time