Currently receiving event registrations. Phone #s coming into RE as "PhoneFinder" type as that is only phone type that has formatting <none>. I want to be able to capture cell and landline #s with the correct type but as these #s are formatted to display with (xxx) xxx-xxxx ext xxx it will not accept these as options for the types on event forms.
The primary phone box is also auto checking for these numbers if no other number is marked as primary. We are still working with constituents to determine which # is their primary. Now I have 'phonefinder' #s marked as type and as primary.
This will require significant manual editing and/or revisions of queries/exports as we don't usually pull PhoneFinder type for these, just those indicated as cell/home.
Thank you for the suggestion of a 'new distinct' unformatted phone type. Will definitely do that as it will make clean up easier. I sort of assumed unformatted was to capture extra digit for international. Yes, will be needed at some point. I have some coming in thru NetC.
Voted for the idea on multiple phone types. Definites yes - 100 votes!
Hi JoAnn,
You are right that we only support "None" formatted phone types today in order to be able to collect international phone numbers (as we are looking ahead to international address support as well for registrants.)
For now I would recommend adding a new phone type with a "None" format just for incoming form submissions so that you're not tying these incoming phone types with actual PhoneFinder numbers. I will keep this Idea open to gauge interest/need from other customers.
In reading a little between the lines, it sounds like you'd ideally like to add multiple phone types to a form for the registrant to tell you they are entering a cell phone versus home phone, is that correct? I would recommend adding your vote to this Idea about that topic:
https://renxt.ideas.aha.io/ideas/RENXT-I-3582
Thank you for the continued feedback!
Samantha McGuin
Principal Product Manager