Outcome. A lead that has already missed its first-contact SLA once and misses it again reaches the owner's manager directly, instead of quietly repeating the same warning to a rep who is not acting on it.
flowchart TD
A[SLA breach count set >= 2] --> B{Owner has a mapped manager?}
B -->|Yes| C[Notify manager + create escalation task]
B -->|No| D[Notify sales ops as fallback]

When to use it, when not to
- UseUse it as a companion to lead-routing-003 or lead-routing-005, once those workflows are already incrementing a breach counter on repeated SLA misses.
- UseUse it when there is a clear, current mapping of each rep to their manager, since HubSpot has no built-in "owner's manager" field to read automatically.
- SkipDo not use it as your first line of SLA enforcement; it only escalates on the second miss, pair it with lead-routing-003 for the first warning.
- SkipDo not use it if your team is small enough that one manager already reviews every SLA breach manually; the added workflow may be more overhead than the manual check.
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.





