We have this same issue too. While I appreciate the answer below about adding a phone number/email address for the guest, this isn't really feasible as sometimes the person registering doesn't have that information and would have to request it from the person first before registering. I'm not sure that would go over well with most constituent bases. It would be better, if at minimum, it searched the address, phone, or email of the registering constituent alongside the name of the guest record and see if those pull matches since in most cases, they are usually registering a spouse.

We are thankful for the feature to search guests and link them to constituents behind the scenes though.

Hi! Thanks for submitting this idea!

On the online registration form in webview, we do automatically attempt to match on guests when the registrant includes enough information for us to match. This means that at a minimum, we need first name, last name, and either email address or phone number to attempt a match.

When just first name and last name are entered for a guest, we do not currently attempt a match.

You can change the named guest/non-constituent that is created for the guest to an existing constituent from the participant list in webview (Edit next to the participant name or from the participant record) or as you mentioned, from database view.

I'd love to hear your thoughts on this. Are you including email address or phone number collection fields for all of your guests?

Thanks,

Samantha McGuin
Principal Product Manager
Blackbaud