The Workflow Library

Library / Lead routing / lead-routing-042

Auto-reassign lead if rep does not accept task within X hours (task-based acceptance flow)

Lead routingContactSales Hub ProfessionalAdvanced~50 min to buildFull spec

Outcome. A lead automatically moves to the next rep in line if the first rep does not acknowledge it within an agreed window, instead of sitting unclaimed because a task notification got buried.

Workflow map Enrollment, branches and actions at a glance lead-routing-042
flowchart TD
    A[Contact owner set/changed] --> B[Reset Assignment Accepted to false]
    B --> C[Create acceptance task, due in 2 business hours]
    C --> D[Delay 2 business hours]
    D --> E{Assignment Accepted still false?}
    E -->|Yes| F[Rotate to next owner, notify sales manager]
    F --> A
    E -->|No, accepted| G[End, lead stays with accepting owner]
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse it when the team wants an explicit acceptance step before a rep is fully credited with owning a lead, not just an assignment and a hope that they see it.
  • UseUse it when reps can reliably perform one simple confirming action (completing a task, logging a call, or checking a property) within the acceptance window, so the workflow has a real signal to check.
  • SkipDo not use it if the team already has a fast, working SLA-breach reassignment based on activity (lead-routing-005); that fiche solves a similar problem with less process, use this one only if an explicit acceptance step is specifically wanted.
  • SkipDo not use it with an acceptance window shorter than reps can realistically act on given normal work patterns (meetings, time zones); an unreasonably tight window turns this into a constant reassignment churn tool instead of an accountability one.
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.7 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.