Hey there, Awesome Customers!
Just a heads up: We'll be taking a breather to celebrate International Workers' Day (May 1st and 2nd - Wednesday and Thursday) and Orthodox Easter from Good Friday (May 3rd) through Easter Monday (May 6th). So, from May 1st to May 6th, our team will be off enjoying some well-deserved downtime.
During this time, our customer support will be running on a smaller crew, but don't worry! We'll still be around to help with any urgent matters, though it might take us a bit longer than usual to get back to you.
We'll be back in action at full throttle on May 7th (Tuesday), ready to tackle your questions and requests with gusto!
In the meantime, you can explore our documentation for Amelia and wpDataTables. You'll find loads of helpful resources, including articles and handy video tutorials on YouTube (Amelia's YouTube Channel and wpDataTables' YouTube Channel). These gems might just have the answers you're looking for while we're kicking back.
Thanks a bunch for your understanding and support!
Catch you on the flip side!
Warm regards,
TMS
In Version 1.3.4 (Released 05.12.2018)
There is a new feature listed: Option to check customer’s name for existing email during the booking – now it is possible to allow customers to schedule the appointment with the same email but different first and last name
We don't use the froont end for customers to make their own booking, so we are entering all our bookings through the backend. When we try to use the same email address for two different customers we get the read warning telling us the email address already exists. Amelia won't allow this feature to work.
What are we doing wrong?
Hi, Paul,
Thank you for choosing Amelia.
Yes, Amelia has this limitation on the back-end, so it's possible to use the same email for multiple users only on the front-end.
You can suggest that as a feature request here, or check if this request was already submitted and vote for it.
Also, as a temporary solution, we would recommend you to book Appointments for your Customers on the front-end in incognito mode (thus, the booking form won't be pre-populated with your Admin/Employee data).
Best Regards.