Current Situation

Lead-to-Related Lead Matching allows Chili Piper to route new leads based on existing lead records in Salesforce that share the same email domain.

Example:

Existing Lead: robbie@chilipiper.com
(owned by Rep 1)

New Lead: sorin@chilipiper.com

Since both share @chilipiper.com, Chili Piper correctly identifies they’re from the same company and routes Sorin’s lead to Rep 1.

✅ This works only if robbie@chilipiper.com
already exists in Salesforce as a lead record at the time Sorin’s form is submitted.

The Problem

If robbie@chilipiper.com exists as a lead record when sorin@chilipiper.com submits the form (but sorin@chilipiper.com does not), there’s no existing lead to match against.
As a result, sorin@chilipiper,.com might will not be routed to rep 1.

Proposed Solution: Person-to-Lead Related Lead Matching

This enhancement would allow Chili Piper to match and route on net new leads, not just existing leads.

So even if the related person (like Sorin) isn’t currently a lead, Chili Piper can still recognize the domain match (@chilipiper.com) and route sorin@chilipiper.com submission to Rep 1.