The Workflow Library

Library / Lead routing / lead-routing-024

Escalate lead to manager when SLA breached twice

Lead routingContactSales Hub ProfessionalIntermediate~35 min to buildFull spec

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.

Workflow map Enrollment, branches and actions at a glance lead-routing-024
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]
action or delay branch public on every spec, paid or not

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.
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.3 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.4 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.