Ticket routing across hierarchical sub-teams (parent/child HubSpot Teams)

Outcome. A ticket routes to a specific sub-team for day-to-day handling, while a parent team lead automatically gets visibility and an escalation path across every sub-team underneath them, without a separate workflow per sub-team's reporting chain.

Workflow map Enrollment, branches and actions at a glance tickets-sla-043

flowchart TD
    A[Ticket created, queue known] --> B{Ticket queue value?}
    B -->|billing| C[Rotate to Support - Billing child team]
    B -->|technical| D[Rotate to Support - Technical child team]
    B -->|unknown| E[Notify parent team lead, add to Needs manual triage]
    C --> F{First-response SLA at risk?}
    D --> F
    F -->|yes| G[Escalate to parent team lead]
    F -->|no| H[End, normal handling]

When to use it, when not to

• UseUse it once hierarchical Teams (parent teams with child teams underneath) are already set up in Settings > Users & Teams, an Enterprise-only structure used mainly for permissions and reporting rollups. Teams come with Professional and Enterprise, and nested teams require Enterprise (https://knowledge.hubspot.com/user-management/create-and-manage-teams).
• UseUse it when a parent team lead needs to see and escalate across every child sub-team's tickets without being individually added to each one, which is what the hierarchy is actually for; this fiche's rotation logic itself is no different from tickets-sla-001, the hierarchy changes who gets looped in on escalation, not how the base rotation works.
• SkipDo not use it expecting hierarchical Teams to change how Rotate record to owner picks a member; the rotate action still needs an explicit pool (a specific child Team or a manually maintained list), the hierarchy is a permissions and reporting layer, not a routing behavior by itself (check in your portal: confirm whether the rotate action can target a parent Team and automatically include all child Team members, or only accepts one Team level at a time).
• SkipDo not use it on a flat, single-tier Team structure; if there are no parent/child relationships in your portal, this is just tickets-sla-001 with extra unnecessary complexity.