Route leads by language (property or browser locale) to native-speaking rep

Outcome. A lead who prefers to be handled in their own language reaches a rep who speaks it, instead of a generalist who has to loop in a colleague mid-conversation.

Workflow map Enrollment, branches and actions at a glance lead-routing-023

flowchart TD
    A[Contact created / Preferred language set] --> B{Preferred language?}
    B -->|french| C[Rotate to French pool]
    B -->|spanish| D[Rotate to Spanish pool]
    B -->|german| E[Rotate to German pool]
    B -->|dutch| F[Rotate to Dutch pool]
    B -->|english / other / blank| G[Rotate to English pool + flag for review]
    C --> H[Set routed date, notify, create task]
    D --> H
    E --> H
    F --> H
    G --> H

When to use it, when not to

• UseUse it when the sales team has reps who each cover one or more languages, separate from or layered on top of territory-based routing.
• UseUse it when preferred language can be captured directly, through a form field or a language-specific version of a page or form.
• SkipDo not use it as the only routing key if territory already implies language reliably (for example a single-language country); combine the two only where they can actually disagree, see Known pitfalls.
• SkipDo not rely on browser locale alone as your only signal; it reflects device settings, not necessarily the person's actual preferred business language.