Outcome. A 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.
flowchart TD
A[Customer submits inquiry form] --> B{Owner known?}
B -->|Yes| C[Notify current owner + create follow-up task]
B -->|No| D[Rotate to CS fallback pool + notify sales ops]

When to use it, when not to
- UseUse it alongside a new-lead routing workflow (lead-routing-001 or
lead-routing-006) that excludes
Lifecycle stage is customerfrom 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. - UseUse it for general contact-us or inquiry forms that both prospects and customers might submit.
- SkipDo 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.
- SkipDo not use it as a substitute for reassigning a customer whose owner already left the company. Fix that first, see lead-routing-012.
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.





