The Workflow Library

Library / Lead routing / lead-routing-035

Route re-engaged (previously closed-lost) contacts back to original owner

Lead routingContactSales Hub ProfessionalIntermediate~35 min to buildalso needs Marketing Hub ProfessionalFull spec

This spec is filed under Sales Hub Professional, and one of its steps belongs to another subscription: add to static list needs Marketing Hub Professional. Both are required to build it as written.

Outcome. A contact who comes back after a closed-lost deal reaches the rep who already knows their history, instead of a stranger starting the relationship over through round-robin.

Workflow map Enrollment, branches and actions at a glance lead-routing-035
flowchart TD
    A[Re-engagement signal fires] --> B{Owner known and active?}
    B -->|Yes| C[Set routed date, notify original owner, create follow-up task]
    B -->|No| D[Notify sales ops, add to Needs manual routing]
    D --> E[Falls back to standard round-robin]
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse it whenever the team wants continuity for a returning contact: the rep who ran the first conversation is usually the best person to pick it back up.
  • UseUse it as a check that runs before the standard round-robin (lead-routing-001 or lead-routing-002), not as a replacement for it.
  • SkipDo not use it if the original owner has left the company or been deactivated; fall back to standard rotation in that case, see Known pitfalls.
  • SkipDo not use it if the team deliberately wants a fresh rep on returning leads (a specific re-engagement or win-back motion with its own dedicated pool); route those through that pool instead.
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.6 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.