We're Moving to a New Support Platform – Starting June 1st!
We’re excited to let you know that starting June 1st, we’ll be transitioning to a new support system that will be available directly on our product websites – Amelia, wpDataTables, and Report Builder. In fact, the new support platform is already live for Amelia and wpDataTables, and we encourage you to reach out to us there.
You'll always be able to reach us through a widget in the bottom right corner of each website, where you can ask questions, report issues, or simply get assistance.
While we still do not offer live support, a new advanced, AI-powered assistant, trained on our documentation, use cases, and real conversations with our team, is there to help with basic to intermediate questions in no time.
We're doing our best to make this transition smooth and hassle-free. After June 1st, this current support website will redirect you to the new "Contact Us" pages on our product sites.
Thanks for your continued support and trust – we’re excited to bring you an even better support experience!
Hi!
I'm using Amelia with WooCommerce, and I've noticed that we can now customize our forms and remove every fields, but the first name during the booking process.
I think it's a great improvement, because it makes it faster for the customer.
However, here's what I found. Let's imagine a customer comes back after a month. Their account has been created during their first purchase, and as they come back on the website, they are already logged in :
- They book another service with Amelia, but they make a typo in their name.
- They go through WooCommerce, where most fields are already populated, thanks to their previous purchase.
When the customer complete the purchase, there will be two Amelia accounts linked to one Wordpress account !
And I can't see how the customer can have access to their previous Amelia account, as the one that is being displayed with the shortcode in the new one.
I admit it, it's a niche situation... But you know what we say, "never trust the user".
I guess what I want to understand is how would you create the most unified experience between WooCommerce and Wordpress so that this kind of event doesn't happen?
Thanks.
Hello, Clément,
Thank you for reaching out to us.
You can enable "Check customer's name for existing email when booking" in Amelia Settings/Roles/Customer or create the e-mail field with mandatory to fill out. One email can only be linked with one customer (as it's in Amelia), so if you have an issue with how WooCommerce is saving these customers, you should reach out to WooCommerce.
If you need some further assistance, please don't hesitate to contact us.
Have a nice day!
Kind Regards,
Stanislav Snagovskiy
[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
You can try wpDataTables add-ons before purchase on these sandbox sites:
Powerful Filters | Gravity Forms Integration for wpDataTables | Formidable Forms Integration for wpDataTables | Master-Detail Tables
Hi!
Thanks for the input, I've implemented it.
However, I don't believe this solves everything, nor that the problem comes from WooCommerce.
Let me try to rephrase it:
Scenario 1: An existing customer use a different email address on Amelia and the same as previously provided during their WooCommerce checkout:
Scenario 2: An existing customer use the same email address on Amelia and another one during their WooCommerce checkout:
WooCommerce does what it's made for and can hardly do better:
- If the customer is logged in, the new purchase is added to the same Wordpress account.
- If the customer is a visitor, a new account is created during the checkout.
On the other hand, I believe you should change your plugin so that it takes into account the email address the customer provides during WooCommerce checkout process, and not the one provided on Amelia.
You could actually do the same with the first name, hence removing the need for the customer to fill anything until the final checkout.
I understand this is not the way your plugin is made, and that it requires time to implement such a thing, but as long as this is not done, some of your customers will complain about the two scenarios I've just mentioned.
I just want to finish by saying that, from my perspective, your plugin is very close from perfection and that this is the only loophole I can still find.
I wish you a good week,
Clément.
Hello Clément,
Thank you for your suggestion. We carefully follow customers requirements and try to implement most of them if they appear in requests from time to time, so we will add to our idea list and look into some possible solutions on plugin side in the future.
If you have any further questions or issues, please feel free to open a new ticket, and we'll gladly help.
Have a nice day!
Kind Regards,
Stanislav Snagovskiy
[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
You can try wpDataTables add-ons before purchase on these sandbox sites:
Powerful Filters | Gravity Forms Integration for wpDataTables | Formidable Forms Integration for wpDataTables | Master-Detail Tables