Outcome. A subsidiary company inherits its territory and owner pool from its parent account instead of being routed as if it were an unrelated, brand-new company.
Workflow map
Enrollment, branches and actions at a glance
lead-routing-037
flowchart TD
A[Company created / parent company set] --> B{Parent company associated?}
B -->|No| C[Standalone company - use lead-routing-006 instead]
B -->|Yes| D{Parent Territory known?}
D -->|Yes| E[Copy Territory from parent, set routed date]
D -->|No| F[Add to Territory pending list, notify sales ops]
When to use it, when not to
- UseUse it when the business sells to organizations with multiple legal entities or locations linked in HubSpot's company hierarchy (parent and child companies), and territory should follow the parent, not be re-derived per subsidiary.
- UseUse it once contact-level territory routing (lead-routing-001)
already exists and this fiche is layered underneath it, filling in
Territoryat the company level before contacts inherit it. - SkipDo not use it if the business has no meaningful parent-child company structure; a flat contact-level territory workflow is simpler, see lead-routing-001.
- SkipDo not use it as a substitute for named-account routing; a strategic subsidiary of a strategic parent should still go through lead-routing-011's suppression, not this general territory logic.
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.6 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.
