Skip to content
The Workflow Library
Get the full library

Route existing-customer inquiry to current owner instead of round-robin

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: Sales Hub Professional.

Contact5 stepsUpdated for HubSpot seat pricing
OutcomeA new inquiry from an existing customer reaches their current owner directly, instead of falling through the cracks because your new-lead round-robin deliberately ignores customers.
Workflow maplead-routing-019
Customer submits inquiry form leads to Owner known?. Owner known? leads to Yes: Notify current owner + create follow-up task; No: Rotate to CS fallback pool + notify sales ops. Yes No Customer submits inquiry form Owner known? Notify current owner + create follow-up task Rotate to CS fallback pool + notify sales ops
Customer submits inquiry form leads to Owner known?. Owner known? leads to Yes: Notify current owner + create follow-up task; No: Rotate to CS fallback pool + notify sales ops. Yes No Customer submits inquiry form Owner known? Notify current owner + create follow-up task Rotate to CS fallback pool + notify sales ops

When to use it, when not to

Use it

  • Use it alongside a new-lead routing workflow (lead-routing-001 or lead-routing-006) that excludes Lifecycle stage is customer from its own enrollment criteria, which is the recommended setup; that exclusion means nothing currently notifies anyone when an existing customer submits a new inquiry, and this fiche fills that gap.
  • Use it for general contact-us or inquiry forms that both prospects and customers might submit.
Read more on when to use itShow less

Skip it

  • Do not use it if your inquiry form is only for pre-sale leads and customers use a separate support channel; route that through tickets-sla instead.
  • Do not use it as a substitute for reassigning a customer whose owner already left the company. Fix that first, see lead-routing-012.
Read more on when to skip itShow less

The rest of this spec

Prerequisites · 3 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 · 5 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 · 4 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 country / region to territory ownerContact15 steps Auto-unassign and re-route lead when owner is deactivatedContact5 steps New lead auto-assignment by owner rotationContact3 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