Qualify globally. Decide locally.
A qualification engine that respects the rules of every region it runs in. GDPR consent, regional buying signals, local-language reasoning, and country-specific routing in one console.
Three rules. Three regions.
The same lead, scored three different ways. Consent, signal, and language each carry their own region-specific weight.
Consent before reasoning
EU leads do not enter the qualification pool without a recorded lawful basis. Lead source, consent timestamp, and the exact opt-in copy are stored next to the record.
block(if consent.expired)
log(source, ts, copy_id)
Signals that mean something here
A topic spike in NA is not the same lead as a tender notice in EU or a hiring burst in APAC. Each region defines what counts as buying intent, and the engine scores against that map.
EU: tender + DACH_RFP_keyword
APAC: hiring + JP/SG headcount delta
Reads the reply in the language sent
A German RFP reply is read in German. A Japanese intro is read in Japanese. No machine-translation lossiness in the criteria check. Reasoning stays in the original language and rolls up to one console.
reason(in_lang)
surface(translation, optional)
One console. Three rulebooks.
Switch the region in the side panel and the qualification rules, consent posture, and routing map switch with it. Same workflow, different defaults.
EU rulebook · consent posture
Right region. Right AE. First try.
Same engine, three regional flows. The routing reads the country code, signal type, and consent state before it hands the lead to a human.
What's in the engine. By module.
Pick the modules that match the regions you actually run. Every module ships with the same audit log and the same console.
Consent ledger
A region-aware record of every lawful basis, every refresh, every withdrawal. Source-of-truth for any audit conversation.
- Per-record consent stateBasis, source, copy ID, timestamp, expiry.
- Region overlaysGDPR, CCPA, PIPL, PDPA, LGPD.
- Erasure workflowRight-to-be-forgotten with a redacted audit stub.
Regional reasoning
A qualification pass that reads the reply in the language it arrived in and scores against the region's own rulebook.
- Local-language passDE, FR, JA, ZH and more. No translation tax.
- Region rulebooksOne per market. Version-controlled. Auditable.
- In-region inferenceEU records reason in EU infra. APAC in APAC infra.
Country-level routing
When a lead is qualified, the routing reads the country code and the signal class before it picks the AE pod.
- AE pod mapsNA-W, NA-E, DACH, UK&I, SG, JP, ANZ, IN.
- Locale-aware briefHandoff brief in EN plus the lead's native language.
- Misroute trapA cross-region misfire flags itself before it ships.
Two teams. Three regions each.
Codenames and metrics from production engagements running NA, EU, and APAC at the same time.
A revenue org that stopped sending the wrong leads to the wrong AEs.
Three AE pods, one global SDR layer, and a steady drip of mis-region handoffs. After the rulebook went live, every lead was scored against its own region and routed to the matching pod. The EU pod stopped triaging US leads. The APAC pod stopped catching DACH replies in English. The console showed a single audit trail across all three.
An industrial seller that finally read its Japanese and German replies in-language.
Replies in DE and JA had been translated to English before scoring, and the criteria check kept missing context. After turning on the local-language reasoning module, the qualification pass read the reply in the language it arrived in. The DACH AE pod started getting briefs in EN plus DE, the JP pod in EN plus JA. Mis-qualified meetings dropped, AE-accepted meetings climbed.
Run one engine. Respect every region.
Tell us which regions you're running and which rulebooks matter most. We'll show you the console mapped to your map.