Person matching looks at a single email field. When Chili Piper resolves an incoming booker against the CRM, the lookup runs against the standard Email field on the Contact or Lead. If the address the person booked with is stored only in a custom or alternate email field, work, personal, preferred, secondary, or other, Chili Piper treats them as a new person.

Requested behavior: let admins configure which email fields participate in person matching, including custom email fields on the Contact and Lead, and have matching check all of them rather than the standard Email field alone. Adding those fields as filters in the Matching Hub does not currently produce a match, so the configuration needs to reach the person lookup itself.