Route leads by product/service interest (form field or page viewed)

Outcome. A lead interested in one specific product line goes to the rep who sells that product, instead of a generalist who has to hand it off after discovery.

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

flowchart TD
    A[Product interest set / qualifying page viewed] --> B{Product interest?}
    B -->|Product A| C[Rotate to Product A specialists]
    B -->|Product B| D[Rotate to Product B specialists]
    B -->|Service C| E[Rotate to Service C specialists]
    B -->|unclear / blank| F[Rotate to Generalist pool + notify sales ops]
    C --> G[Set routed date, notify owner, create call task]
    D --> G
    E --> G
    F --> G

When to use it, when not to

• UseUse it when the company sells multiple distinct products or service lines with different specialist reps, and the lead's interest is knowable at intake (a form field, a pricing page visited, a specific demo request).
• UseUse it for multi-line businesses where a single generalist team cannot credibly speak to every product; specialist first-touch improves conversion.
• SkipDo not use it for a single-product business; there is nothing to branch on, use lead-routing-002 instead.
• SkipDo not use it if product interest is genuinely ambiguous at intake (a lead who only filled a generic "contact us" form with no signal). Route those through the generalist pool as the default branch, do not force a guess.