Skip to content
The Workflow Library
Get the full library

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

One of 565 written HubSpot workflow specs, by a collective of independent HubSpot consultants.

Professional

Seat pricing: Professional edition. To build it, a GTM Seat or an Ops Seat (an Ops Seat cannot create marketing emails or sequences). Per-hub plans: Marketing Hub Professional.

Contact4 stepsUpdated for HubSpot seat pricing
OutcomeA 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 maplead-routing-049
Product Interest set/changed leads to First Product Interest already recorded?. First Product Interest already recorded? leads to No: Set First Product Interest as baseline, no reroute; Yes: New value not in First Product Interest?. New value not in First Product Interest? leads to Yes: Notify current owner of new interest; No: End, no action - already covered. Notify current owner of new interest leads to Maps to a different specialist pool?. Maps to a different specialist pool? leads to Yes: Rotate to new specialist pool, set routed date, create task; No: End, no action - rep judgment call. No Yes Yes Yes No No Product Interest set/changed First Product Interest already recorded? Set First Product Interest as baseline, no reroute New value not in First Product Interest? Notify current owner of new interest End, no action - already covered Maps to a different specialist pool? Rotate to new specialist pool, set routed date, create task End, no action - rep judgment call
Product Interest set/changed leads to First Product Interest already recorded?. First Product Interest already recorded? leads to No: Set First Product Interest as baseline, no reroute; Yes: New value not in First Product Interest?. New value not in First Product Interest? leads to Yes: Notify current owner of new interest; No: End, no action - already covered. Notify current owner of new interest leads to Maps to a different specialist pool?. Maps to a different specialist pool? leads to Yes: Rotate to new specialist pool, set routed date, create task; No: End, no action - rep judgment call. No Yes Yes Yes No No Product Interest set/changed First Product Interest already recorded? Set First Product Interest as baseline, no reroute New value not in First Product Interest? Notify current owner of new interest Maps to a different specialist pool? Rotate to new specialist pool, set routed date, create task End, no action - rep judgment call End, no action - already covered

One of 565 written HubSpot workflow specs, by a collective of independent HubSpot consultants.

When to use it, when not to

Use it

  • Use 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.
  • Use 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.
Read more on when to use itShow less

Skip it

  • Do 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.
  • Do 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.
Read more on when to skip itShow less

The rest of this spec

Prerequisites · 4 items

Every property with its label, internal name, type and options, plus the assets the workflow needs.

Enrollment · 4 parts

The trigger, the criteria as ticked in the UI, the re-enrollment rule and the suppression list.

Steps · 4 numbered actions

Each action in order with its parameters, branches and delays.

Known pitfalls · 4

Traps seen in production, each with what breaks and what to do instead.

Test plan and UAT script · 5 cases, 3 variants

How to prove it works in a test portal, one case per branch, and a sign-off sheet.

Files · PDF, Markdown, JSON, CSV

The properties JSON creates the fields in one call. The workflow JSON documents the build.

Install · 1 click, switched off

The installer creates the properties and the workflow, switched off, then opens a task for what it cannot create. Nothing is deleted, enabled or enrolled.

Unlock all 565 specs, 149 EUR

One-time, excl. VAT. 30-day refund. Installs in 3 portals. Founding price until 30 November.

Read the free Lead routing spec

Not the workflow you needed?

More in Lead routing

50 specs in this section

See all 50 This category, 39 EUR
FreeRound-robin lead assignment by territoryContact15 steps Route leads by product/service interest (form field or page viewed)Contact15 steps New lead auto-assignment by owner rotationContact3 steps First-contact SLA timer with owner reminder taskContact11 steps

Read 12 complete specs before you pay.

One per category, same format as the paid ones. Email only, no card.

We email the link, then a short note when specs change. Nothing else.

149 EUR199

Full library, 565 specs
Get the full library