Because we don't require emails from our clients (a lot of them don't have an email) every time there's a new booking basically for the same client (same name, same phone number), it is registered as another customer. and I imagine in the future it will be very hard to actually find appointments by searching for a specific customer.
(see the screenshot for example)
What could we do to mitigate this issue? Can we somehow tie the user to the phone number? so if it's the same phone number, automatically assign the ID for that person without creating a new one.
Thanks for reaching out to us and apologies for the delayed answer.
Amelia uses the email as the "parameter" to differentiate the user. That being said, by default, no matter if the customer uses the same name and last name, as well as the phone number, Amelia creates a new customer.
If the customer already booked an appointment, in the roles settings, in the Customer Tab, there is an option called "Check customer's name for existing email when booking". If this is enabled, the "existing customers" won't be able to use different first and last names when booking.
Not sure if it fits your needs, but this is the closest option. Please feel free to search through our feature suggestion page, to see if someone may have already suggested this feature. If you can't see it, feel free to add your suggestion there, and as more people vote, the feature will move higher on the priority list.
You can certainly follow our changeLog page if you'd like, where we state any changes/new features/bug fixes during updates and our newsletter, so you're informed about new features, bug fixes, freebies, etc.
As I've said, people don't enter their emails so it would be pointless to enable that option.
What if I drop the email index from the database, and add one for the phone number? Would that switch the differentiating "parameter" from email to phone number?
@Uroš mentioned something about dropping the index in another of my tickets, and I thought it might be an solution for this "issue" as well.
I got that, but all other options like limits etc are based on the customer's email. Regarding the option of dropping the index, I doubt it will work, but you can test it out.
Hello,
Because we don't require emails from our clients (a lot of them don't have an email) every time there's a new booking basically for the same client (same name, same phone number), it is registered as another customer. and I imagine in the future it will be very hard to actually find appointments by searching for a specific customer.
(see the screenshot for example)
What could we do to mitigate this issue? Can we somehow tie the user to the phone number? so if it's the same phone number, automatically assign the ID for that person without creating a new one.
Attached files: duplicate user for same person.JPG
Hello Emanuel,
Thanks for reaching out to us and apologies for the delayed answer.
Amelia uses the email as the "parameter" to differentiate the user. That being said, by default, no matter if the customer uses the same name and last name, as well as the phone number, Amelia creates a new customer.
If the customer already booked an appointment, in the roles settings, in the Customer Tab, there is an option called "Check customer's name for existing email when booking". If this is enabled, the "existing customers" won't be able to use different first and last names when booking.
Not sure if it fits your needs, but this is the closest option. Please feel free to search through our feature suggestion page, to see if someone may have already suggested this feature. If you can't see it, feel free to add your suggestion there, and as more people vote, the feature will move higher on the priority list.
You can certainly follow our changeLog page if you'd like, where we state any changes/new features/bug fixes during updates and our newsletter, so you're informed about new features, bug fixes, freebies, etc.
Let us know if you have any other questions.
Kind Regards,
Stefan Petrov
[email protected]
Rate my support
wpDataTables: FAQ | Facebook | Twitter | Instagram | Front-end and back-end demo | Docs
Amelia: FAQ | Facebook | Twitter | Instagram | Amelia demo sites | Docs | Discord Community
You can try wpDataTables add-ons before purchasing on these sandbox sites:
Powerful Filters | Gravity Forms Integration for wpDataTables | Formidable Forms Integration for wpDataTables | Master-Detail Tables
Thanks for the reply Stefan!
As I've said, people don't enter their emails so it would be pointless to enable that option.
What if I drop the email index from the database, and add one for the phone number? Would that switch the differentiating "parameter" from email to phone number?
@Uroš mentioned something about dropping the index in another of my tickets, and I thought it might be an solution for this "issue" as well.
Hello Emanuel,
I got that, but all other options like limits etc are based on the customer's email. Regarding the option of dropping the index, I doubt it will work, but you can test it out.
Let us know if it works.
Kind Regards,
Stefan Petrov
[email protected]
Rate my support
wpDataTables: FAQ | Facebook | Twitter | Instagram | Front-end and back-end demo | Docs
Amelia: FAQ | Facebook | Twitter | Instagram | Amelia demo sites | Docs | Discord Community
You can try wpDataTables add-ons before purchasing on these sandbox sites:
Powerful Filters | Gravity Forms Integration for wpDataTables | Formidable Forms Integration for wpDataTables | Master-Detail Tables