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.
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]

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





