Multi-touch routing: reroute lead if a second form fill happens with different intent

Outcome. A lead who first showed interest in one product and later fills a form for a completely different one gets flagged and handed to the right specialist, instead of staying with the original rep by default even after their interest clearly shifted.

Workflow map Enrollment, branches and actions at a glance lead-routing-049

flowchart TD
    A[Product Interest set/changed] --> B{First Product Interest already recorded?}
    B -->|No| C[Set First Product Interest as baseline, no reroute]
    B -->|Yes| D{New value not in First Product Interest?}
    D -->|Yes| E[Notify current owner of new interest]
    E --> F{Maps to a different specialist pool?}
    F -->|Yes| G[Rotate to new specialist pool, set routed date, create task]
    F -->|No| H[End, no action - rep judgment call]
    D -->|No| I[End, no action - already covered]

When to use it, when not to

• UseUse it in multi-product businesses where a lead's second, later form fill sometimes signals a genuinely different need than their first touch, and the original routing (lead-routing-013) should be revisited rather than assumed still correct.
• UseUse it once Product Interest (lead-routing-013's property) is already in place and populated by form fills, since this fiche is the "did the value actually change" layer on top of it.
• SkipDo not use it if a single form always captures every product a lead might be interested in at once (a multi-select on one form); there is no "second, different" fill to detect in that setup.
• SkipDo not use it if reps are comfortable simply adding a second product to their existing conversation without a formal reroute; this fiche is for cases where a clean handoff to a different specialist is actually wanted.