Route leads by language (property or browser locale) to native-speaking rep
One of 565 written HubSpot workflow specs, by a collective of independent HubSpot consultants.
Professional
Seat pricing: Professional edition. To build it, a GTM Seat or an Ops Seat (an Ops Seat cannot create marketing emails or sequences). Per-hub plans: Sales Hub Professional.
Per-hub plans: also Marketing Hub Professional
On per-hub plans, one of its steps belongs to another subscription: add to static list needs Marketing Hub Professional. Both are required to build it as written. On seat pricing the edition covers both.
When to use it, when not to
Use it
- Use it when the sales team has reps who each cover one or more languages, separate from or layered on top of territory-based routing.
- Use it when preferred language can be captured directly, through a form field or a language-specific version of a page or form.
Read more on when to use itShow less
Skip it
- Do 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.
- Do not rely on browser locale alone as your only signal; it reflects device settings, not necessarily the person's actual preferred business language.
Read more on when to skip itShow less
The rest of this spec
Not the workflow you needed?
Read 12 complete specs before you pay.
One per category, same format as the paid ones. Email only, no card.
We email the link, then a short note when specs change. Nothing else.
Here it is. Download the pack now (.zip) The link is in your inbox too.
Read the free Lead routing spec