Lead-to-account matching currently relies primarily on the contact's email domain, and when a lead matches multiple accounts, Chili Piper falls back to number of contacts as the default tiebreaker. There's no way to configure website domain as the signal in either case.

Requested behavior: Let admins configure website domain as a matching priority in two ways:

As a primary match signal, matching a lead to the account whose website domain matches, rather than defaulting to the contact's email domain.

As a tiebreaker, when multiple accounts match, selecting the account whose website domain exactly matches the domain provided by the prospect, instead of using contact count.

Why it matters: Contact email domains and website domains often differ, especially for companies with subsidiaries or branded email addresses, so email-domain matching and contact-count tiebreakers can attribute leads to the wrong account. For teams where the prospect's website field is consistently filled in and reliable, website-domain-based matching produces more accurate account attribution.