Outcome. A lead is routed to the rep who sells in their region's currency, and any deal created for them starts in the correct currency from the first record, instead of a rep discovering a currency mismatch mid-quote.
Workflow map
Enrollment, branches and actions at a glance
lead-routing-041
flowchart TD
A[Contact created / Currency Region set] --> B{Currency Region?}
B -->|USD region| C[Rotate to USD rep pool]
B -->|EUR region| D[Rotate to EUR rep pool]
B -->|GBP region| E[Rotate to GBP rep pool]
B -->|blank / unknown| F[Notify sales ops + add to Needs manual routing]
C --> G[Set routed date, notify owner, create call task]
D --> G
E --> G
When to use it, when not to
- UseUse it when the business sells in multiple currencies and reps or teams are split by currency region (a EUR team, a GBP team, a USD team), not only by geography.
- UseUse it once multi-currency is enabled and configured with the correct exchange rates and currency codes for each region the team sells into.
- SkipDo not use it if the business quotes in a single currency regardless of the customer's location; a plain territory workflow (lead-routing-001 or lead-routing-006) is enough.
- SkipDo not use it as a substitute for tax or legal-entity routing; currency region and legal selling entity are related but not always the same thing, confirm which one actually determines rep assignment before building.
The preview ends here. Six sections are in the library.
counted, not blurred
PrerequisitesEvery property with its label, internal name, type and options, plus the assets the workflow needs before you start.4 items
EnrollmentThe trigger, the criteria exactly as they are ticked in the UI, the re-enrollment rule and the suppression list.4 parts
StepsEach action in order with its parameters, its branches and its delays, written as you tick them.15 numbered actions
Known pitfallsTraps seen in production, each with what breaks and what to do instead.4 pitfalls
Test plan, variants and build specHow to prove it works in a test portal, where to look when it does not, the variants for other objects or tiers, and the YAML build spec.3 variants, 3 sections
FilesThe properties JSON creates the fields in one API call, the workflow JSON documents the build.PDF, Markdown, JSON
Install1 click. The installer creates the properties this spec declares and the workflow itself, switched off, then opens a task for the prerequisites that are assets rather than properties, such as a team, a static list or a marketing email. What it created is listed on the install page.1 click, switched off
Unlock the full library,
149 EUR
or the lead routing pack, 39 EUR
One-time, excl. VAT. 30-day refund, no questions asked. Founding prices until 31 October, then 199 and 59 EUR. Includes every spec added later, up to the full 500, and the one-click installer on the full library. Building on client portals? The agency licence at 449 EUR covers unlimited client portals.
